Wellington Wallace

So much has changed that is probably better to close this issue

The AUR package will have to build from the legacy branch https://github.com/wwmm/easyeffects/tree/pulseaudio-legacy instead of using the release file for 4.8.7. The Boost library has changed and the legacy branch source...

Try to reset easyeffects `easyeffects -r` and deleting `~/.config/easyeffects/`. This should bring its state back to normal. Through the years some changes to the presets format were inevitable. And in...

>However, even when I restart the Raspberry Pi, EasyEffects does not launch automatically. The desktop file in the autostart folder requires support from the desktop environment. What is usually the...

>To resolve this issue, I reset the Flatpak permissions. And next, I installed xdg-desktop-portal. This operation eliminated the above warning message, but as I reported last time, I noticed that...

>In other words, when the Raspberry Pi is powered on, monitoring will automatically start in the state it was in the last time it was used. By this do you...

>EasyEffects will not work unless I click the mouse three times: 'input' → 'Effects' → 'Enable input monitoring' every time. Did you enable `Process All Input Streams` in EasyEffects preferences...

>In your environment, EasyEffects starts running automatically without any mouse click operation, right? At least on KDE and GNOME EasyEffects autostarts on login and process audio in the background just...

>After launching Easyeffects, I tried to enable "Launch Service at System Startup" (also enabled "Process All Input Streams"). However, when I rebooted Raspberry pi, Easyeffects did not launch automatically. I...

>Perhaps the option should be renamed to "Start in background at Login", as I think it's equally clear and doesn't misrepresent what actually happens. I do not see a problem...