Re: Newbie AU questions
Re: Newbie AU questions
- Subject: Re: Newbie AU questions
- From: "B.J. Buchalter" <email@hidden>
- Date: Tue, 17 Sep 2002 19:06:37 -0400
- Resent-date: Tue, 17 Sep 2002 19:07:31 -0400
- Resent-from: "B.J. Buchalter" <email@hidden>
- Resent-message-id: <B9AD2DBD.B2C%email@hidden>
- Resent-to: CoreAudio list <email@hidden>
>
on 16/9/02 3:31 PM, Marc Poirier wrote:
>
>
>>> Ideally - an id that contains ALL lower case characters is reserved for
>
>>> use by apple (So your ID could be ACME, Acme, aCME, etc but NOT acme)
>
>>>
>
>>> Not sure actually where you register the ID however...
>
>>
>
>> That would be at http://developer.apple.com/dev/cftype/
>
>
>
> Are you sure about that? It seems weird to me that you would
>
> register a componentManufacturer code via the application creator
>
> code registry. These codes do not serve the same functions at all
>
> and I see no reason why there couldn't be duplication of codes
>
> between the 2 types.
>
>
>
> One other question: Are all-lowercase componentSubType codes also
>
> reserved by Apple, or is it only all-lowercase componentManufacturer
>
> codes that are reserved? It will be a problem for VST -> AU
>
> compatibility if all-lowercase subtype codes are reserved, since that
>
> was not the case for VST plugin "unique ID" codes...
>
>
We would really like to maintain a list of sub-types that implementors of
>
specific types of dsp would conform to.
>
>
For instance, a reverb effect could be identified by the
>
kAudioUnitType_Effect and the kAudioUnitSubtype_Reverb
>
>
Then - different manufacturers provide different implementations of this
>
that in many cases would report similar parameters, etc...
It would seem that this sort of limits a Manufacturer to one implementation
of each effect sub-type, or a manufacturer will have to implement virtual
manufacturer codes. It would seem that we need:
The component type (set in stone)
The sub type (a common effect classification type)
The manufacturer code (a code for all plugs by a particular entity)
And a "flavor" type (which would be unique within the scope of a
manufacturer)
This way we could have
KAudioUnitType
kAudioUnitSubtype_Reverb
KAudioUnitManufacturer_MetricHalo
KMH_SamplingReverb
And
KAudioUnitType
kAudioUnitSubtype_Reverb
KAudioUnitManufacturer_MetricHalo
KMH_SimulatedReverb
And
KAudioUnitType
kAudioUnitSubtype_Reverb
KAudioUnitManufacturer_MetricHalo
KMH_RoomReverb
etc.
Since KAudioUnitType is not really descriptive (e.g. It just identifies that
the component is an AudioUnit) and kAudioUnitSubtype is really being used as
a classification system, KAudioUnitManufacturer is not really enough --
because we will run into the VST namespace problem if that is all we have.
If we use the kAudioUnitSubtype as the manufacturer scoped id, we will
break the classification system. So it probably behooves us to get this
figured out early since there ought to be a bazillion audio units created in
the next little while....
Best regards,
B.J. Buchalter
Metric Halo
M/S 601 - Building 8
Castle Point Campus
Castle Point, NY 12511-0601 USA
tel +1 845 831-8600
fax +1 603 250-2451
If you haven't heard ChannelStrip yet, you don't know what you're missing!
Check out SpectraFoo, ChannelStrip and Mobile I/O at
http://www.mhlabs.com/
Download a 12 day demo from <
http://www.mhlabs.com/demo/>
_______________________________________________
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.