Dalmonegrig
100+ Head-Fier
- Joined
- Aug 14, 2016
- Posts
- 430
- Likes
- 337
How to check (find out) this?As long as the bandwidth is getting over 909kbps, then yes.
How to check (find out) this?As long as the bandwidth is getting over 909kbps, then yes.
Well I'd say in theory: if you're using a newer set of BT headphones (that are using a newer BT standard) it's going to easily be that case (since you're also likely to be close to the phone to have full strength). Just googling, looks like there are apps for checking BT signal strength (so if you'd be at your phone, I guess you'd have to experiment setting distances of your headphones)How to check (find out) this?
I measured it, below are the results.There are apps for checking BT signal strength
Those look like very good numbers: so yes, I'd say you're getting the full 909kbps for CD quality lossless. You'll probably start seeing drops once you try putting your headphones in a case and try moving away from it. From what I could tell of your phone setting screenshots, I think your audio then drops to lossy SBC when the bandwidth goes below 909kbps. I don't know if these meters provide a TX/RX rate. Those provide the actual transmission rate and receiving rate. I'm on my Mac right now (which isn't my most current computer and doesn't have the 6Ghz band my new 6E router is capable of). But under advanced, I can see that it is showing the full Tx rate (WiFi) of 1,300Mbps with a RSSI of -37 dBm.I measured it, below are the results.
![]()
![]()
These indicators are sufficient to assume that lossless sound will be obtained?
Those look like very good numbers: so yes, I'd say you're getting the full 909kbps for CD quality lossless. I don't know if these meters provide a TX/RX rate. Those provide the actual transmission rate and receiving rate.
You’re welcome, and we both learned what is the max Android BT standard available at the momentToday is a good day.
With your help, I have come a long way. In any case, this is the maximum that I managed to squeeze out of bluetooth technology with the help of LDAC.
Thank you very much for your help!
1. As lossy 24/96 would technically result in lower fidelity than lossless 16/44 within the audible band, I do think it’s a “deception” to say it’s hi-res. Although the difference should be inaudible of course.[1] Since LDAC is capable of lossy 96kHz rate, I don't think it's a "deception" to say it's hi-res. [2] To make things more complicated, apparently it has a CD quality "lossless" standard that's open for developers.
That maybe just a perceptual error or might be a real audible difference depending on how the SBC is implemented in that particular device. I recall quite a debate about the audible sound quality of SBC a few years ago, I think when Aptx (or Aptx HD) was released. Some reliable DBTs were carried out and no audible difference was detectable between SBC and lossless across several devices. However, it did depend on maintaining the high quality profile and recommended bitpool. I don’t remember the exact source now and a quick, cursory search didn’t reveal it, so this is anecdotal unless anyone else can find it.I'm playing 24/48 FLAC through UAPP and switching between SBC and AptX, and SBC sounds far better implemented than before and in recordings I hear from that time (2019). However, there is something distinguishable between the two, and it's the dynamic range of the transient peaks in the track I'm listening to.
Aren’t these two assertions contradictory? Your settings and measurements indicate you’re getting lossless 16/44 (and possibly lossy 24/44) but you are having to “assume” you’re obtaining lossless because presumably you can’t hear that you are (which agrees with the fact that there should be no audible difference). So, what have you gained in terms of any audible improvement and how have you “come a long way”?These indicators are sufficient to assume that lossless sound will be obtained? … With your help, I have come a long way.
So, what have you gained in terms of any audible improvement and how have you “come a long way”?
Don't need an app for that, you can just turn on developer mode and change codecs in Dev options.There’s a real easy way to test all of this out on android devices. There are Bluetooth codec changing apps, on the android play store at least, where you can seamlessly switch the codec during a song from Ldac to aptX, etc. good luck noticing huge differences. the changes, to me at least going from aptx adaptive to sbc are so minuscule that it’s probably not worth obsessing over. AptX adaptive to aptX hd, and even regular aptX are fairly inaudible
I hear you…but it’s much easier and seamless when using the appDon't need an app for that, you can just turn on developer mode and change codecs in Dev options.
Lossy wouldn’t be desired for re-encoding or editing vs lossless or uncompressed. But I assume, like other multimedia codecs, there could be really efficient codecs that would have advantages over it’s uncompressed alternative if space/datarate is limited. For example, movies have relied heavily on lossy compression to be able to stream or fit on an optical disc (that includes 48kHz audio getting up to 7.1 channels). Before the current craze for streaming “hi-res”, you had your DVD-A and a limited selection of movies and concerts on blu-ray that were 24/96. If I wanted to recompress one of my few BDs that had the surround 24/96 audio track, I can re-encode them in h.265 video and AAC audio. It’s amazing to me how effecient new compression algorithms are, so I can fit more 4K movies and HD TV shows on a NAS. Of course also, with music reproduction, advantages of 24/96 may be more academic theory.1. As lossy 24/96 would technically result in lower fidelity than lossless 16/44 within the audible band, I do think it’s a “deception” to say it’s hi-res. Although the difference should be inaudible of course.