Re: kAudioUnitProperty_ContextName
Re: kAudioUnitProperty_ContextName
- Subject: Re: kAudioUnitProperty_ContextName
- From: Stefan Gretscher <email@hidden>
- Date: Thu, 29 Jul 2004 01:33:08 +0200
On 27/07/2004, at 3:19 PM, Marc Poirier wrote:
Hmmm, I think that the AU should care.
Fully agreed.
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.
Sorry to repeat myself, but I strongly vote for NOT including the name
of
the AU. Here's why again (hopefully clearer this time):
Some AUs might need plug-in name and context as separate strings.
As an example, image your GUI has some fancy logo picture with your
plug-in name, and you want to display the track info as a smaller string
below that name, so that if the user has several windows of your AU
open he'll know which is which.
Another example that just comes into my mind is multi-channel AUs.
The context would have to depend on scope and element, so that e.g.
a multi-out synth would be able to name its outputs after the contexts
they are routed to. There you certainly don't want the plug-in name to
be part of the routing options.
Now, if the string is "MyAU: track 2, slot 3", then you'll have to
remove
"MyAU: " first before printing the string to the GUI.
While this seems easy at first, there's a lot of potential problems,
e.g.:
- what characters are put between the AU name and the track name?
- what comes first: plug-in name or track name?
- how to deal with potential localization of the name and/or the
context?
- what happens e.g. if the user has named the track after the plug-in
sitting there (e.g. "Delay: Delay Bus")?
There's just so many small issues that would need to be well defined
for everything to work properly that IMHO it would be much clearer for
both hosts and AUs to always leave the plug-in name out of the context.
In dialogs etc. the AU can handle how to merge the name into the
context name just as it needs. Easy to implement, and easy to define
in the standard.
Am 28.07.2004 um 01:03 schrieb William Stewart:
Good point...
OK - the "Entire AU Name" should be set in this member.
Please reconsider this.
Kind regards,
Stefan Gretscher
plug-in development & 3rd party plug-in support
Emagic Soft- & Hardware GmbH
Stefan Gretscher
plug-in development & 3rd party plug-in support
Emagic Soft- & Hardware GmbH
a subsidiary of Apple Computer, Inc.
email: email@hidden
phone: (+49)-4101-495-586
_______________________________________________
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.