Log in

View Full Version : MVBob field order...


joshbm
21st September 2005, 17:23
I just forgot, I heard somewhere that MVBob only works with Top Field First, so in order to use it to deinterlace NTSC DV, you need to switch from Bottom Field First using:

doubleweave().selectodd()

Is this correct?

Regards,
Josh

Revgen
21st September 2005, 17:35
Use Trim() to encode a sample and find out.

I've had a few problems with some BFF material and mvbob myself awhile back.

joshbm
21st September 2005, 17:41
How would that help? Or what am I looking for?

Revgen
21st September 2005, 18:04
Try something like this.

doubleweave().selectodd()
assumetff()
Trim(beginningframe,ending frame) #If you have a 29.97FPS source then using Trim(0,300) will encode the first 10 seconds of your clip.
mvbob()

mvbob is a veerrry slooow filter. Using the Trim function makes sure you can do a short encode to see if the doubleweave().selectodd() parameter helps.

joshbm
21st September 2005, 18:08
Visually there is hardly any difference. I will encode two samples.

Revgen
21st September 2005, 18:19
In my experience, BFF material is sometimes more jerky when it's processed by mvbob. It's not very noticible in still shots.

joshbm
21st September 2005, 18:22
Hmmm both samples are moving and are fluid. One difference I see is 1 file is *slightly* larger than the other.

Revgen
21st September 2005, 18:25
Thats good. Like I said, some BFF material has problems with mvbob. Yours obviously doesn't.

joshbm
21st September 2005, 18:32
Shouldn't all BFF material have problems though, if MVBob was intended for TFF?

Revgen
21st September 2005, 18:35
For better or for worse, Sometimes programs don't do what they are supposed to do.

In this case, it looks like it's for the better.:)

EDIT: I guess if you really wanted to know you could talk to Scharfi's Brain when he's around. He did much of the work.