I too have not yet tried validating an AU on El Capitan yet. That said I think I know what auval is complaining about. Assuming one is using the Core Audio Utility Classes, I think your AU is still compiling and exporting the older interface. For example, the Carbon view dispatch/creation call is typically declared via the AUDIOCOMPONENT_ENTRY macro (in ComponentBase.h). So, to eliminate this warning I think you need to disable the compilation and exporting of the Carbon Component Manager modules/behavior. This is what I did to remove the older interface and just use the v2 AudioComponent API:
1) Use the later version of the AUDIOCOMPONENT_ENTRY macro that doesn't create the ComponentEntryPoint::Dispatch calls. I did this by setting CA_USE_AUDIO_PLUGIN_ONLY in the "Preprocessor Macros" section of my Xcode build settings. You may need to wrap old behavior in your custom AU code/implementation with this macro check to disable those compilation units as well. 2) Remove the "_MyAudioUnitNameEntry" line from your .exp file so that just the "_MyAudioUnitNameFactory" remains. With respect to linking, this works in tandem with the above step. 3) Remove the rezzing build settings/phases and the respective .r files, they are no longer needed (though I have not confirmed if their presence is harmful). 4) Remove _some_ of the Core Audio Utility classes/.cpp files. I don't remember which ones offhand (I know AUDispatch.cpp needs to be removed for sure), but these will cause build errors when the above steps are completed. 5) You may have to do a Clean then Build between some of these steps to see any progress, what with all the linking changes. 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. --Christian On Wed, Sep 30, 2015 at 8:36 AM, Olivier Tristan <[email protected]> wrote: > Hi Guys, > > I have received some report that at least one of our AudioUnit plugin is > not validated under El Capitan. > N.I seems to have the same issue FWIW > > I suppose the issue is related to: > "WARNING: 140: This application, or a library it uses, is using the > deprecated Carbon Component Manager for hosting Audio Units. Support for > this will be removed in a future release. Also, this makes the host > incompatible with version 3 audio units. Please transition to the API's in > AudioComponent.h." > even though I don't know much as I haven't installed El Capitan GM myself. > > Thing is we don't have any Carbon view so I wonder to what this is related. > > Any ideas ? > > Thanks, > > -- > Olivier Tristan > Research & Development > www.uvi.net > > _______________________________________________ > 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/recapitch%40gmail.com > > This email sent to [email protected]
_______________________________________________ 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]
