jerky video encodes

[dvd_master]

I finished authoring an anime video, which i used CCE to encode the main video with, since it's faster then TMPEG. When watching it on a TV, the video is badly jerky, and some ghosting here and there.

I think it's because the video was interlaced when I put it into CCE, then I just encoded.

I've never had this problem when I first run it through VirtualDub, but I still get that unsupported framesize error which no one seems to have a solution to when imported the .vdr through an avisynth script.

Is there something in CCE that will fix this. All the other stuff I personally made which never were interlace to begin with never had these problems, so I think it's just because the source was interlace.

Thanks for any help.

Edit: Oh, I might add this video jerky problem isn't noticible when watching it on the computer.

[wmansir]

You probably got the field order backwards.

If you still have the .mpv you can run it thru pulldown to reverse it.
Try:

pulldown input.mpv output.mpv -nopulldown -tff even

If you don't have the .mpv you can either extract it from your disc, or re-encode. If you reencode change the Upper Field First setting (or Offset Line in 2.67) in CCE.

[kukyfrope]

i had this exact same problem with my end result encodings, but the above remedy worked flawlessly to fix my videos!

AIW Pro capture (MPEG) --> Premiere edit --> Frame Server --> CCE (encoded as upper-field first, progressive & zig-zag :X ) --> .mpv

the video had bad problems with high movement, but then after reading around the net and thinking about how interlacing worked, i noticed my video seemed to be jumping back and forth. it was indeed the incorrect field-rending order that was screwing me up!

[rs008f]

how do you set CCE to encode upper-field first? I have CCE 2.67. Do you change the Offset Line to 2?

[Kedirekin]

Your question is answered in the CCE FAQ post at the top of this forum.

CCE FAQ (Updated) (http://forum.doom9.org/showthread.php?s=&threadid=53770), questions 10 and 11.

You can also use pulldown.exe to change the field order of your MPG without re-encoding. That's what wmansir's post was about. The FAQ (in question 10) also tells you how to do this using ReStream.

[rs008f]

"Always set "Offset Line" to 0 unless your video is interlaced AND bottom field first in which case you set it to 1. Progressive material is always top field first."
Is there a software that can tell me if the AVI video source is interlaced AND bottom field first OR progressive?

[Kedirekin]

You aren't the first to ask. In fact, this is asked often enough it should maybe be in the FAQ as well.

Here's a thread with a couple of suggestions on determining field order - how to tell up field first or down field first? (http://forum.doom9.org/showthread.php?s=&threadid=69870)

As far as I know there is no reliable programatic way to tell if video is progressive or interlaced. You simply need to rely on your eyes.

[rs008f]

pulldown input.mpv output.mpv -nopulldown -tff even
What does the above command do? Does it change the field order to TFF or BFF? I have a feeling TFF, so changing the field order to BFF would be something like this?
pulldown input.mpv output.mpv -nopulldown -tff odd

[wmansir]

Yes, that is right. But you shouldn't have to run that command with CCE.

Why?

Because CCE ALWAYS outputs odd. If you don't check Upper field first, or set line offset to 1, CCE flags the output odd. If you do either of those things CCE shifts the video by 1 pixel vertically and still flags the output odd.

So running:

pulldown input.mpv output.mpv -nopulldown -tff odd

would have no effect on CCE ouput.

[rs008f]

I ran my CCE MPEG-2 video using pulldown and the options -nopulldown -tff even. It just made the video go faster and goes out of synch with the audio. When I used -tff odd, it made the video slower and jerky and goes out of synch with the audio too. Both were played on my PS2. I guess those options do DO SOMETHING on the videos.

[Hudster]

If you open your original capture AVi in Virtualdub, try moving through the frames one at a time, if it's interlaced it becomes apparent pretty quickly.

[rs008f]

I was told 23.976 fps AVI CANNOT be interlaced, it is ALWAYS progressive, is this true?

[hendrix]

Originally posted by rs008f
I was told 23.976 fps AVI CANNOT be interlaced, it is ALWAYS progressive, is this true?

yes...and if your footage is progressive than it wont matter what field order you encode since progressive footage doesn't use fields...it uses whole frames