I am investigating a little bit into Audio Unit v3 (extensions) development and whether or not it is viable to switch from AUv2 to AUv3 for Mac. following the discussions at the apple forum and looking into their sample code as well as the one provided by you (AUv3Synth), it seems to me that the only hosts in question (GarageBand and Logic Pro X) who support AUv3 on Mac are still not supporting the new API fully, leading to many headscratching on my part.
I tested the AUv3Synth demo and it seems there is some misbehaviour:
- If I load the AUv3Synth sample in Logic Pro X (10.3.0) for the first time, the 4 factory presets (that come with the AUv3Synth) load correctly. If I then save a custom preset and load it, the factory presets don’t load anymore.
getting the musicalContext (or transportContext)
- I could not be able to get the
hostTransportStateCallback. This could be because Logic doesn’t privode it for the AUv3 API? In the AUv3Wrapper during the
allocateRenderResourcesAndReturnErrorcall, the corresponding
transportStateBlockare initialized with nil.
Also I noticed that the AUv3Wrapper is not using any parameter grouping with
AUParameterGroup, so you just get a flat list of all parameters. Is this intended?
According to my research, at least the second problem seems to be on account of Logic. Can you confirm these Bugs or do you have any other information concerning the status of the AUv3 API in hosts on macOS?
Thanks for replies!