easyeffects icon indicating copy to clipboard operation
easyeffects copied to clipboard

app stops working when i pause movie or music player

Open Sannn274 opened this issue 5 months ago • 1 comments

EasyEffects Version

7.2.3

What package are you using?

AUR (easyeffects-git)

Distribution

Ubuntu 24.04.2 LTS

Describe the bug

i start easy effects app. then, i play film on chromeI run the easy effect application and it has opened properly. when I run the movie it also works well. but when I pause the movie the easy effect application immediately closes. long story short, I tried to turn on one by one the effects in my effect chain and when I turned off the crystalizer effect everything returned to normal. when the movie is paused it doesn't close the application.

Expected Behavior

I think there is a problem with the crystalizer effect

Debug Log

(easyeffects:11138): easyeffects-DEBUG: 10:51:10.560: stream_input_effects.cpp:201 No app linked to our device wants to play, but the inactivity timer is disabled. Leaving filters linked. (easyeffects:11138): easyeffects-DEBUG: 10:51:10.560: stream_input_effects.cpp:201 No app linked to our device wants to play, but the inactivity timer is disabled. Leaving filters linked. (easyeffects:11138): easyeffects-DEBUG: 10:51:10.801: output_level.cpp:45 soe: output_level: PipeWire blocksize: 1024 (easyeffects:11138): easyeffects-DEBUG: 10:51:10.801: output_level.cpp:46 soe: output_level: PipeWire sampling rate: 48000 (easyeffects:11138): easyeffects-DEBUG: 10:51:10.801: crystalizer.cpp:124 soe: crystalizer blocksize: 1024 (easyeffects:11138): easyeffects-DEBUG: 10:51:10.843: crystalizer.cpp:251 soe: crystalizer latency: 2.0833333e-05 s (easyeffects:11138): easyeffects-DEBUG: 10:51:10.844: effects_base.cpp:311 soe: pipeline latency: 92.9375 ms [1] 11138 killed G_MESSAGES_DEBUG=all easyeffects

Additional Information

No response

Sannn274 avatar Jul 07 '25 04:07 Sannn274

[1] 11138 killed G_MESSAGES_DEBUG=all easyeffects

This is the system killing EasyEffects. Most likely because it considered that the crystalizer plugin spent too much time doing stuff in Pipewire's realtime thread. As the crystalizer plugin can use a lot of CPU some systems have difficulties running it.

wwmm avatar Jul 07 '25 05:07 wwmm