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

[HenrikEnquist]

Is there a way to keep the GUI connected when running CamillaDSP manually?

Yes, just run it with the same command line that the systemd service does, and the gui will be able to connect.
But the gui adds a lot of noise in the logs, so if you can do it with the gui closed, the log gets much easier to read.

 

[maravedis]

Are you using CamillaGUI to make your changes, or are you editing the file with a text editor?

If using CamillaGUI, after making changes select "Apply and save" at the bottom left side of the window, in the box titled "Config".

I'm using the GUI - sometimes the 'apply automatically' doesn't work. (stuck on the warning triangles)

 

[maravedis]

Unfortunately, I've woken up to another crash. I've checked the target_level is default. And resampler is on.
Is there anything else it could be? Faulty Pi5? Presumably there is not much to go wrong in the dac8x?

 

[phofman]

Unfortunately, I've woken up to another crash

What is the "crash" specifically? Please post your current config file.

 

[maravedis]

The fault is sound suddenly goes mono, distant and 'euphonic'. Nothing appears on the Log and the meters in the GUI seem to behave as normal. Switching to anther config and back solves the issue.

 

[phofman]

But the rate adjuster is still disabled, your setup cannot work reliably for longer time:

enable_rate_adjust: null

 

[phofman]

Switching to anther config and back solves the issue.

IMO that's because CDSP restarts the capture/playback chains which resets the buffer positions. After some time buffer issues ensue, logically if the rate adjuster is not working to avoid them.

 

[maravedis]

grr - I had it set to default in the gui. Thank you for helping.

 

[TNT]

Now push "Save" ;-)

//

 

[mdsimon2]

grr - I had it set to default in the gui. Thank you for helping.

enable_rate_adjust (optional, defaults to false)

This enables the playback device to control the rate of the capture device, in order to avoid buffer underruns or a slowly increasing latency. This is currently supported when using an Alsa, Wasapi or CoreAudio playback device (and any capture device). Setting the rate can be done in two ways.

• Some capture devices provide a way to adjust the speed of their virtual sample clock (also called pitch adjust). This is available with the Alsa Loopback and USB Audio gadget devices on Linux, as well as BlackHole version 0.5.0 and later on macOS. When capturing from any of these devices, the adjustment can be done by tuning the virtual sample clock of the device. This avoids the need for asynchronous resampling.
• If asynchronous resampling is enabled, the adjustment can be done by tuning the resampling ratio. Then resampler must be set to one of the "Async" types. This is supported for all capture devices.

enable_rate_adjust: null means that you had it set to default, otherwise it would say false or true, and as shown above default means false. IMO, always best to set the actual value you want and not leave it to default so there are no surprises.

Michael

 

[maravedis]

Yes, understood now. I need to concentrate!

 

[TerryForsythe]

Unfortunately, I've woken up to another crash.

Are you sending to your Pi a constant samplerate of 96000? Does your source vary the samplerate? E.g., with Tidal, even if I have it set to output 192k, it only does so for songs recorded at 192k. If a song is recorded at another samplerate, Tidal streams that song at the other samplerate.

 

[TNT]

Don't show . files in GUI.

//

 

[HenrikEnquist]

Don't show . files in GUI.

Is that gui v2? In v3 it skips dotfiles:

 

[TNT]

V2 - thanks! I'v yet to update my other installation...

//

 

[EmuMannen]

I just finished my CamillaDSP based amplifier, the build documented in this thread:

DSPreamp, the CamillaDSP based amp​

Thanks HenrikEnquist for making it possible. 🙏

 

[m-a]

That's normal, only one process at a time can use an alsa device.

Can you capture logs on debug level from a run where it changes?

Here are the updated debug logs. I’m having a lot of trouble with it, both when changing channels and when it stops playing sound entirely until I restart the Raspberry Pi. I’m seeing the SND_PCM_STATE_PAUSED message when it should be playing sound, but it isn’t.

 

[phofman]

@m-a: I would suggest to try disabling the silencer https://github.com/HEnquist/camilla...17182b63d051/src/countertimer.rs#L65C1-L65C40 , it unpausing seems to cause some issues.

 

[m-a]

@m-a: I would suggest to try disabling the silencer https://github.com/HEnquist/camilla...17182b63d051/src/countertimer.rs#L65C1-L65C40 , it unpausing seems to cause some issues.

Thanks! Will try that. What's the best way to disable the silencer? Would it be to set silence_timeout to 0?

 

[HenrikEnquist]

What's the best way to disable the silencer? Would it be to set silence_timeout to 0?

Yes exactly. For some reason this device doesn't always wake up automatically when playback is supposed to resume. I'm testing if it helps to send a specific unpause request. Looks promising but needs some more testing, and if it works I'll include it in the next release.