Log in

View Full Version : PeachSmoother, GuavaC. and Cnr2 - Artefacts: Settings wrong?


nbarzgar
18th February 2009, 12:34
Hello everyone,

I've got a vhs-tape-capture (PAL, 704x576, PicVideo MJPEG) on which I used the following script:
video=DirectShowSource("D:\xx.avi", audio=false)
audio=DirectShowSource("D:\xx.avi", video=false)
audiodub(video,audio)
Trim(803,74020)
ConvertToYUY2()
GuavaComb("PAL",4)
PeachSmoother(NoiseReduction=25)
Cnr2()
I first tried to put Guava after Peach and encoded to mpeg2 with CCE and got strange artefacts on places as the fingers (or see the side of the nose) in this image:

http://www.barzgaran.de/imgs/Snapshot001_kl.jpg

But the reverse order, i.e. Guava first, Peach afterwards produces the same, so the error seems to be something else...

Can anyone tell me what's wrong? I presume either the filters used, their order or the settings must be responsible in some way... :( Or is it an interlacing problem?
Help will be very much appreciated!

Leak
18th February 2009, 12:38
I don't think anyone is going to be able to help you without a bit of the AVI file you're working from. Could you please post a sample?

Also, are you sure that artifact isn't in your original file too? Or rather - it looks like deinterlacing gone wrong to me...

nbarzgar
18th February 2009, 14:29
Thanks for the fast answer.

No, it's not in the original file, here you'll find a clip (http://www.barzgaran.de/files/sample.avi).
Also info about the original file from MediaInfo:
General
Complete name : D:\xer\Liebesinsel_MJPEG.avi
Format : AVI
Format/Info : Audio Video Interleave
Format profile : OpenDML
File size : 9.18 GiB
Duration : 54mn 31s
Overall bit rate : 24.1 Mbps

Video
Format : M-JPEG
Codec ID : MJPG
Duration : 54mn 31s
Bit rate : 22.5 Mbps
Width : 704 pixels
Height : 576 pixels
Display aspect ratio : 1.222
Frame rate : 24.998 fps
Resolution : 24 bits
Scan type : Interlaced
Scan order : Top Field First
Bits/(Pixel*Frame) : 2.221
Stream size : 8.58 GiB (93%)

Audio
Format : PCM
Format settings, Endianness : Little
Format settings, Sign : Unsigned
Codec ID : 1
Codec ID/Hint : Microsoft
Duration : 54mn 31s
Bit rate mode : Constant
Bit rate : 1 536 Kbps
Channel(s) : 2 channels
Sampling rate : 48.0 KHz
Resolution : 16 bits
Stream size : 599 MiB (6%)
Interleave, duration : 104 ms (2.60 video frames)
Interleave, preload duration : 207 ms

I would not expect faulty de-interlacing to be the problem, since I didn't de-interlace. I also tried DirectShowSource and AviSource in the script - still the same...
:confused:

Didée
18th February 2009, 15:59
From GuavaComb's ReadMe:
Recall
An integer from 0 to 99; 85 by default

This is the really important setting. It decides just how far back into the past the Guava will look in order to confirm that there’s really some shimmering going on. Set it high (above 75%) to avoid artifacts in scenes with repetitive motion. Set it higher (above 85%) to avoid problems with ticker tapes. But don’t set it too high (above 95%), or it’ll need a long time for the filter to kick in.
Recall is in range 0~100. A setting of '75' to '85' is "safe". You have it at '4'. That's like "begging to produce artifacts" ...

Any particular reason why you're working with very old filters like those? A simple FFT3DFilter probably can do much more good than any of those ancient filters.

nbarzgar
18th February 2009, 16:19
@Didée:
Great, thanks, I had overlooked that part... :o
Well, my system isn't the fastest you can get these days... 1.8 Ghz CPU (Pentium 4) and I need it for more than 'just' video-encoding, so I try to find the best compromise between quality and speed... All the FFT3D filters I know and tried were extreeemley slow on my system and sometimes it would take 5x realtime to encode a movie.
The Guava setting I used is from somewhere I don't recall ( ;) ) now... I was in haste when setting up, so I just might have accidentally switched values between filters (i.e. from help-files...)

Anyway, this solves the problem!
I tried Guava's default setting (Recall=85) and there were still specks of black artefacts, but with 'Recall' set to 90 they are gone.

Well, thanks once again and so long!
EDIT: Have FFT3D filters become any faster and would you know of one and could point me to it? I love the quality of the output, there's no denying it! EDIT

Sagekilla
18th February 2009, 21:24
If speed is an issue, you can (If you have a nvidia or ATI card from the past 4 years or so) try the GPU version of FFT3DFilter.

nbarzgar
19th February 2009, 08:02
Thanks, I have downloaded it and the preview seems to be as fast as with the script I used before! Niiiice....
So hopefully, after figuring out the meaning of the settings, I will use it profitably... ;)
:thanks: