TemporalDegrainV2

[tebasuna51]

Originally Posted by joearmstrong

If I understand meAlg settings correctly, then hexagonal search is used by default. Using meAlg=7 should select umh (Uneven Multi Hexagonal search) and give a little quality boost. In my tests it was just a bit slower than the default meAlg=4.

1- Exhaustive search
2- Diamond search
3- Square search
4- Hexagonal search
5- Star-shaped search
6- Successive Elimination Algorithm (SEA)
7- Uneven Multi Hexagonal search (UMH)

Is this correct? I read that from https://forum.doom9.org/showthread.php?p=693742

Don't mistake meAlg with me x264 parameter showed in the post https://forum.doom9.org/showthread.php?p=693742

meAlg in TemporalDegrain-v2.3.4 is used like:

...
Search = meAlg
...
MAnalyse( isb=true, multi=true, delta=maxTR, blksize=BlockSize, overlap=Overlap, search=Search, ...

And search in MAnalyse is not exactly like me parameter:

search = 0 : 'OneTimeSearch'. searchparam is the step between each vectors tried ( if searchparam is superior to 1, step will be progressively refined ).
search = 1 : 'NStepSearch'. N is set by searchparam. It's the most well known of the MV search algorithm.
search = 2 : Logarithmic search, also named Diamond Search. searchparam is the initial step search, there again, it is refined progressively.
search = 3 : Exhaustive search, searchparam is the radius (square side is 2*radius+1). It is slow, but it gives the best results, SAD-wise.
search = 4 : Hexagon search, searchparam is the range. (similar to x264).
search = 5 : Uneven Multi Hexagon (UMH) search, searchparam is the range. (similar to x264).
search = 6 : pure Horizontal exhaustive search, searchparam is the radius (width is 2*radius+1).
search = 7 : pure Vertical exhaustive search, searchparam is the radius (height is 2*radius+1).

Then UMH is obtained with meAlg = 5

[joearmstrong]

Thank you for your help, tebasuna51! TemporalDegrain2's avsi-file linked to that page at meAlg parameters - I misunderstood.

I also tested again the scene change issue with noisier frames - ErazorTT's tip (post 181) to use degrainTR=3 and postMix helped a lot. For me this solved the issue.

So, I finally found my perfect settings for better compressibility:
SetFilterMTMode("TemporalDegrain2", MT_MULTI_INSTANCE)
ConvertBits(16)
crop(...)
TemporalDegrain2 (degrainTR=3, meAlg=5, postmix=50)
ConvertBits(8, dither=0)
Prefetch()

[Sharc]

TemporalDegrain2 throws an error when filtering interlaced footage like

separatefields()
e=selecteven().TemporalDegrain2()
o=selectodd().Temporaldegrain2()
interleave(e,o).weave()

The problem seems to be with multiple calls to QTGMC.

Any suggestion (other than deinterlacing)?

[Selur]

How can one call multiple TemporalDegrain2 instances in one script? (used in example to filter top and then bottom fields while not deinterlacing beforehand)
Since ReuseGlobals and ReplaceGlobals are statically set to false 'DT_SetUserGlobal' atm. TemporalDegrain2 crashes with:

"Multiple calls to QTGMC, set PrevGlobals="Replace" or read documentation on 'Multiple QTGMC Calls'"

(side note: the error message should be adjusted to not refer to QTGMC)

Is there a way to clean a global variable in Avisynth?

Cu Selur

[lollo2]

With AviSynth 2.60 and TD2 version 2.2.1 I did the following (second change seems appropriate):

# reference: http://forum.doom9.net/showthread.php?p=1890163#post1890163
#
# added IsAvisynthPlus = (FindStr(LCase(VersionString()), "avisynth+") > 0) || (FindStr(LCase(VersionString()), "avisynth neo") > 0)
# and changed
# from inHighBits = input.BitsPerComponent()>8
# to   inHighBits = IsAvisynthPlus && input.BitsPerComponent()>8
# to run with AviSynth 2.6 instead of AviSynth+ bypassing the "no function named 'BitsPerComponent" error
#
# changed
# from ReplaceGlobals = false
# to   ReplaceGlobals = true
# to solve QTGMC error "Multiple calls to QTGMC, set PrevGlobals="Replace" or read documentation on 'Multiple QTGMC Calls'"

[Selur]

Would be nice if the latest version would also be adjusted accordingly.

[Sharc]

Originally Posted by lollo2

# change
# from ReplaceGlobals = false
# to ReplaceGlobals = true
# to solve QTGMC error "Multiple calls to QTGMC, set PrevGlobals="Replace" or read documentation on 'Multiple QTGMC Calls'"

Thanks! This did the trick.

[Selur]

Sure, but it would probably be better to make it configurable since Reuse might make sense too (when applying TemporalDegrain2 two times in a row,...)

[ErazorTT]

New update which lets process luma and chorma differently. I found this to be helpfull when the chroma planes are much noisier (or have a drifferent type of grain) than the luma plane. Here is such an example.

That is the original:


This is after adjusting the settings for a clean luma (grainLevel=2,degrainTR=2,postFFT=1,postSigma=2):

It is very clear how much chroma noise is left. And if you compare with the original, you see that the chroma noise is also of completly different nature, noise "blobs" are much bigger than on the luma plane.

After setting the new parameter divSADc=1 and adjusting the new parameter postSigmaC to 8 (grainLevel=2,degrainTR=2,postFFT=1,postSigma=2,divSADc=1,postSigmaC=8):

The parameter postSigmaC allows to set the strength of the fft post processing to a separate value for the chroma planes. This will however invoke two calls which will slow down the processing significantly.

A viable solution without the performance impact would be to only set divSADc=1, which will yield the following result (grainLevel=2,degrainTR=2,postFFT=1,postSigma=2,divSADc=1):

[Dogway]

I know those yellow stain artifacts, I used to clean them with NeatVideo before which worked very good, but I just ported CCD(), gave it a try and found it to perform very good.

src=last
CCD(30,HD=true)
CombinePlanes(src, last, src, planes="YUV")

[kedautinh12]

I seen different between 2.4.3 and 2.5.1 in list download about changelogs and DT_BM3D function

[ErazorTT]

I removed again the paramter divSADc to make things easier for the user. Improved cleanup of the chroma planes generally. No performance impact (<1% speed difference).
The right selection of grainLevel has now however somewhat gained in importance.

With the same parameters as in the second picture of my previous post this leads to the following result (grainLevel=2,degrainTR=2,postFFT=1,postSigma=2):

This result is right inbetween the last two pictures of my previous post!

[kedautinh12]

After got latest ver i got errors when use with postFFT=4 i got what 'devID' means, with postFFT=5 i got what 'devID' means and what 'cuda' means

[ErazorTT]

Yeah, right. I fixed it now in v2.6.2.

[StvG]

v2.6.2 - line #483:

ch ? output.MatchClip(a) : output.mergechroma(a)

What is the filter MatchClip?

[kedautinh12]

Originally Posted by StvG

v2.6.2 - line #483:

ch ? output.MatchClip(a) : output.mergechroma(a)

What is the filter MatchClip?

It's is script from Dogway
https://github.com/Dogway/Avisynth-S...Main.avsi#L110

And other scripts from Dogway to work MatchClip functions

[StvG]

Thanks. I did see the optional plugins.

[ErazorTT]

main change is that by default its now possible to use multiple instances. For example for using different settings on different parts of the clip. Depending on the settings, this will need a lot of memory!

[mastrboy]

Is there a github or similar page for this? This forum is very slow at approving attachements: Attachments Pending Approval: File Type: zip TemporalDegrain-v2.6.3.zip

[Zetti]

You can grab it from his Google Drive in post 1