AU Hosting and Persistence Questions
AU Hosting and Persistence Questions
- Subject: AU Hosting and Persistence Questions
- From: Carsten Gehle <email@hidden>
- Date: Mon, 21 Oct 2002 13:44:08 +0200
Hi!
What is the proper way to manage persistence of AU states? I found
kAudioUnitProperty_ClassInfo, the index of the current factory preset
and the AUs parameters, but I don't think that I have completely
understood the dependencies:
The simple way is to store the parameter values. As this does not
include the factory preset number and does not allow the AU to store
any arbitrary data, I do this:
First, I check if a CurrentPreset is selected.
If so, I store the index of the factory preset. Should I also store
each parameter value in this case?
If CurrentPreset is -1, I ask for the ClassInfo and store that. Though
it does not seem to be intended to store parameter values in this case,
it seems to be needed for some of the current AUs.
What is the recommended way to store a ClassInfo into a data block? Are
the keys fixed or may an AU define additional keys? If the entries are
limited to name, version, type, subtype, manufacturer and data, I can
store each value and the AUs state is stored in the 'data' CFDataRef.
But as ClassInfo is a property list and not a structure, I assume that
an AU may define more keys. Should I then use
CFPropertyListCreateXMLData()?
If I restore an AUs state and have stored ClassInfo and parameters
values, in which order should SetParameter and set ClassInfo be called?
Thanks,
Carsten
_______________________________________________
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.