Dogway's Filters Packs

[LouieChuckyMerry]

Originally Posted by Boulder

That would most likely be enough. You can doublecheck the output video format by adding Info() after the SMDegrain line and opening the script in VDub for example.

Thanks for your reply. It does seem to be enough; unfortunately, adding Info() after the SMDegrain line doesn't show any info upon opening the script in MeGUI or VirtualDub2 .

EDIT: Adding Info() after the SMDegrain line works on my second computer and shows that it's processing in 16bits. Thanks for the new trick.

Originally Posted by StvG

F3KDB doesn't support native 16-bit (only stacked, interleaved). Repalce it with neo_f3kdb.

Good catch, StvG . That explains quite a bit...

Lucky38: Sorry for the confusion.

[DTL]

Some idea about different prefilters usage (including no-prefiter): At testing QTGMC it was found single prefilter mode can not make all areas better in details. With prefilter-ON some areas get better and others not. With prefilter-OFF it is changed. So I make some function to gather most possible details from several filter runs. With deinterlace processing of QTGMC it also collect most of noise from different filter runs also. But it may be tested with SMDegrain too with different prefilters at single processing. The function GetSharpest() included into M_QTGMC listed at https://forum.doom9.org/showthread.p...88#post2001388 and it uses new plugin MostDiffVal.dll to run. Though I think maybe it can be implemented with all internals of AVS like Layer() instead of Average and Expr() instead of MostDiffVal().

