Cabbage Logo
Back to Cabbage Site

Locally build VST not working in Reaper7, invalid CodeSign

#1

Hey, I decided to upgrade to Reaper7 and noticed that my plugin doesn’t load.

I looked at the logs and found out that it’s an unrecognised code signature. Despite the plugin being build locally on the very same machine. I thought macos code signs its own stuff automatically, any ideas what I can do? And no, I ain’t got the money for an apple developer license. The plugin still loads in Reaper5 which is the version I used before, but since it is running in Rosetta 2 I was getting latency issues.

Thanks for the help!

#2

Well I decided to try out the x86 build of Reaper7 and after some file tweaks the plugin works again. Must be the hardened runtime the website talks about, didn’t notice it at first. So far everything seems fine again.

#3

You still need to sign your plugins. Cabbage will try to automatically sign them when they are exported (if this is enabled in settings), but it’s not bullet proof. Both the arm64 and x86 versions of Reaper should be able to load your plugins. Is this not the case?

#4

Well it doesn’t, only the x86 version loads the plugin.

#5

I’m seeing the same issue now myself. What website were you referring to in your earlier mail? Seems like I have some reading to do.

#6

I am able to run vst3 plugins without any issues as long as I sign them locally. Considering development of VST 2.4 was officially stopped in 2018, I guess it might be time to move on. I am not sure Cabbage 3 will support VST2.4 at all.

#7

Well it’s simply the download page on reaper.fm, there is a little note talking about hardened runtime or something just below the link to the x86 version.

#8

Fascinating, well I’m curious where plugin development will go in the near future. VST is an outdated format so makes sense it got ditched. But I’m also concerned about access to future formats becoming limited because everyone tries to lock it behind a paywall. Which is why I’m investigating custom hardware now.

1 Like