QTGMC Deinterlacing Script (v3.384)

[Statick]

hi guys, I'm pleased to report that setting MeGUI to use development updates instead of stable updates, putting it on version 2634, solves the problem. this also updated x265, x264, L-Smash and a bunch of other components, so it's hard to know where exactly the problem was. in any case it's sorted, and if anyone else has the same issue hopefully they will find this.

thanks to everyone for the time taken to help

[real.finder]

new edit http://forum.doom9.org/showpost.php?...postcount=2041

tr2 now can be 4 and 5 for more fun :P

[Dreamland]

Real.Finder

I have an issue with last QTGMC release (2016-12-06)




Help me !

thanks a lot

[real.finder]

Originally Posted by Dreamland

Real.Finder

I have an issue with last QTGMC release (2016-12-06)




Help me !

thanks a lot

you must have last SMDegrain

[ndjamena]

I'm busy modifying QTGMC so that I can do the script in sections to make processing 1080i material using whatever settings I like without it crashing or reducing the framerate to almost nothing (multithreading the script doesn't increase CPU usage any more than running it single threaded).

I think I've already got a working solution, I just have to wait for the finished output, but at the moment I'm up to SourceMatch and have a question.

I don't actually understand everything going on in the script and I'm wonder what is the difference between the main EDI and each of the SourceMatch EDIs... Would it cause any problems if I just fed the main EDI into QTGMC_ApplySourceMatch or does that little bit of code in there change the frames too much for them to be interchangeable?

[ravewulf]

QTGMC 3.34

Given that MvTools2 now supports YV16, I figured I'd create a YV16 version of QTGMC that gets rid of any unneeded YUY2 conversions.

real.finder's 2016-12-06 mod with the following changes:

• Removed YUY2 input support, use YV16 instead (hence the version bump to 3.34)
• Removed most YUY2 workarounds except where still needed for plugins that don't support YV16
• Removed reliance on SSE2Tools. All plugins now support either YV16 or YUY2 directly
• Minimum requirements updated for YV16 support
• RemoveGrain and Vertical Cleaner replaced by RgTools
• Yadif replaced by yadifmod2 (The option to select it directly is still "Yadif" for compatibility if you have it in multiple scripts already, but I can change this if people want it to be "yadifmod2" instead)

FFT3DFilter, NNEDI2, NNEDI, EEDI3, EEDI2, TDeint still rely on YUY2, but accept it directly without SSE2Tools.

AddGrainC, dfttest, MaskTools2, MvTools2, NNEDI3, KNLMeansCL, RgTools, and yadifmod2 support YV16

# --- REQUIREMENTS ---
#
# Input colorspaces: YV12, YV16
#
# Core plugins:
# MVTools2 (2.7.5.22 or above from pinterf https://github.com/pinterf/mvtools/releases)
# MaskTools v2 (2.0b1 or above)
# NNEDI3 (0.9.4.6 or above)
# RgTools
#
# 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
# AddGrainC (1.7.0 or above) - if NoiseDeint="Generate" selected for noise bypass

I'm not sure what other plugins to add to this from previous edits, so the requirements list is probably incomplete. Please let me know if there's something I missed or if you find a problem with my changes.

I've only done a limited set of testing, but hopefully there should be a speed-up for YV16 without all the SSE2Tools planar YUY2 hacks.

[StainlessS]

ravewulf, you should have done timing tests with/without YUY2 hacks in-situ, to tell if any benefit in removal, and then post
results, removal just for the sake of it is not a good idea.

[real.finder]

Originally Posted by ravewulf

QTGMC 3.34

Given that MvTools2 now supports YV16, I figured I'd create a YV16 version of QTGMC that gets rid of any unneeded YUY2 conversions.

real.finder's 2016-12-06 mod with the following changes:

• Removed YUY2 input support, use YV16 instead (hence the version bump to 3.34)
• Removed most YUY2 workarounds except where still needed for plugins that don't support YV16
• Removed reliance on SSE2Tools. All plugins now support either YV16 or YUY2 directly
• Minimum requirements updated for YV16 support
• RemoveGrain and Vertical Cleaner replaced by RgTools
• Yadif replaced by yadifmod2 (The option to select it directly is still "Yadif" for compatibility if you have it in multiple scripts already, but I can change this if people want it to be "yadifmod2" instead)

FFT3DFilter, NNEDI2, NNEDI, EEDI3, EEDI2, TDeint still rely on YUY2, but accept it directly without SSE2Tools.

