• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

RPi + CamillaDSP Tutorial

mdsimon2 said:
You are using a pretty big target level (4 x chunk size), which would not have been possible with V2 which had a max target level of 2 x chunk size - 1. I'd try reverting back to your V2 target level and see if that solves it.
Click to expand...
Setting the target_level to be 2 x chunk size gave me an error, 8192 and 4096 respectively. I now have the target_level set to default and it is working well for me.
 
terryforsythe said:
Setting the target_level to be 2 x chunk size gave me an error, 8192 and 4096 respectively. I now have the target_level set to default and it is working well for me.
Click to expand...
My rpi is 4
With cdsp v2 I had 8192/8192.
2048 chunk size / 6144 target level seems to work.
Here it's night time, I'll listen tomorrow and report the result.
Thanks for the help.
 
HenrikEnquist said:
This would indicate that the problem is on the playback side. If you have time, I would appreciate a debug log!
Click to expand...
It happened again. I had it paused for several minutes (maybe 10?) and when I came back (at 11:48 just before 11:48:30) there was no sound. I checked the log around that time but didn't really see anything so I'm attaching a log going back almost 20 mins.

cdsp debug.txt

drive.google.com drive.google.com
 
mdsimon2 said:
Which RPi are you using?

You are using a pretty big target level (4 x chunk size), which would not have been possible with V2 which had a max target level of 2 x chunk size - 1. I'd try reverting back to your V2 target level and see if that solves it.

If it doesn't I'd try moving to 2048 chunk size / 6144 target level. I don't have a DM7 so I can't directly test your configuration but I can try a similar ALSA loopback configuration at 192 kHz and see how it does.

Michael
Click to expand...
Hello,
I use an rpi4 and the uses are mainly Stream from squeezelite and tv sound with a HIFIME S2 Digi.
For the stream 2048/6144 seems to do the trick, but I reused 4096/4096 as my v2 settings. No more clipping.
For TV, I used 256/768 (256/511 in v2), and there's no sound cutoff.
But there are still alerts:
2025-02-18 13:46:58.683022 WARN [src/alsadevice.rs:122] PB: device is in an unexpected state: SND_PCM_STATE_PAUSED, Paused

They appear when I change channels on the TV, they didn't appear in v2.

I enclose the camilladsp.log and the beginning of my configuration file HIFIME.
Any suggestions are welcome.
 

Attachments

AbacusLX said:
But there are still alerts:
2025-02-18 13:46:58.683022 WARN [src/alsadevice.rs:122] PB: device is in an unexpected state: SND_PCM_STATE_PAUSED, Paused

They appear when I change channels on the TV, they didn't appear in v2.
Click to expand...

It could be that v3 has additional log notifications. I don't think it is anything to worry about. When you change the channel audio is interupted for a moment, so there is nothing to process. I just tested my system. I got the same warning when I manually changed the song.
 
glc650 said:
It happened again. I had it paused for several minutes (maybe 10?) and when I came back (at 11:48 just before 11:48:30) there was no sound. I checked the log around that time but didn't really see anything so I'm attaching a log going back almost 20 mins.

cdsp debug.txt

drive.google.com drive.google.com
Click to expand...
Thanks for the log! It looks like the playback device ends up stuck in the paused state. I have a dac8x, will try this as soon as I have time to set it up.
 
S.M.S.L. PO100 2024: a cost effective 2-channel digital output device that works with CamillaDSP

I just received a S.M.S.L. PO100 2024 to test it for use with my Raspberry Pi and CamillaDSP. It is a 2-channel digital output device with a USB input and SPDIF coax and optical outputs. I got it off of Amazon for $40.

I hooked it up to my Raspberry Pi and ALSA recognized it without issue. AlsaMixer indicates that it does not have any controls, though. So far that does not appear to be an issue. The only configuration change I made was changing the playback device to "hw:AUDIO,0,0" in CamillaDSP. Notably, there was no need to flash firmware to the PO100, which my miniDSP MCHStreamer kit required before I could use it in my setup.

The PO100 is very picky about the USB cable, however. The USB-A to USB-C cable that came with it works fine, and it also comes with a USB-C to USB-C cable. But, I tried two different shorter USB-A to USB-C cables that I have, and neither worked. I found that a little frustrating since I am trying to control the cable clutter.

My original digital I/O device is the MCHStreamer kit. I got that because it has both SPDIF input and SPDIF output. Tidal changing samplerates with song changes created issues with CamillaDSP, though, and SPDIF input does not work with camilladsp-setrate. So, a while back I changed my streamer to the WiiM Ultra to connect to my Raspberry Pi via USB, and that solved my problem. Now I no longer need SPDIF input, and the PO100 is much smaller and looks nicer than the case I 3D printed for my MCHStreamer kit.

The PO100 has very low jitter: https://audiosciencereview.com/foru...ak-measurements-digital-interfaces-dac.40483/. I do not know what is the jitter for the MCHStreamer, and I have not performed a blind comparison of the PO100 to the MCHStreamer. Nonetheless, I do not hear an audible difference between the two, nor would I expect to.

In sum, the S.M.S.L. PO100 2024 is a cost effective 2-channel digital output option for use with CamillaDSP. For those needing more channels there is the S.M.S.L. PO100 Pro, which is $70 on Amazon.

I will continue using the PO100 and provide updates if I run into any issues.
 
