Dogway's Filters Packs

[Dogway]

@akexx777 That's an error on line 215, basically a nmod() call in the Defaults definitions. It works for me so ensure everything is updated and no other older ResizersPack is present.
You can also try with this call nmod(8/2,2,4) which is what is failing on line 215

[alexx7777]

Originally Posted by Dogway

@akexx777 That's an error on line 215, basically a nmod() call in the Defaults definitions. It works for me so ensure everything is updated and no other older ResizersPack is present.
You can also try with this call nmod(8/2,2,4) which is what is failing on line 215

Thank you very much, everything worked!

[tormento]

What about using avs_libplacebo in some of your scripts? It's some weeks that I am playing with it and it's really fast and powerful.

The mitchell downsizing filter is something astonishing to get native anime resolution.

[DTL]

Originally Posted by LeXXuz

I'm still struggling with a bluring effect with SMDegrain in moving areas which really disturbs the overall look of the picture.
To elaborate: I've uploaded four samples of a short scene. Original, 2x denoised with SMDegrain (thSAD 400 and 200)

New tests with 2 stages (non-linear median-like and linear low pass with Gauss kernel) MVs filtering in new MDegrainN release of 26.09.2023 - https://forum.doom9.org/showthread.p...38#post1992038

Still first generation of MVs (no refining) and no prefiltering. mvtools2 script only.

[LeXXuz]

Looks clearly better, especially the skin tones and areas.

[tormento]

I am swearing with the ending of an anime.

The first part of the ending is a resized 1080i 59.94, the second part is a true (I think) 1080i 59.94.

I want to convert them to 23.976 as the rest of the anime. For the second part, I tried to deinterlace and apply IVTC via DGTools but it becomes a mess, as its not a true telecined video.

For the first part I have no ideas too.

[Selur]

you could try TFM+sRestore

[tormento]

Originally Posted by Selur

you could try TFM+sRestore

Is proper to deinterlace without downscaling?

Talking about the first video.

[kedautinh12]

I tried this script with the second part and it's a good result but you need to add some dehalo/dering and derainbow to get a better result

QTGMCp(Preset="Very Slow", Sharpness=0).SelectEven()
prefetch(2)

https://drive.google.com/file/d/1f2d...usp=drive_link

[tormento]

Originally Posted by kedautinh12

I tried this script with the second part

Thanks but the problem isn't deinterlacing but get a decent 23.976

[Sharc]

Weird. For the first part try something like

converttoYV12(interlaced=true)
BWDIF(field=3).selecteven()
RestoreFPS(23.976,1.0)

Edit: still messy,sorry

[anton_foy]

Originally Posted by Dogway

Is there a special scene or frame you have issues with? I tested with the Carrie call (I use tr 1 and 2 and thSAD=400 for the 2nd call) and found it good enough.
Also keep in mind this is a BW film so plane=0 and chroma=false.

The film shows "fizz" grain. It's in between the Carrie example and something stronger like 300. I found that a blksize of 32 is good to avoid catching these kind of big grains, along refinemotion this is a good approach. Filters like SPresso or STTWM are not suited here because they only filter minimal change noise, these are more for DVDs or faint grain.
My general approach with strong grain is a rather strong prefilter (with LFR), and a rather not so strong filter without LFR.

Personally for my encodes I don't like the clean look because they either look psychovisually blurry or sometimes it shows the "screen" effect, like grain stuck over a glass, so I apply some artificial grain after denoising.

@Dogway, how to achieve the "screen" effect you mention here? You mean like applying temporal denoising on a spatial denoised difference kind of? I would like to try this technique just for an experiment.

[Lan4]

Hello. Question about FineSharpPlus.

I use values:
FineSharpPlus(mode=1, sstr=1, cstr=0.1, xstr=0, lstr=1, pstr=4, ldmp=0, hdmp=0)

If you increase "pstr" more than 4, the difference in the result will be almost invisible. If "lstr" is set to 2 (or above), then the difference at pstr=4 or higher becomes more noticeable. This is right?

[Lan4]

Question about using the kernel in DetailSharpen and FineSharpPlus. I'm watching the preview in AvsPmod.

Using gaussian kernel in DetailSharpen(mode=0). Look at the furrows in the image that are most noticeable on the face.


Using box kernel in DetailSharpen(mode=1). Now the furrows have disappeared.


Using gaussian kernel in FineSharpPlus(mode=1)


And using box kernel in FineSharpPlus(mode=-1).


There is no difference. Furrows are present in both last examples, as if the kernel is not switching. Am I right or wrong?

The question is more of a scientific one, since furrows are not visible after encoding, or almost invisible.

