@DEC05EBA Have been able to confirm with correspondence through this issue I posted that the behavior regarding PipeWire's pulse implementation is the issue.
tl;dr: copying/pasting the demo /usr/share/pipewire/pipewire-pulse.conf
as an active system/local conf file and uncommenting/changing the value of pulse.default.frag
to a value of ~8192/48000
or below effectively (or rather, quite literally) brings the behavior back in line with pw 0.3.51.
Not to make assumptions or judge in any way, but I presume that you're using PulseAudio alone in normal use? The changed behavior in PipeWire with pulse input is allegedly supposed to bring behavior in line with native PulseAudio's buffer size.
Pinned Comments
DEC05EBA commented on 2024-11-26 18:52 (UTC)
The aur package gpu-screen-recorder-git was renamed to gpu-screen-recorder. Install gpu-screen-recorder instead or you may experience issues.