Re: Component from ComponentInstance?
Re: Component from ComponentInstance?
- Subject: Re: Component from ComponentInstance?
- From: Marc Poirier <email@hidden>
- Date: Wed, 26 May 2004 22:09:03 -0400 (EDT)
In my tests, I've found that the Component Manager won't even register 2
components with identical ComponentDescriptions. It will make some
choices based on domain (user domain before local domain, local before
system, etc.), version value (higher version is preferred), and maybe
other factors that I don't know about. But anyway, the Component Manager
will never give you 2 components from FindNextComponent that have the same
ComponentDescription, they get weeded out before you can even see them.
Marc
On Wed, 26 May 2004, kelly jacklin wrote:
>
On May 26, 2004, at 12:55 PM, m wrote:
>
>
> I had considered that, in fact my list already contains the Components
>
> and they're descriptions. I'm concerned that perhaps
>
> ComponentDescriptions aren't guaranteed to be unique from Component to
>
> Component. For intstance, the user may have two versions of an AU
>
> installed, and the AU vendor might not have been as scrupulous as one
>
> might like in updating the version flags. Perhaps I'm worrying about
>
> this too much, but NI used to be fairly cavalier about the 'vers'
>
> resource in the past.
>
>
If two AUs have the same ComponentDescription, then already there will
>
be problems, given that the AUGraph interface for creating an AudioUnit
>
into a graph takes a ComponentDescription as the parameter to find and
>
instantiate the AudioUnit.
>
>
I wouldn't worry about it, if I were you. This seems like a pretty
>
pathological edge case to me, and one that you would really have no
>
measure to guard against (or to deal with, if you were using the
>
AUGraph API).
>
>
kelly
_______________________________________________
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.