QTGMC Deinterlacing Script (v3.384)

[real.finder]

as Groucho2004 said

# --- REQUIREMENTS ---
#
# Input colorspaces: YV12, YUY2, others as plugins supports
#
# Core plugins:
#   MVTools2 (2.7.5.22 or above)
#   MaskTools2 (v2.2.5 or above)
#   NNEDI3 (0.9.4.6 or above)
#   RgTools
#
# Core scripts:
#   SMDegrain (3.1.2.92s or above) unless you set tv_range=false
#   AnimeIVTC (2.20 or above) if you work with YUY2 source
#
# Additional plugins:
#   NNEDI2, NNEDI, EEDI3, EEDI2, TDeInt - if selected directly or via a source-match preset
#   yadifmod2 - for Preset="Ultra Fast" or if selected directly
#   FFT3DFilter - if selected for noise processing
#   dfttest (1.9.4 or above) - if selected for noise processing
#       For FFT3DFilter & ddftest you also need the FFTW3 library (FFTW.org). On Windows the file needed for both is libfftw3f-3.dll. However, for FFT3DFilter
#       the file needs to be called FFTW3.dll, so you will need two copies and rename one. On Windows put the files in your System32 or SysWow64 folder
#   KNLMeansCL - if selected for noise processing
#   AddGrainC - if NoiseDeint="Generate" selected for noise bypass
#   chikuzen PlanarTools - if you work with YUY2 source (not necessarily required but may improve speed)

[tebasuna51]

Originally Posted by real.finder

...
don't forget SMDegrain if you use tv_range=true (Default for now) and if you use avs+mt ...

I want use avs+mt to deinterlace my miniDV tapes (PAL 50i 8 bits YV12).

I need SMDegrain, or I can add tv_range=false to QTGMC 3.357s call, or I can use a older QTGMC version?

I'm not sure if the new requirements are for last improvements (high bitdepth, better YUV2 support) or to use avs+mt.

[real.finder]

Originally Posted by tebasuna51

I want use avs+mt to deinterlace my miniDV tapes (PAL 50i 8 bits YV12).

I need SMDegrain, or I can add tv_range=false to QTGMC 3.357s call, or I can use a older QTGMC version?

I'm not sure if the new requirements are for last improvements (high bitdepth, better YUV2 support) or to use avs+mt.

tv_range will just improve motion vectors in tv source (limited range source), you can set it to false even in tv range and that will be like qtgmc 3.32

the new requirements for improve motion vectors (SMDegrain)

and better YUV2 support (animeivtc and PlanarTools)

nothing for avs+mt, but I mention that if someone use any avs+ mt it should be the last one, the older avs+mt was not stable anyway, and because there are new functions for high bitdepth that been in the newer builds of avs+

[tebasuna51]

Originally Posted by real.finder

...nothing for avs+mt, but I mention that if someone use any avs+ mt it should be the last one...

Ok, thanks.

tv_range will just improve motion vectors in tv source (limited range source), you can set it to false even in tv range and that will be like qtgmc 3.32

Then SMDegrain improve my output if my source is tv_range.

I'm not sure if my DV source is tv_range or not, or if depend of decoder config (Cedocida, ...). But this is a question for DV forum.

Thanks.

[hello_hello]

Originally Posted by real.finder

tv_range will just improve motion vectors in tv source (limited range source), you can set it to false even in tv range and that will be like qtgmc 3.32

Gotta ask....
Doesn't "tv_range=true" as the default value make the script guilty of the same behaviour that was deemed undesirable for plugins?
https://forum.doom9.org/showthread.p...22#post1793722
And if it's also the default for SMDegrain, doesn't that make it guilty of the same thing?

I'm just trying to understand why a plugin shouldn't mess with the levels unless specifically told to, but for a script the user needs to be aware of the source levels and set an option accordingly. Or is QTGMC used on full range sources so rarely it doesn't matter?

Maybe the tv-range setting could be called something else such as "clamp" given I assume the end result it pretty much the same and it's possibly less counter-intuitive.

Cheers.

[real.finder]

Originally Posted by hello_hello

Gotta ask....
Doesn't "tv_range=true" as the default value make the script guilty of the same behaviour that was deemed undesirable for plugins?
https://forum.doom9.org/showthread.p...22#post1793722
And if it's also the default for SMDegrain, doesn't that make it guilty of the same thing?