So to run SMDegrain with a set of prefilters (any set may be combined in a chain of GetSharpest(clip1, clip2):

pref1=SMDegrain(prefilter=0)
pref2=SMDegrain(prefilter=1)

GetSharpest(pref1, pref2)

where GetSharpest() is

Function GetSharpest(clip c1, clip c2)
{
  avg=Average(c1.GaussResize(c1.width, c1.height, src_left=0.001, src_top=0.001, p=2), 0.5, c2.GaussResize(c2.width, c2.height, src_left=0.001, src_top=0.001, p=2), 0.5)

  return MostDiffVal(avg, c1, c2)
}

[gispos]

Originally Posted by DTL

Some idea about different prefilters usage (including no-prefiter): At testing QTGMC it was found single prefilter mode can not make all areas better in details. With prefilter-ON some areas get better and others not. With prefilter-OFF it is changed. So I make some function to gather most possible details from several filter runs. With deinterlace processing of QTGMC it also collect most of noise from different filter runs also. But it may be tested with SMDegrain too with different prefilters at single processing. The function GetSharpest() included into M_QTGMC listed at https://forum.doom9.org/showthread.p...88#post2001388 and it uses new plugin MostDiffVal.dll to run. Though I think maybe it can be implemented with all internals of AVS like Layer() instead of Average and Expr() instead of MostDiffVal().

So to run SMDegrain with a set of prefilters (any set may be combined in a chain of GetSharpest(clip1, clip2):

pref1=SMDegrain(prefilter=0)
pref2=SMDegrain(prefilter=1)

GetSharpest(pref1, pref2)

where GetSharpest() is

Function GetSharpest(clip c1, clip c2)
{
  avg=Average(c1.GaussResize(c1.width, c1.height, src_left=0.001, src_top=0.001, p=2), 0.5, c2.GaussResize(c2.width, c2.height, src_left=0.001, src_top=0.001, p=2), 0.5)

  return MostDiffVal(avg, c1, c2)
}

Why isn't it working as expected? It always shows 'c2'

c1=Sharpen(0.80).subtitle("c1")
c2=Sharpen(0.10).subtitle("c2")
GetSharpest(c1, c2)

Edit: The sharper one is returned, but not the subtitle. This confuses me, please clarify.

Edit2: Oh, a combination of both clips will probably be returned. When I use 'a' and 'f' as a subtitle I see that 'a' and 'f' are overlaid.

[DTL]

It works on sample-level granularity from both input clips. So Subtitle text will be mixed (and typically not very well processed as extreme 0 and max values). Better results on natural narrow/limited range.

For test you need to mask-sharpen c1 clip at one area and mask-sharpen c2 clip at different area and process to see if returned both sharpened areas from c1 and c2.

More sad thing about MAnalyse/MDegrain/MCompensate is with different areas grouped MVs errors it also cause different areas global shift (not only fine sharpness lost) so the GetSharpest() will also somehow mix these areas. And with different pre-filters these grouped MVs areas errors also different.

I typically check it as

c1=Process(params1).Subtitle("params1")
c2=Process(params2).Subtitle("params2", align=..some2, not default and not 4)

sh=GetSharpest(c1, c2).Subtitle("gs", align=4)

Interleave(c1, sh, c2)

And check different areas looking in c1 vs sh and c2 vs sh with frame step in VirtualDub.

[DTL]

Finally made replacement of all functions with AVS internal Expr() and ex_Tools for GetSharpest():

Function GetSharpest(clip c1, clip c2)
{
  avg=Layer(c1.ex_GaussianBlur(1.8, UV=3), c2.ex_GaussianBlur(1.8, UV=3), "fast")

  return Expr(avg, c1, c2, "x y - abs x z - abs >= y z ?")

#or some faster 
#return MostDiffVal(avg, c1, c2)
}

The sigma param for GaussianBlur is subject to check for best results (or best for current user/footage/filters/ etc). Currently 1.8 is about equal to GaussResize(p=2) blur. Also compiled plugin MostDiffVal updated to v0.2 with AVX2 functions and opt SIMD manual control (optional or auto). With 8bit it runs about 2 times faster in comparison with Expr() - looks like because Expr() perform internal calculations with float32 and have penalty of convert from integer to float and back.

ex_GaussianBlur() runs about 1.5 times faster in comparison with GaussResize() for blurring. Also Layer("fast") is somehow faster in comparison with Average(0.5,0.5).

About twice faster with not yet tested quality change is single blur of averaged input clips:

Function GetSharpest(clip c1, clip c2)
{
  avg=ex_GaussianBlur(Layer(c1, c2, "fast"),1.8, UV=3)

  return Expr(avg, c1, c2, "x y - abs x z - abs >= y z ?")

#or some faster 
#return MostDiffVal(avg, c1, c2)
}

Edit: With full chroma planes processing (UV=3 for ex_GaussianBlur) the GaussResize still some faster (looks like integer 2 pass V+H AVS resize kernel is faster, at least for not very large radius blur):

Function GetSharpest(clip c1, clip c2)
{
  avg=GaussResize(Layer(c1, c2, "fast"), c1.width, c1.height, src_left=0.001, src_top=0.001, p=2)

  return Expr(avg, c1, c2, "x y - abs x z - abs >= y z ?")

#or some faster 
#return MostDiffVal(avg, c1, c2)
}

[LouieChuckyMerry]

I very recently transitioned from real.finder's last version of NotSMDegrain (3.1.2.116s) to Dogway's most recent version of SMDegrain (4.6.0d), running on Windows 7 with 64-bit AviSynth+ 3.73. It seems to work fine, but I'm trying to understand why the speed is basically the same (within ~5%) but the resulting video bitrate is radically different (roughly a full CRF). To wit, the scripts

SetFilterMTMode("Default_MT_Mode",2)
SMDegrain(TR=4,ThSAD=700,RefineMotion=True,Plane=0,Chroma=False,n16=True,n16_Out=True)
FastLineDarkenMod4()
F3KDB(Y=100,Cb=100,Cr=100,GrainY=0,GrainC=0)
SelectRangeEvery(1000,66)
PreFetch(5)

and

SetFilterMTMode("Default_MT_Mode",2)
SMDegrain(Prefilter=SpotLess(),TR=3,ThSAD=500,RefineMotion=True,Plane=0,Chroma=False,n16=True,n16_Out=True)
FastLineDarkenMod4()
F3KDB(Y=100,Cb=100,Cr=100,GrainY=0,GrainC=0)
SelectRangeEvery(1000,66)
PreFetch(5)

with the filters-plugins

F3KDB__64bit
FastLineDarkenMTMod1_48
LinearTransformation
MaskTools2_2_26_0MTDualSignatureMod_pinterf__64bit
MedianBlur2__1_1__64bit
MVTools2_7_41_0MTMod_pinterf__64bit
SharedFunctions1_153
SMDegrainMod_rf_3_1_2_116s
SpotLess1_07

results in bitrates of 3471 kb/s and 4209 kb/s, respectively, while the scripts

SetFilterMTMode("Default_MT_Mode",2)
ConvertBits(Bits=16)
SMDegrain(TR=4,ThSAD=700,RefineMotion=True,Plane=0,Chroma=False)
FastLineDarkenPlus()
Neo_F3KDB(Y=100,Cb=100,Cr=100,GrainY=0,GrainC=0)
SelectRangeEvery(1000,66)
PreFetch(5)

and

SetFilterMTMode("Default_MT_Mode",2)
ConvertBits(Bits=16)
SMDegrain(Prefilter=SpotLess(),TR=3,ThSAD=500,RefineMotion=True,Plane=0,Chroma=False)
FastLineDarkenPlus()
Neo_F3KDB(Y=100,Cb=100,Cr=100,GrainY=0,GrainC=0)
SelectRangeEvery(1000,66)
PreFetch(5)

with the filters-plugins

ExTools10_1
FastLineDarkenPlus
LinearTransformation
MaskTools2_2_30_0MTDualSignatureMod_pinterf__64bit
MedianBlur2__1_1__64bit
MVTools2_7_46_0MTMod_pinterf__64bit
Neo_F3KDB9_0__64bit
SMDegrain4_6_0d
SpotLess1_07

results in bitrates of 4165 kb/s and 5173 kb/s, respectively. The sources are the same. Any help understanding why the bitrates are so different would be greatly appreciated.

[Emulgator]

Less entropy, less changing high frequency details, and encoder can save bits.
It may not be visible at first, only pixel-peeping and framestepping will tell what those plugins were able to smoothe.
To go through all plugin's parameter's dependencies would make up a matrix which one should like to solve on his side.
From my side of experience I can tell that Dogway's algos give nice details which got to be honoured by bits...
and of course... many thanks, at least from my side.

[kedautinh12]

You can try with High bit depths to see more clearly about speed

[LouieChuckyMerry]

Originally Posted by Emulgator

Less entropy, less changing high frequency details, and encoder can save bits.
It may not be visible at first, only pixel-peeping and framestepping will tell what those plugins were able to smoothe.
To go through all plugin's parameter's dependencies would make up a matrix which one should like to solve on his side.
From my side of experience I can tell that Dogway's algos give nice details which got to be honoured by bits...
and of course... many thanks, at least from my side.

Thank you for a very philosophical answer . And I also appreciate Dogway's work very much.

Originally Posted by kedautinh12

You can try with High bit depths to see more clearly about speed

Please, I don't understand what you mean.

[kedautinh12]

Lol, please search google about High bit depths video and try add converttobit(16) or converttobit(32) and compare both of them again. SMDegrain build by Dogway for speed with High bit depths video not for 8 bit video only

Originally Posted by kedautinh12

Lol, please search google about High bit depths video and try add converttobit(16) or converttobit(32) and compare both of them again. SMDegrain build by Dogway for speed with High bit depths video not for 8 bit video only

I thought it was ConvertBits(16)....

http://avisynth.nl/index.php/ConvertBits

[Emulgator]

BTW, LouieChuckyMerry,

SMDegrain(Prefilter=SpotLess(),TR=3,ThSAD=500,RefineMotion=True,Plane=0,Chroma=False)

does not work, throws an error.
Prefilter=SpotLess() is not implemented this way within SMDegrain 4.6.0d

[DTL]

You may need to add SpotLess() function body to the script before call it or Import() .avsi file with this script function body.

Function SpotLess() is from https://forum.doom9.org/showthread.php?t=181777 .

[LouieChuckyMerry]

Originally Posted by kedautinh12

Lol, please search google about High bit depths video and try add converttobit(16) or converttobit(32) and compare both of them again. SMDegrain build by Dogway for speed with High bit depths video not for 8 bit video only

I'm working in 16-bit (see Post #2946), but will give 32-bit a try. Thanks.

Originally Posted by FTLOY

I thought it was ConvertBits(16)....

http://avisynth.nl/index.php/ConvertBits

ConvertBits(Bits=16)

The above works for me.

Originally Posted by Emulgator

BTW, LouieChuckyMerry,

does not work, throws an error.
Prefilter=SpotLess() is not implemented this way within SMDegrain 4.6.0d

It seems to work fine for me...

[Emulgator]

I see now. This argument takes a clip too, (this is possible, I found it in an old script being (last), and I was expecting an integer argument).

[tormento]

I have always used PureVideo deinterlacer for IVTC from 29.97 to 23.974 by using

DGTelecide(mode=1, pthresh=3.5)
DGDecimate()

but I'd like to try something better.

What do you suggest me from your scripts without incurring in miserable performances?

I have a very old i7-2600k and a nVidia 1660 SUPER gpu and remember that I have to encode it too.

(I was looking at RIFE but I fear it's too heavy, mostly because of double RGB32 and back conversion and, above all, I have no idea if it's suitable for IVTC too)

[rgr]

Originally Posted by DTL

it uses new plugin MostDiffVal.dll to run

Where can I download this plugin?

[DTL]

Latest version is https://github.com/DTL2020/MostDiffVal/releases/tag/0.2 .

But it can be replaced with Expr() call

 Expr(avg, c1, c2, "x y - abs x z - abs >= y z ?")

It is slower with 8bit and may be 16bit because Expr() process always with float internally. But Expr() always available as AVS core function.

I'm looking for a simple script for adding a small transparent "watermark" image to a video clip. (eg:- like Netflix)

[DTL]

Try to load your image with alpha channel and use Overlay() - http://avisynth.nl/index.php/Overlay . If fixed opacity is enough - you can load RGB image without alpha channel and control with
float opacity = 1.0
Set overlay transparency. The value is from 0.0 to 1.0, where 0.0 is transparent and 1.0 is fully opaque. This value is multiplied by mask luminance to form the final opacity.

Or you can load grey mask as separate image too.