[pulseaudio-discuss] [PATCH] Fix: Distorted audio during Bluetooth SCO HFP/HSP playback
tanuk at iki.fi
Sat Sep 16 16:26:34 UTC 2017
On Sat, 2017-09-16 at 10:45 +0530, Arun Raghavan wrote:
> On Sat, 16 Sep 2017, at 12:11 AM, Georg Chini wrote:
> > On 14.09.2017 18:47, Tanu Kaskinen wrote:
> > > Note that even though I wrote "it's best to use 48 as the MTUs by
> > > default" in the quoted mail, I changed my mind later. The choice of
> > > enabling the autodetection was deliberate. The rationale is that we
> > > have two bad alternatives:
> > >
> > > 1) Enable autodetection by default, which will cause regressions. As
> > > the reports come in, the kernel should get fixed. Eventually all
> > > hardware should work out of the box.
> > >
> > > 2) Don't enable autodetection by default. The kernel won't get fixed,
> > > and hardware that requires different MTUs than 48 will never work out
> > > of the box.
> > >
> > > To me option 1 seems worse in the long term, but if you feel
> > > differently, I'm ok with going with option 2.
> > >
> > The view that the kernel will get fixed is very optimistic in my
> > opinion. We already had a few cases and to my knowledge
> > nothing has been fixed so far. People will just disable mtu
> > autodetection and that's it.
> > So I am fine with keeping the option disabled by default.
> Rather than break things directly, I would:
> 1. Get buy-in from BlueZ folks about actually fixing this stuff
> 2. Get a clear set of instructions for users to report problems in a way
> that it would be actionable to fix
> 3. Make this off by default for a couple of releases with a call for
> people to test manually
> 4. Then, make it on by default
That sounds like a fine plan.
Unless there's something else pending, I'll do the 11.1 release
tomorrow with the current stable-11.x contents (or if you get around to
it before me, you can do that too).
More information about the pulseaudio-discuss