MacOS VST questions

I can’t seem to test my MacOS Cabbage 2.10.0 exported VST, none of my VST-capable apps see the plug-in. So far I’ve tried Reaper (and a couple audio apps that I suspect only work with effect type VST).

Pluginval thinks they’re fine and I’ve tried manual code signing, though the ad-hoc signage provided by Cabbage seems to be working. On one of the forum posts I saw an assertion that ad-hoc signing doesn’t work on Ableton, so maybe I’m running into the same kind of thing here?

What are folks doing for testing?

Thanks!

Welp, just installed Bigwig and it sees my VST3 and it seems to be running fine. Apparently Bitwig’s demo mode allows everything to run but disallows saving so this could be a good test platform option.

Seems like a pretty cool DAW, too.

Adding to the list, the free version of Element by Kushview runs the AU fine but isn’t seeing any VST for some reason. Sees LV2, though, fwiw. Might be good for folks who don’t have a Logic license to test AU?

Hello, was it working with the previous versions of Cabbage?

I am developing VSTs on MacOS and I use Ableton Live and it works well.

I use this cmd line to manually sign my plugins: codesign -s - PluginName.vst3 --timestamp --force --deep

1 Like

Thanks for that. I don’t have a copy of Ableton but I guess I can always download the demo. My VST3 in Bitwig work on MacOS so maybe the problem is with the specific MacOS apps I’ve tried thus far rather than with Cabbage.

I forgot I had an Ableton Lite license on my old Mac, so now I’m seeing my VST3 work in both Live 10 and 12. Woot!

1 Like