Re: Filing of User Presets
Re: Filing of User Presets
- Subject: Re: Filing of User Presets
- From: Robert Grant <email@hidden>
- Date: Thu, 24 Oct 2002 07:41:52 -0400
On Thursday, October 24, 2002, at 12:34 PM, Nikolaus Gerteis wrote:
Currently a Logic specific header is written to the file as well, but
we think about removing this and replacing it with a { CFSTR("logic"),
CFData } pair in the property list, so the presets can be loaded by
other hosts as well.
Are you saying that Logic adds some of its own data to a preset (inside
the class info for
a preset?) I guess if the AU developers don't mind then I don't either.
But what happens
if Logic loads up a preset without this extra info? I imagine you apply
some sensible
defaults?
We want to encourage the idea of storing such presets in a standard
location. In my personal opinion the solution
Library/Audio/Plug-Ins/Presets/Audio Units/Manufacturer/Plugin name
would be a good solution. Plus that the user can create subfolders in
there, to organize the presets.
I am somewhat concerned about the need to support this but it seems
limited to synth AUs rather than effects. However there is nothing
stopping us putting presets inside
preset group entries in the Preferences dictionary: E.g.
Root - Dictionary
|- PresetGroups - Dictionary
| |- PresetGroupName - Array
| | |- PresetName - String
| | |- PresetName - String
| | .
| | .
|
|- Presets - Dictionary
| |- PresetName - Class info dictionary
| |- PresetName - Class info dictionary
|
|- UserDefault - String
This would allow us to write a browser interface that lets users select
from either a group
or the entire list of presets.
On the compatibility issue: If a plugin exists as an Audio Unit and a
VST version, Logic provides the possibility to load the VST settings
into the Audio Unit, if the following conditions are met:
1. The Audio Unit sub ID is equal to the unique ID of the VST plugin
(four letter code).
2. The name of the Audio Unit is the same as the one of the VST plugin.
3. The Audio Unit can handle property lists that contain a pair {
CFSTR("data"), CFData } where the CFData member is a representation of
the data the VST plugin returns/gets in the getChunk/setChunk calls.
This sounds good, but I would think that you might want to tag the data
a little more
clearly? Something like: "vstdata"? There's already a "data" entry in
the class info for
the AU preset info.
Thanks,
Robert.
_______________________________________________
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.