CamillaDSP - Cross-platform IIR and FIR engine for crossovers, room correction etc.

[bambadoo]

Thanks for this. Been trying lately getting Camilladsp to work on rpi3b+ and rpi4.
Have som questions and comments that will come

BTW: Running v1.0.0 alpha 5.
Easy upgrade to v1.0.0-rc1 ?

Best regards.

 

[TNT]

Love the subnormal number handling part - talk about attention to detail!

//

 

[xorcz]

I have sound drops with rc1, but I did not tested thoroughly and just reverted back from 1.0.0-rc1 to 1.0.0-alpha2, both from Releases.
The first start of rc1:
Jan 17 21:40:53 dsp camilladsp[711]: 2022-01-17 20:40:53.296420 INFO [src/bin.rs:711] CamillaDSP version 1.0.0-rc1
Jan 17 21:40:53 dsp camilladsp[711]: 2022-01-17 20:40:53.296510 INFO [src/bin.rs:712] Running on linux, aarch64
Jan 17 21:40:53 dsp camilladsp[711]: 2022-01-17 20:40:53.298039 #033[38;5;196mERROR#033[0m [src/bin.rs:777] Invalid config file!
Jan 17 21:40:53 dsp camilladsp[711]: devices: unknown field avoid_blocking_read, expected one of channels, device, format at line 2 column 16

Deleted the row avoid_blocking_read
Jan 17 21:42:30 dsp camilladsp[885]: 2022-01-17 20:42:30.893608 INFO [src/bin.rs:711] CamillaDSP version 1.0.0-rc1
Jan 17 21:42:30 dsp camilladsp[885]: 2022-01-17 20:42:30.893766 INFO [src/bin.rs:712] Running on linux, aarch64
Jan 17 21:42:30 dsp camilladsp[885]: 2022-01-17 20:42:30.897960 #033[38;5;196mERROR#033[0m [src/bin.rs:777] Invalid config file!
Jan 17 21:42:30 dsp camilladsp[885]: devices: unknown field retry_on_error, expected one of channels, device, format at line 2 column 16

Deleted the row retry_on_error
Jan 17 21:47:09 dsp camilladsp[1091]: 2022-01-17 20:47:09.895032 INFO [src/bin.rs:711] CamillaDSP version 1.0.0-rc1
Jan 17 21:47:09 dsp camilladsp[1091]: 2022-01-17 20:47:09.895206 INFO [src/bin.rs:712] Running on linux, aarch64
Jan 17 21:47:09 dsp camilladsp[1091]: 2022-01-17 20:47:09.931796 INFO [src/alsadevice.rs:547] Capture device supports rate adjust
Jan 17 21:47:10 dsp camilladsp[1091]: 2022-01-17 20:47:10.024067 #033[38;5;208mWARN#033[0m [src/alsadevice.rs:228] Wait timed out, capture device takes too long to capture frames
Jan 17 21:47:10 dsp camilladsp[1091]: 2022-01-17 20:47:10.991456 INFO [src/alsadevice.rs:155] Starting playback from Prepared state
Jan 17 21:47:24 dsp camilladsp[1091]: 2022-01-17 20:47:24.378168 #033[38;5;208mWARN#033[0m [src/alsadevice.rs:228] Wait timed out, capture device takes too long to capture frames
Jan 17 21:47:25 dsp camilladsp[1091]: 2022-01-17 20:47:25.318226 #033[38;5;208mWARN#033[0m [src/alsadevice.rs:151] Prepare playback after buffer underrun
Jan 17 21:47:38 dsp camilladsp[1091]: 2022-01-17 20:47:38.739042 #033[38;5;208mWARN#033[0m [src/alsadevice.rs:228] Wait timed out, capture device takes too long to capture frames
Jan 17 21:47:39 dsp camilladsp[1091]: 2022-01-17 20:47:39.679618 #033[38;5;208mWARN#033[0m [src/alsadevice.rs:151] Prepare playback after buffer underrun
Jan 17 21:47:53 dsp camilladsp[1091]: 2022-01-17 20:47:53.106975 #033[38;5;208mWARN#033[0m [src/alsadevice.rs:228] Wait timed out, capture device takes too long to capture frames
Jan 17 21:47:54 dsp camilladsp[1091]: 2022-01-17 20:47:54.047702 #033[38;5;208mWARN#033[0m [src/alsadevice.rs:151] Prepare playback after buffer underrun
Jan 17 21:48:12 dsp camilladsp[1091]: 2022-01-17 20:48:12.215147 #033[38;5;208mWARN#033[0m [src/alsadevice.rs:228] Wait timed out, capture device takes too long to capture frames
Jan 17 21:48:12 dsp camilladsp[1091]: 2022-01-17 20:48:12.526697 #033[38;5;208mWARN#033[0m [src/alsadevice.rs:151] Prepare playback after buffer underrun
Jan 17 21:48:36 dsp camilladsp[1091]: 2022-01-17 20:48:36.152452 #033[38;5;208mWARN#033[0m [src/alsadevice.rs:228] Wait timed out, capture device takes too long to capture frames

