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

Jump to Latest
#5,601
fb,

Again, my appreciation for your help.

One thing I like about DIETPI is you have the ability to view files through FILE EXPLORER without any desktop.

I believe it was you who mentioned winSCP which also gives you this ability.

I was using the mdsimon instructions - but did not know what to do since his "stuff" was for RPI . Of course, I had to insert the version I am using.

This is the part where I was concerned since I am not using RPI or aarch64. I will give it a try and see what happens.
wget https://raw.githubusercontent.com/mdsimon2/RPi-CamillaDSP/main/camilladsp.service -O /lib/systemd/system/camilladsp.service
No need for sudo with DIETPI.

I love my OS to have as little to it as possible - only what is needed. For my music player it is less than 900 mB. So far, the CAMILLADSP is 2.6GB. When I made the kernel for the music player I removed everything I could. This is the tickless kernel which I will try once I get this working. Whether it is as important for this duty is open to question! The kernel work is from BLITZ who posted his ideas and with his help I made a guide to do this. For those interested: https://www.diyaudio.com/community/threads/path-to-noiseless-linux-streamer.391202/

CAMILLADSP and the gui are not dainty! But they are doing lots of work.

Now, back to work trying to get my install to work.
 
Last edited:
#5,602
Hope I have not worn out my welcome.

Should there be something in the camilladsp/config and camilladsp/coeffs folders? There is nothing in mine.

When I type camilladsp on the command line I get this:
root@DietPi:~# camilladsp
-bash: camilladsp: command not found

root@DietPi:~# camillagui_backend
-bash: camillagui_backend: command not found

What have I missed?
 
#5,605
Horneydude said:
Can you try: >systemctl start camilladsp
Click to expand...
And if that doesn't work, try: /usr/local/bin/camilladsp which is where this command: sudo tar -xvf ~/camilladsp/camilladsp-linux-aarch64.tar.gz -C /usr/local/bin/ extracts the file to.

Sorry I missed that you are using Dietpi not on a pi 😅 I assume you've substituted amd64 for wherever you've seen aarch64 in the instructions.
 
  • Thank You
Reactions: rickmcinnis
#5,606
Horneydude said:
, a few simple terminal instructions disabled the Pulseaudio service.
Click to expand...
Another option is leaving PA as is (because it has many relations to other software, can run in user- or daemon- modes, etc.), and disabling the HW cards used by CDSP in PA. That way PA works normally, just never talks to those cards, leaving them free for direct alsa access from CDSP.
 
  • Like
Reactions: Horneydude and fb
#5,607
HenrikEnquist said:
No, the main volume acts on all channels by design. The idea is to keep it as simple as possible to avoid painful mistakes, so it's not possible to bypass it. If you need fixed level outputs, then you will need to keep the main volume on full, add Volume filters to the non-fixed channels, and control those with one of the aux faders.
Click to expand...
Thanks, that's what I thought.
I want three additional outputs for loopback-recording (SPDIF & 2*analogue) with fixed output.
With the way you described it works well.
 
#5,612
I keep having a problem with cargo not being used by DIETPI. It is right there in my root directory. There is something missing in dietpi that is not allowing cargo to function. I have not tried fb's latest suggestion.

Oh, well.

Another of my annoying questions - if someone would be kind enough to humour me - what is the difference in running camilladsp as a service and not?

Is this more difficult to implement? Seems running it as a service one could have more control of it as far as priorities. Again, I fear I am showing my over-enthusiastic ignorance.

fb, you assumed correctly on the substitutions. I missed entirely that that instruction was placing camilladsp in the usr folder. As I slowly learn. THANKS for your help.
 
#5,613
rickmcinnis said:
Another of my annoying questions - if someone would be kind enough to humour me - what is the difference in running camilladsp as a service and not?
Click to expand...
Running it as service, assuming it is enabled, allows it to startup automatically on boot and run without user interaction. You can specify all of your startup options in the camilladsp.service file so that you don't need to manually enter them via the terminal to start CamillaDSP.

rickmcinnis said:
Is this more difficult to implement? Seems running it as a service one could have more control of it as far as priorities. Again, I fear I am showing my over-enthusiastic ignorance.
Click to expand...
I followed the instructions in the link below; it is pretty simple. Mostly copy and paste, though you have to update a couple of service files with your user name, but even for that you can copy and paste the commands into your terminal to open the files:

https://github.com/mdsimon2/RPi-CamillaDSP
 
  • Thank You
