YADIF plug-in .. when working in sections

xberk wrote on 7/2/2014, 10:37 PM
For those familiar with the YADIF plug-in

www.yohng.com/software/yadifvegas.html

I'm working mostly with 1080 60i video. I generally work in sections, render to MXF files 1080 60i and then combine the MXF sections and render to the Internet template 720p. Is it best to apply the YADIF deinterlace to the 1080 60i MXF files or to the the original sections and render to MXF 720p and combine those for the final Internet template 720p?

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

Comments

john_dennis wrote on 7/4/2014, 8:13 AM
You appear to be using the 1080 60i MXF files as low loss intermediates after your rough cuts. The benefit of the Yadif plug-in is better resizing of interlaced material. In this step there is no resizing.

You would be better off leaving your intermediates at 1080 60i if you have other uses for the media at 1080 60i such as Blu-ray or watching from a flash drive attached to your Blu-ray player or smart TV. Seems a shame to change to a lower pixel dimension at the intermediate stage and lose all the other possibilities.
xberk wrote on 7/4/2014, 11:38 AM
Makes sense. Thanks. I thought so but wasn't sure there was some other technical reason it's best to apply the YADIF to the source material.

It's incredibly easy to use the YADIF plug in, especially on the MXF files. Very fast. I even think I'm starting to see the ghosting or double images you guys were talking about on footage with lots of motion.

One possible disadvantage of applying YADIF to the intermediate files is that you can't turn it off for a particular event -- but that's cured easily enough. This is making me much more mindful of the format on all the various media I use in relation to the output needed.

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

jason-duncan wrote on 7/11/2018, 8:38 PM

I just discovered Yadif and I think it's much better than using Blend or Interpolate. I have a silly question; if the original source footage is Lower Field First, do I select LFF in the Field Order dropdown? or do I keep it at the default of HD=upper, SD=lower?

Musicvid wrote on 7/12/2018, 8:47 PM

or do I keep it at the default of HD=upper, SD=lower?

Thats not even a default. Match Media Settings.

jason-duncan wrote on 7/12/2018, 9:12 PM

I guess I'm confused?; every time I open the Yadif plug-in, the dropdown settings are always:

PROCESSING MODE: "temporal & spatial" FIELD ORDER: "hd=upper, sd=lower" PARITY: "lower". So wouldn't that be considered the default settings?

john_dennis wrote on 7/13/2018, 10:39 AM

Use Mediainfo to determine the 1) actual, 2) reported, 3) guessed-at (pick one) field order of your media or look at the field order reported by Vegas when you display the properties of the source file. You want the field order setting in the Yadif plug-in to match the field order of your media.

If a garbage truck runs a red light, t-bones your brand new car and sends you to the hospital, shouting "but the default behavior is to stop when the light is red" won't help your broken leg heal any faster.

jason-duncan wrote on 7/13/2018, 9:20 PM

Vegas reports LFF. But I can't tell what Mediainfo states the

field order is? And since I'm burning this project to a dvd/BD and not uploading online, should I leave it as interlace and just let the player to the deinterlacing? 

john_dennis wrote on 7/14/2018, 12:35 AM

"And since I'm burning this project to a dvd/BD and not uploading online, should I leave it as interlace and just let the player to the deinterlacing?"

Since the target is DVD-Video and/or Blu-ray, there is no reason to de-interlace.

jason-duncan wrote on 7/14/2018, 6:37 PM

99.9% of the posts I've read does say to deinterlace. But I have ran across a few that say not to if output is dvd/BD, so thank you "john_dennis" One problem I have is I'd still like to output to 720, but DVD-A doesn't have an interlace mode at that resolution.

 

Also, can you please guide me to see what Mediainfo says the source footage is as far as Field order goes? 

Musicvid wrote on 7/15/2018, 6:48 AM

Blu-ray authoring in DVDA is 720p, 1080i, which is spec. Some authoring software puts a fake flag for progressive source, but not DVDA. I think I've got that right.