I tried exporting the .vst3 with 1.0.34, but the DAW keeps crashing when loading it. A .log file is generated with the following content after the crash in C:\ProgramData\CabbageAudio\keyb (instrument name):
Cabbage DEBUG: Resetting csound …
csound = 0x000000004ADFDC20 Cabbage.cpp (114) cabbage::Engine::setupCsound [Thread ID: 9120].
@rorywalsh I’ve tested now your new release (v34) and I’m getting the same problem as on the beginning: after compiling the instrument, it won’t load. There is just Cabbage logo in the window.
I again manually set pathToJsSource and pathToCabbageBinary.
Here is the console output:
Any ideas?
This looks like the websocket connection is not connecting. You should be seeing a Client connected message. Remind me again, did you ever get it running on your end?
@Lovre I guess this is not working this time around for some reason? Can you double check your settings.json file?
I have confirmed that the aliasing problem occurs only when pressing the virtual keyboard and not with the MIDI controller (from VS Studio). I think p5 is taking a value of 1 or greater (I couldn’t verify this with printing because my console is black), as when I set this value to the amplitude of vco2 , aliasing occurs. It seems that the keyboard is sending p5 values equal to or greater than 1 when pressed, which causes the distortion. However, in Cabbage 2, the values sent when pressing the keyboard are lower than 1, which prevents the aliasing. If p5 is set to 1, the error also occurs in Cabbage 2.
Regarding the export of VST3, it still doesn’t work on my desktop computer, although I managed to get it working on the laptop. I have several VST3 plugins that work fine, so I’m not sure what the issue is. One thing I appreciate about this new version is that automation in the DAW can now take absolute values entered manually if the range is different from 1 (previously, this was only possible if the range was from 0 to 1). I hope I can get it working on my desktop, where I have my music studio.
Thanks @Alejo, great find! That should be a simple fix. Just need to update some of the JS code. Do you get any errors when exporting on the desktop?
It was apparently the high amplitude.
I only see a message saying that the plugin was exported successfully. I tested it on the notebook with an example exported from the desktop, and it works. Maybe something is outdated in my machine or there’s an incompatibility with the VST3 format that Cabbage uses. I saw that it’s version VST 3.7.12, which seems to be newer than the one used by Cabbage 2.
Hi @rorywalsh ! So I reinstalled extension and in settings.json file I set “jsSourceDir”: “C:/Users/lovre/.vscode/extensions/cabbageaudio.vscabbage-1.0.34-alpha/src”.
After compiling Cabbage instrument directly after that, I get:
When I manually set pathToJsSource in extensions settings, the error is gone but instrument is still not loading…
I can’t imagine any hosts would have an issue with that. If you get a moment, would you try testing the exported plugin with pluginval? It might give us an idea of what’s happening. 
I’m wondering if somehow it’s not actually loading CabbageApp.exe. What do you see in the Cabbage output? Can you copy and paste?
Yes seems to be something in that direction…
Output:
Process exited with code 3221225785 and signal null
Process exited with code 3221225785 and signal null
Can you share your settings.json file?
Of course. Here:
{
"currentConfig": {
"audio": {
"buffer": 512,
"driver": 0,
"in1": 1,
"in2": 2,
"inputDevice": "Default Device",
"out1": 1,
"out2": 2,
"outputDevice": "Default Device",
"sr": 44100
},
"jsSourceDir": "C:/Users/lovre/.vscode/extensions/cabbageaudio.vscabbage-1.0.34-alpha/src",
"midi": {
"inChan": 0,
"inputDevice": "off",
"outChan": 0,
"outputDevice": "off"
}
},
"systemAudioMidiIOListing": {
"audioDrivers": [
"DirectSound",
"ASIO"
],
"audioInputDevices": {
"Mikrofonarray (Realtek(R) Audio)": {
"deviceId": 132,
"numChannels": 2
},
"Primary Sound Capture Driver": {
"deviceId": 131,
"numChannels": 2
}
},
"audioOutputDevices": {
"Default Device": {
"numChannels": 2,
"sampleRates": [
4000,
5512,
8000,
9600,
11025,
16000,
22050,
32000,
44100,
48000,
88200,
96000,
176400,
192000
]
},
"Lautsprecher (Realtek(R) Audio)": {
"deviceId": 130,
"numChannels": 2,
"sampleRates": [
4000,
5512,
8000,
9600,
11025,
16000,
22050,
32000,
44100,
48000,
88200,
96000,
176400,
192000
]
},
"Primary Sound Driver": {
"deviceId": 129,
"numChannels": 2,
"sampleRates": [
4000,
5512,
8000,
9600,
11025,
16000,
22050,
32000,
44100,
48000,
88200,
96000,
176400,
192000
]
}
},
"midiOutputDevices": {
"Microsoft GS Wavetable Synth 1": {
"deviceId": 1
},
"VirtualMIDISynth #1 0": {
"deviceId": 0
}
}
}
}
Hmm, can you open up the extension settings in vscode and clear the path to the Cabbage binary. Then restart. It should find the default path.
Nothing changed. Where should CabbageApp.exe be located?
It should be in the extension folder, in a folder called CabbageBundle, you can try to set this as the path wthin vscode? Call up the set Cabbage binary path command and choose that folder.
yes, CabbageApp is in CabbageBundle folder and I set path to it using Cabbage command but unfortunately no changes
Ok, can you send a screenshot of teh path as displayed in the Cabbage settings within vscode?
Right, that’s not cleal at all 
I was hoping to see if you set the path to the folder containing the binary, or the the binary itself, it should be the folder containing the binary. Can you confirm?
