Re: so, just what is the intended purpose of "subtype" for an AU plugin?
Re: so, just what is the intended purpose of "subtype" for an AU plugin?
- Subject: Re: so, just what is the intended purpose of "subtype" for an AU plugin?
- From: Paul Davis <email@hidden>
- Date: Fri, 12 Mar 2010 11:07:38 -0500
On Fri, Mar 12, 2010 at 11:00 AM, Paul Davis <email@hidden> wrote:
[ ... ]
following up on my own email, i realized something just after i sent
it. the convention in AU land appears to be that a plugin is uniquely
identified by the triplet of "type-subtype-manufacturer". given that
most plugins are FX, type is fixed as "aufx", and the manufacturer is
a given. thus, to uniquely a given plugin from a particular
manufacturer, subtype has to be a plugin ID, not a "type of plugin".
apple gets away with this for their own plugins because they only make
1 of any given type of plugin, or, when there is more than instance,
they differ in the "type" field, eg:
aufc tmpt appl - Apple: AUTimePitch
auol tmpt appl - Apple: AUTimePitch
this means that "subtype" cannot possibly play the role described by:
> "In the file system, an audio unit’s loadable code is contained in a
> bundle. Each such bundle is uniquely identified by a triplet of
> four-char codes. The type code programmatically identifies what the
> audio unit is for—such as mixing or audio format conversion—and
> indirectly specifies the audio unit’s API. The subtype code
> contributes to the bundle’s identification and indicates more
> specifically what the audio unit does. For instance, the subtype of a
> mixer type of audio unit might indicate that it is a multichannel
> mixer."
was this just a thinko in the design of AU?
--p
_______________________________________________
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