Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
11th August 2005, 21:34 | #1 | Link |
the dumbest
Join Date: Oct 2002
Location: Malvinas
Posts: 494
|
Is there any way to remove Mpeg2 blocking?
I mean, I've been using a Sony Z1 and although several times it looks quite good, whenever you shoot anything with random changes (like moving water, a lake, a river, etc) blocking becomes terribly noticeable!!!
I had some success removing some percentage of them, but the artifact still remains noticeable..... Any help welcome.... |
11th August 2005, 21:53 | #2 | Link |
Clouded
Join Date: Jul 2003
Location: Cambridge, UK
Posts: 1,148
|
Lots of ways, including one that comes with dgmpgdec (check its documentation); you can find more by searching for "deblocking"...
__________________
a.k.a. Clouded. Come and help by making sure your favourite AVISynth filters and scripts are listed. |
12th August 2005, 03:22 | #5 | Link |
Registered User
Join Date: Feb 2003
Posts: 299
|
Can you give a pic demonstration ?
Curious, -vhelp
__________________
ESC K7S5A / XP 1800+ / Windows 98 ADVC-100[dvio] / WTVGO[avio] / DC10+[avio] / Canon ZR-10 / Delphi 6 Personal / JVC S-VHS HR-S3910U / Durabrand SSS w/ DVD Player STS75E / Sony TRV-22 FithElement/Dogma/BladeRunner/Contact |
12th August 2005, 05:06 | #6 | Link |
Senior Member
Join Date: Apr 2004
Posts: 1,054
|
BlockBuster is a filter that adds Gaussian Noise. The noise is used to help prevent blocks during encoding, not get rid of blocks that are already there.
I have had some good results with SmoothD, but it is still in early development. http://forum.doom9.org/showthread.php?t=84355 Newer versions of FFDShow install an AviSynth filter, ffavisynth. http://forum.doom9.org/showthread.php?s=&threadid=85447 So you can use FFDShow's post processors on your video. I like Nic's deblocker. SPP will remove any block, but it will also blur your video greatly and is very slow. There will be a trade off between blocks and blurring. Last edited by Video Dude; 12th August 2005 at 05:08. |
12th August 2005, 05:48 | #7 | Link |
Huh?
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
|
I use either Deblock(quant=x) from DGDecode.dll or FunkyDeblock(). Both are awesome deblockers. Be sure to try both, some sources are better handled by the former, some by the latter.
I was also recommended Camembert a couple of times. I only tried it once without good results, but then again the material I tried it on is extremely crappy. Give it a try as well. |
12th August 2005, 10:15 | #8 | Link | ||
Clouded
Join Date: Jul 2003
Location: Cambridge, UK
Posts: 1,148
|
Quote:
Myself, I have very rarely had to use deblocking (nearly all my source being ~9000 kbps DVDs). I've tried dgmpgdec in an experiment and it worked extremely well; and on the whole I would tend to stick with it (varying parameters) where possible because in my view there is a very natural approach to take to deblocking and that requires access to the MPEG-2 coefficients (although I am not certain of what method is actually used by the package). But it sounds like you may need something else... Quote:
__________________
a.k.a. Clouded. Come and help by making sure your favourite AVISynth filters and scripts are listed. Last edited by mg262; 12th August 2005 at 12:43. |
||
12th August 2005, 14:01 | #9 | Link |
interlace this!
Join Date: Jun 2003
Location: i'm in ur transfers, addin noise
Posts: 4,555
|
mpeg2source("blah.d2v",cpu=4) can pretty much be a default.
even if the source doesn't show visible blocks, re-encoding will most likely amplify them, possibly into visibility. also you'll get a compression gain from the slight smoothing. although, when the quantizers get really high (like freak b-frames on high-motion bitrate spikes), dgdecode's deblocking may not be enough - it'll simply see the blocks as edges, because they are so severe that to deblock them would be to deblock the good bits of the image, and turn the whole picture into slush. best thing to do in these cases is find a better source, or turn to homebrew solutions (funkydeblock is old as hell, but still works pretty well by all accounts. it'll get rid of "GOP blinking" when you've got a very low bitrate source encoded with closed-GOP). motion-compensation could be a useful trick for a deblocker, but i'm not sure if meaningful motion can be extracted when the source is in the extremes of blocking.
__________________
sucking the life out of your videos since 2004 |
12th August 2005, 18:06 | #10 | Link | |
Huh?
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
|
Quote:
|
|
13th August 2005, 08:02 | #11 | Link |
interlace this!
Join Date: Jun 2003
Location: i'm in ur transfers, addin noise
Posts: 4,555
|
hehe... funkydeblock uses DGdecode/mpeg2source's blind post processing to do the deblocking part. the only difference is the input is "highpassed" first and the deblocking only applied to the higher frequencies, while a temporal smooth is put on the low frequencies to get rid of blinking/pumping from closed-GOP encodes.
to be honest, i don't even know why it works differently to the internal deblocking of mpeg2source, except that it doesn't have access to the per-frame (per block?) quantisers in the original m2v. i guess it makes block-edges more visible to blindpp (is that an oxymoron? being visible to something blind?) so it can work more effectively. though if your source is clean enough (like an mpeg-2 that's above around 4000kbps and comes from a decent mpeg-2 encoder), then cpu=4 should perform faster and more accurately. i'd certainly try cpu=4 before i try funkydeblock
__________________
sucking the life out of your videos since 2004 |
Thread Tools | Search this Thread |
Display Modes | |
|
|