View Full Version : Blocking / grain around edges
dragon_warrior
8th July 2011, 03:06
Hi everyone. I just want to know what those 'blocking' in the shot is actually called, and how to get rid of it. Thanks :thanks:
Actual size: http://15.imagebam.com/download.php?ID=136510829&salt=65a66f&sec=e8d97e&filesize=269033&filename=9.png
2x upsized using Spline36Resize: http://35.imagebam.com/download/2YJMr9RFetuDaJskIubMWQ/13652/136510832/11.png
Sample: http://www.multiupload.com/WBRV981N3N
-TiLT-
8th July 2011, 03:15
Possibly it is Mosquito-Noise
http://www.pcmag.com/encyclopedia_term/0,2542,t=mosquito+noise&i=55914,00.asp
Ghitulescu
8th July 2011, 07:30
Increase the bitrate during encoding, to discard less data (that has to be "guesstimate" later on).
dragon_warrior
8th July 2011, 10:16
Possibly it is Mosquito-Noise
http://www.pcmag.com/encyclopedia_term/0,2542,t=mosquito+noise&i=55914,00.asp
Thanks but what filter I should use? The site algolith.org seems unavailable to me
Increase the bitrate during encoding, to discard less data (that has to be "guesstimate" later on).
You mean to higher the constant rate factor?
Ghitulescu
8th July 2011, 10:34
So one have to also "guesstimate" that you talk about x264? Probably, but there are here better experts than me to give you hints on configuring x264, despite quality is personal.
pandy
8th July 2011, 10:50
Reduce edge "sharpness" (anti-alias filter before encoding should help), increase bitrate use better encoder.
dragon_warrior
9th July 2011, 00:44
Yep, I was about to encode it using x264 encoder. After testing with various anti-aliasing filters, I could say it didn't help much :(
*edit: Another problem coming up. Anyone mind telling me what it is? Thanks
http://36.imagebam.com/download/wOGDWZMmvoelawKwZZhiug/13977/139764987/1.png
http://11.imagebam.com/download.php?ID=139765002&salt=2dc432&sec=33ff44&filesize=477527&filename=2.png
http://36.imagebam.com/download/hIchZlD9hu0ZdoPlan0uPA/13977/139765055/3.png
Sample: http://www.multiupload.com/FZ45J51FY5
pandy
12th July 2011, 10:26
thumbails - to small to see anything except Fergie ;)
Ghitulescu
12th July 2011, 10:32
Assuming these are the result of your encoding (as opposed to be the source for your encoding), increase the bitrate.
Didée
12th July 2011, 10:54
Seems like a typical case of poooor mpeg-2 compression.
FFT3dFilter probably can make it smooooth (blurry). MDegrain with FFT3d-prefilter (e.g. TemporalDegrain() or MCTemporalDenoise()) would be worth trying.
But as you know, without sample(s) it's hard to predict which filter will or will not "bite".
dragon_warrior
13th July 2011, 10:27
Seems like a typical case of poooor mpeg-2 compression.
FFT3dFilter probably can make it smooooth (blurry). MDegrain with FFT3d-prefilter (e.g. TemporalDegrain() or MCTemporalDenoise()) would be worth trying.
But as you know, without sample(s) it's hard to predict which filter will or will not "bite".
Samples added, :)
Taurus
13th July 2011, 12:10
The sample is from the source?
I wonder why the TMPGEncoder standard quantization matrix was used...
Yeah, at heavy action the encoder got to its limit. Blocking and smearing.
My opinion: use a good deinterlacer (TempGaussMC_beta2 or QTGMC) and leave the rest as it is....
Didée
13th July 2011, 13:10
You are suggesting to deinterlace sources that are telecined (and therefore should be IVTC'ed instead deinterlaced) ?
Taurus
13th July 2011, 13:45
You are suggesting to deinterlace sources that are telecined (and therefore should be IVTC'ed instead deinterlaced) ?
Sorry, you are right.
Never trust DGIndex and Mediainfo :devil::confused:
Just your own two eyes :p
dragon_warrior
13th July 2011, 13:52
The only idea I could think of is :
tfm(pp=0)
o=last
y=o.unknownfilter() #an efficient mosquito-noise remover
replaceframessimple(o,y,mappings=[...]
Consequently, only bad frames are processed while the good ones remain untouched, but I haven't found that 'unknownfilter' yet :D
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.