Re: AU standard incomplete?
Re: AU standard incomplete?
- Subject: Re: AU standard incomplete?
- From: Bill Stewart <email@hidden>
- Date: Wed, 12 Feb 2003 12:08:31 -0800
I think the way the AU handles this is complete:
A user can have as many preset files as they want
The preset format is required to have a certain number of fields - but
an AU can completely customise their preset values past that (and after
all it is only necessary for the particular AU to understand this)
The AU provides a different mechanism for providing factory presets -
they ship in the AU and we have implemented these in our AUs as static
const data in the AU code itself (a factory preset is NOT the XML state
of the au) - that's also how the SampleEffectUnit does this in the SDK.
For VST compatibility we have added a "vstdata" key. We do not plan on
specialising this key any further. If VST provides alternate data
structures, etc, then these should be contained within the data of the
AUPreset that is tagged by this 'vstdata' key.. An AU can generate
these values, but I think the prime use we see for this is that the
host creates an aupreset plist from the VST data and then gives this to
the AU... (A kind of bring my vst presets into my AU please operation
that in many cases will only need to be done once)
OK?
Bill
On Tuesday, February 11, 2003, at 09:47 AM, Marc Poirier wrote:
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 ?
I think that the use of XML settings format, CFStrings, etc. makes it
so
that the possibilities are all very open, for hosts to be very flexible
about this stuff. I think that the current reality is that no hosts
are
giving us many settings capabilities yet, but I think that everything
we
need for everything we want to do is there in the AU API, it's just a
matter of hosts making it happen. With XML, there is no 128 data set
limit.
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 ?
"Autoload" presets are what you would call the "factory presets" in AU.
Unless I am misunderstanding you...
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.
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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.