Deinterlacer plugin for Vegas 10 (Yadif)

[Danny Hays]

Thanks. Is this any different than setting your deinterlace method to interpolate? They look exactly the same to me.

[Matt Crowley]

Not sure about this plugin’s implementation (I have Movie Studio so can’t try it) but the original Yadif (which I use in Media Player Classic) can deinterlace 60i to 60p for example (instead of the standard 60i to 30p), and uses some clever edge/motion detection to actually produce a full-resolution frame from each field, or properly blend together the two fields of a frame even if there is motion that would normally result in combing/ghosting.

I’m not sure (and the help doesn’t really explain), but I guess Vegas’s “blend” mode simply slots two fields together into an output frame (potential for combing where there’s motion), and the “interpolate” mode simply discards one field, and fills in the gaps in the remaining field by copying the lines (with loss of vertical resolution). There could well be more to it though, and I hope there is.

[George Yohng]

To reply to both posts –

About Yadif: it works similarly to Vegas internal ‘Interpolate Fields’, but will generally provide much sharper results, which appear more ‘High Definition’ due to edge-directed interpolation and motion masking.

Vegas does not allow me to double the framerate. I neglected to mention it in the post, but I mentioned that in readme.txt.

So from the original Yadif, only modes 0 and 2 are available.

I need Vegas to query each frame twice with an indication which field is being processed, but found no way to obtain a fractional frame position or a field number.

Regarding settings – it’s reasonable to keep everything by default. I converted original Yadif parameters for subtle tuning, which in most cases is not necessary.

First setting ‘Temporal and Temporal&Spatial’ can make a difference on some clips, where e.g. several interlaced frames repeat, or when there is mostly a static picture.

Here is a detailed explanation of yadif:
https://trac.handbrake.fr/wiki/yadif

The last setting (parity) will take either the upper field or the lower field and interpolate the missing one. In a few camcorders one field has a better quality than the other – then changing this parameter would be preferable.

The middle setting (field order) – I hope to implement framerate doubling some day, so that it can make an importance. But right now one should keep it at its default value.

Thanks,
George.

[James Farnum]

Tried this out in Vegas 10 and it works very well. Great tool!

This might be a stupid question, but is there any way to apply the plugin to the finished, edited clip on the timeline so that the whole film (not just individual files) is processed prior to rendering?
(Selecting all files in the project media bin, right-clicking, selecting media fx… / yadif only seems to process one file, not all of them.

Thanks for helping out a newbie.

[George Yohng]

Please redownload yadif archive from my site. I have added the script to automate this procedure.

Check readme or the website page on how to use it.

[James Farnum]

Thank you very much, George. The script works very well.

One problem I’m having:

Sony Vegas Pro 10.0 shuts down after rendering only a few minutes with a low memory warning — even on short 3 minute clips. Even after restarting my PC and with no other processes running. I have an Intel i7 quad core 920 @ 2.67 GHz with 3 GB RAM (XP Professional). I don’t have this problem even when running processor-intensive plugins like Magic Bullet Looks, etc.

Do you have any idea what could be causing this? (I use your default setting via your script.)

Thanks for any insights.

[George Yohng]

Just one question – are those Magic Bullet plugins OFX or old Vegas style plugins?

I ran rendering with Vegas 64-bit with 30 clips, all with yadif, project length approx 10 minutes in length.

Memory use of Vegas process was steady in the range 450-550MB, and it wasn’t increasing steadily.

I wonder if you may submit this query to Vegas support. Yadif plugin has a source code included, so that they can see that there is nothing extraordinary happening there in order to cause memory leaking.

[James Farnum]

Thanks for your reply, George.

I did some more tests and discovered it was not YADIF causing the problem, but the COMBINATION of YADIF, Magic Bullet Looks and Sony Unsharp Mask. That used more than 800 MB of memory, causing total free RAM to dip below 1300 MB. Using YADIF alone, memeory use was a bit more than 600 MB.

Using all three, render time for a two minute clip would have been over three hours! But, of course, rendering broke off after a few minutes.

Do you know of any way to render with YADIF, then re-render with other plugins while still retaining the YADIF effect in the file? I’d rather render twice and get a complete file than render once with three plugins and get constant breakdowns.

Thanks!