MC noise removal script

[Nightshiver]

I get this error: "There is no function named 'MVAnalyseMulti' "
I have all the latest plugins.

[talen9]

Did you read the announcement of this version?

Originally Posted by Spuds

First is that it has been changed to run with the version of mvtools that josey_wells created, so the function is now called mc_spuds_mvt. It will not run with the last official version of mv_tools, you need the 1.9.6.1+ branch.

You'll find it in the MVTools thread, look at the last posts, not the first one.

[Nightshiver]

what does the +branch mean? On page 49 of the discussion, there are several links to several different versions of 1.9.6.1, but I think the correct one is the 1.9.6.1 final, right?

[Ranguvar]

Get the last posted one by josey_wells

[moviefan]

When I use MC_Spuds_mvt, I still have dancing pixels left in static flat areas... Even when I enable postprocessing, there is movement left and the picture gets blurred more... Is there a way to remove this dithering even more in FLAT AREAS without touching other parts of the picture and harming sharpness in detailed areas?

By the way: I use prefilter=3, frames=1-3 (tried all of them), sharpp=3, blocksize=16, overlap=4-8 any my source is 720x576p

[Ranguvar]

Try adding a FluxSmoothT. If there's already one in MC_Spuds, use higher settings for it.

[Spuds]

I still have dancing pixels left in static flat areas

You can try various increased settings but you run the risk of killing detail in other areas ... everything is a tradeoff Also various issues are still being worked out on the threaded version of mvtools so be careful.

To further increase cleaning try things like:
(aggressive=true) .. This is a two pass mvdegrain option
(temporal=true) .. Another form of two pass mvdegraining but with special limiting
(flow=true) .. This sometimes helps, I think it hurts more often, but depending on the source you may like its results. It uses mvcompensations in place of mvdegrains
(sharpp=0) .. temporarily turn off sharpening to see if that is what is making the pixels stand out.
(strength=4 or strength=5) with prefilter=2, increasing strength changes several items that may help catch those pixels.

You can also just try (mode="high") or (mode="very high") which does much of the above expect for the sharpp=0

Other options are (postprocess=true) for a final 'dusting' or (chro=true) for full luma and chroma plane processing

If none of that works, post a short clip, it might just need some more specific mvanalysis parameters.

[Spuds]

I made some minor tweaks to the _mvt version of the script and rolled all of those updates (mode, motion compensated pre filter, see changelog for full list) into the original script. I also added a "medium high" mode since the delta from medium to high modes was to big.

Both versions are available here along with the updated help file and change log.

Edit: Updated file at link, had one with the old block/overlap defaults

[mozzle]

First, thanks a lot for your work on this very cool script!

It's effective and it's very fun to play with. Thanks especially for modifying for the new, faster version of MVTools.

I was reviewing the documentation and I believe there might be a typo in the thSAD description. The value range is listed as 0-255.


Thanks again for the update!

[ankurs]

been trying to make mcsharpening() work , i get an error saying invalid arguements to the function mcsharpening() whilst i am putting in the denoised clip , any help ? tips on usage ?t :

edit : i am using the latest mvtools , but i am not denoising from mc_spuds , using udegrain /fft3dgpu and taking the clip from there ..

[Lux Delux]

Awesome Spuds, with the latest MT mvtools my FPS increased by 4 without raising CPU usage (using medium_high with tweaked thsad, which is awesome btw)

only thing, when using sharpp=2 I still get this weird 2px border like thingie in my video, example:



look at the very top zoomed. When using limitedsharpenfaster outside of the script it doesn't happen. Any ideas?

[Didée]

@ ankurs: The way mcsharpening() is layed out, you can not use it "externally" for arbitrary post-processing. It works only for internal usage in MC_Spuds.

