On Wed, May 27, 2015 at 02:48:10PM +0200, wm4 wrote: > Apparently it can happen that a mp3 file has junk data between id3 tag > and actual mp3 data. Skip this to avoid outputting nonsense timestamps. > (Two packets had the same timestamps, because the mp3 parser failed to > compute a frame duration.) > > In this case, the junk consisted of 1044 bytes of zero, which > incidentally is the same size as normal mp3 frames in this stream. I > suspect the mp3 was edited with some tool which wiped the Xing/LAME > headers. Data near the end of the file suggests it was encoded with > "LAME3.97", but the normal Xing/LAME headers are missing. So this could > be "normal". mpg123 also attempts to skip at least 64KB of junk data by > scanning for headers. > --- > This assumes the stream buffer is not smaller than 64KB + max. mp3 frame > size, or the seeks could turn into a problem. > --- > libavformat/mp3dec.c | 12 ++++++++++++ > 1 file changed, 12 insertions(+)
applied thanks [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The educated differ from the uneducated as much as the living from the dead. -- Aristotle
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
