Hello, I've been ripping and encoding for some time with SmartRipper 2.41/DVDAVI 1.77.3/TMPGEnc 2.58 and I'm having trouble with one aspect: motion jitter. This is especially noticeable with PAL sources, I don't really even notice it with NTSC. It looks like every moving scene is broken into little jumps on the screen, for example, a car that crosses the screen looks like it makes about 4-5 jumps, the motion is not smooth. It makes the produced clips unviewable. I use primarily VBR and data rate over 2 MB/sec. The quality of the output is very clean indeed. The settings I tried so far for motion in Advanced, were Normal and Motion Estimate Search. I haven't tried the Slow and Real Slow Motion search algorithms, primarily because it would take too long but also because I don't see this problem much in NTSC. Is there something I'm missing here? I noticed in DVDAVI that PAL sources are running at 20 fps when choosing Forced Film. NTSC sources have a higher fps. Should I not use Forced Film for PAL? Is that the reason for this jumpiness in the motion? It's really bugging me that I can't tweak this right, and I haven't been able to find other posts here about this problem. I don't want to have to try every little thing, I'm sure someone must have run across this before. Can anyone make some comments on this? TIA
I got it. It was the Forced Film option in DVDAVI. I have no idea why I always had that on, I think it was mentioned in the SVCD Faq.
A change in Framerate using TMPGEnc produces that little freeze ye. Its not even that big of a freeze but as an encoder you would notice it a lot!
I've got the same problem with a particular movie, but I don't use DVDAVI, I only use Tmpgenc Plus. Is it possible to overcome this problem, or can't Tmpgenc Plus fix this problem? Can anyone help me?
Basically it should be ok if u keep the source framerate. You can try other encoders like Canopus ProCoder 2, which has gotten great reviews behind it now!
OK, so this is what works fine for me to prevent motion jitter problems: DVD2AVI: use forced film for NTSC, not for PAL. This always should end up as a 25 fps frameserver output. TMPGEnc: Normal motion search algorithm, of fast Estimate. Either of those is fine for most movies. De-interlace and filter (usually Double) is only necessary on NTSC sources, on PAL sources I find that even if Interlace is detected, no filter is needed on most new sources (except for old movies which are always interlaced). Good luck and happy encoding!
i had same problem for quite a while. not with all the sesions, and could not predict which ones would and which not. i got rid of the trouble by using 2pass VBR instead of CBR in TMPGEnc. RGDs.
