[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.

[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.

[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.

[George Yohng]

From my findings, it is:

#define SFVIDEOPLUGIN_CAPS_RGBFLOAT 0x00000800

Note, that after this flag you cannot use anymore CSFARGBReadWritePtr class. A new class is required.

If you recompile a plugin, then delete a key in the registry, so that Vegas recognizes it as a floating-point enabled plugin:

HKEY_CURRENT_USER\Software\Sony Creative Software\Vegas Pro\10.0\Metrics\DXImageTransCache.1