Re: Filing of User Presets
Re: Filing of User Presets
- Subject: Re: Filing of User Presets
- From: Robert Grant <email@hidden>
- Date: Wed, 23 Oct 2002 13:14:09 -0400
Well I guess we've got a couple of good starting points for storing
presets:
~/Library/Audio/
and
/Library/Audio/
I would vote for a subfolder called: Presets and then a subfolder
called AU or something
in order to differentiate AU presets from VST presets etc. (I was
thinking about putting
it under Plug-Ins but then it wouldn't mirror the hierarchy properly).
The question then becomes - what goes in the Presets folder. If it's
just a bunch of
.plist files then the user will have to provide an organization scheme
under Presets
or else give each file a *really* descriptive name. Fortunately given
the info in the
class data we can check to make sure a preset goes with an AU before
inflicting it
on the AU :-) I'm not sure how excited I am about building a preset menu
from a directory full of .plist files. It would mean loading all the
.plist files grokking their
class info and adding the right ones. If the user puts them in
subfolders then it would
make it even more unpleasant. This is why I was leaning to a preset
library file. Of course
Music Devices can have a *ton* of presets so even still some kind of
arbitrary subgrouping would be needed.
As far as storing a chain of effects I think I remember Bill saying
that saving the state
of a graph (and thus being able to restore it) is in the plan but no
date yet. Of course
it would be the entire graph, not a fragment (such as the master effect
chain - we really
need those embeddable subgraphs :-) Would be a nice way to handle send
effects too
- if we had a mixer ;-)
Robert.
On Wednesday, October 23, 2002, at 12:20 PM, James Chandler Jr. wrote:
Hi Robert
A standard file format would be great.
Also a standardized place to put presets, so that all hosts would find
them
without a lot of user searching.
Most DirectX filter presets on PC are a pretty standardized registry
storage
format, but different major hosts store the presets in different
places in
the registry. When writing a DirectX supporting host, if one wanted to
find
all possible user presets, one would have to search several places,
which is
unnecessary extra programming work IMO. Would be nice to avoid such
incompatibilities in a brand new AU format.
Another thing which would be nice to standardize, if not already done,
is a
standard format to save an entire series chain of plugins, including
all the
settings for each plugin in the chain.
The little DX Host I write on the PC, has a "plugin group" feature
that I
find very convenient for common settings. It is convenient to set up
and
save ferinstance a master output insert chain including EQ->MultiBand
Dynamics->PeakLimiter, with typical settings already adjusted.
Whenever that
group is needed in a new song, just load the entire thing in one
action,
rather than laboriously inserting each plugin and loading the proper
plugin
preset. This is such a timesaver (IMO), it would be nice if all hosts
could
load/save the same format for plugin chains (and preferably all hosts
would
use a standardized location on the user's hard drive).
James Chandler Jr.
_______________________________________________
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.
_______________________________________________
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.