Right now everything you listened to on wireless are being re-encoded and decided on the fly.
Right now everything you listened to on wireless are being re-encoded and decided on the fly.
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.
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.
... 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?!
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.
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.
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.
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.