How do I know when DSP is active and when it is not? Of course, you should be able to tell by the change in sound. There is an on and off button, but I don’t know when it’s on and when it’s not. Does it change color or something? I have a visual impairment and I may not be able to distinguish some color changes well….
Hello. Yes it color changes from green (active) to grey (inactive). If you prefer, go in FusionDsp settings, there is a button with a changing text “disable effect” or “enable effect”.
Let me know
After the reboot, the power button was indeed grayed out in the off state. After turning on the DSP, playback stopped (radio 80/80). Then the on/off button stopped coloring again. I honestly don’t know if it works well for me.
I have Volumio Primo and the latest Volumio OS update.
When I have some time I will send the log if it helps. I could still be doing something wrong. They can’t rule that out .
I don’t understand…
When the plugin is enable, if you change nothing, there is no sound change.
Change something in Eq, apply, you should hear the difference.
The text on the button change from “click to disable effect” to " click to enable effect". It seems to be clear enough…
This button doesn’t really work, it works when EQ is off, and I have not selected a PEQ preset, and turn it on and select a preset, but when I turn it off, button get greyed out, it doesn’t change anything. I can hear it because of the automatic preamp, volume doesn’t change when I turn it off.
I have to go into settings for fusiondsp and remove all EQ, then I hear volume changes, so DSP is off.
When you disable effect, the preamp remains the same in order to compare effect, not sound level!
So set a true effect, for exemple mute a channel and compare.
I take it that the imported settings should match those that are on the AutoEQ GitHub.
It seems that those Ive loaded the “shelf” type settings are different to those on the AutoEQ GitHub.
This one for instance.( theres another )
Ive also tried manually adding the settings from the AutoEQ Git just to see if it was a different way of expressing the settings. But the EQ’s sound quite different, which one I prefer I dont know , I am just pointing out tht it seems to be using “Lowshelf Hz,dB,slope dB/Octave” instead of “Lowshelf Hz,dB,Q”
Hello
What is the version I f FusionDsp you are using?
Can you please send the txt file you are using?
Do you use load profile using the headphones list?
TY
There is no txt file.
I used the “Import EQ from AutoEQ” and then used the “Choose Headphone Profil” <==(spelling), updated the list then chose my headphones Audeze LCD-2 Fazor.
I see what happens… I followed REW convention for import filters : EQ Filters
LS * LS for a Low Shelf filter (S = 0.9) with frequency,gain and slope
but in Autoeq, LS is defined by freq,gain,Q
So I need to detect when Autoeq or REW is used to switch to the correct filter.
TY for reporting it
Thanks for the update but I had to stop using FusionDSP due to Volumio constantly becoming unresponsive while FusionDSP is activated (reported earlier in this thread).
I changed the log level in CamillaDsp. I hope to see something in future issue… But there is nothing in your log that helps. I can’t reproduce it. So it is very problematic to fix. And no a lot of feedback (good or bad) from users…
Getting logs is obviously important in helping to trace the root cause of a fault.
But if in the midlle of a session, chilling, having a few beers, etc… a fault occurs, the last thing most are going to do is sit in front of the PC and dig out the log. Majority of the time, most will just reboot and continue listening. Obviously doing this overwrites, or renews the log file.
Suggestion: A dubug option in the plugin so that it writes a new date formatted log file each time you reboot.
I have just done a new fresh install of Volumio 3.429 to try the latest FusionDSP 1.0.35 which now imports the AutoEQ presets from the head phone list perfectly …Thanks
although… this version just stops and plays white noise now and again. Either one channel or sometimes both. Sometimes you can select another track and it plays again OK. Others it requires a reboot.
I’m assuming that its FusionDSP causing this, the last install I had with FusionDSP 1.0.33 worked fine the majority of times for 3-4 hour sessions, with only the occasional fault the same as what @Voluminous describes above. ie just stops playing.