Re: Filing of User Presets
Re: Filing of User Presets
- Subject: Re: Filing of User Presets
- From: Marc Poirier <email@hidden>
- Date: Fri, 25 Oct 2002 15:41:46 +0200 (CEST)
>
> 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.
>
>
There is already a data member. It contains the preset data of the
>
plugin. Nothing else for the data I get from the ClassInfo property. It
>
exactly the same, isn't it? If you have a Audio Unit ported VST plugin
>
and put your data into the vstdata key, what remains for the data key
>
to contain? Or do you say you use it instead of the data key, to
>
identify the data as a VST chunk. Then I would prefer to write the
>
chunk data to the data key and add a thrid key like 'vst' or
>
'vstsetting' to identify the setting as a VST compatible one. Then a
>
host, that does not care about the VST-Audio Unit compatibility issue
>
can handle all presets in the same way.
But I think that Bill was saying that they are expecting uniformity in the
base keys (data, subtype, type, manufacturer, name, etc.), and for "data"
that means a dump of every parameter value from every element. Something
other than that in "data" would be non-standard, and that non-standard
data should go in custom keys, and VST chunk data should go in a new
standard "vstdata" key. (This is my understanding of th discussion,
please correct me if I've misrepresented any information.) By doing
things this way, base implementations of RestoreState/SaveState don't go
haywire from the VST chunk data, the vstdata can be unobtrusive and
totally ignored if not supported by the AU, and the "growing body of code
that relies on these keys" that Bill referred to won't go haywire, either.
In my opinion, if an app is trying to load an AU counterpart to a VST
plugin and restore its settings, then the app should create a "data" key
with no data, so that in the worst case, the state is left unaffected, and
in the best case, the "vstdata" is successfully loaded. What do you
think?
Marc
_______________________________________________
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.