[MEncoder-users] Any recent changes that could affect MPEG 2 muxing?

[L. Lee]

On 3/23/11 3:29 PM, "Reimar Döffinger" <Reimar.Doeffinger at gmx.de> wrote:

> On Wed, Mar 23, 2011 at 12:58:24AM -0500, L. Lee wrote:
>> If I execute a mux command to adjust A/V sync in an MPEG 2 stream such as
>> mencoder [inputfile.mpg] -ovc copy -oac copy -ofps 24000/1001 -of mpeg
>> -mpegopts format=dvd:tsaf:adelay=-200:muxrate=40000 -o [outputfile.mpg]
>> using MEncoder svn r32924 (as well as quite a few previous versions),
>> everything works well.
>> 
>> If, however, I execute that command using r33094, the audio tempo appears to
>> be increased greatly, demolishing sync, and the command progress output
>> includes many duplicate frame notifications. The visual output remains
>> unaffected.
>> 
>> Has something changed that can be accommodated by adjusting any of the above
>> command options? The source video is 24 fps with 6-channel audio (AC3).
>> Thanks.
> 
> Mencoder A/V sync code was changed, though I think it should not affect
> the copy case.
> However I think you should always use -mc 0 -noskip if you copy both
> audio and video, and using -ofps probably is a bad idea as well.


Thanks, I tried all of your suggestions, but the problem remains, with
today's SVN as well as with r33094. But, since giving the entire matter some
more thought, I am not at all sure that I have used the mpeg 2 mux function
since building mplayer/mencoder on my system began requiring an internal git
instance of ffmpeg.

I can get the latest version of ffmpeg using svn checkout, but when I point
the mplayer build configuration toward it, I get this message:

"You have an outdated FFmpeg SVN checkout in ffmpeg/, please (re)move or
replace it"

So I wonder if that might be related to my problem. Can you recommend a
build option that would allow me to specify existing ffmpeg source rather
than the one furnished using the mplayer/mencoder git method (which is at
least somewhat different)?

Thanks again.

Laine Lee