*Curious* What ended up causing that infamous "timing screwed" pitch shift issue when seeking that's been fixed in 4.0?

[literaldehyde]

**Just curious about the technical reasons behind it, if anyone knows.**

I'm referring to the bug where when seeking rapidly in an audio track, particularly .mp3 files, the pitch would distort (usually lower) for a few seconds before correcting itself. In the debug, it would show lines like:

Code: Select all

playback too late: up-sampling timing screwed (drift: ) playback too late: up-sampling

I've noticed this bug for the better part of a decade, cross-platform (Win + Android), and I remember it being immune to all the different audio output module, resampler, and time-stretching options.

What ended up causing it and how'd you guys fix it?

Cheers!