Cabbage Logo
Back to Cabbage Site

Command 'Cabbage: Export as VST3 Synth' resulted in an error

#1

Hello,

I’m getting the following error when trying to export to both instrument and effect using Cabbage 3

image

Here’s the .csd, just a simple test:

<Cabbage>[

{"type":"form","caption":"Effect","size":{"width":580,"height":300},"pluginId":"def1"},

{"type":"rotarySlider","channel":"gain","bounds":{"left":500,"top":200,"width":80,"height":80}, "text":"Gain", "range":{"min":0,"max":1,"defaultValue":0.5,"skew":1,"increment":0.01}}

]</Cabbage>

<CsoundSynthesizer>

<CsOptions>

-n -d

</CsOptions>

<CsInstruments>

; Initialize the global variables.

ksmps = 32

nchnls = 2

0dbfs = 1

instr 1

endin

</CsInstruments>

<CsScore>

;causes Csound to run for about 7000 years...

i1 0 z

</CsScore>

</CsoundSynthesizer>
#2

Thanks @hdale94 - I’ll take a look.

#3

Did you get a chance to test vst export on Windows? Tried the newest version of vscabbage, but I’m still getting the same error on windows 10 :thinking:

#4

Crap, I will check this tomorrow. I was looking for this message but somehow couldn’t find it! Thanks for the reminder!

1 Like
#5

This should be fixed now. I’ve also added a new option in the settings to bundle resources into the plugin folder. Let me know if you can now export Ok. New build should be ready shortly.

#6

I tried to export to VST with version 1.0.33 using the “button” example, and the instrument causes a crash in the DAW (Nuendo, Ableton). Studio One doesn’t crash, but I can’t see the user interface, it seems something is wrong.
I’m not clear on this point from the documentation: “Bundle Resources Tells Cabbage to bundle all resources into the plugin folder, otherwise, all resources, including the .csd file, will be placed into the CabbageAdio resources directory.” That’s why I’m unsure whether I should bundle the resources before or after exporting the synthesizer as a VST3. Also, I don’t see any .csd file inside the folder, I only see a .vst3 file and a .pdb file.

#7

Oh I just added that today, it’s probably best to disable that option for now. Your resources will appear in the c:/ program data / cabbage audio folder. I tested this today before pushing and it was working ok. But I’ll take a look.

#8

I’m away from home currently, thought I had a windows laptop here but I can’t seem find it… I’ll look some more, but otherwise I will test it when I get back in a week :+1:

1 Like
#9

Testing now with newest build (1.0.34-alpha), but I’m still having some trouble exporting. When I export either synth or effect, there is no error message anymore, but the exported vst3-file never shows up in the folder.

This is where I’m trying to export to:
C:\Users\Dale\Documents\Work\Cabbage 3

#10

VST3’ should go in a fixed location, from Steinburg’ website:

image
image725×180 20 KB

#11

Yes, but is that necessary when exporting a vst3 from vscabbage? Thought this was when running the file in a DAW?

#12

Oh my apologies, you’re right, you should be able to export it anywhere you like, do you see any output messages when you export?

#13

This time I actually got a message, I wonder if there is a property in a settings.json file from a older version?

image
image1905×991 115 KB

#14

I think you have the js source path set to a previous version, but you’re now using a more recent version so that path is no longer valid. If you update your jsSourcePath to the new install location it should work. You shouldn’t really have to do this at all, but I can’t work out why this path is automatically set for some people.

#15

image
image1453×529 27 KB

It was actually in the vs-code settings for the vscabbage extension, is this stored in a .json file somewhere?

#16

Right, I found it at:
C:\Users\Dale\AppData\Roaming\Code\User

{

    "files.autoSave": "afterDelay",

    "editor.formatOnSave": true,

    "editor.detectIndentation": false,

    "editor.insertSpaces": false,

    "tabnine.experimentalAutoImports": true,

    "editor.defaultFormatter": "esbenp.prettier-vscode",

    "prettier.useTabs": true,

    "files.eol": "\n",

    "workbench.colorTheme": "Default Dark+",

    "javascript.updateImportsOnFileMove.enabled": "always",

    "typescript.updateImportsOnFileMove.enabled": "always",

    "security.workspace.trust.untrustedFiles": "open",

    "editor.stickyScroll.enabled": false,

    "cabbage.logVerbose": true,

    "cabbage.pathToJsSource": "c:\\Users\\Dale\\.vscode\\extensions\\cabbageaudio.vscabbage-1.0.23-alpha\\src"

}
#17

So I figured out why it did not export at all, I tried exporting when I was in the compiled instrument tab in vscode, switching to the .csd allowed me to export :+1:

#18

Right, I should add a way to allow this :+1:

#19

I’m noticing when I upgrade vscabbage, the paths remain the same in the VSCode settings:
image

Not sure if there’s anything one can do to update this automatically to the new version, but currently I need to update this manually.

The same is needed with the settings.json file at: C:\Users\Dale\AppData\Local\Cabbage

#20

If you have avalue set, it will persist. The idea here is to not have any value set, and let the extension select the correct path based on the version, but for some reason that’s not working. I’m in the process of rewriting the back-end again, it should make these things a lot easier to debug.

1 Like