View Full Version : Deinterlacing Summary?
jeffy
26th February 2007, 14:54
I used search so I know that this topic is quite well covered in many posts, however can someone summarize what deinterlacer can produce arftifacts, leave some combing or bob flickering and also make a note about speed and a link to a thread plus latest version?
eg. TomsMoComp - fast, can leave some artifacts,
latest version http://www.trbarry.com/TomsMoComp.zip
thread: http://forum.doom9.org/showthread.php?t=28778
some other: TDeint, LeakKernelDeint, KernelDeint, MCBob, MVBob.... :thanks:
EDIT: also Restore24, CRestore, RePAL, DeBlend etc.
Pookie
26th February 2007, 16:12
You're just the guy to do it, Jeffy. :) How about testing and posting your results?
Thanks in advance...
steve77
26th February 2007, 20:12
You know, I think it's a good idea too, because I found (and still find) it sometimes hard to find various scripts + pros/cons for the various deinterlacers.
MCBob is supposed to be the best for pure interlaced materials, followed by MVBob and then TDeint.
IVTC should only be used for NTSC video with 3 progressive frames followed by two combed.
Pookie said it best though, and you'd be doing the community one hell of a favor, especially the newbies
jeffy
26th February 2007, 20:38
The problem is I am overlooking artifacts, which is bad and the conclusions would be consequently bad. :(
Mug Funky
27th February 2007, 01:57
however can someone summarize what deinterlacer can produce arftifacts, leave some combing or bob flickering and also make a note about speed
(i'm assuming a 50i source for the below stuff)
they all produce artefacts. it all depends what kind. strictly speaking, any kind of visible interpolation is an artefact (artefact meaning evidence of some kind of process having been applied).
deinterlacing in general is a tradeoff between different kinds of artefacts - what are acceptible or not, and that also depends on your desired output.
- straight 50i to 50p for playback without resizing means combs wouldn't be annoying even if some got through. bobbing motion may be more annoying, or crunchy horizontals from "threshold noise" may be more annoying.
- for standards conversion, residual combing is completely unacceptible, as even the smallest visible amount will cause ugly "shimmering bars" when the result is resized. usually in this case bobbing motion is the preferred result because framerate conversion will cause it to happen at a much lower frequency (so it's fine for moving areas). threshold noise is bad here, but not as bad as combing. usually a postprocessor like vinverse is a good thing to use after a deinterlacer in this case.
- for encoding progressive, you're looking for an aesthetic balance, but also have to bear in mind that combing, bobbing and especially threshold noise will all have a negative effect on compression, reducing quality in other places.
- for video projects (you're shooting a short film or something similar), aesthetic quality takes precedence over everything - which makes it subjective and thus different for everybody.
then of course, there's speed considerations.
but to make things simple, by default i use tdeint (with "expand=4" to avoid threshold noise) followed by vinverse. even on HDV stuff i wouldn't go further than that for speed reasons (and quality - interlace is the least of HDV's problems). maybe for something like SDTV that needs to be output to film i'd use mcBob.
hope that gives some kind of idea :)
jeffy
27th February 2007, 07:48
Mug Funky, thank you very much for a good summary. Reminded me, that I should add some other functions to the first post :)
I read TomsMoComp might produce artifacts but until someone (http://forum.doom9.org/showthread.php?t=122698) pointed me where to find them, I didn't see them. Speaking about this thread, does someone please have any idea how to help?
Regarding vinverse function, I was never able to find where to get it, although I saw it used several times in scripts posted here. Could you please tell me where it is?
Terka
27th February 2007, 17:04
look at
http://www.compression.ru/video/deinterlacing/index_en.html
someone tried FieldsKit deint?
DarkT
27th February 2007, 23:15
Yo, I think you might find this usefull:
http://heptium.sh.cvut.cz/~integra/deint/
Terranigma
27th February 2007, 23:23
I think that test was done by scharfis_brain a good while back.
I think This (http://forum.doom9.org/showthread.php?t=117025&page=7) is better since it included mcbob as well. :p
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.