Demi9OD
9th September 2007, 19:02
I think I figured out the best way to deal with my telecined ntsc dvds with shitty cuts/fades/edits. This is not for anime or fully interlaced stuff. TFM would always leave me with choppy scenes where it was matching or decimating the wrong frames, and seemed to give bit of a shimmering edge to slowly moving objects. Just through trial and error with lots of different plugins I stumbled on these variables that have lasted me through 6 episodes with 0 mistakes.
CPU goes way up during fades that I know are half/half progressive/interlaced edited together as the deinterlacer kicks into full time gear, and I would definitely not recommend running it in conjunction with seesaw on anything lower than a C2D 2.8ghz.
You will lose audio synch and drop frames on a very long string of interlaced/edited frames if you don't leave enough of a buffer on your overall cpu (50-60%), so drop seesaw if you can't maintain that and turn up the luma sharpening on resize a bit to compensate. The collage pic shows how it spikes on those scenes. I was at ~35% on clean material seconds before.
I cannot work good NR into this script, everything I try screws with avisynth decimating incorrect frames, or has to be done after resize in ffdshow and tears out a good chunk of that 50% buffer I needed to maintain stable during difficult scenes. This could be solved with another 300-400mhz and ffdshow HQDN3D post resize. Any better solutions are welcome.
I think this can work for progressive as well. But for now I'm just decoding in nvidia pv mpeg2 decoder and letting ffdshow handle raw frames for progressive. I don't run any tdeint/tfm for progressive. With nvidia pv set to auto/smart it will just blend the 1% of frames in film that are interlaced, and thats good enough for me so I can use fft3dgpu on film sources.
Feel free to poke holes in this because :stupid: and obviously don't know the real guts behind these plugins. Here is a short clip (http://rapidshare.com/files/54506768/bad_fades.demuxed.rar.html) exemplifying the issues I was trying to fix.
SetMemoryMax(1024)
tdeint(mode=2,order=1,tryWeave=true)
TDecimate(mode=1,hybrid=1,conCycle=1,chroma=false)
#FFT3DGPU(sigma=1.2, precision=0, mode=2) ###?GPU Cannot Keep up with extra frames?
#MT("FluxSmoothT(3)",3) ###Creates incorrect Decimates
MT("SeeSaw(NRlimit=0, NRlimit2=5, Sstr=2.22, Szp=1, Slimit=9, Sdamplo=16, Spower=1, sootheT=95, SdampHi=39)",3)
http://i5.photobucket.com/albums/y167/Demi9OD/IVTC/th_collage.png (http://i5.photobucket.com/albums/y167/Demi9OD/IVTC/collage.png) http://i5.photobucket.com/albums/y167/Demi9OD/IVTC/th_strip.png (http://i5.photobucket.com/albums/y167/Demi9OD/IVTC/strip.png)
CPU goes way up during fades that I know are half/half progressive/interlaced edited together as the deinterlacer kicks into full time gear, and I would definitely not recommend running it in conjunction with seesaw on anything lower than a C2D 2.8ghz.
You will lose audio synch and drop frames on a very long string of interlaced/edited frames if you don't leave enough of a buffer on your overall cpu (50-60%), so drop seesaw if you can't maintain that and turn up the luma sharpening on resize a bit to compensate. The collage pic shows how it spikes on those scenes. I was at ~35% on clean material seconds before.
I cannot work good NR into this script, everything I try screws with avisynth decimating incorrect frames, or has to be done after resize in ffdshow and tears out a good chunk of that 50% buffer I needed to maintain stable during difficult scenes. This could be solved with another 300-400mhz and ffdshow HQDN3D post resize. Any better solutions are welcome.
I think this can work for progressive as well. But for now I'm just decoding in nvidia pv mpeg2 decoder and letting ffdshow handle raw frames for progressive. I don't run any tdeint/tfm for progressive. With nvidia pv set to auto/smart it will just blend the 1% of frames in film that are interlaced, and thats good enough for me so I can use fft3dgpu on film sources.
Feel free to poke holes in this because :stupid: and obviously don't know the real guts behind these plugins. Here is a short clip (http://rapidshare.com/files/54506768/bad_fades.demuxed.rar.html) exemplifying the issues I was trying to fix.
SetMemoryMax(1024)
tdeint(mode=2,order=1,tryWeave=true)
TDecimate(mode=1,hybrid=1,conCycle=1,chroma=false)
#FFT3DGPU(sigma=1.2, precision=0, mode=2) ###?GPU Cannot Keep up with extra frames?
#MT("FluxSmoothT(3)",3) ###Creates incorrect Decimates
MT("SeeSaw(NRlimit=0, NRlimit2=5, Sstr=2.22, Szp=1, Slimit=9, Sdamplo=16, Spower=1, sootheT=95, SdampHi=39)",3)
http://i5.photobucket.com/albums/y167/Demi9OD/IVTC/th_collage.png (http://i5.photobucket.com/albums/y167/Demi9OD/IVTC/collage.png) http://i5.photobucket.com/albums/y167/Demi9OD/IVTC/th_strip.png (http://i5.photobucket.com/albums/y167/Demi9OD/IVTC/strip.png)