3 ms·
The audio compression / limiting can be done client-side, at playback time, offloading the cost of the operation
by dcwca 8y ago
The audio compression / limiting can be done client-side, at playback time, offloading the cost of the operation
- Drdrdrq 8y agoEven better, the whole limiting could be done client side, in OS or browser.
- CamperBob2 8y agoTrue, but that would involve modifications to the decode side of the audio codec. That's where the feature should be implemented (if not in the OS itself) but it's apparently not there. It needs to be supported on every platform, and deploying it wouldn't be anyone's idea of trivial. On the server side, they could maintain a separate compressed audio track and switch to it when requested. They should have the ability to do that anyway for alternate languages and commentaries and such. Whether it would be more cost-effective to maintain a separate set of compressed tracks or to decode/compress/re-encode on the fly, I don't know. It might be tempting to maintain caches of compressed tracks created on demand. That way they'd almost never incur a runtime penalty on the server, and also wouldn't have to pay a lot for storage. More than a weekend's worth of work at that point, though.