I'm just trying to understand why a plugin shouldn't mess with the levels unless specifically told to, but for a script the user needs to be aware of the source levels and set an option accordingly. Or is QTGMC used on full range sources so rarely it doesn't matter?

Maybe the tv-range setting could be called something else such as "clamp" given I assume the end result it pretty much the same and it's possibly less counter-intuitive.

Cheers.

Good question

things here are different, nnedi3 is used in many functions that deal with many color format even with rgb in Y8

and the tv_range here do TV to full range convert for better result, While the range parameter in nnedi3 just did clamp the values to tv range

and tv_range here don't effect the output directly, it just done in prefilter, and not only relate to tv range, it's simply call Dither_Luma_Rebuild and it's can be used for curve dark enhancement by Str (strength) and Amp (amplitude) parameters while do TV to pc converter, see SMDegrain documentation or wiki page for more info

[LigH]

Issues with QTGMC v3.357s reported: post with screenshots comparing versions 3.354s and 3.357s; MPEG2 test clip; sample script how QTGMC is used

It looks like a lot of blending in the latest version.

[real.finder]

Originally Posted by LigH

Issues with QTGMC v3.357s reported: post with screenshots comparing versions 3.354s and 3.357s; MPEG2 test clip; sample script how QTGMC is used

It looks like a lot of blending in the latest version.

work fine here with frame 67 after QTGMC

MPEG2Source("E:\ORG.d2v", cpu=0)
AssumeTFF()
QTGMC( Preset="Slow" )

what SMDegrain he had? what he get with tv_range=false?

[LigH]

SMDegrain v.3.1.2d ... that was the reason to request it being mentioned in the source header.

[real.finder]

Originally Posted by LigH

SMDegrain v.3.1.2d ... that was the reason to request it being mentioned in the source header.

and maybe the problem he don't use masktools 2.2.5 or up

and here the requirements same as the script header in last QTGMC https://forum.doom9.org/showthread.p...99#post1802599 (see the next post too)

[LigH]

Just curious that the same selection of plugins still works with a slightly earlier QTGMC version. Was there so much difference? Surprising. It looks so frail.

Your suggestions will be tested...
_

Success with Masktools2 v2.2.6!

[real.finder]

Originally Posted by LigH

Just curious that the same selection of plugins still works with a slightly earlier QTGMC version. Was there so much difference? Surprising. It looks so frail.

Your suggestions will be tested...

if you mean use old QTGMC with new plugins (masktools 2.2.6 for example) then yes it work, and if you mean using last QTGMC with old plugins then no, it will not work right cuz there are changes in lut lines that will not work with old masktools even in avs 2.6 or 8 bit in avs+

[tebasuna51]

New thread created from old thread QTGMC Deinterlacing Script (v3.32), because https://forum.doom9.org/showthread.p...33#post1804533

@real.finder
Please edit the first post in order to show last version, changes, downloads, plugins packs, title, etc. at your choice.

[nhope]

tebasuna51

[Selur]

would be nice if the first post could contain an up-to-date plugins&co pack,...

[real.finder]

@tebasuna51

done with what I can I do for it

[pinterf]

Found a thing in masktools2 2.2.6, Y, U and V when negative (memset) values are provided, are not scaled automatically from 8 bits.
This was missed somehow, though I have written in the documentation that only threshold-like parameters are scaled.
But this is not a consistent bahaviour when users have to care about which parameter is scaled, which is not scaled.
So this is fixed in the soon-to-be-released 2.2.7.

Looked inside the qtgmc script and yes, it is using
CNmt128 = ChromaNoise ? 3 : -128
then
output = (ShowNoise == 0.0) ? cropped : finalNoise.mt_lut( "clamp_f x range_half - " + string(ShowNoise) + " * range_half +", U=CNmt128,V=CNmt128 )
so it won't scale properly in 10+ bits.

2.2.7 update (along with other fixes) is on the way, you don't have to change the script, just make a note that masktools 2.2.7 is necessary.
EDIT: released

[real.finder]

done

[Music Fan]

Where can we find masktools 2.2.7 ?
I only found the Changelog ;
https://github.com/pinterf/masktools/releases/tag/2.2.7

edit : ok, found it, the link is actually below the changelog of v2.2.1

[LigH]

Originally Posted by real.finder

# Core scripts:
# SMDegrain (3.1.2.92s or above) unless you set tv_range=false
# AnimeIVTC (2.20 or above) if you work with YUY2 source

How do I discover to which posts these attachments were attached?