Reliably finding the binary for an audio unit from a host
Reliably finding the binary for an audio unit from a host
- Subject: Reliably finding the binary for an audio unit from a host
- From: Stefan Gretscher <email@hidden>
- Date: Wed, 06 Jul 2011 15:41:14 +0200
Hello,
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?
Thank you,
Stefan Gretscher
_______________________________________________
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