This is a familiar scenario, which happens whenever opening a VST for the first time. However the usual solution is not working!
MacBook Pro 2014, Big Sur OS 11.6.8
The VST3 is Aeolus (organ emulator)
I go to System Preferences / Security & Privacy
I see the message “Aeolus.VST3” was blocked from use because it is not from an identified developer. I click “Open Anyway”… but nothing happens.
Dorico’s error message won’t go away, even with repeated “Cancel”
Eventually Dorico launches, without the VST listed in the plug-in manager.
Is this Dorico? Or Aeolus? Or my computer?
FYI I’m having the same trouble opening the VST3 of Aeolus in Audacity. The Audio Unit version did open in Logic but it took several tries.
Perhaps one of you can help me with my confusion about VST file formats.
The Dorico manual says that 5.0.* uses VST 2. But I’ve never seen a .vst2 file extension. And I’m trying to squish a .vst3 into Dorico now. Is it just not going to work even if I get it past MacOS security?
Is it possible you googled the manual and ended up with an early Dorico manual circa 2017? Dorico 5 definitely loads VST3 and you can white list VST2 if you need to. Get the current manual from the help menu inside Dorico.
Dorico did support VST3 plugs from the very beginning. In fact, we even drive the community of plug developers to drop VST2 support and to let Dorico’s audio engine only load VST3 plugs. Well, we have started this transition already by dropping VST2 on Apple Silicon. So VST2 is dead, long live VST3.
And yes, VST3 plug-ins are always detected automatically, you don’t need to whitelist them or anything.
But we also scan for VST3 plugs and do a quick short test with every plug-in. Should the test fail, the plug-in goes onto a blacklist and won’t get looked at anymore in the future. So if you are missing a plug-in on the list of available plug-ins and you that plug is VST3, then please create a diagnostics report and send to us.
Lastly, Dorico’s project file extension is *.dorico and into that project file go data chunks which represent the state of the plug-ins. At project close down Dorico collects those status data from every plug (actively used in the project) and at project loading time again, it distributes the data to the individual plugs. But this whole process is transparent for the user and all done automatically, so you will never see or deal with *.vst3 files.
Does that make sense to you?