Wellington Wallace

> so then increasing quantum remains my only option? I tried changing the default one from pipewire.conf but it seems it doesnt have any effect on the soundcard line... not...

> still dont know what to do about discord having a say in my soundcard's quantum... What you are seeing will happen with other applications too. By default pipewire's dynamically...

>It turns out that the problem goes away if I turn off the inactivity timeout (Preferences > Audio > Enable inactivity timeout > off). Unfortunately, Easy Effects uses CPU all...

> To be clear, turning off the inactivity timeout doesn't _cause_ stuttering - it fixes it (for me), or at least so it seems over the course of today. Oh......

>What exactly is a "supported" version of PipeWire? I run 1.5.81 which seems to be one of the PipeWire 1.6 Release Candidates. PipeWire's latest stable release is `1.4.9`. It is...

> So much for 1.5.81 up to 1.5.83 being ABI and API compatible with 1.4.x I guess 😅 To make things even more bizarre it seems that it actually works...

> I also have exactly the same issue with pipewire `1.4.9` and easyeffects `8.0.3` on NixOS If possible try to test on `8.0.5`. You might be affected by a different...

I think I had the intention of doing that and completely forgot about it.

>What would be the use for dry/wet sync/offset adjustment? In most cases they allow the effect strength to be controlled. I do not know if something special happens when using...

>I still don't really understand why dry/wet time offset would be needed. I am not sure. Usually time difference creates echo/reverberation. But that is what many impulse files already do....