aptX-LL stuttering since 3.3

[vØidward]

I was pretty excited when I got aptX low latency working since it just carries over the settings from desktop mode - but it seems since then, which was only a few weeks ago, it's no longer usable, It constantly crackles and stutters. Switching to the aptX-HD mode seems to be a perfect experience again, minus the latency.

I don't remember any bluetooth audio related changes in recent patch notes, so I assume the 3.3 OS update included some new drivers which are doing this. Would be nice if someone could take a look.

[goatpwner]

I have AirPods 2nd gen. I noticed the audio latency is bad, and haven’t messed with any settings yet. Just chiming in for visibility of your post, Bluetooth audio latency should be better by default. Shouldn’t have to change codecs in desktop or make any other adjustments.

[HoloPengin]

Same issue here, still not fixed

[RavenWorks]

Just got an aptX-LL device; this is still happening. It'll be fine for upwards of half an hour, and then suddenly it's crackling more often than it's not, and restarting the speaker doesn't help for long. In my brief experimenting, aptX-HD seems to not have the same issue.

[Broseph Joseph]

LL is low latency because it has a shallow audio packet buffer [20ms or so], it stutters when the buffer runs dry. this is the same concept as anti-skip on what we used to call 'CD players'. that means youve got air interference which is running the buffer dry, or software side stalls doing the same thing.

[RavenWorks]

OK, I just confirmed something that makes me suspect it's a driver problem: once the problem starts,
- restarting the speaker doesn't fix it
- quitting the software doesn't fix it (the steam deck launcher UI stutters too, which makes it very unlikely it's a software-side stall)
- restarting the entire steam deck DOES make the problem go away again!

It only happens to me once every few days, but once it starts, it comes and goes every few minutes until I reboot the entire steam deck, and then it's gone for days again. Something at the OS level is getting into a bad state that only a reboot fixes.