Vst is black-listed

Questions
1

Hi,
Probably I missed the point.
I am running the extension vstplugin v0.5.4 on SC 3.13.0 and on mac osx 12.7.2.
How can I solve the following black-listed plugins?

-> VSTPlugin
searching in '¨~/Library/Audio/Plug-Ins/VST'...
found 0 plugins
searching in '/Library/Audio/Plug-Ins/VST'...
'/Library/Audio/Plug-Ins/VST/ATKCompressor.vst' is black-listed.
'/Library/Audio/Plug-Ins/VST/ATKTransientShaper.vst' is black-listed.
'/Library/Audio/Plug-Ins/VST/ATKTransientSplitter.vst' is black-listed.
...

Thanks,
Y.

2

What’s the console output of a clean search, e.g. after VSTPlugin.clear?

3 
VSTPlugin.clear;
VSTPlugin.search(s);
------------
// Post window
waiting for '/Library/Audio/Plug-Ins/VST/ATKCompressor.vst'...
// then I get the popup (see screen capture below) ...
// so whatever I choose "Show in Finder" or "Cancel" the console output:
probing /Library/Audio/Plug-Ins/VST/ATKCompressor.vst... couldn't load! Operation not permitted [1]
------------

Screenshot 2024-01-22 at 15.38.36
Screenshot 2024-01-22 at 15.38.36656×720 85.4 KB

4

Go to the terminal and run:

xattr -cr “the folder where the plugins are”

This should get those plugins out of purgatory.

Sam

2 Likes
5

This is mentioned explicitly on the release page!

EDIT: Ah, the release page only talks about the extension itself, but doesn’t mention VST plugins. I need to be more explicit!

6

Hi @Spacechild1, @Sam_Pluta,

thanks! With the solution above I got my examples with VSTPlugins running again on OS 15.1.

I get the message “This operation is no longer supported” when following the instructions there:

Thanks again for this amazing extension.

best

Daniel

7

Thanks! I just noticed that in INSTALL.md · master · Pure Data libraries / vstplugin · GitLab we only clear the quarantine flags from the VSTPlugin binaries, but not from the actual VST plugins.

I think I have to add xattr -rd com.apple.quarantine <path-to-VST-plugins> to step 1.

I get the message “This operation is no longer supported” when following the instructions there

The instructions consist of several steps. Which step exactly triggers the message above?

8

It’s these operations of Step 2 that trigger the messages:

spctl --add --label “ApprovedVSTs” *.vst *.vst3

spctl --enable --label “ApprovedVSTs”

VSTPlugins itself made no problem, but I cannot recall at the moment if I enabled that before at some point or with step 1 …

9

Thanks! The commands above try to add the VST plugins to the GateKeeper’s whitelist, e.g. if plugins are not notarized or codesigned. Seems like this has been deprecated. (I remember I’ve heard that before.) Actually, SuperCollider is built with entitlements to allow unnotarized plugins, so I think spctl shouldn’t be necessary anyway.

In your case, I think the problem was that the plugins are not notarized and had the quarantine attribute set (e.g. because they have been downloaded with Safari). Sam’s solution removed the quarantine attribute, that’s why the plugins worked again.