Re: AU standard incomplete?
Re: AU standard incomplete?
- Subject: Re: AU standard incomplete?
- From: Marc Poirier <email@hidden>
- Date: Mon, 10 Feb 2003 18:35:33 +0100 (CET)
>
I'm just a newcomer to AU, but one thing I noticed right off is the
>
standard seems to be lacking a description of a settings file. VST
>
includes a description of fxp and fxb storage formats and the result is
>
that one can use settings saved in one host in another host. With AU's,
>
settings saved in Metro can't be opened in Logic. I'm assuming that's
>
due to a deficiency in the standard as opposed to a deficiency in the
>
host implementations. Is that right?
Yeah, like Urs said, it's Logic's current failure to follow the AU
settings format rules, which is something due to be fixed. But, heh heh,
I find the idea that VST has a "standard" way of doing settings pretty
funny... In my opinion, VST handles settings so incredibly poorly. There
are basically 4 "standards" which is ridiculous. There is chunk-preset,
chunk-bank, nonchunk-preset, and nonchunk-bank. There's no protocol
for handling the nonchunk settings if the parameter scheme changes (there
is in AU, though). There's no protocol for upgrading from nonchunk to
chunk. Ahhh... I could go on, but I basically I just really think that
VST does all of this horribly.
>
In addition, hosts are encouraged to open .fxp files in a way that if
>
a) PlugIn name matches, b) ComponentSubType == VST PlugIn ID, they pass
>
over a proper plist with the fxp's chunck data inside a data key named
>
"vstdata" to the plugin.
>
>
I'm not certain if and how .fxb files are to be treated. Maybe call it
>
"vstbank"? Bill? Anyone?
I was thinking that the plugin would hopefully store something in their
"chunk" data that indicates how many settings are in there. AU currently
doesn't do a user-state bank thing internally, it's a host task rather
than a plugin task. And that is in direct conflict with the VST way of
doing this stuff, where "presets" and user state are all cloudy and
jumbled together with stored settings, etc. What I'm personally doing now
is adding to my VST chunk data which VST "preset"/"program" is the
currently active one when settings were stored, so that if imported a
"bank" to AU, that will be the setting that will be extracted.
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.