View Full Version : I need a simple deinterlacing advice
sasam
25th August 2005, 15:01
Im a AviSynth novice and I need a advice on which deinterlacing plugin/script should I use.
I capture TV shows (not anime) with lots of noise in 512*384 resolution. With virtualdub I use only smartdeinterlacer but for AviSynth there are so many deinterlacers and I am confused.
I currently use simple Tdeint() function but I dont know on which material Tdeint is good and where not.
For example when I use Tdeint() the picture looks like it has much more noise than the interlaced original, but it is nice with the ultraslow mvbob() and BlendBob() (to restore the framerate) which works 1-2fps. As I understand mvbob is a new kind of very smart deinterlacers. Is there anything like it which doesn't double your framerate?
Im looking for a high quality but not very slow deinterlacer. What plugin/script would you recommend me?
Guest
25th August 2005, 15:05
Try LeakKernelDeint().
Leak
25th August 2005, 15:19
Try LeakKernelDeint().
That's exactly what I was going to recommend... :D
np: Future Sound Of London - Smokin Japanese Babe (ISDN)
Didée
25th August 2005, 15:20
I capture ... in 512*384 resolution.
Too little information about your capturing process to be sure, but it could be that the frame structure is already destroyed beyond hope. You must not change the vertical resolution of 576 (PAL) or 480 (NTSC), unless you're only cropping. Vertical resizing most probably will produce a big mess that is not to repair, if no "interlaced resizing" method is used.
sasam
25th August 2005, 15:37
I use IUvcr and asus tv fm card for PAL B capture and I didn't notice any difference beetwen capturing in full resolution and then resizing. I have leakkerneldeint. So how to use it? Simple AVISource("a.avi").LeakKernelDeint didnt work
MOmonster
25th August 2005, 16:35
You have to set the order (leakkerneldeint(order=1) or 0). Please read the readme, there aren´t so many parameters. ;)
Mug Funky
25th August 2005, 16:50
if your captures have a lot of noise, a deinterlacer will probably be getting thrown off by it. i've attempted to write a wrapper for leakkerneldeint that's noise tolerant, but it's not that good yet :) it'll get better when masktools's expand function gets a horizontal-only mode.
the nicer hardware deinterlacers work this way - noise adaptation and motion adaptation, with kerneldeint-style deinterlacing.
leak or neuron: any chance of modding kerneldeint so it can input a binary mask (in yv12 or y8 of course)? or would the speed not be any different to regular maskedmerge?
mg262
25th August 2005, 16:51
But please also take on board Didée's point: it is very probable that because of your capturing method the video is no longer interlaced. What you're supposed to do is capture in full (vertical) resolution, and then either a) deinterlace and resize or if you want interlaced output b) separate fields, resize, and weave the fields together again.*
If you resize an interlaced clip, either implicitly when capturing or explicitly in the script, the result will be a mess that is not interlaced (and is not strictly speaking progressive either... it's just a mess). There may be resizers that will deal with interlaced content properly, but IIRC the built-in ones don't (someone will correct me pretty quickly on this if I am wrong...).
*b) has subtleties that you will need to deal with... ask if you want to go this way.
sasam
25th August 2005, 17:15
When I capture in full resolution and then resize to my original resolution it is messed up, but when I capture in my original resolution it looks fine.
Mug Funky
26th August 2005, 11:57
that didn't make sense to me...
original resolution (ie what's coming into your capture card) as far as your capture card is concerned is 480 lines*. vertical resolution on TV is not negotiable, and horizontal resolution relies on signal quality. but vertical resolution is always the same.
so if you capture in 640x480 or 704x480, or 720x480, then you'll get the proper interlace structure. if you need to resize vertically, you'll have to separate the fields or deinterlace first, as the odd-even order it extremely important.
this doesn't apply to progressive images of course - they can be resized just fine.
* if you're in PAL land, it'll be 576 lines, but i'm guessing you're in NTSC land.
sasam
26th August 2005, 14:55
Now I use leakkernelbob(order=1,twoway=true).blendbob for deinterlacing. The result is identical to vdub smartdeinterlacer but a bit sharper. It is very fast too. It is good for me because when it blends frames it looses some of the noise.
Is it recommended to use bobing and then debobing like I have done?
mg262
26th August 2005, 15:03
It's difficult to discuss these things in the abstract. Could you provide a short unprocessed, losslessly compressed, clip from your source?
sasam
27th August 2005, 08:07
I am now satisfied with deinterlacing but I have another question. Sometimes on this channel horizontal bars appear and not because of interlacing but something else,they are also visible on TV (regular TV). Is there a filter which can handle this situation shown in the picture:
http://img376.imageshack.us/img376/884/untitled0ea.jpg
Mug Funky
27th August 2005, 09:49
defreq or fanfilter can probably handle that.
when you see it on the teev, does it make a strange noise? ABC melbourne gives a similar looking effect that i've not been able to figure out - almost like a vertical jitter in line placement, but that makes no sense at all...
sasam
27th August 2005, 11:12
It doesnt make any strange noise, it is very static.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.