On 1/10/2015 2:16 AM, Christian Rober wrote:
One last warning:  I know hosts have been updating to the AudioComponent
(v2) API since ML, but IIRC some still required the older API.  I assume
that if a host has not yet adopted these v2 semantics, then your AU will
not load, which may cause some confusion during this upgrade.

Any idea whether this is a Catch-22 for host developers?

I've been sticking with the Component Manager APIs in my host to maximise backward compatibility with older OS versions. If I start using AudioComponent I wonder whether that will break loading old plugins.

Ross.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to