Re: Newbie AU questions (AU types and subtypes)
Re: Newbie AU questions (AU types and subtypes)
- Subject: Re: Newbie AU questions (AU types and subtypes)
- From: Bill Stewart <email@hidden>
- Date: Thu, 19 Sep 2002 10:04:06 -0700
I third it, so I guess that carries it...
Rather than having to open the Audio Unit though to get this additional
information, a component has resources (which are generally being replaced -
we hope! - by plists)
So, what we'll do is look into what we could do there that would provide
more meaningful information about the types of thing(s) and audio unit does
- this won't be done in the short term however (unless someone wants to
explore this further and make us a suggestion we can't refuse!)
So, to revise...
(1) The componentType of an AudioUnit should be one of the types that are
defined by us (and to flog a dead horse, we're *not* expecting anyone
developing units now to be supporting the V1 - kAudioUnitType 'aunt' - so
we're talking about the class of Type ID's that are defined in the Jaguar
header - <AudioUnit/AUComponent.h>
(Whilst I'm on this as well, one of those types is incorrectly defined - and
will be fixed in the next developer update. kAudioUnitType_MusicEffect was
defined as 'aumx' - but this is also the same declared type as the mixer, so
this is redefined to be 'aumf', the mixer type will continue to be 'aumx')
(2) The manufacturerID is an unique code that identifies which company is
responsible for inflicting their DSP on the rest of us innocents.
ManufacturerID tables are kept by Apple, and to ensure the uniqueness of
your own ID, you should register this with Apple. Details can be found at:
http://developer.apple.com/dev/cftype/
(3) The subType has no restriction, or suggested guidelines, on how this is
defined.
Host applications can sort AudioUnits based on manufacturer or component
type, but cannot rely on any logical ordering or usage of the subtype field.
OK?
Bill
on 19/9/02 1:27 AM, Jim Wintermyre wrote:
>
>>> What about Paul's suggestion to use three characters of the
>
>> subtype to indicate the standard categories? This could be refined
>
>> to specify that subtypes starting with three lower case characters
>
>> are reserved by Apple to indicate the generic categories, and then
>
>> each manufacturer could create more than one variation for each
>
>> standard effect. subtypes with an upper case character in any of
>
>> the first three digits would indicate an AU which is not conforming.
>
>
>
> Personally I like B.J.'s suggestion better. People are bound to get
>
> it wrong doing this split-function 4-byte ID thing, and I doubt that
>
> most people will even be utilizing the standard effect type thing
>
> anyway, so I think it's best to have it be a separate property, for
>
> those effects that want to conform to a standard type.
>
>
I second that motion...
>
>
Jim
>
_______________________________________________
>
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
__________________________________________________________________________
"...Been havin' some trouble lately in the sausage business," C.M.O.T.
Dibbler replied.
"What, having trouble making both ends meat?"
__________________________________________________________________________
_______________________________________________
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.