Re: How are AU User Presets handled?
Re: How are AU User Presets handled?
- Subject: Re: How are AU User Presets handled?
- From: Glenn Olander <email@hidden>
- Date: Wed, 12 Feb 2003 15:24:57 -0800
Bill Stewart wrote:
The host should then build the user preset menu based on the names of
directories that are contained within the plugin preset dir. (This
could actually be a recursive n-level deep series of pop up
menus/directories for the categorization freaks:)
That's the right idea, but a hierarchical menu really isn't
the right GUI mechanism. If you're browsing through your Pads/Industrial
subdirectory, you want a single click to take you to the next patch
so you can audition a large number of patches quickly.
See Chainer or Crystal for examples. Or, is the actual presentation
style up to the host?
As for the session activities - I think that is out of the scope of the
AU and is a host issue.
Absolutely.
But one question does remain
Logic currently builds the preset menus for you - so this is really an
issue of how the host will present user presets to the user. We are not
expecting the AU's view to build these menus - or are we? That is the
only point of confusion I have about this discussion as our previous
discussions were discussions about how the host apps would handle
these, NOT the AUs.
This seems like a task common to every AU, so it sounds like it might be
best done by the host. The only reason some plugs handle it in VST is
because some hosts handle it so poorly.
One additional thought. in VST, importing a patch is a destructive
operation: The current patch is overwritten. For that reason,
Crystal has an undo for this operation. I presume it would also
be destructive with an AU? If so, would an undo be a good idea?
- Glenn
_______________________________________________
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.