3 ms·
And decoding the whole file, in turn, would be easy in any other use-case (iTunes does this for "gapless playback" calculation) but podcasts are quite often str
by derefr 10y ago
And decoding the whole file, in turn, would be easy in any other use-case (iTunes does this for "gapless playback" calculation) but podcasts are quite often streamed, and only once.
Probably the simplest "clever hack", if Apple wanted to fix this on their own, would be for all the podcast feeds registered through iTMS to get their files retrieved by the iTMS servers once, chewed through to calculate this information, and then all the calculated "keyframe" offsets injected as an opaque extra data field for each feed item of the iTMS-served podcast feed, where the Podcasts app can pick it up.