terryforsythe said:
The PO100 is very picky about the USB cable, however. The USB-A to USB-C cable that came with it works fine, and it also comes with a USB-C to USB-C cable. But, I tried two different shorter USB-A to USB-C cables that I have, and neither worked. I found that a little frustrating since I am trying to control the cable clutter.
Click to expand...

Today I received a new 1ft. USB-A to USB-C cable from Amazon. It works great with the PO100.
 
I have been experimenting with HifiberryOS DSP on an RPi 3b+ with a DAC+DSP hat but HifiberryOS is one of the buggiest things I've come across, so I want to try something else. Would it be possible to run CamillaDSP on a 3B+ for PEQ/room correction using REW or Housecurve measurements and filters? Or would that be too much and should I look elsewhere? My aim is to simple input to the Hifiberry via Toslink, perform DSP and then output to my amp via either Toslink or RCA.
 
ErikRM said:
Would it be possible to run CamillaDSP on a 3B+ for PEQ/room correction using REW or Housecurve measurements and filters?
Click to expand...
Yes.

I use REW to make measurements and add PEQs in CamillaDSP. It works great. Also, REW will output filters in the format required for CamillaDSP, so you can just copy and paste.

I also generated FIR files in REW, and used those in CamillaDSP. That also works. But, I need to fine tune my FIR file generation skills; I was getting a little bit of ringing. I may experiment with it further at some point.
 
terryforsythe said:
Yes.

I use REW to make measurements and add PEQs in CamillaDSP. It works great. Also, REW will output filters in the format required for CamillaDSP, so you can just copy and paste.

I also generated FIR files in REW, and used those in CamillaDSP. That also works. But, I need to fine tune my FIR file generation skills; I was getting a little bit of ringing. I may experiment with it further at some point.
Click to expand...

Great, thanks! I was wondering about this as the thread and GitHub instructions only mention the Rpi 4 and 5 but it's good to hear that my hardware is suitable too.
 
ErikRM said:
Great, thanks! I was wondering about this as the thread and GitHub instructions only mention the Rpi 4 and 5 but it's good to hear that my hardware is suitable too.
Click to expand...
github.com

GitHub - HEnquist/camilladsp: A flexible cross-platform IIR and FIR engine for crossovers, room correction etc.

A flexible cross-platform IIR and FIR engine for crossovers, room correction etc. - HEnquist/camilladsp
github.com github.com

Make sure you select the correct version for your Pi. The installation may be different than for the RPi 4 and 5.
 
I've followed the guide on GitHub but can't get access to CamillaDSP. I've gone through steps 1-6 but cannot access CamillaDSP either through hostname:5005 or 192.168.xxx.xxx:5005. When I use "sudo service camilladsp" and "sudo service camillagui" both give me the response "unrecognized service"

Any ideas on what I'm doing wrong? My Rpi is a 3B+ with RaspberryPi OS.
 
ErikRM said:
I've followed the guide on GitHub but can't get access to CamillaDSP. I've gone through steps 1-6 but cannot access CamillaDSP either through hostname:5005 or 192.168.xxx.xxx:5005. When I use "sudo service camilladsp" and "sudo service camillagui" both give me the response "unrecognized service"

Any ideas on what I'm doing wrong? My Rpi is a 3B+ with RaspberryPi OS.
Click to expand...

What do you see when you run "service camilladsp status" and "service camillagui status"?

Michael
 
mdsimon2 said:
What do you see when you run "service camilladsp status" and "service camillagui status"?

Michael
Click to expand...
× camillagui.service - CamillaDSP Backend and GUI
Loaded: loaded (/lib/systemd/system/camillagui.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Thu 2025-02-27 15:34:34 CET; 35min ago
Duration: 12ms
Process: 24195 ExecStart=/home/username/camilladsp/camillagui_backend/camillagui_backend (code=exited, status=203/E>
Main PID: 24195 (code=exited, status=203/EXEC)
CPU: 6ms

Feb 27 15:34:34 raspberrypi systemd[1]: Started camillagui.service - CamillaDSP Backend and GUI.
Feb 27 15:34:34 raspberrypi (_backend)[24195]: camillagui.service: Failed to locate executable /home/username/camillads>
Feb 27 15:34:34 raspberrypi (_backend)[24195]: camillagui.service: Failed at step EXEC spawning /home/username/camillad>
Feb 27 15:34:34 raspberrypi systemd[1]: camillagui.service: Main process exited, code=exited, status=203/EXEC
Feb 27 15:34:34 raspberrypi systemd[1]: camillagui.service: Failed with result 'exit-code'.

And

● camilladsp.service - CamillaDSP
Loaded: loaded (/lib/systemd/system/camilladsp.service; enabled; preset: enabled)
Active: active (running) since Thu 2025-02-27 14:01:20 CET; 2h 10min ago
Main PID: 973 (camilladsp)
Tasks: 6 (limit: 755)
CPU: 1.143s
CGroup: /system.slice/camilladsp.service
└─973 camilladsp -s camilladsp/statefile.yml -w -g-40 -o camilladsp/camilladsp.log -p 1234

Feb 27 14:01:20 raspberrypi systemd[1]: Started camilladsp.service - CamillaDSP.
 
You must log in or register to reply here.

Similar threads

G
RPi5 + CamillaDSP help needed
Replies
16
Views
2K
mdsimon2
M
Back
Top Bottom