That was my thinking also but it was simpler to do it then to explain 
Cabbage: Path To Cabbage Binary
c:\Users\lovre\.vscode\extensions\cabbageaudio.vscabbage-1.0.34-alpha\src\CabbageBundle
Cabbage: Path To JS Source
C:\Users\lovre\.vscode\extensions\cabbageaudio.vscabbage-1.0.34-alpha
I also tried here with C:\Users\lovre\.vscode\extensions\cabbageaudio.vscabbage-1.0.34-alpha\src but no difference
I solved It!! It was a conflict with Csound6! I now removed Csound6 completely from my PC and now it works
P.S. And only now I see your post " If you wish to use Cabbage 3, just rename the Csound6 folder." 
If I wasn’t so happy, I’d be quite frustrated by this 
Happy days. Give it a go and see what you think!
I have attached the exported .log file from pluginval. Something I have noticed is that on neither of the two computers I have is the .vst3 recognized in Ableton Live (not even on the laptop where I was able to run the plugin in Cubase). I hadn’t tested it in Ableton before, and there it is not detected and does not appear in the list.
Plugin val .log:
Starting tests in: pluginval / Scan for plugins located in: C:\Program Files\Common Files\VST3\Cabbage\keyb.vst3\Contents\x86_64-win\Release\keyb.vst3…
creating serverCabbage DEBUG: Resetting csound …
csound = 0x00000265BC4738C0 Cabbage.cpp (114) cabbage::Engine::setupCsound [Thread ID: 10388]
Num plugins found: 1
Starting tests in: pluginval / Plugin info…
Starting tests in: pluginval / Editor…
Finished validating: C:\Program Files\Common Files\VST3\Cabbage\keyb.vst3\Contents\x86_64-win\Release\keyb.vst3
*** FAILED WITH EXIT CODE: 3221225477
Finished batch validation
I will test with Ableton Live tomorrow. Pluginval doesn’t give us much info in this case. I’ll try it myself tomorrow at the highest level and see if I can manage to trip it up.
Hi Rory, I’ve been getting similar issues to what’s been happening above but it has been a little harder to follow as I am on Mac. I’m getting this error on save
ERROR: No Cabbage binary found at /Users/markojeremic/.vscode/extensions/cabbageaudio.vscabbage-1.0.42-alpha/src/CabbageBundle/CabbageApp. Please set the binary path from the command palette.
I have tried manually setting it as well as leaving it blank so i am assuming that it is an issue with csound6/csound7 being on the same system. I tried deleting every trace of csound6 but that didnt work either. I saw some mentions above of renaming csound6 but I can’t seem to find where to do that on Mac. If you have any idea on how what a fix could be that would be much appreciated.
[EDIT] I’ve kept looking through everything mentioned in this thread and i think i’ve tried everything there is to try. I’ve renamed csound6, manually set json and binary paths but im still getting errors to do with binary path not being found
On Mac you don’t need to rename anything, the two versions of Csound can live hand in hand. I was focusing more on the problems uses were having on Windows with this version, so I haven’t actually tested on mac in a bit. I’ll do so this morning and let you know. I may have to tweak a few things.
@MarkoJ0621 I just tested here on MacOS and I noticed a few things with it. I’ve made a new release. Can you test it? You can install Csound 6 and 7 side by side on macOS without any issues. Cabbage2 will use Csound6, and Cabbage3 will use Csound7.
Can you try to install the extension again, then hit run cabbage in the bottom right and see what messages you get? You should get a websocket connection message. If so open a .csd file and hit save. That should bring up the UI. There are some positioning issues with the UI, but I’ll sort them shortly. For now, I just want to know if it runs Ok for you.
Seems to be running just fine now! Great to see.
That’s great. Did you notice anything off with the UI? Can you try opening one of the examples (you can access them via the command pallete). I’m seeing odd positioning, but maybe it’s just me.
I believe there’s a bug to do with exporting as a plugin, as im getting an error about vscode being unable to find a binary because it’s searching for a directory with an old name.
even though I have the most recent version installed. Looking forward to trying to make custom UI’s with webcam interfaces and hydra visuals soon!
Thanks, I’ll sort that out shortly
Hi Rory, got a chance to come back to working on custom UI’s but still struggling to export a vst.
Im getting an error about being unable to find CabbagePluginSynth.vst3. Im on MacOs.
I’ve tried setting both paths blank but that doesn’t seem to helping as the error about being unable to find a file just returns with “” instead of the default directory.
Are you using the very latest pre-alpha package? I got a little preoccupied with Windows these past few weeks. I haven/t test on Mac in a while. I’ll look at this tomorrow when I get a chance.
I’ve started a new build, this one should be able to find the binaries Ok.
will try it soon!
Hey everybody, just a quick question: i can’t locate the binary of csound 7 on my mac. i used the .pkg which rory linked in this thread.
can someone help? i already checked the common directories for this.
Solved: it’s get installed into the Applications/ dir
I still have problems. I get no errors or warnings, but the GUI will not show up. i checked the thread a found the problem with the settings.jsonwhich was ok on my mac. i compile the instrument and the beautiful cabbage shows up, then i go into edit mode and it gets blank.
any idea what i’m doing wrong?
i get this issue too sometimes, still unsure on wether it’s something i’ve configured wrongly or just bugs.
