Re: The Plugin Settings Approach.
Re: The Plugin Settings Approach.
- Subject: Re: The Plugin Settings Approach.
- From: Glenn Olander <email@hidden>
- Date: Wed, 12 Feb 2003 08:31:35 -0800
Exactly. That would be excellent. Is there any movement to make such a
thing happen with Audio Units?
- Glenn
B.J. Buchalter wrote:
What _is_ missing, from VST (and perhaps AU) is a good solution to
the second problem. Ideally you should be able to easily add a patch
to the library and efficiently browse it from any host,
preferably with one-mouse click loading a single patch for auditioning.
-Glenn
Now, this is actually the approach that Pro Tools has implemented for years.
The *current* state of the plug in the session is stored as a chunk in the
session. All named settings are stored as files in a globally accessible
location (or a local location if the user so chooses). There is no
import/export required, and the state files may be managed in the Finder.
Obviously in the PT case, PT defines the global location. In the AU case,
the global location should be defined by Apple and every compliant host (or
plug-in) should support it.
Note that there is a fundamental difference between current state and named
settings. Pro Tools gets this right. VST does not. IMHO, individual settings
should be represented by one preset file (XML is file). "Banks" should be
represented by directories containing preset files. If we want to bundle the
directory so that it looks like a file to a casual user, that would be fine.
Multiple "banks" should be available to the user at any given time in all
hosts -- organized and browse-able hierarchically.
_______________________________________________
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.