Re: Chunk?
Re: Chunk?
- Subject: Re: Chunk?
- From: Marc Poirier <email@hidden>
- Date: Fri, 23 Sep 2005 09:07:56 -0400
On Sep 23, 2005, at 8:45 AM, john smith wrote:
Hi,
Does AU have something like chunks (in the VST sense)?
No, AU is better. AU uses CFDictionaries for state storage, which
includes by default all of the basic stuff you'd need (parameter
storage, plugin ID, etc.). And this is all handled without you even
needed to think about it in AUBase::SaveState() and
AUBase::RestoreState(). And then, if you need to extend that with
any further data, you can add in your own keys/data to the dictionary
(after calling those from your overridden implementations to take
care of the basics). And then for your added data, you don't need to
do some opaque data dump either, 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.
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.
All parameters are considered automatable.
You can use the AU parameter unit kAudioUnitParameterUnit_Indexed
(although technically representation will still be float, but
interpreted like integer) or kAudioUnitParameterUnit_Boolean (ditto).
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: | |
| | >Chunk? (From: "john smith" <email@hidden>) |