Linux

48199 readers

1369 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

KDE Neon - Force bluetooth aptx instead of LDAC? ...or fix bluetooth stuttering (lemm.ee)

submitted 1 year ago* (last edited 1 year ago) by iturnedintoanewt@lemm.ee to c/linux@lemmy.ml

14 comments fedilink hide all child comments

Hi guys! Is there a way to get my KDE Neon to prefer aptX over ldac_HQ? If I understand it correctly, ldac seems to be a bit more unstable jumping over different bitrates when having interference, and aptX might be more stable? I'd like to try the difference, but not sure how to force Neon to work with the aptX codec with my headsets (Sony XM2 and XM5). I'm trying all this because I don't seem to be able to get any decent audio quality. It's super broken, stuttering constantly. Even changing from A2DP sink to the HFP mode (which I understand it to have lower bitrate and latency due to being designed for talking) improves it just very slightly, with the stutter continuing. This doesn't happen if I boot into windows on the same computer, audio works flawlessly.

you are viewing a single comment's thread
view the rest of the comments

[–] iturnedintoanewt@lemm.ee 2 points 1 year ago* (last edited 1 year ago) (2 children)

Thanks...where's that advanced settings you mention? I don't seem to be able to find it. On the headset I'm only allowed to choose the audio container, between A2DP sink and HFP, but no specifics regarding LDAC or AptX. https://imgur.com/a/zi6YJZU

[–] InverseParallax@lemmy.world 2 points 1 year ago

Check, sec I have to look, there's a library that helps with codecs.

[–] InverseParallax@lemmy.world 1 points 1 year ago (1 children)

Your headset doesn't support anything above sbc I think.

[–] iturnedintoanewt@lemm.ee 1 points 1 year ago (1 children)

That...is not correct. As mentioned, these are the higher end Sony XM2 and XM5. They support LDAC, at least the XM2 also AptX and HD, and some others.

[–] InverseParallax@lemmy.world 1 points 1 year ago (1 children)

Yeah, I added later, you might need to add the bluez stack to get proper ldac and aptx support, pulseudio only supports sbc by default.

[–] iturnedintoanewt@lemm.ee 1 points 1 year ago* (last edited 1 year ago) (2 children)

...on OP I did mention that ldac_HQ was already being selected, and stuttering. I wanted to change to aptX instead. So bluez stack is/was installed. But nevermind, I ended up changing the whole audio stack to pipewire. Seems to work much better than pulseaudio, and has more options to individually choose my specific codec, not just the container (sbc/a2dp sink).

[–] InverseParallax@lemmy.world 2 points 1 year ago (1 children)

Pulseaudio is... bad.

I'm just wondering how you knew you were on ldac if it didn't show up in output settings, I mean I have a led that says, but I'd want to know from linux too.

[–] iturnedintoanewt@lemm.ee 1 points 1 year ago

Hmmm some of the console commands I was using for troubleshooting listed the enabled codec. But no idea on how to change it from there.

[–] InverseParallax@lemmy.world 1 points 1 year ago

Sorry, I sent this reply to myself:

https://wiki.archlinux.org/title/Bluetooth_headset

Anyway, had the same fight with bluez5, pipewire fixed it too, is there nothing it can't solve?