(You need either motion vectors or MV-compensated frames for this operation, but you don't have them available when you're starting with source.AnyOfTheMCDenoisers(). Therefore, it's needed to modify the "AnyOfTheMCDenoisers()" script itself.)


@ Lux Delux: Hmm ... that could be caused by some plugin filters that silently don't process the outmost border pixels. Such behaviour can cause a slight "edge" (processed pixels beneath not-processed pixels), which subsequently might get amplified by upfollowing filtering operations.
Just a guess, needs further investigation at which stage that border thingy gets introduced.

[Nikos]

Didée for the contra mcsharpening which is the most suited sharpening routine.
a. mt_lutxy(clp,clp.RemoveGrain(11,-1), "x y == x x x y - abs 16 / 1 2 / ^ 16 * "+Str+"
\ * x y - 2 ^ x y - 2 ^ "+Str+" 100 * 25 / + / * x y - x y - abs / * + ?"), with Srt in the range 0.8-1.5

b. mt_lutxy(clp, clp.RemoveGrain(11,-1), "x x y - "+Str+" * +"), with Srt~1.5

c. the above with Srt=1, mt_lutxy(clp, clp.RemoveGrain(11,-1), "x x y - +")

d. Something else... for sharpening on several frequency ranges, not just a simple 3x3 kernel.

In my test without temporal limiting, the sharpening effect of a is very strong. With temporal limiting, the results are almost identical.

[ankurs]

Originally Posted by Didée

@ ankurs: The way mcsharpening() is layed out, you can not use it "externally" for arbitrary post-processing. It works only for internal usage in MC_Spuds.

(You need either motion vectors or MV-compensated frames for this operation, but you don't have them available when you're starting with source.AnyOfTheMCDenoisers(). Therefore, it's needed to modify the "AnyOfTheMCDenoisers()" script itself.)

so i am supposed to denoise using mc spuds before using mcsharpening ?

noob here , dont know how to internally put mcsharpening in mc_spuds.avs and use it

which mc denoiser i assume ur asking me to edit mc spuds or mc spuds mvt isnt it ?

edit : so dumb of me , got it thanks a lot didee !

[Spuds]

@Lux Delux ... Glad you are seeing the speed increase, the new mvtools is a nice improvement. I'm not sure what would be causing that top line error, could you please let me know how you were calling the script and the clip size? Also does this appear on all clips you process or was that one somehow a special case?

@ankurs ... mcsharpening is inside of mc_spuds and is on by default, you can turn it off with sharpp=0 or change it to contra with sharpp=1 or LSF with sharpp=2. Its not a standalone function as it needs some value information that is calculated from within mc_spuds, notably the motion vectors. Could you make it standalone, yes, is it worth it if not already doing mc work, most likely not.

@Nikos ... Not sure if one is more suited or not, its the old do you like smode=4 or smode=3? I have made a small update to the routine so that it performs the sharpening to an upsized clip, more in full spirit of LSF so the results are now different.

The files at the old link have been updated if you want to give it a try.

[Lux Delux]

Hey Spuds , here's an example where it happens with an NTSC source

mpeg2source("D:\EXTREME_LIMITS\d2v\VTS_01_1.d2v",info=3)
ColorMatrix(hints=true,interlaced=true)

TFM(order=1)
TDecimate()
vinverse()
crop(8,12,-8,-12)

mc_spuds_mvt(mode="medium_high",edgeclean=true,edm_lo=25,edm_hi=25,thsad=200,sharpp=2)

or a different PAL

mpeg2source("D:\BATMAN_1966\d2v\VTS_01_1.d2v",info=3)
ColorMatrix(hints=true)

crop(4,14,-4,-14)

mc_spuds_mvt(mode="high",thsad=170,sharpp=2)

BTW is no one else experiencing this? So I know whether it's perhaps a .dll that screws up with the rest.

[Didée]

Aahh ... the script is adding black borders to pad the input clip to mod16 resolutions. Black borders introduce a hard edge, that can cause unwanted effects.
Instead, try padding by repeating the border pixels:

  # calculate the appropriate borders so its width and height are mod 16, these will be removed later
  x_temp      = ab16(clp.width)
  x1          = round(x_temp / 2.0)
  x0          = int(x_temp - x1)
  y_temp      = ab16(clp.height)
  y1          = round(y_temp / 2.0)
  y0          = int(y_temp - y1)
  
  # add blank borders (to improve frame edge processsing and make the clip mod 16), we will remove these at the end.  
  # clp = clp.addborders(x0,y0,x1,y1)  
  clp = clp.pointresize( clp.width()+x_temp, clp.height()+y_temp, -x0, -y0, clp.width()+x_temp+.001, clp.height()+y_temp+.001 )
  nullclp = blankclip(clp)

("+.001" is there for compatibility with Avisynth 2.5.6, not needed for 2.5.8)

This should improve on the issue given that the borders of the input clip are clean. However, if there're any dark pixels left over from original borders, YMMV.

[Lux Delux]

I'll try it out once a current encode using MC is finished

[Didée]

Oops, there was an error in the suggested modification (I misinterpreted what ab16() is calculating).

Code above has been corrected.

[Lux Delux]

Can't find any borders for now so it seems that fixed it. Thanks again Didee