Is TMPGEnc Source Range Not Accurate?

[heyjjjaded]

When encoding my home videos from AVI to MPEG2 with TMPGEnc Plus, I am noticing that the start & end points are occasionally a bit off from what I selected in the Source Range option. Is this normal? Is there a better way to be more precise in selecting the start & end points of my videos? Thank You!

[duhmez]

A beter way indeed. Frameserve the video with avisynth would be an excellent way of getting precise cuts. Recommend you also install avisynthesizer , and VCF2AVS to add in the process. yte another way is frameserve from virtualdub. This process is all done with a gui and will be easier and quicker and produce the resukts you need.

[sacajaweeda]

Another vote for Avisynth

[heyjjjaded]

I'll take a look at Avisynth. Thanks guys.

[housepig]

what is your source footage that you are using for input?

I've done a lot of videos where I captured in multiple parts (to minimize the effects of dropped frames), and used the source range section in TMPG to make single-frame-level cuts (ie part #1 ends on frame 500. part 2 starts on frame 475. I set the source range for part 2 to frame #501 and encode) and I never had any problems with it drifiting or not starting / stopping on the frames I entered.

source vids were usually full-D1, 29.97fps 720x480 avi files using the Huffyuv codec.

[heyjjjaded]

housepig -
I'm doing it just like you. These are our family home videos that I am transferring in about 10 minute-segments to minimize dropped frames and audio sync problems. After a few more tries with TMPGEnc Plus, I am starting to think that the 2 or 3 problems I had with start & end points may have just been human error/my fault. I've always loved the quality of the TMPGEnc Plus encoding and now I think that the minimal problems I was having were my own fault. Thanks.