I have to laugh, one of my mates is an audiophool. Nice guy, but I think he believed everything the sales guy told him. Has all the gold plated, woo woo cables etc... Claims he has a golden ear but was unable to hear that his record player turns a little too fast. I was listening to a song I had heard many. many times and told him it's slightly too fast. He didn't believe me.
Anyway, what I'd love to know from people smarter than I am is this... He streams all his music to his overpriced premium sound system via a Bluetooth DAC. Does Bluetooth recompress audio and result in degradation of the original source material?
I mean it sounds perfectly fine. I have a Bowers and Wilkins audio system in my car which sounds phenomenal but I still stream to it using Bluetooth. I'd just be curious to know if there is any real perceivable difference in audio quality versus playing music directly from a phone via the audio output.
There are two things that could be a problem with Bluetooth (or any digital transfer system);
The former is, generally, not a problem in unidirectional audio transfer, even if it's "live" -- we cope pretty well with the multiple second delay in terrestrial TV. (until the radio transmission of same sports event is 2 seconds earlier...) Basically we have no reference as to "when" and then we have to accept what's coming at us as "now", FSVO. For prerecorded media, it's of course mostly irrelevant.
The latter is of course more complicated; it depends on EMI levels, distance (mostly as distance tends to introduce more line-of-sight challenges), physical barriers to radio waves et c.
Actually, I lied. There
is a third thing, and that it is that Bluetooth is vertically integrated. There are only those applications in the various OSI equivalent layers as the standards owner of Bluetooth saw fit to include. This means that there's a scant few audio codecs specified for Bluetooth audio, and given a decent RF link, it's mostly about comparing codecs and their performance. You don't get 2mbit/s AES3 bit-clean 24bit/48KHz, no matter how hard you try.
If your BT link is APT-X compatible
in both ends (there's a negotiation, so you might end up lower), though, it's practically transparent. I've been on the fringes of some serious testing of this at a former employer, and the data supports APT-X at 576kbit/s as pretty wide open. The earlier SBC standard might not be as transparent. There are a few other newer standards that look to be promising, but IMNSHO the APT-X is your best bet.
Also you need to think about the encode-decode chain in entirety. Since the BT link, as observed above, requires recoding, you have at minimum a storage format -> BT recode -> BT decode chain to factor in. If you listen to streaming radio, the best case probably is more like:
Linear sound file or live transmission (both at 48KHz 24-bit) goes into processing for streaming and then to the live stream encoder, coming out as AAC 192kbit (highest encoding standard at previous employer), which is received by your phone, recoded to a Bluetooth transport format, sent over the BT link, and then unpacked and played back.
If it's a "normal" show, it's more like a 384kbit MPEG2 file played back; the L24 storage option is reserved for classical music.
Phew!
The mere thought that the directional arrows on your
Ethernet cable would need to be correctly oriented in this is criminally insane.