kAudioUnitProperty_ContextName
kAudioUnitProperty_ContextName
- Subject: kAudioUnitProperty_ContextName
- From: Marc Poirier <email@hidden>
- Date: Tue, 20 Jul 2004 15:04:56 -0400
I sent this a couple of weeks ago, but got no reply, so I'll try again:
The kAudioUnitProperty_ContextName seems like a nice idea and useful,
though unfortunately also seems to be a neglected corner of the AU API.
There's no support for handling it in AUBase, the docs are very scant,
and I tried 15 or so hosts to see if they supported it and (not
surprisingly) none did (update: Live 4 now does as of Saturday). I do
have a few specific questions about it, though:
1) Should the text (the property's value) include the AU's name plus
extra context info, or only the extra context info? In other words,
let's say for example I had the plugin "Robocop FX" inserted on track
3. Would a possible ContextName be something like "Robocop FX: track
3" or just "track 3"?
2) ContextName is not covered in CF_AU_Properties.text nor are its
CoreFoundation semantics covered in the regular docs for the AU API:
/Developer/Documentation/CoreAudio/AudioUnits/Topics/
au_properties.html#kAudioUnitProperty_ContextName
I am guessing that it is the norm (the AU creates or retains the value
for the client on GetProperty, and retains the new value on
SetProperty), but it seems to me like this should be explicitly stated
somewhere.
3) If the property's value has not yet been Set but someone tries to
Get it, is the correct behavior for the AU to supply a null CFStringRef
and return noErr, or to return an error? And if an error, which one?
I have tried implementing this in my Turntablist AU (for identifying
the plugin in its file chooser dialog and file-not-found alert), but I
don't know if I got these details right...
thanks,
Marc
_______________________________________________
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.