Re: auval problem
Re: auval problem
- Subject: Re: auval problem
- From: tahome izwah <email@hidden>
- Date: Mon, 15 Jun 2009 13:22:41 +0200
Never mind, I found the info. Here it is for reference in case anybody
else has this problem:
In AudioUnitProperties.h, line #614:
/*!
@abstract Keys contains in an audio unit preset (ClassInfo) dictionary
@discussion These strings are used as keys in the
AUPreset-"classInfo" dictionary
The actual keys are CFStrings to use these keys you define the key as:
static const CFStringRef kMyVersionString = CFSTR(kAUPresetVersionKey);
*/
#define kAUPresetVersionKey "version"
#define kAUPresetTypeKey "type"
#define kAUPresetSubtypeKey "subtype"
#define kAUPresetManufacturerKey "manufacturer"
#define kAUPresetDataKey "data"
#define kAUPresetNameKey "name"
#define kAUPresetRenderQualityKey "render-quality"
#define kAUPresetCPULoadKey "cpu-load"
#define kAUPresetElementNameKey "element-name"
#define kAUPresetExternalFileRefs "file-references"
It seems you need at least kAUPresetVersionKey, kAUPresetTypeKey,
kAUPresetSubtypeKey and kAUPresetManufacturerKey in order for the AU
to pass auval.
Thanks again
--th
2009/6/15 tahome izwah <email@hidden>:
> Thank you!
>
> Is there a list of keys and values that are mandatory for a plug in to
> work? I cannot call the base classes' SaveState to create the plist
> info for me (I have a good reason for this) and need to construct the
> plist from scratch.
>
> Thanks!
> --th
>
>
> 2009/6/12 William Stewart <email@hidden>:
>> CFShow(theClassData)
>>
>> if you look in AUBase::SaveState you'll see that there are a collection of
>> keys added there to identify which AU the class data comes from - seems like
>> you are misssing a key
>>
>> Bill
>>
>> On Jun 11, 2009, at 8:24 PM, tahome izwah wrote:
>>
>
_______________________________________________
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