Cabbage 3 coexist with older Cabbage

Cabbage 3
1

Hi,

Congratulations on the new everything. The future looks bright!

Just starting to get into it, while also having a few hundred older Cabbage plugins, one of my first questions is if it is possible configure my system (on Windows) so that both old plugins and the new Cabbage 3 (Vscode Cabbage server, and the exported plugins) can work at the same time?

I have both Csound 6 and 7 installed here. If I set the path order with Csound 6 first, my old Cabbage plugins load and work in the DAW. In this case, I can access Csound 6 on the terminal with ‘csound’ and Csound 7 with ‘csound7’. Then, the Cabbage server in VScode will not run as it finds the wrong Csound version. Then, if I change the order in the PATH so that Csound 7 comes first, then the Cabbage server in VScode works, but my old exported Cabbage plugins fail to load (can find start point).

It would be immensly useful to be able to still use my old Cabbage plugins and start working with Cabbage3 and Csound7 for my new ones.

2

This is a good question. And one I don’t have a good answer for. I think I will need to speak with the Csound devs about possible solutions to this particular conundrum. :+1:

[edit] I’ve open a github issue with a proposed solution. The timing of this isn’t great, but I think something will need to be done. MacOS users don’t have this issue, it seems a little unfair that Windows users should not have to suffer like this :rofl:

3

Ok. Thanks. Looking forward to hear and see how it goes.

4

We’ve been discussing it and I think we will proceed with this change. It will mean Cabbage 2 and Cabbage 3 plugins will be able to live side by side! :clap: