PDA

View Full Version : Nandub help


jerets
3rd December 2003, 22:49
I'm getting some noise in my final divx encodes and am not sure what kind of noise it is (misqueto, artifacts, etc) and what might correct it.
http://divxpic.freewebspace.com/images/divx.jpg

From the screenshot above, the noise circled in green is a clear noise and sort of lays on top in one place (even while other figures move about) until the scene moves it. This seems to be happening a lot.

The noise circled in blue is a multi-colored fuzz and most appears within areas of motion.

I'm capturing from TV at 702x480, encoding at 1100 bitrate, and using an avs script for my filters:

LoadPlugin("D:\avisynth\UnDot.dll")
LoadPlugin("D:\avisynth\New\TomsMoComp.dll")
AVISource("d:\Capture.avi")
TomsMoComp(1,5,1)
Undot()
Crop(2,12,-2,-4)
LanczosResize(512,384)

I switched to TomsMoComp instead of KernelDeint b/c less dots and color fuzz seem to appear. Not really sure what it is...

Any suggestions or advice?
Thanks so much
Jerets =)

iago
4th December 2003, 01:04
Typical divx3 artifacts. Imho, there's not much you can do about them. Use another codec.

Wolfman
4th December 2003, 01:13
capture at lower res 702 is pointless 356 is better. divx3 is being dug up with the dinosaurs!

jerets
4th December 2003, 21:16
thanks guys. i've switched to xvid and it made a difference =)
Thanks again,
Jerets

esby
6th December 2003, 02:14
I guess the problem must be coming from persistant noisy frames,
which increase the probability that the codec goof...

I don't know about the resolution used for capture,
not capturing anything myself,
but 352*XXX is definitely LQ,
and according to some guides i read
(including the capture one),
they suggests to use hq resolution when you can,
even if you are capturing from a vhs
(due to the difference of analogic vs numeric resolution)...

And of course, even if you think div3 is being dug up to the dinosaur,
i should reminds you that they got extinct 65 millions of years ago :)
and not two-three years ago :)
Seriously speaking the difference between the results may be smaller than you think...
Of couse in case of bad source and // or very low bitrate, new codecs are definitely better now...

esby

PS: and of course, filtering affects the compression, so if you modify your filter chain,
some problems might be gone (and some might appear :devil:)