Cabbage VST on macOS

[leonsp]

Hi,

I’ve got a problem with exporting an instrument plugin (just a simple synth) on macos. I’ve tried different formats (.vst,.vst3 etc) but no daw I’ve tried (Cubase,Reaper, Audacity) was able to detect it.

I only intend to use these for my own use.

I ve tried the advice from a different forum post: How to Codesign OSX Plugins

But while opnening Reaper and Audacity, there appeared an error message, that indicated codesign didn’t work. Maybe I didn’t do it the correct way. I was confused about the assets that go into resource folder.

Is there a simple solution to this? Isn’t there a way to export it without siging?

I’m fairly new to cabbage but I also tried the some code on windows and everything worked fine.

macOS 14.3.1 (23D60)

Chip Apple M1 Ultra

Cabbage 2.9.0

Leon

[rorywalsh]

Hi Leon, welcome to the forum. Can you try one of the newer beta builds. You can find info about them here:

Latest beta packages available here (updated links)

Cabbage packages are created remotely each time a commit is made to the Cabbage GIT develop repository. These builds are beta and can be accessed here Just follows the steps shown here: [2021-04-29 09.22.35] Please do not report issues to this thread. Report them to the Cabbage Slugs section of the forum; and please reference to reference the build tag if you can.

The newer versions of Cabbage add a ‘ad-hoc’ signing setting that you can enable. But the success of this largely depends on what tools you have installed, or came with your OS. Can you try the latest build and see if that works?

@leonsp

Isn’t there a way to export it without siging?

No. MacOS won’t allow you to run anything that isn’t signed. Try enabling the setting in Cabbage and Cabbage will try to codesign the plugin for you, but if that doesn’t work you have to do it yourself. FWIW, adhoc signing is pretty trivial, just run the following command on your plugin bundle:

codesign --force --deep --sign - /path/to/MyPlugin.vst3