Re: The Plugin Settings Approach.
Re: The Plugin Settings Approach.
- Subject: Re: The Plugin Settings Approach.
- From: "B.J. Buchalter" <email@hidden>
- Date: Wed, 12 Feb 2003 09:20:12 -0500
>
1. I set up a Reverb plugin just the way I like it.
>
2. I can use that same Reverb plugin setting in *any* host app I choose.
>
3. I can go to ~/Documents/PluginSettings and see all my plugin data
>
saved as .XML files, which I can then easily back up.
>
4. Plugins know which settings file to load for each host apps
>
project, using the hash (or filename, simply) passed to them at
>
load-time. Likewise, this same hash is used at save-time to
>
associate session settings with plugin settings.
OK, but this does have a number of practical problems as well:
1) If the user copies the session file to another computer without copying
the plug-in settings files, they cannot open the session properly (e.g. The
session is not self contained).
2) If the hash changes for some reason the link breaks -- any number of
unexpected events could cause this to happen.
3) If you change the contents of the preset later, it will in-advertently
change one or more sessions (silently). This is a huge problem. If this is
avoided by having unique setting files for each session, the management of
the settings becomes the users problems.
>
> 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.
Best regards,
B.J. Buchalter
Metric Halo
M/S 601 - Building 8
Castle Point Campus
Castle Point, NY 12511-0601 USA
tel +1 845 831-8600
fax +1 603 250-2451
If you haven't heard ChannelStrip yet, you don't know what you're missing!
Check out SpectraFoo, ChannelStrip and Mobile I/O at
http://www.mhlabs.com/
Download a 12 day demo from <
http://www.mhlabs.com/demo/>
_______________________________________________
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.