You are not logged in.
Pages: 1
Just posting in case anyone else runs into it, but if you use a localhost pulse server for audio output between different users, pipewire 1.6.5 seems to really break it for some reason and I haven't worked out why.
Downgrading to 1.6.4 and blocking the updates made things good again.
-> libpipewire: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1)
-> pipewire: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1)
-> pipewire-alsa: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1)
-> pipewire-audio: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1)
-> pipewire-jack: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1)
-> pipewire-pulse: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1)
-> pipewire-session-manager: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1)If anyone knows how to make 1.6.5 happy, would like to know.
Cheers.
Last edited by pezz (2026-05-22 23:16:34)
Offline
Done some more investigating, this seems to be affecting mpv exclusively.
VLC and a bunch of other audio / video apps are fine.
Offline
Please don't post PSA-style topics. If you want some help diagnosing the issue, please modify your topic title accordingly.
Mod note: moving to Multimedia and Games
Last edited by WorMzy (2026-05-16 12:21:02)
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
mpv -ao pulse thunderstruck.mp3
mpv -ao pipewire thunderstruck.mp3
mpv -ao alsa thunderstruck.mp3Does this affect all of those?
Offline
Apologies for the hyperbole, sorry mods.
It's ao=pulse with a network output defined (e.g. 127.0.0.1 server for multiuser).
Everything else is fine.
Offline
I have this problem too. I play xonotic under X under an user different from the display owner and I got a totally garbled audio. I managed to obtain an acceptable output by tweaking the pipewire config files, in particular I added 44100 rate inside the pipewire.conf file.
default.clock.allowed-rates = [ 44100 48000 ]
But the overall result is still not optimal as the sound is a bit cracking.
Just posting in case anyone else runs into it, but if you use a localhost pulse server for audio output between different users, pipewire 1.6.5 seems to really break it for some reason and I haven't worked out why.
Downgrading to 1.6.4 and blocking the updates made things good again.
-> libpipewire: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1) -> pipewire: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1) -> pipewire-alsa: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1) -> pipewire-audio: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1) -> pipewire-jack: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1) -> pipewire-pulse: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1) -> pipewire-session-manager: ignoring package upgrade (1:1.6.4-1 => 1:1.6.5-1)If anyone knows how to make 1.6.5 happy, would like to know.
Cheers.
Offline
Does changing the default sample rate to 44100 achieve anything?
Sanity check, you're using pipewire-pulse are are not running pipewire and PA concurrently?
Do you have https://archlinux.org/packages/extra/x86_64/rtkit/ (working)?
Offline
Modified the topic, not sure whether to mark as solved, but it works for me.
Trying a bunch of config options and pulse-latency-hacks=no in my mpv.conf has done the trick:
ao=pulse
pulse-host=127.0.0.1
pulse-latency-hacks=noLast edited by pezz (2026-05-22 23:18:39)
Offline
https://man.archlinux.org/man/mpv.1#pulse~4 actually points that out.
Let's see whether janp can confirm this.
https://wiki.archlinux.org/title/Mpv#Fi … from_pause might need an update.
Offline
Pages: 1