Bug#1054019: broken sample rate passthrough

2024-12-23 Thread Richard Lewis
On Mon, 23 Oct 2023 10:04:18 +0200 =?UTF-8?B?RHlsYW4gQcOvc3Np?= wrote: > Le mar. 17 oct. 2023 à 19:59, Nicholas D Steeves a écrit : > > 0.3.82-1~bpo12+1 solves the bug :) > > Great! :-) > > > Rather than close this bug as fixed right away, do you think it would be > > worthwhile to keep it open

Bug#1054019: broken sample rate passthrough

2023-10-23 Thread Dylan Aïssi
Hi Nicholas, Le mar. 17 oct. 2023 à 19:59, Nicholas D Steeves a écrit : > > Oops! Yes, thank you, I forgot to test a newer pipewire after tiring > and running out of time during the initial investigation. > > 0.3.82-1~bpo12+1 solves the bug :) Great! :-) > Rather than close this bug as fixed r

Bug#1054019: broken sample rate passthrough

2023-10-17 Thread Nicholas D Steeves
Hi Dylan, Oops! Yes, thank you, I forgot to test a newer pipewire after tiring and running out of time during the initial investigation. 0.3.82-1~bpo12+1 solves the bug :) Rather than close this bug as fixed right away, do you think it would be worthwhile to keep it open and/or add something to

Bug#1054019: broken sample rate passthrough

2023-10-17 Thread Dylan Aïssi
Hi Nicholas, Le dim. 15 oct. 2023 à 23:27, Nicholas D Steeves a écrit : > > So yeah, it looks like Pipewire's default sample rate is always > applied when using pipewire or JACK sinks, despite > "default.clock.allowed-rates" being set, except with using pulseaudio. > I'm not sure why this is the

Bug#1054019: broken sample rate passthrough

2023-10-15 Thread Nicholas D Steeves
Package: pipewire Version: 0.3.65-3 Severity: normal Hi, Unfortunately using mpv's Pipewire driver results in audio being resampled, which introduces resampling artifacts. While I discovered this bug in bookworm's mpv_0.31.1-4, I've confirmed that it is still present in 0.36.0-1. That said, as