Log in

View Full Version : Improving "stuttering"


carlmart
1st March 2009, 11:51
This hasn't got to do with any specific project, but I noticed something I call "stuttering" or "choppy" effect in movements, particularly evident in pans and subject movements.

I've had it even in videos I shot myself, when going from the mov edit to m2v. As if there were frames missing for the movement or as if the movement, pan or subject, is fragmented in several persisting frames. That's what makes it look "choppy" or "stuttered". Let's hope you understand what I mean.

This is sometimes more evident in PAL to NTSC conversions.

Is there any avisynth filter or plugin that deals with it and improves it somehow?

Guest
1st March 2009, 15:30
There are too many possible causes to give you a generic solution. You need to post about a specific case, giving a sample of the source material and describing how you processed it.

carlmart
1st March 2009, 16:07
There are too many possible causes to give you a generic solution. You need to post about a specific case, giving a sample of the source material and describing how you processed it.

Yes, I understand. This is something I remember happened when I converted PAL stuff shot with my Z1 camera to NTSC and edited all together with NT stuff.

Perhaps I would have to wait till it happens again to sample it here. I remembered about it when I saw some mention on another topic about this choppy effect, but I didn't want to interfere with my own concerns and I didn't have a specific case to work on.

Guest
1st March 2009, 16:20
Converting PAL to NTSC using non-motion-compensated methods will introduce judder, which could be called "choppiness".

carlmart
1st March 2009, 16:32
Converting PAL to NTSC using non-motion-compensated methods will introduce judder, which could be called "choppiness".

OK. Until now I have using Procoder as my conversion program.

How do you deal with judder? What plugins might help compensate it?

Guest
1st March 2009, 18:00
You can't compensate it, but only avoid it.

Use motion-compensated standards conversion instead of frame/field duplication.

carlmart
1st March 2009, 20:35
You can't compensate it, but only avoid it.

Use motion-compensated standards conversion instead of frame/field duplication.

Good answer. How do I do that? Through a specific program or through avisynth?

Alex_ander
1st March 2009, 20:51
How do I do that? Through a specific program or through avisynth?
For fresh framerate conversion (not for repairing dropped frames) you can use MFlowFPS function of mvtools2 plugin for AviSynth.
http://avisynth.org.ru/mvtools/mvtools2.html