Mpeg Conversion stutter problem - TMPGEnc

[Delta3000]

Hi all, I've searched for help regarding this, but none of it seems relevent for me.

I am doing (possibly the most simple?) conversion process in TMPGEnc: converting 29.97fps SVCD mpeg to 29.97fps NTSC DVD. But I am getting a very slightly stutter picture output - its almost like there are frames missing.

Everyone else Ive seen getting this problem have been converting avi's > DVD or doing framerate conversions, but not in this case. It has happened for the last 3 movies I've changed, and they're all similar to this:

480x480 29.97fps > 352x480 29.97fps @3500kb/s bitrate, m2v+wav

I use the NTSC normal wizard, and I don't alter any of TMPGEnc's default settings other than the filesize at the end to allow for 2 halves of the movie to fit on one DVD.

I've compared the original mpeg with the m2v file on my pc and the stutter is there, so I can rule out any process other than the TMPGEnc conversion. Can anyone help?

Thanks in advance.

[teegee420]

Try using the opposite of the field order selected the first time. If it was originally top field first, try bottom field first, and vice versa. Of course this will involve re-encoding so you may want to create a short clip with a fair amount of motion in the scene.

[Delta3000]

Thanks.

I just tried that and theres no difference Its not show stoppingly bad, but I notice it and it annoys me...

[teegee420]

Try opening the svcd mpeg with FLASkmpeg. See if it shows a detected frame rate off 23.976. If it does, then the frame rate conversion to 29.97 could be causing the problem.

[Delta3000]

Ok cool I've done that, and what I see is:

Fps: NTSC 29.97fps
Detected fps: FILM 23.97fps

Im not sure which it is here... If its 23.97, does this mean I should use reverse 3:2 pulldown instead of interlace when converting? Or do I choose 3:2 in the advanced properties of TMPGEnc (a little confused about this process tbh)?

As a side question, what would you use this Flask program for over any other?

[teegee420]

If its 23.97, does this mean I should use reverse 3:2 pulldown instead of interlace when converting? Or do I choose 3:2 in the advanced properties of TMPGEnc (a little confused about this process tbh)?

Let me preface by saying that this is just a theory of mine. I can't guarantee my suggestion will yield your desired outcome. That said, here's how I would set up TMPGEnc:

As a side question, what would you use this Flask program for over any other?

Before I discovered Virtualdub MPEG2 I used to use FlaskMPEG to convert mpeg-2 to DivX and XviD. It just so happened I remembered that it could detect 3:2 pulldown.

[Delta3000]

Thanks, that looks like it would do the trick if TMPGEnc would let me change the framerate in that window you linked... ehehe.

[Delta3000]

Oh no wait, I changed the "content of movie" to film movie and thats now given me all the values I need as per your post. Im off to try this now, I'll let you know how I got on :>

[Delta3000]

It seems to have worked a treat! Thanks for the help teegee420

[teegee420]

Well I'll be damned! One of my hunches actually turned out to be correct. Glad you got things working.

[Delta3000]

Yeah!

At least it has removed the constant stammer, however it still jerks a little from time to time - more so when it has cutscene or fast action takes place, but it gets a grip of itself after a few seconds. Does this mean I have to do a slow motion search conversion in tmpgenc as opposed to a fast one? Or is there an easier (read: quicker) way? /crosses fingers

[teegee420]

You could try using a slower motion estimation but it will take much longer to encode and there's really no guarantee it will even work. You may want to experiment on a short clip.