Log in

View Full Version : Removing these combing(?) artifacts


turbojet
4th November 2013, 07:16
http://i.imgur.com/JD8fKiXl.jpg (http://imgur.com/JD8fKiX)

I'm not sure if this is combing or some other artifact but after trying about 10 deinterlacers I could not find anything that worked.

Sample at http://www.sendspace.com/file/s6yyra if anyone wants to take a stab at it.

manono
4th November 2013, 11:00
Those aren't interlacing artifacts, but low bitrate artifacts. Maybe try Deblock_QED on it.

It IVTC's cleanly and shouldn't be deinterlaced at all

Guest
4th November 2013, 13:21
Not sure about that being low bitrate artifacts. It looks like somebody did a bad deinterlacing on it, or processed interlaced video as if it was progressive or something. So, turbojet, please tell us more about your source...where you got it and how it was captured/processed. It will be better to mitigate this at the root cause.

qwerty1983
4th November 2013, 20:23
I think it's 3:2 pulldown. Try inverse telecine

turbojet
5th November 2013, 00:25
Deblock_QED didn't do much but blur the image http://i.imgur.com/cB8Gf4Xl.jpg (http://imgur.com/cB8Gf4X)

Source is untouched capture from local CBS affiliate, not cable/satellite

It's 3:2 pulldown and the image in OP is after ivtc. If you frame step the 2 dirty frames out of 5 are really bad looking at times in the mpg from OP. The artifacts really pop out after ivtc while playback in WMP/WMC of the original 30fps mpg it doesn't show much at all, although the dirty frames are still there.

Guest
5th November 2013, 00:27
You'll get much better help if you post an unprocessed source sample. It's unbelievable that CBS would broadcast anything so bad as what you have shown. If the unprocessed source looks that bad, then you need to look at your capture process. How did you capture that?

turbojet
5th November 2013, 00:57
Original is in the OP. The capture doesn't look nearly that bad, basically the 2 dirty frames need to be cleaned up to 2 identical clean frames to remove 1. Captured with WMC with no errors according to videoredo. It's not common to find things like this but it is common in a few shows I watch like "The Crazy Ones' here and 'The Blacklist' on NBC.

Guest
5th November 2013, 01:12
Original is in the OP. You said:

"the image in OP is after ivtc"

So which is it?

I'm interested in the *unprocessed* source.

turbojet
5th November 2013, 01:38
Below the image I wrote: Sample at http://www.sendspace.com/file/s6yyra if anyone wants to take a stab at it.

Quoting doesn't work, too short.

Guest
5th November 2013, 02:19
OK, I see.

Then it's a case of garbage in garbage out. There's nothing useful you can do for this.

turbojet
6th November 2013, 00:57
Had a feeling that might be the case after looking at it frame by frame, thanks for taking the time to look.

feisty2
7th November 2013, 15:44
typical mpeg2 compression artifacts
use strong mdegain
something like

a=last
a.smdegrain (tr=12,thsad=2000,thsadc=2000).repair (a,mode=13)

should clean the mess

turbojet
9th November 2013, 08:51
SMDegrain is really slow, I suppose MT could help but I don't plan on spending all that much time for the few times this issue occurs, thanks for the suggestion though.

TDecimate(hybrid=1) does something interesting, it discards the bad frames, mostly, and blends the surrounding good frames. This would work great if instead of blending it would interpolate the surrounding 'good' frames, is that possible?

feisty2
9th November 2013, 12:43
SMDegrain is really slow, I suppose MT could help but I don't plan on spending all that much time for the few times this issue occurs, thanks for the suggestion though.

TDecimate(hybrid=1) does something interesting, it discards the bad frames, mostly, and blends the surrounding good frames. This would work great if instead of blending it would interpolate the surrounding 'good' frames, is that possible?

yes, it's doable,you can simply remove unfixable bad frames and create a good frame by using MFlowFps in MVTool2,but if the frame is in the middle of a high motion, the interpolated frame would be very ugly (artifacts like image dilaceration) so I still suggest using MDegrain instead of MFlowFps, MDegrain can almost fix any kind of bad frames if "thSAD" is high enough

Taurus
9th November 2013, 12:46
typical mpeg2 compression artifacts
use strong mdegain
something like

a=last
a.smdegrain (tr=12,thsad=2000,thsadc=2000).repair (a,mode=13)

should clean the mess

@feisty:
your code snippet gives me:
MAnalyse does not have a named argument "multi"" (SMDegrain v.2.2d)
Using Avisynth 2.6.0.5 MT (SET's build)
mvtools2 v.2.5.11.13
mt_masktools26 2.0.48.0
A simple call "smdegrain()" works fine.

feisty2
9th November 2013, 12:55
@feisty:
your code snippet gives me:
MAnalyse does not have a named argument "multi"" (SMDegrain v.2.2d)
Using Avisynth 2.6.0.5 MT (SET's build)
mvtools2 v.2.5.11.13
mt_masktools26 2.0.48.0
A simple call "smdegrain()" works fine.

you should use MVtools2mod from ditherpackage if tr>3 or lsb=true

Taurus
9th November 2013, 13:08
@feisty2:

Thank you

HeadFi
6th August 2016, 17:15
typical mpeg2 compression artifacts
use strong mdegain
something like

a=last
a.smdegrain (tr=12,thsad=2000,thsadc=2000).repair (a,mode=13)

should clean the mess

Hahaha that is insane radius mate. It will take weeks to encode :))

feisty2
6th August 2016, 17:38
well...
do you really have to resurrect a 3 yrs ago thread...?

kuchikirukia
8th August 2016, 08:23
If OP tried tr=12 he still might be encoding it.