HAvsFunc

[tormento]

I am thinking about giving a try to VapourSynth.

I mainly use SMDegrain from real.finder and it basically needs MVTools, Masktools and KNLMeansCL.

AFAIK Masktools is included into VS core, KNLMeans is compatible but I have doubts about which versione of VS MVTools I have to use: single precision ones or the other one? What are the differences?

I'd like also to know if there is an implementation of CompTest.avsi:

PHP Code:

function Comptest(clip c, float percent)
{
  frange = floor(14./(percent/100.))
  return SelectRangeEvery(c, frange, 14)
} 


[Myrsloik]

Originally Posted by tormento

I am thinking about giving a try to VapourSynth.

I mainly use SMDegrain from real.finder and it basically needs MVTools, Masktools and KNLMeansCL.

AFAIK Masktools is included into VS core, KNLMeans is compatible but I have doubts about which versione of VS MVTools I have to use: single precision ones or the other one? What are the differences?

I'd like also to know if there is an implementation of CompTest.avsi:

PHP Code:

function Comptest(clip c, float percent)
{
  frange = floor(14./(percent/100.))
  return SelectRangeEvery(c, frange, 14)
} 


1. ALWAYS use vsrepo. It's your friend and will give you the right versions of everything. Especially for things like HAvsFunc it will save you hours of looking for things.

2. MVTools differences; the single precision one is just what the name implies, a special version that only supports single precision float.

3. Untested but something like this:

import math

def comptest(clip, percent)
  frange = math.floor(1400/percent)
  return clip.std.SelectEvery(cycle=frange, offsets=list(range(0, 14)))

[tormento]

Originally Posted by Myrsloik

MVTools differences; the single precision one is just what the name implies, a special version that only supports single precision float.

Thanks for your reply.

But what version do I need to run HAVSFunc?

[Myrsloik]

Originally Posted by tormento

Thanks for your reply.

But what version do I need to run HAVSFunc?

Normal

[tormento]

Originally Posted by Myrsloik

Normal

As you are so kind, how would you translate this AVS script into VS script?

PHP Code:

SetMemoryMax(8000)
SetFilterMTMode("DEFAULT_MT_MODE", 2)
LoadPlugin("D:\eseguibili\media\DGDecNV_x64\DGDecodeNV.dll")
DGSource("E:\in\something.dgi",ct=0,cb=0,cl=0,cr=0)
CompTest(1)
SMDegrain (tr=4, thSAD=500, refinemotion=false, n16=true, mode=0, contrasharp=false, PreFilter=4, truemotion=false, plane=4, chroma=true)
Prefetch(6) 


[ChaosKing]

import vapoursynth as vs
import math
import havsfunc as haf
core = vs.core
core.max_cache_size = 8000

def comptest(clip, percent):
	frange = math.floor(1400/percent)
	return clip.std.SelectEvery(cycle=frange, offsets=list(range(0, 14)))
  
clip = core.dgdecodenv.DGSource(r"E:\in\something.dgi", ct=0,cb=0,cl=0,cr=0)
clip = comptest(clip, 1)
clip = haf.SMDegrain(clip, tr=3, thSAD=500, RefineMotion=False, truemotion=False, plane=4, chroma=True, prefilter=4)


clip.set_output()

mvtools only supports tr=3 or less.
You don't need prefetch or MTModes in VS.

[tormento]

Originally Posted by ChaosKing

mvtools only supports tr=3 or less.

That's a big NO for me as I recover old videos with lot of noise/grain.

Is it a limit of the SMDegrain script implementation or of MVTools standard? I read that MVTools goes up to MDegrain24, at least for simple precision version.

tr [int: 1, "2", 3, 4, 5, 6, ...]
Temporal radius. Select between MDegrain 1, 2, 3, 4, 5, 6 or higher. Higher is generally better, but also much slower and improvements get less drastic.
This can be considered the strength of the denoising. tr 4, 5 and 6 (limit is tr=128, 64 for interlaced) require Dither's MVTools2 mod.

Originally Posted by feisty2

