I switched to the CVS version of mpeg2enc, and while transcoding a NTSC mpeg2 w/ pulldown (via transcode) I got some funny results. The .m2v seemed ok (mplayer reports the correct frame rate), but the resulting multiplexed .mpg has major sync problems - the video gradually falls behind, and mplayer plays it very jerky. I discovered by trial and error that forcing mplayer to play back at 40fps corrected the sync and made it smooth again. None of this happens with mpeg2enc from 1.6.1, or using transcode's built-in mpeg2 encoder. So the obvious question is, is something wrong with the CVS mpeg2enc? I used "mpeg2enc -f 8 -a 2 -F 4 -p -n n" and "mplex -f 8 -V", and I also used tcmplex from transcode.
In what ways can a .m2v file have its framerate screwed up? (and where does 40fps come from?) I just thought it had a single framerate in the header (perhaps with a pulldown flag) followed by a stream of frames. But I dumped a series of stills, and there are no extra or missing frames. I also tried further transcoding using transcode's internal coder, and this seemed to fix the problem. So is this a header problem or do .m2v files store timestamps of some sort that got screwed up? Dan ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
