[MPlayer-users] [BUG] mencoder -vf softpulldown -oac mp3lame ==> audio corruption?

[D Richard Felker III]

On Sun, Oct 26, 2003 at 01:26:30AM -0800, Corey Hickey wrote:
> [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
> Hi,
> 
> I seem to have run into an odd bug wherein using -vf softpulldown seems
> to cause bad audio distortion for mencoder, with this message:
> 
> Too many video packets in the buffer: (4096 in 8274071 bytes).
> Maybe you are playing a non-interleaved stream/file or the codec failed?
> For AVI files, try to force non-interleaved mode with the -ni option.
> ds_fill_buffer: EOF reached (stream: audio)
> 
> [--full logs uploaded--]
> 
> If I encode the audio to mp3lame, the sound gets distorted at 72
> seconds, and then gets completely bad at 82 seconds. If I use -oac copy,
> the audio sounds fine but the encoded video looks like it "jumps
> backward" a frame every couple seconds.
> 
> Normally, I would have just thought I ripped the disk poorly, clean it
> off, and try again, but mplayer can play the troublesome section without
> a problem, even with -vf softpulldown.
> 
> =================================================
> I am uploading some files to mphq ftp incoming.
> All of the below files are also available at:
> http://bugfood.casa-z.org/mpbug/audio/
> 
> softpulldown-audio-src.vob
>     Unfortunately, I couldn't really cut the beginning off this, so it's
>     61MB :(
> 
> softpulldown-audio-mp3.avi, softpulldown-audio-mp3.log
>     mencoder softpulldown-audio-src.vob -vf softpulldown -ovc lavc \
>     -lavcopts vcodec=mpeg4 -oac mp3lame -ofps 23.976 -o \
>     softpulldown-audio-mp3.avi &> softpulldown-audio-mp3.log
> 
> softpulldown-audio-copy.avi, softpulldown-audio-src.vob
>     mencoder softpulldown-audio-src.vob -vf softpulldown -ovc lavc \
>     -lavcopts vcodec=mpeg4 -oac copy -ofps 23.976 -o \
>     softpulldown-audio-copy.avi &> softpulldown-audio-copy.log
> 
> softpulldown-audio-description.txt
>     The text of this message
> 
> ===================================================
> Now, before anybody reminds me that encoding right after using
> softpulldown is a bad idea, I know that. :) These are just simplified
> test cases.

Encoding with -vf softpulldown and -ofps 23.976 (without any inverse
telecine) is a bad idea. I bet if you remove the -ofps the problem
goes away... :)

I'll try to look at this in more detail soon though.

Rich