MDegrain question

[Frank K Abbott]

I just want to be sure of this. Is MDegrain exclusively for interlaced sources because Didée referred to a Mdegain2p script that is better suited for progressive material. That is nearly the case for every script unless the encoder is wanting to compress interlaced or degrains before deinterlacing. In that case is there a MDegrain3p script with MDegrain3?

PS - I tried to use MDegrain2p but I always get an error "there is no function named MVAnalyse"

[Didée]

Old MVTools (v1.x) used the naming scheme MVxxx().
New MVTools (v2.x) use the naming scheme Mxxx().


Generally, MDegrain is for progressive content only. Someone had made a script function "MDegrain2i()" that handles interlaced content more correctly (by internally doing separatefields -> MDegrain -> Weave). (Also with additional even/odd splitting? - can't remember...)

Then, at some other point, someone advised someone else that he doesn't need to do all this vec1=/vec2=/../vecXX=../MDegrain manually, because he could just use the MDegrain2i() function.

At that point I hopped in and warned that that's a bad idea because MDegrain2i is for interlaced content (where the OP was dealing with progressive content), and so I pointed to a MDegrain2p function. (Did I point to, or did I convert the 2i function to 2p ... can't remember.)

[Frank K Abbott]

Oh I see so the MDegrain2i and 2p scripts are for the older MVTools (v1.x). The newer MDegrain uses MVTools (v2.x) which handles progressive content correctly from what I understand.

[Didée]

Both "old" and "new" MVTools handle progressive content correctly.

The point is just that a function specifically made for interlaced content is not good to use on progressive content.

[Frank K Abbott]

Oh I get it now. Thanks Didée! :)