ja1bbp

> > 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...

I have been trying to install Easyeffects natively on Raspberry pi5 for the past two weeks. Installing without Flatpak was very time-consuming because many errors occurred during the build. But...

> Which desktop are you using? The autostart of files inside `~/.config/autostart/` is the desktop environment responsibility. Below is information about the autostart file that was generated when I natively...

> It does not seem to use autostart files. Yes, after analyzing this code it is clear that it doesn't work as I expected. This is the current situation of...

Thank you for the information. I tried various things based on your advice and the information in #3635. However, the automatic launch and automatic execution of Easyeffects did not work...

>Hum... As I am not this plugin's author the only way is an ugly way. Destroying the whole plugin instance and recreating it. It >is doable. But jumps in audio...

Hi, I have considered the mechanism of the occurrence of the latency problem I reported. I will record it as a memo for myself. I hope it will be helpful....

Thank you for your feedback. Based on your advice, I have investigated whether the EasyEffects plugin threads are running with real-time (RT) scheduling. Below is a summary of my findings....

>Hum... Then the ugly hack where the plugin instance is destroyed may be needed. But probably only for the deepfilter >plugin. Doing this for all plugins would just waste effort...

Thank you very much. I appreciate your efforts!!