MBAFF Do i need to do anything to it?

[ArcticFox]

Im backing up my blu-ray onto my media server and ive come across some discs which have MBAFF material like BBC Robin Hood and Die Hard.

I have a basic understanding of what MBAFF is but do i need to do anything to the interlaced parts or can i just load them into DGAVCDEC and encode them using MEGUI?

[neuron2]

If you want your final product to be progressive you'll need to deinterlace it in your script. If you want it to remain interlaced, you'll need to use interlaced encoding in MEGUI.

[ArcticFox]

So i should run it through a standard deinterlacer as if it was an interlaced DVD?

Thanks.

[Adub]

Well, yeah. Sort of. Just make sure that you adjust your deinterlacer accordingly to match this source, but it deinterlaces just the same.

[neuron2]

Watch out, though. If it is telecined, then use IVTC instead of deinterlacing.

[ArcticFox]

Ok great thanks for the information.

[AntiJw]

If the MBAFF-source isn't telecined, is the default setting of Yadif() good to use? I can't get any information about TFF or BFF on my MBAFF-source..
Thanks in advance.

[neuron2]

I can't get any information about TFF or BFF on my MBAFF-source..
Sure you can. Do it the old fashioned way:

http://neuron2.net/faq.html#order

[AntiJw]

Sure you can. Do it the old fashioned way:
http://neuron2.net/faq.html#orderThanks again neuron2. I've already encoded a MBAFF-source using Yadif(), which is "order = -1 : field order as Avisynth assumes (default)." Do you think Avisynth's assumption may be correct or should I encode it again, using your safe "old fashioned way"?

[neuron2]

That's not possible to answer without seeing your script, and maybe even not after that.

Always use the manual inspection method I gave to avoid problems.

You can check the field order of your encoding now and if it is correct then you are OK.

[AntiJw]

My AVS looked like this:
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\fft3dfilter211\fft3dfilter.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\dgavcdec102\DGAVCDecode.dll")
Load_Stdcall_Plugin("C:\Program Files\AviSynth 2.5\plugins\yadif_20070722\yadif.dll")

AVCSource("C:\VideosHD\video1.(h264).dga")
Yadif()
Crop(2, 0, -2, -2)
fft3dfilter(sigma=0, bt=5, ow=16, oh=16, sharpen=0.4)
spline36resize(1280,720)

[neuron2]

AVCSource() does not yet detect and pass the field order. It always assumes TFF in the latest version (but watch out, earlier versions assumed BFF!). Almost always, though, AVC sources are TFF, so you are probably OK using version 1.0.2 as you are.

[LoRd_MuldeR]

Try "Yadif(mode=1)" and review the output of your script in a Player or in VirtualDub.

If the field order is okay, you'll see fluid motion. If it's wrong, you will see the video jump forth and back like crazy...

[AntiJw]

I tried
AVCSource("E:\video.dga")
AssumeTFF()
SeparateFields()
and
AVCSource("E:\video.dga")
AssumeBFF()
SeparateFields()
but the only difference when single stepping forward through the motion in VirtualDub was that TFF moved up the frame a pixel each 2nd frame (but didn't continue motion at those frames) while BFF moved down the frame a pixel each 2nd frame (but didn't continue motion at those frames). I didn't notice any "object moving steadily from left to right would move right, then jump back left a little, then move right again, etc."
It seems unlikely that it's a progressive source, because DGAVCIndex and MediaInfo recognizes it as "MBAFF".


EDIT: Thanks LoRd_MuldeR, I'll try that. Now I tried that, and my encoded video had fluid motion.

[neuron2]

but the only difference when single stepping forward through the motion in VirtualDub was that TFF moved up the frame a pixel each 2nd frame (but didn't continue motion at those frames) while BFF moved down the frame a pixel each 2nd frame (but didn't continue motion at those frames). I didn't notice any "object moving steadily from left to right would move right, then jump back left a little, then move right again, etc." Then you have progressive content, and so the field order does not matter.

It seems unlikely that it's a progressive source, because DGAVCIndex and MediaInfo recognizes it as "MBAFF". No, there's no necessary connection between the nature of the content and the method of encoding. You've made the definitive test above. Anyway, it's unlikely that a BluRay film would be interlaced.

And since it is progressive, you have no need for deinterlacing at all!

[AntiJw]

Anyway, it's unlikely that a BluRay film would be interlaced. And since it is progressive, you have no need for deinterlacing at all!The source is a HDTV-capture, not BluRay, although that might not matter?!
Is it bad to deinterlace that source (with Yadif(-1), as I did), or will the encode be as if I wouldn't encode it with deinterlace? I wonder, because if it's bad, then I'll encode it again (without deinterlace).

[paulvdb]

In the opening post you mentioned BBC's Robin Hood. I don't have it on BluRay but I saw it when it aired on BBC HD and the only interlaced parts were the credits at the end of the episodes. Everything else was progressive.

[neuron2]

The source is a HDTV-capture, not BluRay, although that might not matter?! Your first post says this: "Im backing up my blu-ray onto my media server and ive come across some discs which have MBAFF material like BBC Robin Hood and Die Hard."

So, how did you capture the HD material?

Is it bad to deinterlace that source (with Yadif(-1), as I did), or will the encode be as if I wouldn't encode it with deinterlace? I wonder, because if it's bad, then I'll encode it again (without deinterlace). You degrade the quality by deinterlacing unnecessarily. Whether that is bad enough for you to bother re-encoding is a decision only you can make.

[AntiJw]

Your first post says this: "Im backing up my blu-ray onto my media server and ive come across some discs which have MBAFF material like BBC Robin Hood and Die Hard."
So, how did you capture the HD material?

Sorry, I'm not the thread-creator (my source is HDTV-capture). I just didn't want to create a new thread about the same subject (MBAFF).
Thanks, I don't want to "degrade the quality by deinterlacing unnecessarily", so I'll encode it again :-P

[neuron2]

OK, sorry, I didn't notice your thread hijack. :)

[AntiJw]

OK, sorry, I didn't notice your thread hijack. :)Yeah, similar-looking handles (starting with 'A', and no avatar), but the thread is rather old, so I guess it's okey that I hijacked the thread :)