[fabioseixal]

@Dogway, I've been experimenting ex_Vibrance(), to be more precise the Recovery mode to get back the proper saturation after rainbow removal.
The issue is that ex_Vibrance is working okish, i.e., it does recover contrast in areas that where lost, but the problem is that it is also getting back the rainbows in some places.
There also frames where the issue is even worse than before (see below)

Any idea why? I mean, any idea if this can be avoided?
This idea of getting back the contrast after removing the rainbows is a neat idea and it would be awesome to be able to make use of it.


Here is an example.

Source: (Rainbow is visible in the centre near the hole, near the vertical lines etc)



Source + Scomb: Rainbows are gone



Source + Scomb + ex_Vibrance: Rainbow is back and vertical lines are now surrounded by a Yellowish "aura", i.e., rainbow effect is accentuated



Script used:

DGSource("ep1.dgi")

vibrance=last
scomb()
ex_vibrance(1.0, mode="Recover", Rc=vibrance)

PS: Yes, the video is interlaced, that's where scomb really shines. Probably that's the issue... oh well
PS2: I made the same test but with progressive video and the issue remains exactly the same

[Dogway]

Sorry for the delay, I'm quite busy now with APP development.

@fabioseixal: I think in this case it's better to increase saturation or vibrance. If your filtering is local then the difference of saturation in "recovery" mode is also going to be local. "Recover" works better with mostly global desaturation like denoisers and such.

For DeRainbow I used to use:

edgy=FlatMask(2.0).ex_expand()
ex_merge(last,FFT3DFilter( sigma=2, sigma2=8, sigma3=12, sigma4=4, bt=3, plane=3, ncpu=4),edgy.ex_expand(),Y=2,UV=3,luma=true)

but FFT3DFilter is slow so you can try other denoisers.
I also had this expanded version which kills rainbowing further and preserves saturation a bit better.

o = last
derain = o.ex_median("median",Y=2,UV=3)
Hmed   = ex_luts(o,o,mode="median",pixels="-2 0 -1 0 0 0 1 0 2 0",UV=2)
Hedge  = ex_lutxy(Hmed,o,"x y - abs 8 *",UV=128)
ex_merge(o,derain,Hedge.ex_expand(2),luma=true,Y=2,UV=3)

edgy=FlatMask(2.0).ex_expand()
ex_merge(o,FFT3DFilter( sigma=2, sigma2=8, sigma3=12, sigma4=4, bt=3, plane=3, ncpu=4),edgy.ex_expand().ex_vibrance(1),Y=2,UV=3,luma=true)

Originally Posted by Lan4

Question about using the kernel in DetailSharpen and FineSharpPlus. I'm watching the preview in AvsPmod.

Using gaussian kernel in DetailSharpen(mode=0). Look at the furrows in the image that are most noticeable on the face.

There is no difference. Furrows are present in both last examples, as if the kernel is not switching. Am I right or wrong?

The question is more of a scientific one, since furrows are not visible after encoding, or almost invisible.

I'm not sure to understand "furrows" in this case, but the implementation in both sharpeners are different, to compare them equally you'd need DetailSharpen() with med=true. As for FineSharpPlus' I might revise the non-linear values as I get a gray clip out of shrpD var. Actually I fixed an issue on _cstr var as spline() was going out of bounds.

[Lan4]

In Finesharp, increasing the LSTR and PSTR parameters softens the sharpness. In FinesharpPlus, on the contrary, it increases sharpness. I'm right? Showing a preview from AvsPmod:

https://imgsli.com/MjE2NDkx

[Lan4]

This is how I understand how Finesharp works. LSTR softens flat areas and textures. PSTR softens edges without affecting flat areas or textures. Screenshots after encoding:

sstr=5, lstr=1, pstr=1 (all other values are at minimum, 0 or 0.1)



sstr=5, lstr=5, pstr=1



sstr=5, lstr=1, pstr=5



But I don't understand how FinesharpPlus works. I have to guess with the values to get the result I want.

[Dogway]

@Lan4: Sorry for the delay, FineSharp non-linear sharpening is an old implementation, whereas FineSharpPlus one is based on LSFplus in Smode=5, if any you might want to compare to that. This is not to say everything's right on FineSharpPlus, the contrary, I need to give it a review to see why I'm getting a flat grey shrpD clip, as well as confirm your suspicions. When I get some time I will let you know. Maybe I open an issue ticket on the repo so I don't forget.

[poisondeathray]

ex_vibrance does not seem to work for 10bit or 12bit 420/422/444 input. 8bit, 14bit, 16bit ok

Do you prefer issues reported here or github issues tracker ?