Hello
I am using vstsdk3612_03_12_2018, and few customers reported us that plugins won’t run on their Logic Pro. They gets verified with PASS result, but are not shown on the plugins list.
It’s strange issue because it works on most Logics but not all.
MacOS is Catalina/Big Sur
I suppose it was my bug within stereo/mono bus configuration. Default is Stereo arrangement and I deleted SupportedNumChannels 1 channel configuration and it works with Logic. However Logic should report this and/or in Validator.
We managed to solve the problem on 99% Logics Pro, however we have still few user’s Macs where our AU plugin is not shown in the Instruments list. It is correctly detected & validated in Plugin Manager. SDK is 3.6.12. How to debug the problem with Logics? Steinberg please help.
Hello Arne
We contacted Apple and they said that “this is not Logic failure” :(.
They said this may have different causes including user permissions etc.
Do you (Steinberg) have the same problem with your plugins that they are not recognized on the Instrument list in Logic but they are “successfully validated” and nothing helps?
Sometimes clearing the cache helps but not on every computer. Clearing cache is not problem for the users, but sometimes nothing helps except creating the new account. This is most important issue for us.
If you cannot talk about this on the public forum I can talk to you by company e-mail address.
Funny. Did Apple tell you why Logic does not see the plug-ins while all other AU hosts see them?
We have not heard back from Apple regarding this issue and as this issue happens to other developers too who are not using the wrapper included in the SDK we see Apple in the liability to fix it, or at least give feedback what the problem is.
Every time I load Logic Pro 10.7.7 I get a “failed to create” error. See attached. I have to click 23 times before it goes away, then Logic Pro loads. Plugin Manager lists all AU"s successfully validated. Apple support and internet search have not been able to correct this. Someone please help! Thank you in advance!
We can confirm this issue. It only happened on some machines in the Latest Logic and GarageBand versions. It didn’t occur on other machines running the same OS and Host versions running the same plugin build.
Deleting the AU cache didn’t fix it, but, strangely enough, changing the aufx ID helped, so this along with the observation that creating a new user account helps, seems to point to some weird caching issue. It’s really unfortunate that Apple doesn’t seem to care, but I acknowledge that it’s kind of hard to reproduce.
I found the following command to be the only thing that allows Logic (11.1) to see changes to my plug-in’s supported channel configurations during development, aside from changing the plug-in’s version in Info.plist > AudioComponents.
The AudioComponentCache stores information about supported channel configurations and Logic appears to query this when deciding which plug-ins to show for a track.