digitalFAQ.com Forums [Archives] - Recording Video: Wrong field order?

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)

- Video Capturing / Recording (http://www.digitalfaq.com/archives/capture/)

- - Recording Video: Wrong field order? (http://www.digitalfaq.com/archives/capture/13258-recording-video-wrong.html)

Anerboda

01-27-2005 12:52 AM

Recording Video: Wrong field order?

I'm having a bit of a problem to get my old Hi8 tapes captured to DVD.
My procedure:
Capture with VirtualVCR at 704x576 using PicVideo MJPEG, quality=19.
Using this script:

Code:

AVISource("D:\capture.avi") 

KernelBob(order=1,sharp=true,threshold=7) 

AssumeFrameBased() 

Undot() 

RemoveGrain()

Cnr2()

ConvertToYV12()

Deen()

Letterbox(16,16,16,16)

AssumeBFF() 

SeparateFields() 

SelectEvery(4,1,2) 

Weave()

My capture is TFF hence this line:

Code:

SelectEvery(4,1,2)

I encode with NuEnc, interlaced BFF because of this line in the script:

Code:

AssumeBFF()

but when I watch the movie on my SAP, the movie stutter, like the fields are in the wrong order...?
My question is: doesn't this line

Code:

AssumeBFF()

need to be

Code:

AssumeTFF()

The script is inspired by Boulder here: http://www.kvcd.net/forum/viewtopic.php?t=13768

-Anerboda

Boulder

01-27-2005 02:59 AM

The resulting field order in your original script is TFF. That's because KernelBob outputs BFF, which is then switched to TFF by SeparateFields().SelectEvery(4,1,2).Weave().

Anerboda

01-27-2005 03:35 AM

Quote:

Originally Posted by Boulder

The resulting field order in your original script is TFF. That's because KernelBob outputs BFF, which is then switched to TFF by SeparateFields().SelectEvery(4,1,2).Weave().

That would explain the wrong fieldorder. I encoded interlaced with BFF :cry:
Just to be absolutly sure, this means that I should keep the AssumeBFF, and let NuEnc encode interlaced with TFF?
Is there any way to determine if the resulting mpg has the correct fieldorder, without actually burn it and test it in my SAP?
It could cost a few DVD-R, before I get it right. (I don't have a DVD-RW!)

-Anerboda

Boulder

01-27-2005 04:27 AM

Yep, you can leave the script as it is and encode as TFF. Or you can replace AssumeBFF() with AssumeTFF() and then use SeparateFields().SelectEvery(4,0,3).Weave(). It's the same.

You can see the incorrect field order when you play the clip in PowerDVD for example, at least when auto-deinterlacing is disabled. The motion will be jerky as hell if the field order is incorrect.

incredible

01-27-2005 04:53 AM

You should everytime use the assumexFF() parameter in your capture scripts as avs evrytime uses its default BFF. So avisynth with assumetff() at the beginning gots the right flag for correct further treatment by filters etc. AND also the encoder finally!

Quote:

I encoded interlaced with BFF

You did encode fieldbased BUT the flag of the fieldorder was set to BFF, means you dont have to reencode again, but use restream just to change the Fieldorder Flag in your final encode. Thats just avalue in the seqHeader.

Boulder

01-27-2005 05:01 AM

By the way, there's a new version available:

http://forum.doom9.org/showthread.php?s=&threadid=81322

The plugin's now called LeakKernelDeint so you'll have to delete the old kerneldeint.dll from the plugins folder to avoid problems. The KernelBob function is renamed to LeakKernelBob.

With this version, you can remove AssumeFrameBased from the script as it's already done by the function itself.

Anerboda

01-27-2005 08:39 AM

Quote:

Originally Posted by incredible

Thanks for the tip Inc, it worked like a charm :D

@Boulder, thanks for the link to the version of KernelDeint, now called LeakKernelDeint, I will use that for my next conversion. (I have a lot of Hi8 video tapes that I need to get on DVD-R). Interesting reading in that tread at Doom9 too.

-Anerboda