Cabbage Logo
Back to Cabbage Site

FL Studio crashes when trying to open VST plugin from Cabbage

#1

I made an extremely simple test synth in Cabbage, exported it as a “VST Plugin Synth” and put it a folder. I then went into FL Studio’s Plugin Manager, added the path to that folder into the Plugin search paths (with the type VST). I then clicked “Find installed plugins” and the correct plugin appeared in orange. It had all the (ostensibly) correct details, status: ok, format: VST, kind: Apple + Intel, effect: Synth, Vendor: CabbageAudio. I then closed the plugin manager and opened up the FL Studio plugin browser on the left-hand side (in the main FL Studio window) and dragged the new plugin into the Channel rack. FL Studio then quit by itself and shortly after, a window saying “FL Studio quit unexpectedly” popped up.
As far as I know I did not use any special code that would make some error.

Is there any step I’m either missing or doing wrong here?

#2

Do the example plugins from Cabbage work in FL?

#3

I just checked and they do not work. They still crash FL when trying to be opened.

#4

If it helps at all, I’ve also been having a problem where exporting as a standalone application generates a “damaged or incomplete” app. I’m using a mac for everything.

#5

That’s discouraging. I’m not an FL Studio user, but hopefully someone else will chime in.

#6

I would scan the plugins with pluginval to double check that it’s definetely FL firstly

#7

Hello, if you want you can send your plugin and I can try to load it in FL. Having the csd could also be useful.

I am on a M3 Intel Mac and developed VSTs that work on FL so I might be able to help.

Julien

#8

What version of Cabbage are you using? If you’re using the latest public release, 2.9, you need to update. I just triggered a new build now, which will be available here in a short while:
https://dev.azure.com/rorywalsh/cabbage/_build?view=runs
If you’re not already using the latest, try that one when it’s cooked. :+1:

#9

I created a google drive folder with them: https://drive.google.com/drive/folders/1aPA0bsqB1gRhBuabpGkmIxTmMOdxGpi3

#10

I scanned the plugins and they all passed the tests, so maybe it’s a problem with FL?

#11

I just tested here and it worked fine, what version are you using? I see that my last trigger didn’t build due to issue with DevOps, but this version should work Ok…

#12

It appears I’m using 2.9.0, given that’s the update listed here and I downloaded Cabbage only a couple days ago. Did you test using the latest version of FL? If so I might try updating, since I haven’t in a while.

#13

I just updated both FL Studio and Cabbage to the latest versions (Cabbage to 2.10 and FL Studio to 25.1.2) and FL still crashes when trying to load the plugin.

#14

I’ve looked in the error message, and it says the reason for termination was “Namespace CODESIGNING, Code 2 Invalid Page” which I believe means there’s a problem with signing somewhere. Could Cabbage be not completely or adequately signing the files when I export something? (Or something else, I’m not super familiar on signing)

#15

Ah, you’ll need to sign them manually. Can you run this command on your plugin?

codesign -s - "you plugin name and path" --timestamp --force --deep

The auto-signing by Cabbage can be a little hit and miss.

#16

It finally worked!! Thank you so much

#17

Great, and sorry that you had to go through this. Apple don’t make things easy :frowning: