Dogway's Filters Packs

[Dogway]

@Blankmedia: I'll have a look at the first issue, I don't see any nand there though
For the second one you should input the results of clipstats in 8-bit into ex_levels manually
Then ex_levels won't try to read scene ranges

[Fjord]

LSFplus v6.0 ex references ex_CAS() on lines 767-770. ex_CAS() existed in SharpenersPack until it was renamed to CASP() in SharpenersPack v4.0 (mix).

LSFplus v6.0 mix references CAS() in the same places (lines 763-766), but CAS() does not appear to be defined anywhere.

Shouldn't these references to ex_CAS() and CAS() in LSFplus be replaced with calls to CASP() from the current SharpenersPack v5.1? Or do ex_CAS() and CAS() exist in some other plugin or script that I need to import?

[rgr]

What else am I missing to try QTGMC+? I updated nnedi3.dll to 0.9.6.43, but I still have this message.

[avisynth @ 000001f3668c01c0] Script error: nnedi3wrap does not have a named argument "dh"
(C:/Program Files (x86)/AviSynth+/plugins64+/QTGMC+.avsi, line 1171)
(C:/Program Files (x86)/AviSynth+/plugins64+/QTGMC+.avsi, line 965)

[Boulder]

Originally Posted by rgr

What else am I missing to try QTGMC+? I updated nnedi3.dll to 0.9.6.43, but I still have this message.

[avisynth @ 000001f3668c01c0] Script error: nnedi3wrap does not have a named argument "dh"
(C:/Program Files (x86)/AviSynth+/plugins64+/QTGMC+.avsi, line 1171)
(C:/Program Files (x86)/AviSynth+/plugins64+/QTGMC+.avsi, line 965)

There are possible fixes in this GitHub issue: https://github.com/Dogway/Avisynth-Scripts/issues/69

[rgr]

Explained.
Somehow I downloaded QTGMC+ today and an older version was downloaded.

[Dogway]

Originally Posted by Fjord

LSFplus v6.0 ex references ex_CAS() on lines 767-770. ex_CAS() existed in SharpenersPack until it was renamed to CASP() in SharpenersPack v4.0 (mix).

LSFplus v6.0 mix references CAS() in the same places (lines 763-766), but CAS() does not appear to be defined anywhere.

Shouldn't these references to ex_CAS() and CAS() in LSFplus be replaced with calls to CASP() from the current SharpenersPack v5.1? Or do ex_CAS() and CAS() exist in some other plugin or script that I need to import?

Thanks, fixed now, uploading. Indeed I forgot to update the call to CASP(). As for LSFPlus Mix, CAS is a plugin, now I added a version to imply it's an external dependency.

I uploaded also some of the updates for the last few months. Mainly ResizersPack, adding the 'sc' (SceneChange) argument so I can disable it in FillMissing stand alone function, to force RIFE to interpolate even if it's a big change.
TransformPack also saw some more additions, like TM_Daniele() tonemapper which I dig in, S-Log2, and in Main a few more gamuts.

Originally Posted by rgr

Explained.
Somehow I downloaded QTGMC+ today and an older version was downloaded.

Yes, I was going to suggest to update. I guess it works now.

@Dogway,

FYI,

I was just checking out the updates you've recently done, and in the Ex & Mix mods, LSFplus has some mismatched, erroneous details & dates.

[Dogway]

Originally Posted by FTLOY

@Dogway,

FYI,

I was just checking out the updates you've recently done, and in the Ex & Mix mods, LSFplus has some mismatched, erroneous details & dates.

Thanks, fixed now.

Originally Posted by Dogway

Thanks, fixed now.

You're welcome, and thanks for the updates, it's been a "minute".

[kedautinh12]

ExTools and Stabilization Tools Pack still outdate in the info

hello,

i have silly question: Which prefilter from these below is weaker:

2 = strong median/gauss blur
3 = very strong median/gauss blur (IQMV -Variable Inter Quartile Median- filter)
4 = spatio-temporal median/gauss filter (IQMST)

and in what sources type would be better to use one from these?

[simple_simon]

@Dogway, would you consider incorporating a grain function in Gradfun3plus that is similiar to the one in Gradfun2dbmod that only adds grain to areas of that frame that have been debanded?

I'm trying to deband some digital animation footage but the debanding doesn't survive encoding with x264 even at crf=18. I've tried using your Filmgrainplus after Gradfun3plus but that gives the whole image a grainy look that I don't want with digital animation. I just need enough grain in the debanded areas to prevent the encoder from reintroducing the banding.

[rgr]

Originally Posted by Dogway

Yes, I was going to suggest to update. I guess it works now.

But I had just downloaded QTGMC+ for the first time an hour earlier. I don't know why I downloaded the version "QTGMC 3.89 + mod by Dogway 2022, based on 3.382s". It will remain a secret.

At 10 bit depth it looks 20% faster. Great job

[rgr]

Originally Posted by Dogway

I uploaded also some of the updates for the last few months. Mainly ResizersPack, adding the 'sc' (SceneChange) argument so I can disable it in FillMissing stand alone function, to force RIFE to interpolate even if it's a big change.

I just downloaded FillMissing (version with " Add 'sc=false' to RIFEwrap to force MI by Dogway on Feb 18, 2024")

and I get:

Avisynth open failure: Script error: RIFEwrap does not have a named argument "sc" (C:/Program Files (x86)/AviSynth+/plugins64+/FillMissing.aysi, line 50)

Edit: ResizersPack I also downloaded the old version. But after updating I get:
Avisynth open failure: Script error RIFEwrap does not have a named argument "gpu_id" (C:/Program Files (x86)/AviSynth+/plugins64+/FillMissing.aysi, line 50)

Edit 2:After correcting the typo on line 50 (gpu_id -> gpuid)
"Avisynth open failure: RIFE: gpu_thread must be between 1 and 2 (inclusive) (C:/Program Files (x86)/AviSynth+/plugins64+/ResizersPack.aysi, line 667) (C:/Program Files (x86)/AviSynth+/plugins64+/FillMissing.aysi, line 50) "

On line 667, gpu_thread can take the values 2 or 4. Do I have a different version of RIFE?

[kedautinh12]

Did you update ResizerPack?
https://github.com/Dogway/Avisynth-S...izersPack.avsi

You need update all dependencies of fill missing to latest version
https://github.com/Dogway/Avisynth-S...ssing.avsi#L17

[kedautinh12]

Originally Posted by rgr

I just downloaded FillMissing (version with " Add 'sc=false' to RIFEwrap to force MI by Dogway on Feb 18, 2024")

and I get:

Avisynth open failure: Script error: RIFEwrap does not have a named argument "sc" (C:/Program Files (x86)/AviSynth+/plugins64+/FillMissing.aysi, line 50)

Edit: ResizersPack I also downloaded the old version. But after updating I get:
Avisynth open failure: Script error RIFEwrap does not have a named argument "gpu_id" (C:/Program Files (x86)/AviSynth+/plugins64+/FillMissing.aysi, line 50)

Edit 2:After correcting the typo on line 50 (gpu_id -> gpuid)
"Avisynth open failure: RIFE: gpu_thread must be between 1 and 2 (inclusive) (C:/Program Files (x86)/AviSynth+/plugins64+/ResizersPack.aysi, line 667) (C:/Program Files (x86)/AviSynth+/plugins64+/FillMissing.aysi, line 50) "

On line 667, gpu_thread can take the values 2 or 4. Do I have a different version of RIFE?

I think you need waiting for Dogway to fix it

[kedautinh12]

I got this error when tried SMDerain's latest ver:
My script:

LWLibavVideoSource("C:\Users\ADMIN\Downloads\LR_11.avi")
SMDegrain(6, 400, prefilter=6, ContraSharp=true, RefineMotion=true, plane=4, limits=false, DCTFlicker=false, gpuid=1)

Sample

[StainlessS]

@K,
AVI Codec is "LAGS", Lagarith.
LWLibavVideoSource loads as RGBP (Planar RGB 8bit), try convert to YV12. (KNLMeansCL seems to require YUV).
I cant test, my setup KNLMeansCL requires BM3D_CUDA which I dont have. I seem to also have old version SMDegrain.

EDIT: My ver$ Smdegrain call to KnlMeansCL uses,

        nlckl   = Eval("  nlc.KNLMeansCL(D=d, A=a, h=h, s=s, device_type=device_type, device_id=deviceid, rclip=nlrc,  wmode=wmode, wref=wref, channels=UV" + knlm_params + ")")

which I presume produces the KnlMeansCL "Must Use 'RGB' with RGB colorspace", error.

[tormento]

@Dogway

Just remembering you to look at the new DGDenoise

The syntax changed so the script is now broken.

[tormento]

I can sort out what do OPP and UV (and its values) in:

ex_BM3D(clip a, float "sigma", int "radius", string "preset", bool "OPP", int "UV", bool "tv_range", int "gpuid")

Any idea? I have tried to look at the avsi but can't understand the conditions.

And why do

ex_BM3D(preset="Light") or ex_BM3D(preset="light")

or

ex_BM3D(preset="Normal") or ex_BM3D(preset="normal")

sometimes spit out "Wrong preset" error?