EDIT10:
test11
1. Binary Part: Extended Degrain to Degrain24 (24, it's my lucky number!)
2. Resurrected vmulti features from MVTools 2.6.0.5, implemented via a python module, "tr" works up to 24, guess no one will ever use a time radius > 24.... maybe?

Originally Posted by ChaosKing

You don't need prefetch or MTModes in VS.

How I set or limit the number of threads? DGSource and KNLMeansCL are very Video RAM demanding on multiple sessions with hi resolution video.

[ChaosKing]

You can use a different smdegrain version instead, it supports tr > 3: https://github.com/Selur/Vapoursynth...ster/G41Fun.py

It uses the single precision MVTools version from here
https://forum.doom9.org/showthread.php?t=172525

that means you must filter it in 32 float precision.

Add also this then:

import mvsfunc as mvf
import math, mvmulti
clip = mvf.Depth(clip, 32) # this before smdegrain

How to limit thread count: http://www.vapoursynth.com/doc/pytho...re.num_threads

[tormento]

Originally Posted by ChaosKing

that means you must filter it in 32 float precision.

Thanks, man!

And how will I dither back to 8 bit?

[ChaosKing]

Originally Posted by tormento

Thanks, man!

And how will I dither back to 8 bit?

clip = mvf.Depth(clip, 8)

[tormento]

Originally Posted by ChaosKing

clip = mvf.Depth(clip, 8)

I ended to do a try with your first script before using higher TR and I get lower fps on VS than AVS+, i.e. 10,58 vs 14,43.

So I watched at the created mkv: the VS is a slideshow of the same lenght of the original movie, made of still pictures, the AVS+ is the correct sampled video.

There is something wrong with the comptest. When you have time, would you please debug it for me?

P.S: I tried to use the other function with tr=4 and VS crashed miserably. Is there anything wrong?

PHP Code:

import vapoursynth as vs
import math
import G41Fun as G41
import mvsfunc as mvf
import math, mvmulti
core = vs.get_core()
core.max_cache_size = 8000

core.std.LoadPlugin("d:/eseguibili/media/DGDecNV_x64/DGDecodeNV.dll")
clip = core.dgdecodenv.DGSource("E:/in/2_06trinita/chiamarlo.dgi",ct=136,cb=136,cl=0,cr=0)

clip = mvf.Depth(clip, 32) # this before smdegrain

clip = G41.SMDegrain(clip, tr=4, thSAD=500, prefilter=4)

clip = mvf.Depth(clip, 8)

clip.set_output() 


[ChaosKing]

Script looks correct to me. Have you looked at the fps of your created video?
You can also see some infos in vsedit if you press F6, like this

Script was successfully evaluated. Output video info:
Frames: 28621 | Time: 0:19:53.734 | Size: 1920x1080 | FPS: 24000/1001 = 23.976 | Format: YUV420P8

[tormento]

Originally Posted by ChaosKing

Script looks correct to me. Have you looked at the fps of your created video?

No video created, as it crashed.

Could you please apply to a real clip and tell me?

[ChaosKing]

The Mvtools dll by feisty2 expects avx2 instruction set. Does you cpu support avx2?

You could try another compiled version from here https://forum.doom9.org/showthread.p...82#post1823382

[tormento]

Originally Posted by ChaosKing

The Mvtools dll by feisty2 expects avx2 instruction set. Does you cpu support avx2?

Nope.

Will give it a try.

Could you please find some spare time to write a working comptest?

Thanks!

EDIT: not crashing anymore but painfully slow, such as 1.0 fps instead of the 10-12 I was getting with standard MVTools.

[ChaosKing]

Originally Posted by tormento

Nope.

Will give it a try.

Could you please find some spare time to write a working comptest?

Thanks!

EDIT: not crashing anymore but painfully slow, such as 1.0 fps instead of the 10-12 I was getting with standard MVTools.

The comptest output is the same except for the fps
This should use the original video fps

def comptest(clip, percent):
	frange = math.floor(1400/percent)
	return clip.std.SelectEvery(cycle=frange, offsets=list(range(0, 14))).std.AssumeFPS(clip)

[tormento]

Originally Posted by ChaosKing

The comptest output is the same except for the fps
This should use the original video fps

def comptest(clip, percent):
	frange = math.floor(1400/percent)
	return clip.std.SelectEvery(cycle=frange, offsets=list(range(0, 14))).std.AssumeFPS(clip)

Thanks, I will try when this movie will finish to encode.

No hint anyway for MVTools single precision. Too slow to have acceptable performance. I asked for another no AVX2 binary and the author replied me that the script is a whole mess.

How I wish standard MVTools would support highter TR...

[Boulder]

Do you absolutely need SMDegrain or would some other denoiser do? Off the top of my head, I'd say that any details will be long gone with radius 3 at strong settings anyway so you could do with something faster.

[tormento]

Originally Posted by Boulder

Do you absolutely need SMDegrain or would some other denoiser do?

I am open to alternatives with same level of detail retaining/performance. Not found any, until now.

[Sharc]

Originally Posted by tormento

I am open to alternatives with same level of detail retaining/performance. Not found any, until now.

Difficult to advise when we don't know your source.....