FusionDsp : the complete Dsp center for Volumio3 and Volumio4!

Subject: CRITICAL BUG: FusionDSP forces YAML overwrite with syntax error, causing CamillaDSP crash loop.

Hello,

I am experiencing a critical and persistent bug in the latest version of FusionDSP on Volumio, which prevents CamillaDSP from running.

1. Problem Description (Critical Crash Loop)

CamillaDSP fails to start (State: Offline) because the FusionDSP plugin forces an overwrite of the camilladsp.yml file with a corrupted template every time the service is restarted (Off -> On or sudo reboot).

2. The Core Bug (YAML Syntax Error)

The corrupted template being forced by FusionDSP contains a fatal YAML syntax error on the devices section:

FATAL BUGGED LINE:

devices:
  samplerate: 44100capture_samplerate: 44100

Hello, I just wanted to report after a few days of frustration and trying to figure out whats wrong that having DSP plugin activated makes all my streamers not play music. I re-installed, rolled back. jumped between volumio 3 and 4 and nothing worked untill started activating and de-activating every single setting in the streamers and when i inactivated DSP music started playing again.

Hi,
after upgrading to Volumio 4 I have the same issue. I am on plugin version 2.0.75 and volumio 4.073. Log: http://logs.volumio.org/volumio/oLnyLEl.html
Thank you

I updated to 4.082 and the problem still persists.

Hello,
Thank you for reporting this.
Just to better understand what happens.
Does this happen just after plugin install, with no eq change?
Can you make it work if you change eq type to let’s say EQ15?
I’m investigating, but I made no change for months and I don’t see (yet) why it fails…

edit : I found an error when resampling is enabled in FusionDsp. I’m going to fix it. Can you confirm on your side this?

FusionDsp v2.0.76

  • fix for resampling issues (no sound)
  • fix error message
    Please test and feedback!
    :wink:

Thank you for your quick response. Unfortunately that wasnt the issue in my case, I do not have resampling enabled. Therefore the update did not solve the problem for me. I made another Log: http://logs.volumio.org/volumio/IeVB7i2.html
I will try with other EQ settings and let you know about the outcome later
Thanks

Thank you so much for trying balbuze. Unfortunatley updating and trying different kinds of EQ didnt help in my case. The only thing that makes it play again is inactivating the plugin so far.

http://logs.volumio.org/volumio/8G1Taj9.html

Hey!
Can you please disable all plugins, reboot and enable only FusionDsp with a 15 bands EQ?
Test with a track or radio , enable disable efffect and post a new log link.
Thank you.

I think i found the issue with my setup. The problem seems to only occur when I set the first (and only) parametric eq to ā€žNoneā€œ. I currently only need the loudness and the distance settings, so that was always set to none. When I change it to a Peaking eq with some random values I can here music again.

Marvellous! You found an issue! :grinning:
I try to fix it tomorrow!
Thank you!

Great! No hurry from my side, since the workaround does its job for me, but maybe thats also the fix for Pseudonym031.

1 Like

FusionDsp v2.0.77

  • fix for ā€œno soundā€ when a filter was set to ā€˜None’
  • fix for Loudness not updated with volume change

Enjoy the music! :wink:

3 Likes

it works! :smiley: thank you!

@balbuze

While reviewing my logs and troubleshooting my touchscreen over a month back, my AI agent pointed out the following:

At present, PeppyMeter captures audio via an ALSA loopback device (snd_aloop).
This method is reliable and works across a wide range of environments, even for users without DSP engines or advanced configurations — an excellent default choice. However, when FusionDSP (CamillaDSP) is active, the audio path becomes:
Volumio → FusionDSP (CamillaDSP) → ALSA loopback → PeppyMeter → DAC

:bulb: Suggested Enhancement

Add an optional ā€œCamillaDSP Monitor / FIFO modeā€ inside PeppyMeter’s configuration or Advanced tab.

When enabled:

  • PeppyMeter would read the signal directly from a secondary CamillaDSP output (monitor branch) or a FIFO file (e.g., /tmp/peppyfifo).
  • No ALSA loopback would be needed.
  • The signal would remain perfectly synchronized with CamillaDSP’s main output and share the same clock domain.
  • Users who do not use FusionDSP would continue to use the default loopback path — nothing changes for them.

No critique…more an observation from someone who uses both FusionDSP and peppymeter basic.

:pray: Closing Note

I hope this suggestion is received in the spirit intended — as a respectful contribution from an enthusiastic user who deeply values your work.

Thank you once again for maintaining and improving this wonderful project.

Works for me now! Thank you very much and merry Christmas

1 Like

Hello,
thank you for your suggestion…
But…
I don’t get any advantage of doing it.
FusionDsp and Peppymeter/spectrum must run alone, or both activated. The alsa path can’t be different for each config.
The loopback device in peppy do not alter the signal because there is no conversion in it

pcm.peppy_inx_raw { 
   type meter
    slave.pcm "hw:Loopback"
    scopes.0 peppyalsa
}

and it is used as a fake output, sending to nothing! A null or Dummy would do the same…
The AI can give good or bad info… :wink:

@balbuze

I will PM you.

FusionDsp v2.078 stable
Add Tilt filter in parametric EQ.
Thank you @nerd

But you’d better use a high or lowshelf filter with a low Q value as explained here : Feature request: tilt as parametric eq Ā· Issue #219 Ā· HEnquist/camilladsp Ā· GitHub

2 Likes

Thank You @balbuze and @nerd !

Really great work! Much appreciated and long awaited! I love the fact hat you are listen to us regular Volumio users, So a big THANKs to all of you fantasic developers here!

Kind Regards / C