Log in

View Full Version : Seeking help on what filter to use for "chroma" like noise.


FulciLives
13th February 2007, 09:34
Hello !!!

I have this fairly well encoded h264/AVC video file that I copied from my computer to my Pioneer DVD recorder (DVR-531H-s) using the S-Video output of my Nvidia GeForce PCX 5300 graphics card. I did it this way because of DRM issues keeping me from being able to convert the video file "as is" on the computer.

Unfortunately I guess the Video Output of my graphics card is not that great and I got this weird "chroma" noise like "pattern" in the video. I originally set the DEFLICKER option to ZERO which the Nvidia help file said to do for DVD playback. The pattern was VERY bad. I then set the DEFLICKER option to 100% and it is much less pronounced now but still visible.

I have uploaded an image of the DVD so you can see what it is I am talking about. Basically I ripped the DVD and run it through DGIndex to get a D2V project file and created a simple script so that I could load it into VirtualDubMod then did a copy and paste to Photoshop and saved as a JPEG with 100% quality. I did resize the DVD from 720x480 to 852x480 as it is 16x9 WS NTSC.

I did try Convolution3D but only the most "robust" processing mode (the one called "vhsBQ") seemed to help at all but even then it only helped a bit while overly softening the image.

Any ideas on what AviSynth filter(s) to use in order to clean this up or smooth it out a bit etc.?

Thank you!

- John "FulciLives" Coleman

P.S.
I could upload a small videoclip to RAPIDSHARE.COM if that would help at all. Please note that the video is 29.970fps and doesn't appear to be IVTC'able so I just intend to leave it at 29.970fps when I re-encode with CCE.

*** EDIT ***
Actually the problem is more like "dot crawl" than "chroma noise" ... if you look closely there is a "checkerboard" type pattern over the video.

rfmmars
13th February 2007, 17:11
Do you have the same pattern if hooked to an analog monitor? If so and not seen on your computer monitor, then the graphics or capture card is at fault.

I have seen this on a 7130 chipset capture card where the provided software was at fault. Changing to DeScaler let me reset the card and the problem was gone.

Richard
photorecall.net

FulciLives
13th February 2007, 18:17
Do you have the same pattern if hooked to an analog monitor? If so and not seen on your computer monitor, then the graphics or capture card is at fault.

I have seen this on a 7130 chipset capture card where the provided software was at fault. Changing to DeScaler let me reset the card and the problem was gone.

Richard
photorecall.net
Well in order to capture the video to DVD I simply played it back through my Nvidia graphics card to a stand alone DVD recorder using the S-Video output of the Nvidia graphics card.

If I understand you correctly then what you have said does not apply to my situation.

- John "FulciLives" Coleman

Chainmax
14th February 2007, 03:07
That does seem to look like dotcrawl. I recommend you to use DeDot() right after loading the source and DeGrainMedian() somewhere after IVTCing/Deinterlacing if the video is not progressive and anywhere else if it is. You will probably need to give DeGrainMedian a bit more strength, check its readme for easy intrustionc on how to do so. After than, you will probably need to use LimitedSharpenFaster, followed by some slight AddGrain.

FulciLives
14th February 2007, 07:26
That does seem to look like dotcrawl. I recommend you to use DeDot() right after loading the source and DeGrainMedian() somewhere after IVTCing/Deinterlacing if the video is not progressive and anywhere else if it is. You will probably need to give DeGrainMedian a bit more strength, check its readme for easy intrustionc on how to do so. After than, you will probably need to use LimitedSharpenFaster, followed by some slight AddGrain.
Sorry to sound so clueless but I was at the:

http://avisynth.org/warpenterprises/

I see no filter called DeDot

Also what filter for the LimitedSharpenFaster function?

I do already have the DeGrainMedian and AddGrain filters.

I see there is a filter called UnDot ... should I try that?

Thanks!

- John "FulciLives" Coleman

foxyshadis
14th February 2007, 17:57
LimitedSharpen (http://avisynth.org/mediawiki/LimitedSharpen) (YAY WIKI'S BACK)

Weird that DeDot isn't there, though you can usually find such things by googling "avisynth <plugin name>". In this case, you don't even need it, RemoveGrain(1) is identical and faster. (wrong)

FulciLives
15th February 2007, 05:45
Thank you!

- John "FulciLives" Coleman

Chainmax
15th February 2007, 15:46
foxyshadis, if I understand correctly, RemoveGrain(mode=1) is just a noise remover and if it does indeed remove dotcrawl, it's a side-effect. In Any case, as per a recommendation made by Mug Funky a long time ago, I stand by my recommendation to use DeDot() before IVTCing/Deinterlacing and DeGrainMedian after IVTCing/Deinterlacing. Your recommendation makes me think I should add RemoveGrain(mode=5) for extremely difficult cases where not even those two can undo the damage, so thanks for that :) http://smilies.vidahost.com/otn/wink/thumb.gif.
Here's the download link for DeDot YV12 (http://nullinfo.s21.xrea.com/#DeDot_YV12).

foxyshadis
15th February 2007, 20:00
DeDot = RemoveGrain(1), they're completely equivalent. Same algorithm, same effect, RG just does it faster. RemoveGrain started out as a way to extend DeDot's median clipping into stronger denoise effects, but mode 1 is still the same.

There's also a mode, um, 6? 7? that's just mode 1 on even/odd fields, for interlaced material, if that's an issue. (incorrect again)

BigDid
15th February 2007, 20:23
DeDot = RemoveGrain(1), they're completely equivalent...
Hi Foxy,

Hummm, are you sure not mistaking with undot?
See Kassandro explanation:
http://forum.doom9.org/showthread.php?p=525984#post525984

More on dedot:
http://forum.doom9.org/showthread.php?t=98219

Did

foxyshadis
15th February 2007, 22:26
Well, obviously ignore everything I said, then. Ugh, maybe I need more sleep.

BigDid
15th February 2007, 22:43
Well, obviously ignore everything I said, then.
The grey color for edited/corrected/out of date/unaccurate text is a good idea :)
Ugh, maybe I need more sleep.
Have a good night then.

Did

Chainmax
16th February 2007, 03:24
Don't sweat it, foxyshadis: you're one of the very few remaining veteran members with lots of knowledge and who treats us in a very nice and polite matter. The "dollar bill" praise also holds true in your case :) http://smilies.vidahost.com/otn/wink/thumb.gif.

Hellworm
16th February 2007, 21:52
defreq(source,fx=45,fy=-50,dx=5,dy=5,fx2=45,fy2=50,dx2=5,dy2=5)

Edit:
this ones better
defreq(fx=45,fy=-50,dx=10,dy=10,fx2=45,fy2=50,dx2=10,dy2=10,sharp=0,sharp2=0)
This does also remove the last remainig patterns, introduced by the sharpening, which is default at 50. (picture is the old code)