In my case, yes, for two sources. One is roonbridge (at 192kHz S32LE into Loopback 0), the other spotifyd (at 44.1kHz S16LE into Loopback 1), both running on my RPi4. My third source (the RME ADI-2 FS Pro itself) doesn't use alsaloop. The pop only seems to arise intemittently when switching to spotifyd, and never when switching away from spotifyd.
I've just remembered that I used to use Loopback 1 for a second roonbridge output, also running at 192kHz S32LE, and never encountered any pops switching between the two roonbridge source/configurations.
Last edited:
I don't know if it will be enough of a fix, but recent versions of librespot support S32LE output, unlike spotifyd. Still limited to 44.1 kHz though.
Edit: also how have you hooked up dmix / plug?
Edit: also how have you hooked up dmix / plug?
Last edited:
If I'm missing something really simple, I'd love to know! I'm running CDSP on a headless RPi4 to which I stream in two ways:
- Spotify client sends Spotify Connect instruction to spotifyd on RPi4 > alsaloop > CDSP > external soundcard
- Roon Core > Roon Bridge > alsaloop > CDSP > external soundcard
Similarly, Roon's Core streams from my home server to a network device that the Roon Core recognises as compatible. On my RPi4 I have Roon Bridge running, which the Roon Core recognises. Roon Bridge offers the Core all the hardware devices it can detect locally (my external soundcard, the two virtual alsaloop cards and the RPi4's headphone output) so again I need to insert alsaloop between Roon Bridge and my external soundcard to loop the stream through CDSP.
I also have a third source which doesn't involve alsaloop at all since CDSP connects to the hardware directly:
- CD > external card > CDSP > external card
I see. By alsaloop you mean the loopback device, snd-aloop. Alsaloop is https://linux.die.net/man/1/alsaloop which some people use in their chains too.
I'm using alsaloop only to support analogue in on my PI from my TV.
TV (RCA) -> 5.1 soundcard (USB) -> (hw:2,0) Alsaloop (hw:Loopback,0) -> CamillaDSP (HDMI) -> Suptronics X6000 DAC
I don't have any USB based option nor SPDIF input on the Pi to be able to listen to TV through the speakers.
Having explained that back to you... I don't know why I don't capture directly from hw:2 and just switch the capture sources in CamillaDSP when it comes to sourcing from MPD.
Every device in the chain increases latency as it unavoidably introduces more buffers. Latency may be an important criterium when watching a TV.
There is a readme specifically for Windows here: https://github.com/HEnquist/camilladsp/blob/master/backend_wasapi.md
I suppose you already looked there. Where are you stuck, and what are you trying to do? Just run the dsp, or also the gui?
@HenrikEnquist, I'm trying to get CDSP installed on PiCorePlayer (RPi4) and I've run into some issues.
I followed the instructions from Lykkedk's github page and can get the GUI running, but CDSP remains offline.
I have tried extracting your v1.0.3 file and running it, but I can't get it to start. I don't get any errors but nothing happens. Also, I get "-sh: camilladsp: not found" unless I prefix sudo. I tried piping to an err log file but it is empty. Switches -c -h -v don't help.
If you have any ideas I'd be greatfull.
THX
edit:
I followed the instructions from Lykkedk's github page and can get the GUI running, but CDSP remains offline.
I have tried extracting your v1.0.3 file and running it, but I can't get it to start. I don't get any errors but nothing happens. Also, I get "-sh: camilladsp: not found" unless I prefix sudo. I tried piping to an err log file but it is empty. Switches -c -h -v don't help.
If you have any ideas I'd be greatfull.
THX
edit:
Last edited:
even running the camilladsp binary without anything will give you error output.
Are you sure your PATH variable contains the location of where you put the binary? - which looks like a camilladsp sub-directory under your "tc" users home directory? e.g. /home/tc/camilladsp?
What is your full command line? including your YML config?
Paste / attach your YML here so we can validate it.
@chuckt62 PiCorePlayer (or rather TinyCoreLinux that it's based on) works a little different than normal Linux systems. I have never used it so I can't help you with where to place binaries etc, but others here should be able to help with that. If you need to use sudo to run camilladsp, then you have some permission issue.
Is it a 32 or 64-bit system? You need to get the matching camilladsp build. Running "camilladsp --help" must print the help text. Before that works, there is no point in trying anything else
Is it a 32 or 64-bit system? You need to get the matching camilladsp build. Running "camilladsp --help" must print the help text. Before that works, there is no point in trying anything else
I somehow ended up bricking that SD card and started over w/32bit pCP. I'll try again w/64bit if I can get it running.
Some progress has been made though. I can run CDSP from cli and gen the log file. It might be failing from the loopback device, I can't figure out how to create it in pCP as it doesn't use module.d (I used 'snd-aloop' in the file snd-aloop.conf and placed it in /etc/modules.d on ubuntu).
config.yml:
log:
Some progress has been made though. I can run CDSP from cli and gen the log file. It might be failing from the loopback device, I can't figure out how to create it in pCP as it doesn't use module.d (I used 'snd-aloop' in the file snd-aloop.conf and placed it in /etc/modules.d on ubuntu).
config.yml:
log:
I created the loopback device and get a little further, "sudo modprobe snd-aloop", but I don't know how to make it persistent yet.
It's probably failing on the playback device now, MOTU M4. I have only been able make it work with plughw:CARD=M4,DEV=0 on pCP. It worked with hw:CARD=M4,DEV=0 on ubuntu... Or, maybe it's because I'm listening to it while trying to start CDSP?
log:
It's probably failing on the playback device now, MOTU M4. I have only been able make it work with plughw:CARD=M4,DEV=0 on pCP. It worked with hw:CARD=M4,DEV=0 on ubuntu... Or, maybe it's because I'm listening to it while trying to start CDSP?
log:
Last edited:
If I pause the player and click the 'Power' button (it's not setup to actually kill the player), it goes further but it seems to have failed and I need to Ctrl-C out of it.
EDIT: well it looks like CDSP is actually running, no need to Ctrl-C out.
I just don't get any sound when I start the layer.
big log:
EDIT: well it looks like CDSP is actually running, no need to Ctrl-C out.
I just don't get any sound when I start the layer.
big log:
Last edited:
It's running now. Camillagui somehow picked up the plughw:M4 from the Squeezlite setup, even though my config file had hw:M4.
I added the plug prefix to the loopback device and boom... it works.
Now to figure out persistent snd-aloop, running cdsp at startup and why pCP needs the plug hw
.
I added the plug prefix to the loopback device and boom... it works.
Now to figure out persistent snd-aloop, running cdsp at startup and why pCP needs the plug hw
.
I put 'modprobe snd-aloop' in /opt/bootlocal.sh to get a persistent loopback device.It's running now. Camillagui somehow picked up the plughw:M4 from the Squeezlite setup, even though my config file had hw:M4.
I added the plug prefix to the loopback device and boom... it works.
Now to figure out persistent snd-aloop, running cdsp at startup and why pCP needs the plug hw
I can't get cdsp to load from there though...
Update for anyone interested:
There seems to be a problem with linux and handling Intel's CPU P-states in combination with firewire interfaces.
Turning off C-states did not help. I have found the solution/workaround by accident - when stress testing the cpu (100% load of all cores with s-tui) CDSP buffer level dropped and became rock solid (5-hour test with no underruns).
The solution was to turn CPU frequency scaling governor to performance in linux kernel (running the CPU at fixed speed set in the BIOS should also work). I highly recommend this solution even if you don't have firewire, it should improve stability/buffer level for every type of interface. CPU frequency scaling doesn't seem to work well for audio pipelines.
I was able to achieve completely stable setup with:
96kHz sample rate, 512 chunk size and rock-solid 256 sample buffer size (going below 2048 samples of buffer wasn't possible before the workaround)
Setup:
Xeon E3-1220 V6 + TI Firewire card + MOTU 828MK3 all IO enabled and in active use
Cheers,
Tom
