I’ve recently upgraded from Dorico 3.5 to 5, and a VST sampler that I was using in a project (TX16Wx) is no longer loading correctly (or at all). The plug-in is currently on the “Blocked Plug-ins” list in preferences, and whenever I try to add it to the “Allowed Plug-ins” list, it will allow me to apply it, but nothing changes in the vst instrument drop-down menu when I go to load the plug-in. When I return to the preference window, that plug-in is now duplicated on both the blocked and allowed plug-ins lists. This occurs for any plug-in I try to add to the allowed list from the blocked list. I’m on a mac, running Sonoma. Thanks in advance for your help!
What is your computer configuration and OS?
Posting a Diagnostic Report may speed someone’s diagnosis of your situation.
Dorico Diagnostics.zip (1.3 MB)
I’m running macOSx Sonoma 14.2.1
If these are VST2 plug-ins, they won’t run on Apple Silicon Macs.
It’s a VST3 plugin and it worked fine in Dorico 3.5 before I upgraded.
It comes as both, VST2 and VST3 plug-in, as it seems.
However the VST3 version got blacklisted for yet unknown reasons.
The VST2 version is not blacklisted but also somehow not recognized.
Therefore, even though it is whitelisted, it won’t turn up, because it can’t be found.
I will send later a script to find out why the VST3 version got blacklisted.
1 Like
Here we go: Download the attached zip file to your Downloads folder and unzip it .
Then invoke Terminal.app (via spotlight search) and type in or copy/paste the following commands:
sudo chmod 777 ~/Downloads/scanVSTs.sh
Hit the enter/return key and you’ll be prompted for your password. Type that in and enter/return again. Then the next command
~/Downloads/scanVSTs.sh
After hitting enter/return the script will start executing and after a minute or so it will create on your Desktop a new file called scanVSTsOutput.txt. That one please post here.
Thanks
scanVSTs.sh.zip (1.6 KB)
Ok here it is! Sorry for the delay, my computer is University-owned so I needed get an administrator to use the terminal for me.
scanVSTsOutput.txt.zip (2.4 KB)
Thanks for the data. It is strange though, the script now invoked the vstscanner on every plug-in you have and also the TX16Wx.vst3 (yes, the VST3 version) now also got scanned to be okay.
So let’s try to reset the scanner cache and enforce a fresh scanning of all plugs with you. So go to your home directory and from there to ‘Library/Preferences/Dorico 5 AudioEngine’ and delete the folder ‘Dorico 5 AudioEngine VST3 Cache’. On the next restart Dorico (or the audio engine) will rescan all VST3 plugs. Let’s see the outcome of that.
I currently have the same problem but running on windows 11 with the VST3 Krush has anyone found a fix yet? The preferences in Dorico finds two different identical Krush VSTs and when I try to whitelist them it generates another set of two in the blacklist files. Any help would be very appreciated!
Welcome to the forum, @matthew2. Is it possible that there are both VST2 and VST3 versions of the Krush plug-in on your system? Perhaps it would be a good idea to do Help > Create Diagnostic Report and attach the resulting zip file here. @Ulf should be able to tell you what’s going on.
Here you go, I’m pretty sure it’s only one VST version as there’s only one file in the folder and when I move or delete the file it goes away. I am using a custom file directory if that could make a difference?
Dorico Diagnostics.zip (313.8 KB)
I can’t find a plug-in called “Krush” in the list of VST3 plug-ins that the audio engine has found. Might it be appearing under another name? Who is the manufacturer?
Krush is made by Tritik, it appears as blacklisted in Dorico so I’m not sure why it wouldn’t show up.
Sorry, but in the diagnostics data you attached earlier, I cannot find anything from Tritik, neither as VST2 or VST3, nor as blocked or non-blocked item.
I’ll try and send another diagnostic file maybe? This time using a different VST, thanks for the help though.
Update, it appears to now be working? I think the solution to any issues is to create the default VST directories Dorico is looking for as they didn’t exist already and use those? But I was effectively just getting frustrated and restarting Dorico and moving the file around repeatedly so I’m not entirely sure. Hope this helps anyone with the same issue!