Re: Is it possible to provide AudioUnits a Short Name?
Re: Is it possible to provide AudioUnits a Short Name?
- Subject: Re: Is it possible to provide AudioUnits a Short Name?
- From: William Stewart <email@hidden>
- Date: Fri, 3 Nov 2006 18:15:53 -0800
Doh! I didn't quite get the context.
On 03/11/2006, at 3:18 PM, Stefan Gretscher wrote:
Am 03.11.2006 um 20:48 schrieb William Stewart:
On 03/11/2006, at 9:47 AM, Jim Heintz wrote:
I would like to be able to offer long and short names for a
plugin I am working on.
Currently the way a plugin specifies it's name it in the ".r"
file like this:
#define NAME "MANUFACTURER: NAME"
i.e.
#define NAME "Jobob Plugs-Inc: Jobob Super Cool EQ"
If Joebob has more than one plug, this naming becomes a problem
when viewed on the Logic Insert area of the Logic Channel strip.
It would appear as "Jobob Su".
If Jobob has another plug named:
#define NAME "Jobob Plugs-Inc: Jobob Super Cool Amp Model"
They would both appear as "Jobob Su".
This sounds like a bug in Logic - we always anticipated that the
manu name would be broken out and used in a different context than
the AU name (for instance, have a look at how we use these in
AULab). Please file a bug - details are at http://
bugreporter.apple.com
Logic does break out the manufacturer name (as separated by the
':') from the resource fork.
In Jim's example it would split the names just like AULab as "Jobob
Super Cool EQ" and "Jobob Super Cool Amp Model".
That still would leave the app with two plug-ins named "Jobob Super
Cool ..." which is too long to differenciate when displaying it in
the channel strip.
To illustrate the problem in AU Lab: insert an AULowpass and an
AULowShelf, they look very similar in the channel strip, just a one-
letter difference:
<pastedGraphic.png>
But how to solve this issue other than just naming the AUs
differently...?
I mean even if there was a way to provide some short name, how to
guarantee that no other manufacturer comes up with the same or very
similar short name?
How about CoreAudio providing some utility function host apps can
call which looks at all the names of all the AUs that the host
wants to use and shortens them to the length requested by the host
app in a way that they are still recognizable but also differ
enough from each other to remain meaningful to the user?
I'm not sure we'd change this - not sure that we'd really be able to
make the situation that much better. We workaround the problem in
AULab by having a popup help thingie show up if you hover over the
effect name with the mouse (not ideal, but something)
Bill
Best,
Stefan
Thanks
Bill
Is it possible under the AudioUnit standard to supply a short
name that would be used in cases like this?
Best regards,
Jim Heintz
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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