Re: The Plugin Settings Approach.
Re: The Plugin Settings Approach.
- Subject: Re: The Plugin Settings Approach.
- From: Glenn Olander <email@hidden>
- Date: Tue, 11 Feb 2003 18:50:59 -0800
I'd have to agree with Marc. This sounds like a design an engineer
would be happy with, but not a musician. Imagine trying to gather
up all the files you used in a project for backup or to carry
to another studio.
I believe there are two fundamentally different ways that patches
are archived:
1) as a faithful record of the settings used in a particular project
2) as a library from which patches may be retrieved for use in future
projects.
Solving #1 with a chunk (sorry for the VST terminology) in the song
file is a fine solution.
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
This way:
a) Plugins are treated as 'mini applications' with their own context,
stashed in the users ~/Documents/PluginSettings dir, and these
settings are usable across *any* of the applications which will play
host to the plugin.
-The plugin datastore should be *separate* from the app datastore,
yet use a properly computed and well-documented hashing function to
be able to do its own load of settings on a per-session basis,
per-app, as well as saves.
b) The user can load plugin settings across-projects.
-If I set up a nice plugin Reverb in a LAW song one day, I *should*
be able to load that same plugin Reverb in a Pro Tools session file
later as well, simply by picking "LAW Songs - Happy Days - Reverb
Plugin Setting" from the Reverb Plugins 'preset' list (I *hate* the
use of the term 'preset' for a software plugin...) when I load the
plugin in ProTools.
_______________________________________________
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.