Another "QTMGC" mess 🥴

[NoahLoot]

Okay, a few things, you are using QTGMC as denoiser not as deinterlacer.
QTGMC is normally meant to do light clean up or residual combing and similar stuff.
Using something like:

clip = qtgmc.QTGMC(clip, Preset="Fast", InputType=1, TR2=3, Sharpness=1.0, SourceMatch=0, Lossless=0, EZDenoise=10.00, NoisePreset="Fast", MatchPreset2="Medium", MatchEnhance=0.05, Denoiser="KNLMeansCL")

especially EZDenoise=10, will kill a lot of fine details.
DetailSharpen is trying to enhance fine details and contrast, but if you use something like EZDenoise=10 you already kill everything that is there.

So my suggestion is either:
a. move DetailSharpen before the denoising
or
b. lower the Denoising

With EZDenoise=10 it is normal that DetailSharpen or FineSharpen won't find many details to enhance.
Sane values should be 0-3 and normally better 0-1.5.

=> To me Hybrid still does seem to behave as it should.

Cu Selur

Usualy i never use strength 10 for KNLmeans denoiser.  I just used that value to magnify the issue, or trying to expose it rather.

True, i never go above 1,5 - 3.0 max.  But then again, in that range usuall the knl denoiser from QTGMC is strongly present .  But now, it's as if it's doing nothing at all !!???

You know, knlmeans tends to smoothen image while retaining the sharp contours, much different from making something blurry to mask imperfections / noise you know.
Well, that output effect isn't just as clean anymore like it used to be

 
Of course, it is also possible that the results could be worse or better depending on the type of video source material I am trying to clean up 🤔.

But i've could have sworn i've been using this particular profile for a long time to clean up SD & even HD content, and always with succes ... Untill now ¯\_(ツ)_/¯

---

Look i have a better screenshot taken while using KNLmeansCL seperate filter. 

Okay, not helping either,...

But surely, you can visually see not much gets filtered in the image on your right side   .
Again, using KNLMeansCL (seperately) i've used strength 2.0 wich is pretty pretty HIGH, and you ought to see a much smoother image usually , practically much less noise !?

The strength is set to 2.0 in knlmeans, but as you can see something is realy off with knlmeans filter in general  Huh

2 and 10 *qtgmc internal factor are totally different!

You mean Strength factor from KNLmeansCL (seperately) vs KNLmeans through QTGMC , right?

It used to be a much .. MUCH.. cleaner output quality !?

when was that?

I can't remember, but i do remember it's quite a few builds back

Cu Selur

Side note: What Hybrid does when 'KNLMeans(CL)' is selected:
1. if no gpu accelleration is enabled it will use vsnlm_ispc
2. if gpu and a nvidia card is available, it will use vsnlm_cuda
3. if a gpu and a only non-nvidia card are available, it will use KNLMeansCL

I have always used an nvidia gpu with hybrid.
Even when knnlmeans was still working correctly back then   .

Well, i sill have an old hybrid build from back in the day.  i will install that and see what the result is..🤔

Could it be , something has gone wrong during installation?
Is it usuall safe to install a fresh hybrid revision over an existing installation ?

Please don't tell me that I have to uninstall and remove everything every time a new dev is released.
I do use the "torch🔥" addon pack you know 😰!