Cabbage Logo
Back to Cabbage Site

Cabbage VCV-rack export

I know this might be a pipedream but what about a VCV rack export for cabbage?
I think it would be game-changer for VCV surely if we can export csound/cabbage files directly to or create VCV rack modules.

I got a basic Csound VCV interface working Ok. I think it would be quite a lot of work to recreate the same GUI interfaces in VCV as we have in Cabbage. I am leaning towards the same approach I took with CsoundUnity, that is users can develop instruments in Cabbage, but they would load as native interfaces in VCV. Building on Windows might also be a pain as Csound is now built with MSVC and not gcc. I can’t promise any movement on this soon, but it’s on my radar :wink:

1 Like

Hi Rory !

Your menu entry for exporting to a Rack plugin raised some interest on the official VCV Rack users group page. What’s the status of this aspect of Cabbage ? Is it going forward ? V1 of VCV Rack will be released soon, might be a good time to review the possibilities of Cabbage + VCV Rack. Btw, I’ve used some Cabbage-made VSTs hosted in Rack, the results are iffy. Some plugins work fine but I often get a lot of JUCE assertion errors caused by the plugin.

Also btw: I built the latest Cabbage and CabbageLite. It was kind of a pain to get everything built that I wanted, particularly the full version of Cabbage, but I did get it all compiled and running. And given the very slight acceptance of VST3 in the major DAWs (excepting Bitwig, of course) I hope that Cabbage will continue to export as VST2.

Best regards,

dp

Hi Dave, I’ve no returned the VSV Rack project in quite some time as I don’t use VCV. But It must be said that it’s only a simple implementation. On the other hand, doesn’t VCV rack now support VSTs? So doesn’t this make the whole thing rather redundant?

Regarding building on Linux, I’ve not spent too much time in Linux lately, so I’m not sure of where things stand there, but I will take a look shortly. And rest assured that I intend to support Linux Native VST in all forms :wink:

@davephillips it would appear that you were trying to build with the master branch? I’d stay clear of that one as it is well behind the dev branch, which should build out of the box. Note that you will need to put the VST2 files into a vst2.x folder and place it within the /SDKs/VST_SDK/VST3_SDK/pluginterfaces folder. The contents of mine contains the following the following files:
aeffect.h aeffectx.h vstfxstore.h
After that it should build without any problems. I just tested here and it built straight out of a fresh clone of the develop branch.

Thanks, Rory, I’m on develop now. I had a problem with the buildCabbage script, it wouldn’t pick up the path to the VST SDK. I resolved the problem by running Projucer on CabbageIDE.jucer and adding the path to the Extra Includes. Also, when I try to export as a VST effect or synth I get an error that /usr/bin/CabbagePluginEffect.so can’t be found, and indeed, I can’t find it. Am I missing steps somewhere ?

Did you run the installCabbage script? Doing so will install Cabbage and place binaries into the usual system dirs. If you don’t install, you should still be able to run Cabbage and export plugins so long as the .so files are contained in the same directory as the Cabbage app itself. Everything gets built into the ‘build’ dir when buildCabbage.sh is called. Look in there for the .so files. If they are not there then they didn’t build.

The IDE now depends on the VST SDK too since I added the ability for it to load 3rd party plugins. I’ll update the .jucer files. Thanks for letting me know.

Right-o, the .so files aren’t building. I’m getting this error:

Compiling GenericCabbageEditor.cpp
/bin/sh: -c: line 0: unexpected EOF while looking for matching "' /bin/sh: -c: line 1: syntax error: unexpected end of file /bin/sh: -c: line 0: unexpected EOF while looking for matching"’
/bin/sh: -c: line 1: syntax error: unexpected end of file
MakePluginEffect:199: recipe for target ‘build/intermediate/Release/include_juce_audio_plugin_client_Unity_f9553f92.o’ failed

What’s Unity and do I need it ? [Edit: Never mind, I looked it up. I don’t think I need it, so I’m disabling it in the makefiles.]

Whoops, I’ve also removed that from the dev branch. Sorry about that. Is it building Ok now?

Still no joy. Now the build fails here:

Compiling CsoundPluginProcessor.cpp
/bin/sh: -c: line 0: unexpected EOF while looking for matching "' /bin/sh: -c: line 1: syntax error: unexpected end of file MakePluginEffect:185: recipe for target 'build/intermediate/Release/CsoundPluginEditor_3f0e809d.o' failed make: *** [build/intermediate/Release/CsoundPluginEditor_3f0e809d.o] Error 1 make: *** Waiting for unfinished jobs.... /bin/sh: -c: line 0: unexpected EOF while looking for matching"’
/bin/sh: -c: line 1: syntax error: unexpected end of file
MakePluginEffect:190: recipe for target ‘build/intermediate/Release/CsoundPluginProcessor_dc39856c.o’ failed
make: *** [build/intermediate/Release/CsoundPluginProcessor_dc39856c.o] Error 1
/bin/sh: -c: line 0: unexpected EOF while looking for matching "' /bin/sh: -c: line 1: syntax error: unexpected end of file MakePluginEffect:180: recipe for target 'build/intermediate/Release/CabbagePluginProcessor_8a6343af.o' failed make: *** [build/intermediate/Release/CabbagePluginProcessor_8a6343af.o] Error 1 /bin/sh: -c: line 0: unexpected EOF while looking for matching"’
/bin/sh: -c: line 1: syntax error: unexpected end of file
MakePluginEffect:170: recipe for target ‘build/intermediate/Release/include_juce_audio_plugin_client_VST2_dd551e08.o’ failed
make: *** [build/intermediate/Release/include_juce_audio_plugin_client_VST2_dd551e08.o] Error 1
Compiling GenericCabbageEditor.cpp
/bin/sh: -c: line 0: unexpected EOF while looking for matching "' /bin/sh: -c: line 1: syntax error: unexpected end of file MakePluginEffect:175: recipe for target 'build/intermediate/Release/CabbagePluginEditor_4348213a.o' failed make: *** [build/intermediate/Release/CabbagePluginEditor_4348213a.o] Error 1 /bin/sh: -c: line 0: unexpected EOF while looking for matching"’
/bin/sh: -c: line 1: syntax error: unexpected end of file
MakePluginEffect:195: recipe for target ‘build/intermediate/Release/GenericCabbageEditor_50c74848.o’ failed
make: *** [build/intermediate/Release/GenericCabbageEditor_50c74848.o] Error 1
cp: cannot stat ‘./build/CabbagePlugin.so’: No such file or directory
JUCE v5.4.1

I just pushed some changes through now to address a few things. I think they address the issues you’re having. Sorry about this, I know how frustrating it is! But the build and install scripts should work fine now.

Hey Rory, you rocked it, thank you ! All good now, export as VST works as advertised, I’m a happy Cabbage camper again. Btw, I exported the waveguide1 processor, it loads and apparently works well in the VCV Host FX module. I’ll let you know if I run into any really horrible problems. :slight_smile:

Meanwhile, yeh, I don’t know how much work you want to put into the Export As VCV Rack Module. It’s a great idea, but if Rack’s VST hosting works okay there’s not much need for that export function. I admit it would be cool though. At any rate, now is not the time to work on it, VCV Rack v1 is close to a release date and the code is still unsettled. If you do want to put any effort into it, you should probably wait until v1 shakes out after its release, let things settle into stability.

Thanks again for all the help, Rory, it’s much appreciated.

I already got bitten once by the constant state of flux in the VCV code base. It’s like hitting a moving target. I’ll definitely be waiting till it settles down again before revisiting it!

1 Like