Flux Smoothing + TV Captures + KVCDx3
 

I've been playing around for sometime with the KVCDx3 templates with awesome results from my DVD rips! For these conversions i usually use a temporalsmoother(2,1) just in a hope to increase compression a little.

However, my TV captures (Wintv Go with analogue source using composite in) are proving a little more tricky and I just wanted to ask some questions about how best to apply the filters. I am capturing at 544x576 25fps PAL using huffyuv with AVI_IO and the btwincap drivers. The source seems fairly clean although the usual analgue noise is there. I found that these captures need a far higher bit rate to look good using about 30 mins per Cd. I've been using Fluxsmooth (15,15) and whilst the source now seems nice and clean - occasionaly, usually on peoples faces during motion, a funny strobing artifact is there. My main question therfore, is this due to the filter because i've not de-interlaced my source. Do the filters not work as well with the interlaced tv captures. If so - what deinterlacer should i use - i've tried bob() but it converts my source to 50fps. An example script i would use is:

########

AviSource("D:\Captures\capture_2.00.avi")
ConvertToYUY2()
LegalClip()
FluxSmooth(temporal_threshold=15, spatial_threshold=15)
temporalsmoother(2,1)
LegalClip()

##############

Thanks for some great templates! :D
Jim

Re: Flux Smoothing + TV Captures + KVCDx3
 

I've never tried it, but I imagine you'll get strange (and certainly suboptimal) results if you use FluxSmooth on interlaced material. This holds true for almost all smoothing filters.

Check out the Decomb plugin by Donald Graft. If your material is pure interlaced (i.e. not telecined or hybrid) you can just use the line

FieldDeinterlace()

after AviSource. This will deinterlace while retaining your existing frame rate.

I use TomsMoComp for my captures. There's less visible jagged edges than with FieldDeinterlace or GreedyHMA. The only thing is you'll need to find out if your capture is bottom field or top field first. Mine is bottom field first (the most usual one) so the parms I use are simply (0,0,1).

I use many filters on interlaced materal.... here is an example of how it works. It's really quite simple to fix the problem by taking interlacing to your advantatge. This is what I use for hybrid or interlaced clips to perserve interlacing and apply a good de-noise. If the source was over 95% telecine I would use decomb and this would not be a problem.


SeparateFields()

even = SelectEven().FluxSmooth().PeachSmoother(NoiseReduc tion = 35, Stability = 20, Spatial = 120)
odd = SelectOdd().FluxSmooth().PeachSmoother(NoiseReduct ion = 35, Stability = 20, Spatial = 120)

Interleave(even,odd).Weave()

hey Snowmoon

I tried your little bit of script but Avisynth gives an error at the start of the line that says..... even =

saying it expects a ( or a ,

What am I doing wrong?

Thanks

Many thanks - i'm going to try the SeperateFields option tonight!

One question, how doe one PeachSmooth?

Jim

caish5: Dunno, check the spelling of the commands.

PeachSmoother can be found here... I found it works great on TV captures for stabilizing the picute. Flux or peach by themselves has disadvantages, but together it's quite amazing the noise they can remove without damaging the picture.

http://forum.doom9.org/showthread.php?s=&threadid=36575

NoMoSmooth is a similar idea, but peach appears to be faster and has a good locking algo.


COOL.... while I was writing this I see that ViewFields was ported to avisynth giving up another option..

ViewFields()

FluxSmooth()
PeachSmoother(..)

UnViewFields()

Much simpler. http://www.geocities.com/siwalters_uk/viewfields.html

Cool - will try peach smoother later!

There doesn't appear to be an unViewFields function - never mind.

HEH HEH! Peach Smoother is excellent - really recommend it with seperating the fields - cuts down some jerkyness i was noticing :P

However, my strange strobing effect is still there but i now don't think its related to interlacing. I think its to do with colour and brightness as it only occurs with bright areas on the screen. I have set the brightness and contrast of my capture card fairly low and when viewing the captures on my monitor they are quite dark (these done using huffyuv using yuv). However, the encodes are considerably brighter on my TV with faces being very very bright. Am i doing something wrong - does TMpegenc not like the yuv source? Is there an avisynth script to stop the capture exceeding a colour range?

Cheers,

Jim