You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love fusionDSP and probably use the equalizer the same way many of us do: to correct my headphones. When playing through the main speakers, I turn the EQ off.
Turning it on an off in volumio UI is tedious: go to plugins / switch tab to installed plugins /open fusion DSP settings / ...
I think it would be great to have either of the two alternatives:
a simple button on the main screen to turn EQ on/off or to cycle through presets (off /preset1/preset2/preset3)
even better: if there was a way to achieve the same from the commandline, so I could use a button on my IR remote for it
I don't know to what degree the volumio plugin system allows this, but either of the two (or both) would be a great step forward in usability.
The text was updated successfully, but these errors were encountered:
While waiting for a proper solution, I built a little workaround:
I created a shell script that manipulates volumio's plugins.json and then restarts the volumio service.
That script I call via two buttons on my IR remote - it takes "on" and "off" as arguments and enables/disables fusiondsp accordingly. Works like a charm.
The content in my lircrc to call it is quite simple, too: begin prog = irexec button = KEY_VOLUMEDOWN config = /home/volumio/switch_fusiondsp.sh off end begin prog = irexec button = KEY_VOLUMEUP config = /home/volumio/switch_fusiondsp.sh on end
I love fusionDSP and probably use the equalizer the same way many of us do: to correct my headphones. When playing through the main speakers, I turn the EQ off.
Turning it on an off in volumio UI is tedious: go to plugins / switch tab to installed plugins /open fusion DSP settings / ...
I think it would be great to have either of the two alternatives:
I don't know to what degree the volumio plugin system allows this, but either of the two (or both) would be a great step forward in usability.
The text was updated successfully, but these errors were encountered: