3 ms·
Yeah, memory on these devices tends to be pretty tight. The other challenge with buffering ahead so much is that if you do skip, you’ve basically used your ener
by vlovich123 3y ago
Yeah, memory on these devices tends to be pretty tight. The other challenge with buffering ahead so much is that if you do skip, you’ve basically used your energy budget for 0 value. You’d have to make the argument that there’s net savings, but that would only materialize with predictions that are right enough that the savings outweigh the times you lose (e.g. a simplest heuristic would be if the audio stream has been live for 5 seconds without skipping, send the available buffer at faster than realtime).
- spockz 3y agoIIRC, Spotify applies a similar strategy also for deciding which music to already fetch from the servers when listening to a playlist to minimise the gap between pressing next song and actual playback. It seems like it should be exactly the same algorithm for sending it to the headset, with the exception of other sounds like notifications/calls.