3 ms·
In a sort of off topic question which I had for two years now. If the world, or vast majority of the world are using wireless headphone or speakers. And all us
by ksec 4y ago
In a sort of off topic question which I had for two years now. If the world, or vast majority of the world are using wireless headphone or speakers. And all using codec with the Bluetooth profiles. Shouldn’t we just encode the original music ( Original as in Spotify and Apple Music ) with those codec to avoid conversion lost? Even AAC on Bluetooth headset are not pass through.
Right now everything you listened to on wireless are being re-encoded and decided on the fly.
- NovaDudely 4y agoI second this. It this just a case of the BT audio spec just isn't considered good enough? Or it there another reason?
- dopa42365 4y ago>Or it there another reason? As you can see, no one that isn't forced to has any interest in aptX. Someone (everyone?) in the BT consortium makes/made additional money from using something proprietary. Otherwise BT would just support Opus for many years already.
- NovaDudely 4y agoThere it is! Explains it perfectly. Thanks!
- deleted 4y ago[deleted]
- netr0ute 4y agoIn practice, this can't actually happen because what if you need to play a notification sound? Then you would need two different streams to send to the device without having to reencode everything.
- ksec 4y agoIf I remember correctly Bluetooth Dual Steam is a thing on latest Profile.
- wolpoli 4y agoI can't think of any technical reason why companies cannot work on changing their audio stack and adding to the next Bluetooth specification to support this scenario. I am not sure what would be the benefit to doing this work through, other than saving encoding stop on the device side.
- grishka 4y agoThis but in general this isn't how audio APIs are structured. Some apps would do their own decompression, for example. Some may want to do some additional processing on the PCM data as they play it. In general, all related APIs and apps are built with the expectation that decompression happens locally on the device. It would be a massive undertaking to change that.
- MayeulC 4y agoUsually wireless streams have variable bitrate to deal with packet loss. If there is interference or the receiver is far (both means the signal/noise ratio is lowered), the quality is lowered to require less bandwidth.
- meinheld111 4y agoVariable bitrate is for cost saving/efficiency, no?
- MayeulC 4y agoNot really, encoding (compression) is first and foremost about saving bandwidth. And bandwidth is sometimes limited, for the same reason your Wi-Fi network gets slower as you get further from it, or if interference is received (microwave, neighbors downloading, etc). You have no choice but to reduce bandwidth, or start losing data on the link. Instead, you'll transmit more parity data, and maybe switch to less sensitive encoding schemes. Depending on the bounds you expect to be working in (ie, 10-100 Mbps is more comfortable than 3-5000 kbps), you pretty much need variable bitrate codecs to gracefully handle the (often temporary) bandwidth dips. Everything is a tradeoff: frequency ranges could be enlarged to increase bandwidth at the cost of interference, transmission power at the cost of energy efficiency and interference. And you can't do a lot (except beamforming) against propagation losses, so expected ranges have to be taken into account as well. It is true that the above makes less sense if audio is transmitted ahead of time, which makes it not latency-sensitive. By then though, why bother with that specific encoding? You're usually limited by memory on the receiving side, however.
- Aardwolf 4y agoHow would this work for gaming and phone calls? How would the operating system know whether you're playing music, or gaming/phone calls? Would you want your OS to know whether you're playing music or gaming? (personally I wouldn't, since not for every application it'll be obvious what it is and it's guaranteed OS will make annoying wrong choices)
- justeleblanc 4y ago> Would you want your OS to know whether you're playing music or gaming? ... Is that a trick question? Yes. My OS is not a malevolent entity from which I should hide everything. It's going to know it anyway. Who sends audio packets to the sound card?!
- vetinari 4y agoEasily, just like any other passthrough. It doesn't need to know what the application is, just what the application is trying to do. So application would check the capabilities of the audio sink, compare that with properties of the source, and if they match, just shuffle the buffers without decoding; let that be a concern later in the pipeline (i.e. hardware). Done.
- moogly 4y agoGo with the lowest common denominator (read: quality)? No thank you.
- Melatonic 4y agoNot everything at all is using wireless - think about any home stereo or speaker setup. Also do we really want to move to even LOWER quality codecs for the source material on streaming services? We should be pushing for the opposite - higher quality source material.
- ksec 4y ago> LOWER quality codecs I was thinking of Lower quality codec but with higher bitrate. Instead of source material being 256Kbps AAC, we could be doing 800Kbps with a low latency codec but zero re-encoding.