Re: AU2 - questions about presets and ClassInfo
Re: AU2 - questions about presets and ClassInfo
- Subject: Re: AU2 - questions about presets and ClassInfo
- From: Marc Poirier <email@hidden>
- Date: Wed, 2 Oct 2002 22:29:47 +0200 (CEST)
Thanks for all of the helpful info, Bill, I have a much better
understanding of the AU approach to presets now. It's a lot different
from what I'm used to (VST), although I think much better. Just a couple
more questions lingering now:
Am I correct that the preset number for user presets is not really of any
concern to the AU? It is more just a piece of info for the host and its
own settings storage management?
Since factory presets are read-only, then does that mean that the name
can't be modified by the user? Because in AUBase::DispatchSetProperty, it
is possible to change the name of a factory preset (not in the AU
executable of course, but at least for that instance). Is this a bug or
correct behaviour?
I would also think that, in the case of choosing a factory preset as the
CurrentPreset, it also shouldn't matter if a name is supplied. But in
DispatchSetProperty, a name is required:
case kAudioUnitProperty_CurrentPreset:
<snip>
if (newPreset.presetName) {
if (newPreset.presetNumber < 0 || NewFactoryPresetSet(newPreset) == noErr) {
<snip>
} else
result = kAudioUnitErr_InvalidPropertyValue;
} else
result = kAudioUnitErr_InvalidPropertyValue;
Shouldn't that be something more like:
if ( newPreset.presetName && (newPreset.presetNumber < 0) )
// ...store the new name and set the preset number...
else if ( (newPreset.presetNumber >= 0) && (NewFactoryPresetSet(newPreset)
== noErr) )
// ...only set the preset number...
else
result = kAudioUnitErr_InvalidPropertyValue;
Maybe I'm wrong about this, though...
Thanks again,
Marc
_______________________________________________
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.