AddGrainC, dfttest, MaskTools2, MvTools2, NNEDI3, KNLMeansCL, RgTools, and yadifmod2 support YV16

I'm not sure what other plugins to add to this from previous edits, so the requirements list is probably incomplete. Please let me know if there's something I missed or if you find a problem with my changes.

I've only done a limited set of testing, but hopefully there should be a speed-up for YV16 without all the SSE2Tools planar YUY2 hacks.

good, you did a lot of work, but why not do it like this:-

if the source is YUY2 then did convert it to yv16 and if plugins need YUY2 (like FFT3DFilter) then convert it back to YUY2 and after that plugin convert back to yv16 until the end of script and in the end convert the output to YUY2

with this you will not need to did another edit in the future in case all filters have yv16 support

yadifmod2 is good but unfortunately that will make winxp users unhappy

[Groucho2004]

Originally Posted by real.finder

yadifmod2 is good but unfortunately that will make winxp users unhappy

Why's that? Works fine for me on XP.

[real.finder]

Originally Posted by Groucho2004

Why's that? Works fine for me on XP.

that what readme say

#yadifmod2
## Yet Another Deinterlacing Filter mod for Avisynth2.6/Avisynth+

yadifmod2 = yadif + yadifmod

### Info:

version 0.0.4

### Requirement:
- Avisynth2.6.0final/Avisynth+r1576 or greater.
- WindowsVista SP2 or later.
- Visual C++ Redistributable Packages for Visual Studio 2015.

edit: test it now in winxp in VirtualBox, and it realy work

[ravewulf]

Originally Posted by real.finder

good, you did a lot of work, but why not do it like this:-

if the source is YUY2 then did convert it to yv16 and if plugins need YUY2 (like FFT3DFilter) then convert it back to YUY2 and after that plugin convert back to yv16 until the end of script and in the end convert the output to YUY2

with this you will not need to did another edit in the future in case all filters have yv16 support

yadifmod2 is good but unfortunately that will make winxp users unhappy

For the most part I followed the advice from Writing better AviSynth plugins By tp7 - Stop YUY2 section on avoiding YUY2 where possible and relying on users to add ConvertToYV16().QTGMC().ConvertToYUY2() if keeping YUY2 is necessary for any reason, but it would be trivial to automate this step with conditional conversion internally at the start and end if it is considered important enough.

As for plugins that don't support YV16 yet and require YUY2, I think what you suggested is what I already did - unless I'm misunderstanding you. The remaining conversions have been moved to directly before/after filters that need YUY2 instead of having sections of interleaved YUY2 and sections of planar YUY2 as it was before.

[Groucho2004]

Originally Posted by real.finder

test it now in winxp in VirtualBox, and it realy work

Chikuzen did not test XP compatibility and with VS2015 it's safe to assume that without some special switches it won't work on XP. So, stating VistaSP2 as a minimum is the sensible thing to do in this case.

[real.finder]

Originally Posted by ravewulf

For the most part I followed the advice from Writing better AviSynth plugins By tp7 - Stop YUY2 section on avoiding YUY2 where possible and relying on users to add ConvertToYV16().QTGMC().ConvertToYUY2() if keeping YUY2 is necessary for any reason, but it would be trivial to automate this step with conditional conversion at the start and end if it is considered important enough.

As for plugins that don't support YV16 yet and require YUY2, I think what you suggested is what I already did, unless I'm misunderstanding you. The remaining conversion have been moved to directly before/after filters that need YUY2 instead of having sections of interleaved YUY2 and sections of planar YUY2 as it was before.

you did it in another way, you did support yv16 in hack way, and dropped YUY2, my suggested is to did YUY2 support in more clean and fast way (same as you did but for YUY2 not yv16)

and the yv16 support is work in pure yv16 and that mean now not all features of qtgmc work with it, until all plugins supports yv16, and when that happened you will not need to did another changes

[dandyclubs]

QTGMC 3.34 bug?

D:\Worker\AVSMeter>AVSMeter.exe -avsinfo

AVSMeter 2.4.6 (x86) - Copyright (c) 2012-2016, Groucho2004

