GarageBand/Final Cut Pro invoke the InfoHelper application to scan AU plug ins and create a plist of available plug ins. My plugin causes a crash of this application and thus does not end up in the list of available plug ins.
Final Cut Pro first runs auvaltool, but then runs InfoHelper in a similar way to Garageband. Since my plugin uses Qt as a GUI front end, Qt only supports instantiating the UI on the main thread. In an attempt to fix the issue, the startup code was forced to run on the main thread using dispatch_sync(dispatch_get_main_queue(), ...). This results in a deadlock in InfoHelper, whether this is called from Factory or Construct in the Audio Unit. Garageband then allows the plugin to load, but InfoHelper stays open until Garageband is closed. Final Cut Pro shows the plugin in its list but then also hangs on instantiation. InfoHelper remains open as well. Logic Pro X works fine but I'm a little worried that the same AU validation will be ported to Logic in the near future. Also, I've read that AUV3 allows plugins to be loaded in process using kAudioComponentInstantiation_LoadInProcess, but I don't see a way to do this with AUV2 aside from porting to V3. Does anyone have any tips on how to solve this? I'm a little stumped at the moment. _______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list (Coreaudio-api@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to arch...@mail-archive.com