There were drops in the sound.

Back with 1.0.0-alpha2, very happy, no drops. I am using it daily, never had crackling or drops.
Jan 17 21:48:44 dsp systemd[1]: Started CamillaDSP Daemon.
Jan 17 21:48:44 dsp camilladsp[1117]: 2022-01-17 20:48:44.115429 INFO [src/alsadevice.rs:518] Capture device supports rate adjust
Jan 17 21:48:44 dsp camilladsp[1117]: 2022-01-17 20:48:44.195449 INFO [src/alsadevice.rs:123] Starting playback from Prepared state

Current config: https://pastebin.com/hzy0iKct

Running on the CM4 as USB Gadget device.

 

[HenrikEnquist]

@xorcz Could you try modifying the code a little and compile a test version yourself? If yes, could you try increasing the factor 2 here to 4?
https://github.com/HEnquist/camilladsp/blob/next100/src/alsadevice.rs#L223
That will make it wait longer before giving up, I think this has a good chance of solving it.

 

[phofman]

I am looking into the issues of using the nonblocking alsa CDSP with the gadget. I am receiving similar timeouts. Hopefully will analyze the details and fix it in a few days...

 

[HenrikEnquist]

I haven't noticed any such problems on my Pi4, weird. I'll set it up and do some more listening with it. Do you get the dropouts all the time, or only sometimes?

 

[HenrikEnquist]

Ok I have my pi hooked up and camilladsp playing music that it captures from the gadget. No problems at all! I'm running a custom kernel (5.14-rc5 with phofmans feedback patches), maybe makes a difference?

 

[bambadoo]

Tried to ask a question a couple of posts ago
Its has probably been said before but what is the easiest way of upgrading from one version of camilladsp to another?
lets say from 1.0.0 alpha to rc?

Using rpi3b+ for this one.

 

[HenrikEnquist]

Tried to ask a question a couple of posts ago
Its has probably been said before but what is the easiest way of upgrading from one version of camilladsp to another?
lets say from 1.0.0 alpha to rc?

Using rpi3b+ for this one.

Sorry missed this one! There aren't any big changes. Just replace the binary. And if your config has the "retry_on_error" or "avoid_blocking_read" properties then remove them.

 

[beneix]

Ok I have my pi hooked up and camilladsp playing music that it captures from the gadget. No problems at all! I'm running a custom kernel (5.14-rc5 with phofmans feedback patches), maybe makes a difference?

For what situation is that custom kernel required?

 

[bambadoo]

Sorry missed this one! There aren't any big changes. Just replace the binary. And if your config has the "retry_on_error" or "avoid_blocking_read" properties then remove them.

Thanks will try. Last time I replaced the binary. Restarted camilladsp and only got errors. Had to revert.
The GUI also said it was the former version.

BR

 

[bambadoo]

Did not work for me unfortunately.

pi@kjellern:~ $ sudo service camilladsp status


● camilladsp.service


Loaded: loaded (/lib/systemd/system/camilladsp.service; enabled; vendor preset: enabled)


Active: activating (auto-restart) (Result: exit-code) since Wed 2022-01-19 10:29:42 CET; 157ms ago


Process: 813 ExecStart=/home/pi/camilladsp/camilladsp -p 1234 /home/pi/camilladsp/configs/camilladsp.yml (code=exited, status=101)


Main PID: 813 (code=exited, status=101)


CPU: 25ms





Jan 19 10:29:52 kjellern camilladsp[838]: devices: unknown field avoid_blocking_read, expected one of channels, device, format at line 2 column 16


Jan 19 10:29:51 kjellern systemd[1]: camilladsp.service: Main process exited, code=exited, status=101/n/a


Jan 19 10:29:52 kjellern camilladsp[841]: 2022-01-19 09:29:52.247093 INFO [src/bin.rs:711] CamillaDSP version 1.0.0-rc1


Jan 19 10:29:52 kjellern camilladsp[841]: 2022-01-19 09:29:52.247386 INFO [src/bin.rs:712] Running on linux, aarch64


Jan 19 10:29:52 kjellern camilladsp[841]: 2022-01-19 09:29:52.249303 ERROR [src/bin.rs:777] Invalid config file!


Jan 19 10:29:52 kjellern camilladsp[841]: devices: unknown field avoid_blocking_read, expected one of channels, device, format at line 2 column 16


Jan 19 10:29:51 kjellern systemd[1]: camilladsp.service: Failed with result 'exit-code'.


Jan 19 10:29:52 kjellern systemd[1]: camilladsp.service: Scheduled restart job, restart counter is at 82.


Jan 19 10:29:52 kjellern systemd[1]: Stopped camilladsp.service.


Jan 19 10:29:52 kjellern systemd[1]: Started camilladsp.service.


Jan 19 10:29:52 kjellern systemd[1]: camilladsp.service: Main process exited, code=exited, status=101/n/a


Jan 19 10:29:52 kjellern systemd[1]: camilladsp.service: Failed with result 'exit-code'.


Jan 19 10:29:53 kjellern systemd[1]: camilladsp.service: Scheduled restart job, restart counter is at 83.


Jan 19 10:29:53 kjellern systemd[1]: Stopped camilladsp.service.


Jan 19 10:29:53 kjellern systemd[1]: Started camilladsp.service.


Jan 19 10:29:53 kjellern camilladsp[844]: 2022-01-19 09:29:53.499532 INFO [src/bin.rs:711] CamillaDSP version 1.0.0-rc1


Jan 19 10:29:53 kjellern camilladsp[844]: 2022-01-19 09:29:53.499797 INFO [src/bin.rs:712] Running on linux, aarch64


Jan 19 10:29:53 kjellern camilladsp[844]: 2022-01-19 09:29:53.501826 ERROR [src/bin.rs:777] Invalid config file!


Jan 19 10:29:53 kjellern camilladsp[844]: devices: unknown field avoid_blocking_read, expected one of channels, device, format at line 2 column 16


Jan 19 10:29:53 kjellern systemd[1]: camilladsp.service: Main process exited, code=exited, status=101/n/a


Jan 19 10:29:53 kjellern systemd[1]: camilladsp.service: Failed with result 'exit-code'.

 

[HenrikEnquist]

Your config has "avoid_blocking_read" (and probably "retry_on_error" too). Edit the file to remove them!
I you use rc1 with the released version of the gui there will be some issues since that one also puts those properties into the config. When I make the final 1.0.0 release I'll also publish a matching gui.

 

[HenrikEnquist]

For what situation is that custom kernel required?

It was required to play around with the usb gadget improvements before they were included in a stable kernel. I think they are included in the latest now, but better to ask @phofman

 

[bambadoo]

Sorry, did not catch "remove" quite. Just disabled with GUI and that was not enough
Working now with some minor issues like you said. Thanks.

 

[HenrikEnquist]

Manjaro (unstable) on the Pi with mainline kernel 5.16 seems to work just fine. I've been listening to glitch-free music for an hour now. I play music on a linux laptop, via the gadget and camilladsp on the pi, to a usb dac.
@phofman and @xorcz what software versions are you running?

 

[phofman]

Henrik, I am working on the non-blocking patches, I will send them to you hopefully today. In my case the glitches are combination of target_level and initial buffer fill which yields large changes in speed param. IMO no problem in next100 branch.

 

[mdsimon2]

I have been listening to RC1 on my RPi4 + Ubuntu Server 21.10 64 bit (5.13 kernel) + MOTU Ultralite Mk5 today with no issues.

Michael

 

[HenrikEnquist]

I know what causes the problems for @xorcz ! Big thanks to @phofman for figuring out there is an important missing piece in the non-blocking alsa code (and for contributing a fix)
There will be an rc2 very soon that fixes this.

 

[henrikbremerskov]

I have a couple of questions about CamillaDSP. Sorry if these have been covered in this thread already.

1. ROUTING
From the online docs I get the idea that the available routing consists of input > splitting/copying/adding channels > processing the channels > output. Depicted graphically, that might look something like this:

I couldn't quite figure out how a "branching" filter tree could be created, e.g. one like this:

Can the branching filter tree be created in CamillaDSP and if so, how?


2. DELAY:
I see there is delay functionality. Does this implement "fractional delay" and is able to produce any arbitrary amount of delay (up to some upper limit), or only delay in increments of one sample period (e.g., increments in time of 1/sample_rate)?

It's been a long time since I looked at the software, but after a read through today I am really impressed. Too many features to not give it a try! Great work Henrik, you have really been working hard on this.

Hi CharlieLaub
can you possibly point me to some literature that describes the benefits of branching filter ?

Best regards
Henrik