Re: AU standard incomplete?
Re: AU standard incomplete?
- Subject: Re: AU standard incomplete?
- From: Roman Thilenius <email@hidden>
- Date: Tue, 11 Feb 2003 09:32:01 +0100 (MET)
>
> 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.
i just saw it at osxaudio and was about to answer to urs and
markus .. jesus, its already here in my email. -
well once back in the days nobody needed chunks for the
delays and reverbs we had.
that all came later with NI or with these samplers of the steinberg
LM style scripts presets.
oh and of course with dfx plug-ins.
that many host programs such as steinberg and bias couldnt
save unlimted amount of chunks for a while wasnt nice.
that a few programs like the MAX enviroment couldnt read and
write the chunk presets and banks at all was worse.
in practice people do not need to export or import presets or banks
so often, at least not for effect plug-ins.
now the question;
what will there be so different (from .fxp) for the avarage user with
.aupreset ?
is unlimited number of presets standart which every developer has to use ?
the 128 preset limit in VST is a mess.
what about clipboarding ? what about names and namelength ?
there are a few vst plugins out there which do not have "biult-in"
presets or only one. the developers avoided the mess with the chunk formats
and with the mac/pc or MAS/RTAS/VST compatibilty by creating their
own import export dialogs and formats. (linplug, waves, NI, ohm..)
what i would like to see in VST 3.0 and/or audiounits
is that you can make your _own autoload presets for every plugin.
only that makes sense to me.
is that planned for AU ?
if you need an example how preset handling should look like have a
look at the waveshell !
<flame>right now all i see is that logic 6 can not even save .aupreset
properly</flame>
/roman
http://vst-mac.info
--
+++ GMX - Mail, Messaging & more
http://www.gmx.net +++
NEU: Mit GMX ins Internet. Rund um die Uhr f|r 1 ct/ Min. surfen!
_______________________________________________
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.