Re: Presets etc.
Re: Presets etc.
- Subject: Re: Presets etc.
- From: Urs Heckmann <email@hidden>
- Date: Wed, 8 Jun 2005 11:33:21 +0200
Hiya,
I think so, yes.
But a year later, I'm a bit uncertain about the scope. Can an instance
of an AU have its own Factory Presets or are the Factory Presets global
for all instances? If latter, how are we supposed to notify our other
instances? Or is the host responsible to notify all instances of the
plugin about the change? Do the other instances need to know at all?
I think someone of the CA team or Marc should comment here.
Cheers,
;) Urs
Am 08.06.2005 um 09:33 schrieb Jeremy Sagan:
Hello!
Is this the best way to listen for changes in the factory presets:
err = AudioUnitAddPropertyListener(au,
kAudioUnitProperty_FactoryPresets, myfactoryPresetChangedProc,
this);
static void myfactoryPresetChangedProc(void *plug, AudioUnit ci,
AudioUnitPropertyID inID,
AudioUnitScope inScope, AudioUnitElement inElement)
{
switch (inID)
{
case kAudioUnitProperty_FactoryPresets:
RefreshFactoryPresets(VPlug);
break;
}
}
Thanks,
Jeremy
On Apr 28, 2004, at 10:32 AM, Urs Heckmann wrote:
Hiya,
Specs wise, you can propagate a new list of Factory Preset by firing
a notification that kAudioUnitProperty_FactoryPresets has changed 8-)
Then, a well behaved host shouldn't hesitate to query this property
once again and update its preset menu.
But I guess, this is not the case currently...
However, unlike VST lingo, IIRC this would account for all instances
of that AU plugin.
Cheers,
;) Urs
Am 28.04.2004 um 15:48 schrieb Pavol Markovic:
Dear list,
I've read many opinions that VST mimics limited abilities of hw
machines. But isn't the AU fixed factory preset list something
restricted, too? Where is the software flexibility - it's main
advantage over hw. It's true that you can have fixed preset list for
simple reverb and work with it without problems, but for synths you
need patches sorted into categories - and to let users manage them,
to add new preset banks - this is what makes them usable. Yes Urs'
way is fine, but this works only for AU only plugins, unless you'll
write your own AU preset handler on other (sw and hw) platforms. But
this way it is AU format which dictates how the things have to be
organized.
PM
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
urs heckmann
email@hidden
www.u-he.com
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden