View Full Version : Vector adaptive per-pixel deinterlacing - can it be done with avisynth?
tre31
4th April 2007, 09:05
Vector adaptive per-pixel deinterlacing (yes what ATI's AVIVO uses on x1xxx cards, and yes they are obviously patented and protected by NDA's) - can it be done with avisynth or whats the closet/highest quality deinterlacer (and possible spatial noise reduction) there is for avisynth.
Examples would be appreciated as I don't have a degree in avisynth scripting/extensive video compression math knowledge.
If not, well IMHO, its the best deinterlacing/clearest picture I have seen on MPEG-2 dvb-t source material (yes I've tried and am using purevideo atm and find it too be inferior - onboard gfx - until I get another ATI card), I just would like too achieve the same kind of effect using avisynth too get better quality encodes.
Thoughts, comments, theories, much appreciated :)
Didée
4th April 2007, 09:35
The deinterlacer said-to-be of highest quality is MCBob, which is to find in the flow of this thread (http://forum.doom9.org/showthread.php?t=117025). Direct link to the latest version (http://home.arcor.de/dhanselmann/_stuff/MCBob_v03c.avs).
Beware, it is an extremely slow filter, lightyears away from realtime processing!
OTOH, I'm confident that it uses more sophisticated technics than ATI does. ;)
tre31
4th April 2007, 10:33
Thanks, any chance you have a example usage for me too work with? (I'm just not sure how too import scripts - syntax) and example parameters too the function - meanings of it all (couldn't find any documentation on your site).
Cheers :)
btw. speed is not really an issue as far as I'm concerned I use multithreaded xvid encoding on a moderately overclocked Opteron165 @ 2250mhz with 1gb ddr600 (250fsb mem is 100% stable .. higher requires better cooling - ie. water - expensive atm).
Didée
4th April 2007, 11:11
Things like speeding up Xvid by multithreading, and such, is of no concern in that respect. With MCBob (which cannot be run multithreaded), we're talking of strrrong hardware needs to process faster than one frame per second. :D
tre31
4th April 2007, 11:23
Things like speeding up Xvid by multithreading, and such, is of no concern in that respect. With MCBob (which cannot be run multithreaded), we're talking of strrrong hardware needs to process faster than one frame per second. :D
heh, fair enough, no examples?, can't seem too get removegrain too work atm (testing in AvsP for the moment).
Removegrain: invalid mode 20 line 222 in mcbob_v03.avs (Removegrain 01/05/2005)
latest MCBob_v03c.avs
using avisynth 2.5.7.0 (yea I know its old from gordianknott).
-------------------
#IMPORTS
Import("F:\Program Files\AviSynth 2.5\plugins\MCBob_v03c.avs")
# PLUGINS
LoadPlugin("F:\Program Files\AviSynth 2.5\plugins\mvtools.dll")
LoadPlugin("F:\Program Files\AviSynth 2.5\plugins\EEDI2.dll")
LoadPlugin("F:\Program Files\AviSynth 2.5\plugins\RemoveGrain.dll")
LoadPlugin("F:\Program Files\AviSynth 2.5\plugins\medianblur.dll")
LoadPlugin("F:\Program Files\AviSynth 2.5\plugins\mt_masktools.dll")
LoadPlugin("f:\PROGRA~1\GORDIA~1\DGMPGDec\DGDecode.dll")
LoadPlugin("f:\PROGRA~1\GORDIA~1\AviSynthPlugins\decomb.dll")
mpeg2source("I:\tv_captures\Mythbusters-Cell.Phone.Destruction.d2v")
mcbob()
crop(2,0,714,572)
LanczosResize(640,352)
Undot() #might remove that depending on your denoising quality..
----------
Didée
4th April 2007, 11:29
Oh, Mythbusters. Use SeparateFields().SelectEven(). IMO, that's quality enough for that nonsense content. ;)
Regarding RemoveGrain, see here (http://forum.doom9.org/showthread.php?p=976573#post976573).
tre31
4th April 2007, 11:41
[QUOTE=Didée;979316]Oh, Mythbusters. Use SeparateFields().SelectEven(). IMO, that's quality enough for that nonsense content. ;)
its just a test, got plenty others too encode (builds up pretty quickly), btw thx for the quick replies, good too see a dev who actively supports his work :)
got it working now, think it will take me some time too figure out how too work it though...
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.