Custom AU Data (unseen by user, stored by host)
Custom AU Data (unseen by user, stored by host)
- Subject: Custom AU Data (unseen by user, stored by host)
- From: Izhaki <email@hidden>
- Date: Tue, 07 Nov 2006 16:50:39 +0000
Hi all,
I might be overlooking something, but even after going through the SDK
and various internet resources I couldn't quite understand what is the
right way to go about the following issue:
There are more than a few instances where the host application should
store and restore a plug-in data (ie, parameters/properties) which is
not visible for the user. Sometimes this data cannot be expressed using
a determined amount of Float32. A few examples would be a sample name on
a sampler, a control that only defines the behavior of other controls in
the UI (say button latch), or some linked list which hasn't got a
determined size (say, a dynamic version of a multitap delay implementation).
So what is the right way to implement such a behavior in an AU plug-in?
My current guess would be kAudioUnitMigrateProperty_FromPlugin, but
there is very little documentation on it, which leaves me unsure.
Thanks for your help,
Izhaki
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden