• WANTED: Happy members who like to discuss audio and other topics related to our interest. Desire to learn and share knowledge of science required. 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

I'm having issues importing my v2 configs. It says import is successful but the config is full of errors and says invalid.

1.jpg


2.jpg
 
mdsimon2 said:
I'd recommend switching, see here for some more info on virtual environments -> https://henquist.github.io/pycamilladsp/install/. Short story is installing the CamillaDSP python libraries the old way could corrupt the system python installation, this is why we've needed to use "--break-system-packages" to install them. If you want to uninstall the old camilladsp python libraries you can do so by running "sudo pip3 uninstall camilladsp camilladsp-plot --break-system-packages".

I also just updated the tutorial to move the installation of the virtual environment and CamillaDSP python libraries in to the GUI step. This makes it more clear what you exactly need to run to install the virtual environment and libraries.
Click to expand...
Well, I did the suggested uninstall of the old camilladsp python libraries and attempted to re-install, but that didn't go well so I ended up doing the install from scratch.
 
mdsimon2 said:
piCorePlayer is structured differently from most linux distros, certainly very different from the debian based distros like Ubuntu and Raspberry Pi OS that I am somewhat familiar with. There is another project devoted to installing CamillaDSP on piCorePlayer, I recommend you follow that -> https://github.com/JWahle/piCoreCDSP.
Click to expand...
Thanks. I'd completely forgotten about that project! Last night I spent some time trying to get it working but had many issues with alsa and the alsa_cdsp plugin not playing nice with CamillaDSP. I reimaged and started again twice and still couldn't get it working, even when I didn't use the alsa_cdsp plugin and used the alsa loopback method instead. This particular Raspberry Pi 3b is using the vc4hdmi driver to output audio via the HDMI port to an AVR, so I suspect it's something to do with the vc4hdmi driver. Unfortunately, I can't do much about the driver because it's required to output 24-bit audio over HDMI. I'm now reconsidering using piCorePlayer for running CamillaDSP.

mdsimon2 said:
For me, Raspberry OS Lite is stable, relatively light and has tons of documentation which makes it ideal. When I first started this tutorial I used Ubuntu Server because it had a newer kernel which was needed to use various MOTU interfaces, however it was always significantly slower than Raspberry Pi OS Lite. This is very obvious when using the OLED screen or observing restart times. Now that Raspberry Pi OS Lite uses a modern kernel I do not see a reason to use Ubuntu Server.
Click to expand...
I did something similar for the newer kernel on a Pi4, but used Debian instead. I've been meaning to replace Debian with piCorePlayer, but I may have to reconsider that plan now :D
 
So I've been running CDSP v3 for a few days now and the only issue I've come across is when I leave my TV input paused for too long (at least several minutes) and then hit play there is no audio. The only way to get audio back is to reload the config in the CDSP GUI, use my remote to cycle through my CDSP configs until I get back to the one I was just on or use pyCamillaDSP to execute a reload command.
 
Blew said:
Has anyone tried using the new Fosi VOL20 volume control knob to control volume on CamillaDSP on a Raspberry Pi via Bluetooth?
fosiaudio.com

Fosi Audio VOL20 Bluetooth Volume Control Knob

Multimedia Volume Knob: The VOL20 is a versatile desktop volume controller with Bluetooth wireless and USB-C connectivity, offering real-time volume adjustments. Perfect for music lovers, gamers, and professionals who demand precise volume controlMulti-Functional: Simple yet versatile, the...
fosiaudio.com fosiaudio.com
Click to expand...

I assume there still needs to be some kind of process running in daemon mode that translates the VOL20 actions to CamillaDSP or LMS remote calls.
 
Hi Michael,
Thanks for the new V3 write up, worked perfectly!
One question about labels. For the capture device it is obvious where to enter them.
For the (8) channels of the playback device, I cannot find where to enter them.
There is no option for it in the GUI under capture device, nor in the mixer tab.
So I tried adding them to my config:
playback:
channels: 8
device: hw:CARD=D20,DEV=0
format: S32LE
type: Alsa
labels:
- Tw L
- Tw R
- Mid L
- Mid R
- Wf L
- Wf R
- Sub L
- Sub R

but this gave an error that labels are unexpected an the config won't load.
Where can I put the labels?

Edit: found the answer on H Enquist's site: they must be given in the mixers section. This works:
mixers:
2x8:
channels:
in: 2
out: 8
description: null
labels: ["Tw L", "Tw R", "Mid L", "Mid R", "Wf L", "Wf R", "Sub L", "Sub R"]
 
Last edited:
meooms said:
Hi Michael,
Thanks for the new V3 write up, worked perfectly!
One question about labels. For the capture device it is obvious where to enter them.
For the (8) channels of the playback device, I cannot find where to enter them.
There is no option for it in the GUI under capture device, nor in the mixer tab.
So I tried adding them to my config:
playback:
channels: 8
device: hw:CARD=D20,DEV=0
format: S32LE
type: Alsa
labels:
- Tw L
- Tw R
- Mid L
- Mid R
- Wf L
- Wf R
- Sub L
- Sub R

but this gave an error that labels are unexpected an the config won't load.
Where can I put the labels?

Edit: found the answer on H Enquist's site: they must be given in the mixers section. This works:
mixers:
2x8:
channels:
in: 2
out: 8
description: null
labels: ["Tw L", "Tw R", "Mid L", "Mid R", "Wf L", "Wf R", "Sub L", "Sub R"]
Click to expand...

Glad to hear you got it worked out. There should be a labels option in the Mixer tab of the GUI, do you not see something similar?

1738591604159.png


Michael
 
glc650 said:
Toslink via Hifime S2 Digi.
Click to expand...

I'll try playing with this today. I've noticed some of the pause / unpause behavior is different on V3, devices that previously would never do so end up in the stalled state. It wouldn't surprise me if this means that some devices get tripped when coming out of the stalled state.

I assume you were using the S2 Digi successfully with your TV prior to V3?

Michael
 
mdsimon2 said:
Glad to hear you got it worked out. There should be a labels option in the Mixer tab of the GUI, do you not see something similar?

View attachment 425805

Michael
Click to expand...

Yes I did see that, but it only gave me options for 2 channels. So I gathered these must be the input channels.
Even now, with 8 output channels labelled in yaml, it only gives me the option for naming 2 channels.
The complete label is ok, just like you show, but the drop-down menu still has 2 options only, with Tw L and Tw R filled in now.
These are my first 2 output channels.
 
meooms said:
Yes I did see that, but it only gave me options for 2 channels. So I gathered these must be the input channels.
Even now, with 8 output channels labelled in yaml, it only gives me the option for naming 2 channels.
The complete label is ok, just like you show, but the drop-down menu still has 2 options only, with Tw L and Tw R filled in now.
These are my first 2 output channels.
Click to expand...

Ah, yes, I forgot about that, it is confusing. It will only give a drop down for two playback channels, but you can enter more channels by just typing them out and separating them with commas as shown in my screenshot.

Michael
 
mdsimon2 said:
, it is confusing. It will only give a drop down for two playback channels, but you can enter more channels by just typing them out
Click to expand...
I'm aware of this, will fix in the next gui version.
 
I tried using the S2 Digi all day in a V3 configuration with the MOTU UL Mk5 as playback device, source was an Apple TV 3.

It worked great, would go in and of pause without issue. I could leave it in pause for hours and it would come out of it fine.

I also tried unplugging the power cord for Apple TV to see if that would trip it up, unplugging would cause the configuration to go in to the stalled state but it would resume without issue if plugged back in. I also tried leaving it unplugged for an hour and it still came out of stalled.

Of course this is just one source and it is certainly possible other sources have some issues with the S2 Digi / CamillaDSP.

Michael
 
mdsimon2 said:
I assume you were using the S2 Digi successfully with your TV prior to V3?
Click to expand...
Yes and nothing else changed. It also doesn't happen every time (I'd say at least 50% of the time though) and it never happened with v2.

mdsimon2 said:
I tried using the S2 Digi all day in a V3 configuration with the MOTU UL Mk5 as playback device, source was an Apple TV 3.

It worked great, would go in and of pause without issue. I could leave it in pause for hours and it would come out of it fine.
Click to expand...
Interesting. I'm using a FireTV 4k Max. I only use a few apps on it (and so far I've only used a couple of those with v3) but so far I've had the issue with Kodi and Netflix.
 
You must log in or register to reply here.

Similar threads

I
pi_player: an application that extends the use of camilladsp to a fully functional preamp/streamer
Replies
7
Views
2K
Frunse
F
IAtaman
Using OrangePi Zero2 as an equalizer between USB source and USB DAC
2
Replies
22
Views
7K
10PSPMemSticksForMiku2007
10PSPMemSticksForMiku2007
Back
Top Bottom