GNOME Bugzilla – Bug 132746
mp3parse/mpegaudio plugin broken (skips way too much)
Last modified: 2004-12-22 21:47:04 UTC
I've tried running an mp3 file through mp3parse like this in both 0.6 and 0.7.x (cvs-head): gst-launch filesrc location=in.mp3 ! mp3parse ! filesink location=out.mp3 (purpose was to clean mp3 from random rubbish and tags before processing it further). However, the output mp3parse produces contains noticable skips when played, so something is not working right. Source 1: (has clean mpeg audio frame sync at beginning): filesize 4303306 mp3.in (source, contains ID3v1 tag at the end) 4302889 mp3.out-0.6 (sounds like source) 4214403 mp3.out-0.7 (has at least 1 audible skip or error/second) Source 2: (first clean mpeg audio frame sync at byte 252): filesize 3393919 mpeg.in (source, has no ID3 tags) 3393411 mpeg.out-0.6 (sounds like source) 3320635 mpeg.out-0.7 (constant audible skips) So it looks like there has been a regression since 0.6.4 and 0.7.x-cvs-HEAD. Cheers -Tim
I worked on that, I probably broke something.
We're sometimes parsing one byte too much, the header indicates a certain length but the frame is really one byte shorter... We probably committed a fix for this in 0.6.x but forgot to apply it to HEAD, too. Or I accidently removed it, dunno... Working on it.
Fixed