Cabbage3 alpha release

[ph_ne]

I guess, i have trouble with multiple csound versions on my system. I need my Csound6, because i have plugins, that can’t compile for Csound7 yet. i have both version installed. but i guess, the vscode csound extension is relying on the terminal to execute csound and this could be a conflict with cabbage and the linked csoun7 version?

EDIT: i tested csound --version in the vscode terminal and it shoes csound 6.18. i gues, i have to change this for vscode

EDIT: this was not the problem. i set in my .zshrc to the csound 7 executable, so that everytime i call csound --version also in the vscode terminal i get the csoun 7 version - but i did not help.

[rorywalsh]

Did you get this sorted? Csound7 and Csound6 can live side by side on a Mac without much problems. Cabbage3 will always look for Csound in the Applications/Csound folder, which Cabbage2 will look for it in the frameworks folder. You can also choose which Csound to use with the csound-vscode extension by calling up the ‘Select Csound’ command.

[rorywalsh]

Ah I see you found a solution on the Csound list

[ph_ne]

unfortunately not:

@ph_ne

EDIT: i tested csound --version in the vscode terminal and it shoes csound 6.18. i gues, i have to change this for vscode

EDIT: this was not the problem. i set in my .zshrc to the csound 7 executable, so that everytime i call csound --version also in the vscode terminal i get the csoun 7 version - but i did not help.

i do not know what to do else

[rorywalsh]

@ph_ne

EDIT: i tested csound --version in the vscode terminal and it shoes csound 6.18. i gues, i have to change this for vscode

This is the same for me. The system Csound is 6 on my machine. But Cabbage3 will always use Csound7 from teh Applications folder. Cabbage2 will use the system Csound. And teh exported plugins will also use the system Csound.

@ph_ne

EDIT: this was not the problem. i set in my .zshrc to the csound 7 executable, so that everytime i call csound --version also in the vscode terminal i get the csoun 7 version - but i did not help.

I think it should run csound6 from the terminal, not 7. If you want to play around with 7 do so from vscode as you won’t have to change any paths or anything. Just make sure you have the latest csound-vscode extension installed and bring up the command palette, then type Csound: Browse.. you’ll see the command appear. From there you can select whatever version of Csound you want to run. But you also need to run it using the vscode commands. The terminal will always run the system Csound.

[ph_ne]

Thank you for clarifying!

So, my problems, that the Cabbage GUI does not appear is not related to the running csound version.

What else can i check?

[rorywalsh]

Are you using the latest beta build for Cabbage 3? If so, try the following:

• Remove the settings.json file from your ~/Library/Application Support/Cabbage folder
• After installing the latest extension, open the extension settings and reset all path fields so they are empty. For example:
  
  
  
  This will force the extension to look in the default locations.
• Luanch the command palette, Cmd+Shift+P and choose select audio devices.
• Start the Cabbage server by clicking the Run Cabbage button:
  
• Use the command palette to open an example file - Cmd+Shift+P Cabbage:Open a widget example
• Hit save to launch the instrument.

If these steps don’t work, can you enble the verbose logging in the Cabbage settings and see if that provides any further information. If it doesn’t can you open the developer console in vscode

and see if that gives any useful info.

Let me know how it goes

[ph_ne]

@rorywalsh

Luanch the command palette, Cmd+Shift+P and choose select audio devices.

This is not an avaible option at my vscode.

[rorywalsh]

Sorry, those commands aare correct. Set your devices and launch. I’m going to be away from teh PC for the next few hours, but I’ll check in again later.

[ph_ne]

Also choosing in and out devices does not work. there is nothing happening there

[rorywalsh]

You’re not giving me much to go on here. What do the logs say?

[ph_ne]

Sorry! Here are my logs:

[rorywalsh]

Thanks @ph_ne, can you post the cabbage console output? When you start Cabbage you should get some text in the main vscode console. Can you post that too?

[ph_ne]

Cabbage extension is now active!
Found a find free port: 9991

This is what i get. Looks ok to me?

[rorywalsh]

And what does it print when you hit the run Cabbage button I mentioned earlier, seems to me like you might not be starting the Cabbge server. You need to start the server before running any instruments. It’s in the steps I outlined previously. Click the ‘Run Cabbage’ icon on the bottom right of the vscode window. Only after that can you start to run instruments.

[ph_ne]

Sorry, Rory. But i did do the steps you mentioned. I also reinstalled the csound extension forvscode - which runs at my system.

I did this process now again:

• deleted settings.json
• downloaded ‘https://github.com/rorywalsh/vscabbage/releases/tag/1.0.63-alpha’ and installed via ’ Install from VSIX’
• reset all path fields (which already was)
• selecting audio output or input devices does nothing at my system, should it prompt me avaible devices? But it gives me this ouput: Cabbage: extension path: /Users/philippneumann/.vscode/extensions/cabbageaudio.vscabbage-1.0.63-alpha
• starting the cabbage server gives me this:
  Updated permissions for Cabbage binary: /Users/philippneumann/.vscode/extensions/cabbageaudio.vscabbage-1.0.63-alpha/src/CabbageBinaries/CabbageApp Found a find free port: 9991
• hit save on an widget example just gives me the green/white/blues cabbage screen

[rorywalsh]

Did you enable verbose logging in teh Cabbage extension? When the Cabbage server starts, you should see something like this in the vscode console:

What’s also odd is that when you choose ‘Select Audio Output Device’ from the command palette, you should see a list of devices.

Can you copy and paste the contents of your settings.json file? I wonder if it is a permission issue with the settings.json file?

[ph_ne]

@rorywalsh

Did you enable verbose logging in teh Cabbage extension? When the Cabbage server starts, you should see something like this in the vscode console:

I did activate verbose logging:

When i Run cabbage, this is all i get:
Found a find free port: 9991

These are my settings.json:

    {
        "currentConfig": {
            "audio": {},
            "jsSourceDir": "/Users/philippneumann/.vscode/extensions/cabbageaudio.vscabbage-1.0.63-alpha/src",
            "midi": {}
        },
        "systemAudioMidiIOListing": {
            "audioDrivers": "",
            "audioInputDevices": {},
            "audioOutputDevices": {},
            "midiInputDevices": {},
            "midiOutputDevices": {}
        }
    }

@rorywalsh

I wonder if it is a permission issue with the settings.json file?

In response of this i did run:
chmod +x ...

but my settings.json do have:

[rorywalsh]

Hmm, this is strange. Your settings file looks like the dfefault one that is created when you install the Cabbage extension. The first time you start the Cabbage server it should populate that file with your audio devices. Do you see a popup notification that Cabbage has started when you start the Cabbage server? You should see one in the bottom right notification area.

Ok, can you try running the CabbageApp binary from the command line, i.e,

cd /Users/philippneumann/.vscode/extensions/cabbageaudio.vscabbage-1.0.63-alpha/src/CabbageBinaries
./CabbageApp

The output you see there should be the same you see when you start Cabbage from within vscode. Maybe the permissions issue is with the actual Cabbae binary?

[ph_ne]

zsh: bad CPU type in executable: ./CabbageApp - is Cabbage compiled only for M-Chips?