Re: Chunk?
Re: Chunk?
- Subject: Re: Chunk?
- From: Marc Poirier <email@hidden>
- Date: Fri, 23 Sep 2005 10:15:11 -0400
On Sep 23, 2005, at 9:29 AM, john smith wrote:
Thanks for the answer.
And then for your added data, you don't need to do some opaque
data dump either
An opaque data dump is excactly what I need, no more and no less.
Is this possible?
You can add CFData to the dictionary.
, you can add as many data-type- defined separate items in there
as you want. Taking care to stick to the key namespace
convention of prefixing them with your AU manufacturer 4-char
ID. This is all covered in the docs, for more detail.
What docs would that be? I'm having trouble finding it.
/Developer/Examples/CoreAudio/Documentation/AudioUnits/Topics/
au_properties.html#kAudioUnitProperty_ClassInfo
If no: How do I define whether a parameter is automateable / non-
automateable? (by automateable I also mean whether it can be
controlled by an external controller)
Also (if no), how do I make a parameter which is not a float?
I don't understand either of these "if no" scenarios since they
have nothing to do with saving and restoring state.
Well, my reasoning is that if there's no such thing as a chunk,
then I would need to add it as non-automateable parameters. Sort of
a hack though.
I still don't get it...
Marc
_______________________________________________
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
References: | |
| >Re: Chunk? (From: "john smith" <email@hidden>) |