Re: Reliably finding the binary for an audio unit from a host
Re: Reliably finding the binary for an audio unit from a host
- Subject: Re: Reliably finding the binary for an audio unit from a host
- From: Stefan Gretscher <email@hidden>
- Date: Thu, 07 Jul 2011 11:33:33 +0200
Am 07.07.2011 um 08:59 schrieb tahome izwah:
> - (NSString *)bundlePath gets you the path to the bundle, once you have identified it.
Sure, but the question actually is how do I identify it in first place?
-Stefan
> 2011/7/6 Stefan Gretscher <email@hidden>:
>> since audio units can be installed in multiple locations (e.g. user vs. local domain), it is possible for a user to get confused about which plug-in (and more particular, which version of a given plug-in) is installed where.
>> To resolve this confusion, one could consider designing a dialog similar to Logic's Audio Unit Manager, but with an extra column added containing the location of the each audio unit on the disk.
>> The problem is, how can the host retrieve this information reliably, when it only has FindNextComponent() as a starting point?
>> I mean, when you program an audio unit you can use your own well-known and hardcoded bundle identifier to find the binary, but this information is not available from the outside (i.e. from the host) as far as I can tell -
>> at least I did not find according API in the Component Manager or in the newer Audio Component Service. Am I missing something obvious here?
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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