Re: kAudioUnitProperty_ContextName
Re: kAudioUnitProperty_ContextName
- Subject: Re: kAudioUnitProperty_ContextName
- From: William Stewart <email@hidden>
- Date: Tue, 27 Jul 2004 16:03:47 -0700
Good point...
OK - the "Entire AU Name" should be set in this member.
Thus, "Turntablist: Track 3" would be set.
Bill
On 27/07/2004, at 3:19 PM, Marc Poirier wrote:
>
On Jul 27, 2004, at 12:25 PM, William Stewart wrote:
>
>
> We also looked at this recently and realised that AUBase doesn't
>
> support this (and that it isn't documented either). So, we'll add
>
> support to this in AUBase before we revise the SDK.
>
>
Excellent. :)
>
>
>
> On 27/07/2004, at 4:27 AM, Stefan Gretscher wrote:
>
>
>
>> Am 20.07.2004 um 21:04 schrieb Marc Poirier:
>
>>> The kAudioUnitProperty_ContextName seems like a nice idea and
>
>>> useful, though unfortunately also seems to be a neglected corner of
>
>>> the AU API.
>
>> I'll try to add support for this to Logic soon, but we'll need to
>
>> answer your questions first. :-)
>
>>
>
>> Here's how I'd suggest kAudioUnitProperty_ContextName should be
>
>> handled:
>
>>
>
>>> 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"?
>
>> In my opinion it only should contains "track 3", because each AU
>
>> knows its name and can add it or not as applicable. Adding strings
>
>> is easier then removing the name to get the pure context string.
>
>
>
> The AU shouldn't care what is in the String and furthermore the AU
>
> shouldn't modify the string in any way. So either approach would be
>
> appropriate but I would think the common usage would be to just set
>
> the "track 3" string, rather than the full name (however, if you have
>
> localised names, it might also be common usage to store the entire
>
> string) - either way it shouldn't matter for the AU.
>
>
Hmmm, I think that the AU should care. My AU does care. ;) Because
>
the way that I use it in Turntablist is for file chooser dialogs and
>
error alerts. Ableton Live does now support this, with plugin name
>
included, and so the result you get, for example, with an error looks
>
like this:
>
>
Turntablist / track 3: Could not open file.
>
>
If my AU were to "not care" and assume that the name is not included,
>
then I would have to prepend it and then I might get:
>
>
Turntablist: track 3: Could not open file.
>
or
>
Turntablist: Turntablist / track 3: Could not open file.
>
>
depending on the host. I do care about which happens.
>
>
Personally, I am in support of specifying that the AU name should be
>
included, as Live does. Because that makes sense to me as the entire
>
"context name." But most important to me is that it be specified, one
>
way or the other, and not left open assuming that AUs should not care
>
either way.
>
>
>
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.
>
>
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
Culture Ship Names:
Ravished By The Sheer Implausibility Of That Last Statement [GSV]
I said, I've Got A Big Stick [OU]
Inappropiate Response [OU]
Far Over The Borders Of Insanity And Still Accelerating [Eccentric]
________________________________________________________________________
__
_______________________________________________
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.