Crash Deinterlacer.. settings??

DJPadre wrote on 5/30/2006, 8:32 AM
ive tried afew different settign configurations and i find that this deinterlacer is MUCH sharper than the Vegas one. On a plasma or a LDC projector, the difference IS noticable, so i want to start using this as an oupt vide effect.

Now ive tried different settings, but for some reason, either my motion getss too choppy, or too blurry....

it seems the interpolation of the 2 fields into the single frame (im in Pal Land) arent very accurate or more than likely, its taking ONE field and deinterlacing it, and using THAT as the Frame (as opposed to interpolating teh 2 fields)

any thoughts?? Ive read Chans write up of this (i think it was his) but im yet to be totally satisfied with the results. Also i found that slowmotion becomes EXTREMLY choppy.

When shooting native with teh DVX, thers no probem, but when tryin to combine interlaced footage with tehnative 25p, the difference is vastly noticable.

any thoughts are appreciated

Comments

DJPadre wrote on 6/1/2006, 7:12 AM
anyone?
GregFlowers wrote on 6/1/2006, 10:19 AM
Here are some instructions I saved from a previous thread. I have not tested these personally but the person who posted it seemed to like the results.

Quote:
Getting the right settings is a little tricky.
For HDV material I suggest you start your own experiments from the following setup:
"Motion processing" -> "Field only"
"Compare color channels" -> On
"Use cubic for interpolation" -> On
"Motion map denoising" -> On
"Motion threshold" -> 5
"Scene change threshold" -> 100
All other boxes should be unchecked.

Again, this works way better than any of Vegas' own deinterlacers.
End quote
DJPadre wrote on 6/1/2006, 2:52 PM
These are the settings im currently using, however i find with motion threshold set to 5, that choppiness IS slightly more obvious, but put it to 6, and its as clean as a whistle. Also the recomended 10-15 is useless IMO as combing is ugly and VERY noticable

Another thing i noticed yove mentioned Motion porcessing @ field only . im using frame and field and find that this has worked quite well in the past..

hmm.. i think more testing is required...