Reactions: rickmcinnis
#5,614
rickmcinnis said:
keep having a problem with cargo not being used by DIETPI.
Click to expand...
You don't need to use cargo for anything! It's only needed if you want to compile CamillaDSP from source. I publish binaries that work on most systems with each release. You just need to download the correct one and decompress it, that's it. The latest are here: https://github.com/HEnquist/camilladsp/releases/tag/v3.0.0

But it seems that quite a few people miss this in the readme, so it's obviously not good enough. My problem is that I have spent so much time staring at that readme that I'm getting quite blind to any issues. Help appreciated!
 
  • Like
  • Thank You
Reactions: rickmcinnis and mdsimon2
#5,615
I have the shortcoming of obsessing over details that no longer matter.

PLEASE no apologies from you of all people. I cannot imagine the thought and time that has gone into this project.

Of course, I should have noticed the difference in the instructions that mdsimon had provided for RPI though the basics of that are useful to all with translation and what I was reading on your README. I thought I was missing something and sure enough I was! The problem it was the opposite of what I thought I was missing.

Tonight - I begin again.

I have been enjoying the resources of DIYAudio for many years and there have been many fine projects presented but I do not think ANY have matched the grandeur of camilladsp. I can only imagine how beautiful its namesake must be.

Can't wait to use it!

Thanks, yet again.
 
#5,617
Help ... I'm using Camilladsp on Kubuntu 24.04 and 24.10 on an Intel x86 machine with Pipewire & Wireplumber & Loopback
I can play audio, process it through Camilladsp and send it out on a multichannel dac ... BUT

I have 2 challenges
  1. Unable to open 8 channels in the "source" ie. the player (VLC say) can open and use 8 channels but Camilladsp can open no more than 6
  2. Channels are mapped in an odd manner. Basically Centre & LFE are both sent to the same channel and RL & RR are both sent to the same (different to Centre&FLE) channel
I've not found a way to resolve either of these challenges
Using speaker-test and easy-effects it seems that pipewire and loopback are interacting ok ... each of the 8 channels tested shows up in the easy-effects monitor

Qpwgraph suggests pipewire connects everything correctly - it shows 8 Loopback channels connected as expected on Kubuntu 24.10

Here are the pipewire loopback definitions in ~/.config/pipewire/pipewire.conf
{ factory = adapter
args = {
factory.name = api.alsa.pcm.sink
node.name = "alsa-sink"
node.description = "My-Loopback-Snk"
media.class = "Audio/Sink"
api.alsa.path = "hw:Loopback,0,0"
audio.channels = 8
# audio.position = [ FL FR RL RR FC LFE ] # No combination of channel names or format fixes the mapping, in source/sink or both
resample.quality = 10
stream.dont-remix = true # Doesn't make any difference to mapping problems
}
}
{ factory = adapter
args = {
factory.name = api.alsa.pcm.source
node.name = "alsa-source"
node.description = "My-Loopback-Src"
media.class = "Audio/Source"
api.alsa.path = "hw:Loopback,1,0"
audio.channels = 8 # Camilladsp can only open 6 channels
resample.quality = 10
stream.dont-remix = true # Doesn't make any difference to mapping problems
}
}
]
Click to expand...


SoftwareVersion On Kubuntu 24.10Version On Kubuntu 24.04
Camilladsp (installed using the nifty install scripts)v 3.0.2v 2.0.3
KubuntuV 24.10 kernel 6.11.0-14-genericv 24.04 kernel 6.8.0-53-generic
Pipewirev 1.2.4v 1.0.5
Wireplumberv 0.5.6v 0.4.17
Easy Effectsv 7.1.7

Note that I also posted an entry in AskUbuntu with a little more debugging detail (no replies yet) AskUbuntu Question - Pipewire & Loopback

Multi-channel audio works well with Camilladsp when sent directly via Alsa Loopback, the problems seem to relate to using pipewire & wireplumber

It's likely I've misunderstood or misconfigured something ....so I'd rather not waste Henrik's time chasing a non-existent problem

Is anyone else successfully sending multichannel audio to camilladsp using pipewire & alsa's loopback ? Any pointers on what to change, where to look or debugging ?
 
#5,619
yes, ignoring the loopback name changes (supposed to protect the guilty 🙂

Chain ie .... Speaker-test --> Pipewire My-Loopback-Snk --> Pipewire My-Loopback-Src --> Camilladsp ---> Alsa hw:1,0 dac

or diagram from qpwgraph while testing with speaker-test
qpwgraph_pipewire_camilladsp_20250217_190905.png
 
You must log in or register to reply here.
Top Bottom