Latency Regression?
Version, Distribution, Desktop Environment: Pipewire 0.3.20+nightly-210122.fc33, on Fedora 33 with Gnome
Description of Problem: As far as I can tell PIPEWIRE_LATENCY and PULSE_LATENCY_MSEC are being ignored. I'm following the settings laid out here for 5 Msec and completely leaving out the memlock and xrun section. I cannot get period/rate to drop below 3969/44100 for rhythmbox, firefox is in that range as well.
I ended up going back to stock settings and ended up with with my system drip sound, sounding like two coconuts banging together, or horse hooves (Should have recorded it). Also had to raise my headroom to 512 to avoid xruns which I never had to do before. Ended up back on 0.3.20+nightly-210121.fc33.x86_64.
I'm suspecting commit 652a4ae2.
Is this the intended behavior going forward?
How Reproducible: Very, just install the latest nightly on Fedora.
Steps to Reproduce:
- Install the latest nightly
- Reboot
- Get high latency's
Actual Results:
Expected Results:
Additional Info Eg. pw-dump > file (As Attachment Please):
May have to provide a pw-dump later as I've had to fallback to 0.3.20+nightly-210121.fc33.x86_64 so it wouldn't be from the affected version.