You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had some trouble with both the VST3 and AU versions of Xenos when trying to install on Mac. For VST3 I used VCV Rack as my host, which is built for Intel and runs under rosetta on my M1 Mac Mini running macOS 13.4.
I am aware that I need to go to system settings/security and click the "Open Anyway" button:
But that has no effect. The button stays there and I keep pressing it and nothing happens. It doesn't seem to matter whether I click "Show In Finder" or "OK"; in any case I have to click one or the other many times (like 30) before the dialog stops popping up.
Trying to load the AU version in Logic, Logic flags it as not-openable, I go into the plugin manager and check the "use" box but it still says "couldn't be opened".
Nothing shows up in Security Settings - or rather, it is still showing that the vst3 was blocked from use.
Do you have any tips on addressing this?
The text was updated successfully, but these errors were encountered:
Hello,
I had some trouble with both the VST3 and AU versions of Xenos when trying to install on Mac. For VST3 I used VCV Rack as my host, which is built for Intel and runs under rosetta on my M1 Mac Mini running macOS 13.4.
I am aware that I need to go to system settings/security and click the "Open Anyway" button:
But that has no effect. The button stays there and I keep pressing it and nothing happens. It doesn't seem to matter whether I click "Show In Finder" or "OK"; in any case I have to click one or the other many times (like 30) before the dialog stops popping up.
Trying to load the AU version in Logic, Logic flags it as not-openable, I go into the plugin manager and check the "use" box but it still says "couldn't be opened".
Nothing shows up in Security Settings - or rather, it is still showing that the vst3 was blocked from use.
Do you have any tips on addressing this?
The text was updated successfully, but these errors were encountered: