Re: How are AU User Presets handled?
Re: How are AU User Presets handled?
- Subject: Re: How are AU User Presets handled?
- From: Urs Heckmann <email@hidden>
- Date: Thu, 13 Feb 2003 09:52:33 +0100
There's a certain case when Preset handling gets a bit more tricky.
That is, when a MusicDevice's state (or an Effect's as well) consists
of more than one preset. This can be a common thing with multitimbral
synths (like the TC and Waldorf VSTis) or devices that allow for
filling more than one preset slot for "morphing". - I guess in these
cases it might be better to have the actual preset browser inside the
effect whereas the "official" preset mechanism would handle the whole
multipatch (all settings for all slots) at once. It would be a similar
issue that occurs in sample playback devices where multisamples are
"subpresets" inside preset settings. I think it should be up to the
plugins to handle those cases, as I think this is also the case on
other platforms.
Suggestion:
However, an idea that came up recently (on GMPI discussion) was
offering a mechanism to provide "grouping" of parameters or
subsettings. In AU world this could be done easily on the state-side by
having multiple keys/fields inside the state/xml data. This way - with
some add-on metadata / properties in the specs - a user could for
example chose to only load filter settings from one preset and
envelope/modulation settings from another. In above case (multitimbral
presets), grouping would allow for retrieving single patches out of
multipatch data. The mechanism could be provided either by the host or
the plugin. A standard would be nice.
;) Urs
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.