CamillaDSP 4?

[Bwaslo]

I'm looking at CamillaDSP in Ubuntu on a laptop PC, just to get familiar with the territory and ran across something odd (to me at least). I did the installation pretty sure for released version 3, but when when I do

>camilladsp --version​

in the terminal, I get this response: "CamillaDSP 4.0.0-draft".

I can't even find a reference for a version 4.0.0 with a web search. Anyone know what is going on?

 

[voodooless]

It seems you got this version:

GitHub - HEnquist/camilladsp at v4.0.0-preview.1

A flexible cross-platform IIR and FIR engine for crossovers, room correction etc. - GitHub - HEnquist/camilladsp at v4.0.0-preview.1

github.com

How did you install it?

 

[Bwaslo]

Thanks, apparently I did. Surprised that didn't show in my websearch.

I did a download of Camilla some months ago, but got distracted before doing much else. Maybe I managed to install that one by mistake.

 

[Bwaslo]

I got version 3.0.1 extracted and put where I can find it. Now, I'm trying to get the "websocket" stuff working so I can see the Camilla web based GUI, but not going well.

I start camilladsp with the command:

sudo camilladsp --port 8080 /home/bwaslo/camilladsp/stdio_inout.yml

that starts up, no error messages, should be accessible at http://127.0.0.1/ or at http://127.0.0.1:80,
...but trying that each time gives me the message:

"WARN [src/socketserver.rs:540] Connection failed: WebSocket protocol error: No "Connection: upgrade" header"

in the linux terminal, and in the browser (Firefox or Chromium) I see:

​

Can anyone give me any clues around this? The docs are pretty terse and jargony about the websocket thing.

 

[voodooless]

Try http://127.0.0.1:8080

 

[Bwaslo]

Try http://127.0.0.1:8080

Thanks. I sctually did that previously, same responses (sorry, I mistyped above, both the sudo camilladsp call and the web url were matched at ports 80, or at 8080, result was the same either way. They see each other but won't connect. Some kind of websocket error on one side or the other).

 

[voodooless]

For a web interface you’ll need a separate project;

GitHub - HEnquist/camillagui-backend: Backend server for camillagui

Backend server for camillagui. Contribute to HEnquist/camillagui-backend development by creating an account on GitHub.

github.com

 

[Bwaslo]

Downloaded that and extracted the file. But how is it used? Set it running before fireing up camilladsp?
"The easiest way to run the gui is to download and run one of the published bundles.". according to the readme.
Is not the websocket for the gui? If not, what is it?

 

[voodooless]

Is not the websocket for the gui? If not, what is it?

Yes it is. But the websocket is just a computer interface. You cannot directly use it in your browser. That’s where the gui comes in.

I think the documentation is pretty clear on how to set it up?

The order of starting doesn’t matter that much. Just make sure both run before you interact with the browser.

 

[3ll3d00d]

The websocket server is in the camilladsp process, the Camilladsp-backend is the websocket client in this context. The browser connects to the backend, the backend connects to cdsp itself.

 

[alfred_j_kwack]

No need for a separate GUI project.
Here, try this

• Go to : http://camillaeq.his.house/#/connect
• On the form, enter the IP address of your camillaDSP instance (or localhost) and 8080 for the control port. Leave the spectrum port blank.
• Click connect. If the connection succeeds but says degraded you're connected to your CamillaDSP. The amber/degraded bit is because of the spectrum part.
• Now on the left hand menu click on the icon that looks like a sliders (equalizer), or the one that looks like a link (pipeline editor)

If you want to know more, head over to : https://github.com/AlfredJKwack/camillaEQ

 

[AlfaNovember]

When I was building my CamillaDSP installation, I found it useful to validate the CamillaDSP websocket was properly up and running using a small tool called 'websocat' https://github.com/vi/websocat

the command itself is a one-liner run as a systemd one-shot service, which ensures that cdsp is listening on the proper port before the client services start. I'm using both camillagui and roon-extension-cdsp; either one can make a adjustment to the cdsp process via the websocket.

/bin/bash -c 'IP=$(ip route get 1.1.1.1 | awk "{print \$7}");echo "Waiting for WebSocket on $IP:1234..."; until echo | websocat ws://$IP:1234 >/dev/null 2>&1; do sleep 2; done; echo "WebSocket ready on $IP:1234"'

My notes to myself are here in case you find them useful: https://github.com/alfanovember/camilladsp_crossover_config