VersionString: AviSynth+ 0.1 (r2294, MT, i386)
VersionNumber: 2.60
File version: 0.1.0.0
Interface Version: 6
Multi-threading support: Yes
Linker/compiler version: 14.0
Avisynth.dll location: C:\Windows\SysWOW64\AviSynth.dll
Avisynth.dll time stamp: 2016-10-26, 17:29:37 (UTC)
PluginDir+ (HKLM, x86): C:\Program Files (x86)\AviSynth+\plugins+
PluginDir2_5 (HKLM, x86): C:\Program Files (x86)\AviSynth+\plugins


[CPP 2.6 plugins]
C:\Program Files (x86)\AviSynth+\plugins+\ConvertStacked.dll [n/a]
C:\Program Files (x86)\AviSynth+\plugins+\DePan.dll [2.13.1.0]
C:\Program Files (x86)\AviSynth+\plugins+\DePanEstimate.dll [2.10.0.0]
C:\Program Files (x86)\AviSynth+\plugins+\DirectShowSource.dll [n/a]
C:\Program Files (x86)\AviSynth+\plugins+\ImageSeq.dll [n/a]
C:\Program Files (x86)\AviSynth+\plugins+\masktools2.dll [2.1.0.0]
C:\Program Files (x86)\AviSynth+\plugins+\mvtools2.dll [2.7.7.22]
C:\Program Files (x86)\AviSynth+\plugins+\nnedi3.dll [0.9.4.32]
C:\Program Files (x86)\AviSynth+\plugins+\RgTools.dll [0.93.0.0]
C:\Program Files (x86)\AviSynth+\plugins+\Shibatch.dll [n/a]
C:\Program Files (x86)\AviSynth+\plugins+\TimeStretch.dll [n/a]
C:\Program Files (x86)\AviSynth+\plugins+\VDubFilter.dll [n/a]

D:\Worker\AVSMeter>AVSMeter.exe H:\WORK\video.avs

AVSMeter 2.4.6 (x86) - Copyright (c) 2012-2016, Groucho2004
AviSynth+ 0.1 (r2294, MT, i386) (0.1.0.0)

Script error: There is no function named 'ExtractU'.
(D:\Portable\Megui\AvisynthFilters\QTGMC.avsi, line 774)
(D:\Portable\Megui\AvisynthFilters\QTGMC.avsi, line 399)
(H:\WORK\video.avs, line 10)



SetMemoryMax(4096)
Import("D:\Portable\Megui\AvisynthFilters\MtModes.avsi")
#Import("D:\Portable\Megui\AvisynthFilters\LSFmod.v1.9.avsi")
Import("D:\Portable\Megui\AvisynthFilters\QTGMC.avsi")
#Import("D:\Portable\Megui\AvisynthFilters\SMDegrain.avsi")
Import("D:\Portable\Megui\AvisynthFilters\FineSharp.avsi")
LoadPlugin("D:\Portable\Megui\AvisynthFilters\KNLMeansCL\KNLMeansCL.dll")
LoadPlugin("D:\Portable\Megui\tools\lsmash\LSMASHSource.dll")
LWLibavVideoSource("H:\WORK\video.lwi")
QTGMC(Preset="Slow")
#crop
KNLMeansCL(d = 1, a = 1, h = 2)
#LSFmod(defaults="slow")
FineSharp()
#resize
Prefetch(8)



how to fix?

[StainlessS]

Script error: There is no function named 'ExtractU'.

Oops, methinks is Avs+ only.

EDIT: Post where 'ExtractU' first appeared (Nov 26 2016):- http://forum.doom9.org/showthread.ph...28#post1787428

[StainlessS]

Dandyclubs,

VersionString: AviSynth+ 0.1 (r2294, MT, i386)

You need more recent version avs+, at least 20161208 r2337dev I think.

[ndjamena]

I had that.

The script checks to see if AVS+ is being used and if it is uses that filter, but I had the "official" version of AVS+ from the home page which apparently was too old...

[ndjamena]

http://forum.doom9.org/showthread.ph...29#post1788529

According to this, ExtractU wasn't implemented until last month, which is odd becuase the script is definitely checking for "r1576" in the version string which was a build released back in 2014.

ssispmt = Findstr(VersionString(), "AviSynth+") != 0 && Findstr(VersionString(), "r1576") == 0

I must be missing something.

[StainlessS]

ExtractU wasn't implemented until last month

Mentioned last month, but supporting version not posted till 6th of this month, ie 11 days ago.

[ndjamena]

The version string I'm being given now has r2337 in it, so unless I'm misreading the code QTGMC isn't using ExtractU with the latest build of AVS+ anyway.


-edit-

OK then, I misread it.