Cabbage Logo
Back to Cabbage Site

Cabbage 3 server terminated when starting

#1

I’m having some problems running .csd files with the newest version of vscabbage: 1.0.93-alpha on windows 10.

Happens with all files (existing or new ones created from commands) :thinking:

image
image1386×908 68.7 KB

#2

Ah, you’re right in the middle of another overhaul. I’m dropping the websocket server in favour of pipes which will allow windows users to run this extension without having to give network permissions. Only I started the rewrite on my Mac and haven’t got around to checking it works on windows yet. I will do tomorrow, if you can just hold out another day…

#3

Alright :+1:

#4

Do you have better luck with this one?


You shouldn’t be seeing any messages regarding free ports, if you are, I suspect it’s not running the latest version. Maybe you need to nuke the package and then try installing again? I’ll let you know tomorrow how I get on, I’ll hopefully have a working package again soon for windows.

#5

Uninstalled the extension and installed the one you sent, still getting a similar error, but it’s printing something else for sure

image
image1381×725 33.9 KB

#6

Ah Ok, I’ve just landed in the world of Windows. Let me start debugging.

p.s. how do you like my ASCII Cabbage :rofl:

#7

I saw the big Cabbage text and I immediately felt like some sort of hacker out of a movie :rofl:

#8

Excellent, it had the desired effect then :rofl:

1 Like
#9

I have found and fixed the problem. I’m just triggering a new build now. :+1:

#10

So now I can both run and export plugins, but when loading the plugin (in this case an effect) in a DAW, the DOM-tree is empty.

image
image1736×855 44 KB

The channels defined in the Cabbage-section however exist when I dug a little deeper.

image
image1416×1025 48.2 KB

#11

Thanks @hdale94, I need to test these latest changes in a DAW :+1:

#12

Should be good to go now @hdale94 New build underway.

#13

Still getting the same with the newest version 1.0.102-alpha. No UI in a DAW, but the files seem correctly exported :thinking:

image
image1116×209 18.5 KB

#14

I’m seeing this awsell. But of course my local build behaves just fine :roll_eyes: I’ll take a look.

#15

Oh wait, i think I know what happened here. I did some refactoring yesterday evening that I didn’t test in the plugin build… testing it now…

#16

No, that’s not the problem. I’m stumped on this one. It was working fine on my work PC when I left yesterday, but here at home I’m seeing the same issues as you. It looks like the index.html isn’t loading :thinking:

#17

I’m going to have to wait till Monday to get this one solved. My PC at home just isn’t up to scratch. :frowning:

1 Like
#18

That was quite a trip. It looks like some kind of update to the edge framework on Windows suddenly caused things to break. I have identified the problem and a solution, but I have yet to implement it. I’ll let you know. Sorry about this, this stuff is outside my control.

#19

Alright, keep me updated :+1:

#20

Ok, this i fixed, but I’ve no yet pushed a new build. There is something I would like to update with regards to the Cabbage JSON. I’m going to remove the range object, and inline it with the channel object. So what would previously look like this:

{
    "type": "rotarySlider", 
    "bounds": {"left": 20.0, "top": 20.0, "width": 80.0, "height": 80.0}, 
    "channel": "harmonic1", 
    "range": {"min": 0.0, "max": 1.0, "value": 0.0, "skew": 1.0, "increment": 0.001}
},

will now look like this:

"channel":{
    "harmonic1":{
        "min": 0.0, "max": 1.0, "value": 0.0, "skew": 1.0, "increment": 0.001
    }
}

This ellimates the range object, and means I no longer longer have to iterate over the channel object, an then sync to the range object. In single channel widgets this isn’t a big deal, but it gets a little messy with widgets that have multiple channels, like an xypad for example. Or an image in which you want to send mouse coordinates, and button press events.