QTGMC Deinterlacing Script (v3.32)

[-Vit-]

Originally Posted by Boulder

-Vit-,

are you planning to recompile "your" plugins with the changes regarding the new Avisynth 2.6 CVS commit?

If the original plugin authors recompile then my modded versions will be unnecessary, since the changes make my fix redundant (I believe). However, as several of the plugin authors are no longer around, I will do something about it....

[jfcarbel]

Looking to take some footage from Panasonic HD Camera that is 1080 60i and deinterlace it to 1080 30p. I would preferably like to edit in Vegas and then render to x264 if possible.

Anyone have done with same type video with this deinterlacer and can suggest a process?

[noee]

Originally Posted by jfcarbel

Anyone have done with same type video with this deinterlacer and can suggest a process?

I can't get into the "editing" process I use, but, fwiw, I have a very simple setup for final encode with x264 that is quite reliable and delivers very consistent results. Here is an example I use for archiving for video that I don't need full 1080p or are of lower importance (source is from Canon 1080i60):

AVS script

SetMemoryMax(900)
SetMTMode(5,6)
AVCSource("C:\Temp\movie.dga")
ChangeFPS(last,last,true)
SetMTMode(2)
AssumeTFF()
spline64resize(1280,1080)
QTGMC(Preset="Super Fast", EdiThreads=6)
SelectEven()
spline64resize(1280,720)
Return last

You can guess how the source indexing is done...Of course, you can play with the options depending on your desired results.

x264 commandline (CRF example):

...\applications\x264\x264_32_10.exe --colormatrix bt709  --preset SuperFast --tune Film --crf 22 --aq-mode 3 --output "E:\Temp\output.h264" "E:\Temp\encode.avs"

I have an audio conversion step (FFMpeg), an indexing step and at the end, MKVMerge.

HTH.

[henryho_hk]

Originally Posted by jfcarbel

Looking to take some footage from Panasonic HD Camera that is 1080 60i and deinterlace it to 1080 30p.

What is the model number of the camera?

[jfcarbel]

Originally Posted by henryho_hk

What is the model number of the camera?

Panasonic HDC-SD800

[-Vit-]

Here is a package of plugins for QTGMC using the latest Avisynth 2.6 interface. They may provide better multi-threading stability:
QTGMC 32-bit Plugins [Vit-2.6] (mirror1 | mirror2)
Thanks to SubJunk for the filehost-free mirror!

These plugins have been updated to the latest 2.6 interface:
- MVTools, MaskTools, NNEDI3, EEDI3, RemoveGrainSSE2, RepairSSE2, dfttest, FFT3DFilter, AddGrainC, VerticalCleanerSSE2, TDeint
The dlls are named as normal (for now).

These plugins are provided in their original form (not updated because they have no source code; or are legacy; or use the C interface).:
- Yadif, SSE2Tools, NNEDI2, EEDI2, NNEDI

The updated plugins will only work with versions of Avisynth 2.6 that support the new interface. Currently I believe that's only SEt's latest Avisynth 2.6MT build.
The new interface removes some code that was embedded in every plugin that could cause multi-threading problems. So these plugins may be more stable, although many multi-threading issues are memory-related these days. It's fine to use some updated plugins and some older ones. But the more new versions you get, the better for MT stability.

This package is provided for test purposes only, it's not "official" yet. Partly because these plugins are no longer "modded", they're just up to date, and I hope that some of the original authors will provide "official" builds eventually. Also there's a dll versioning problem now - we have 2.5 plugins, 2.6-old-interface plugins, modded versions of those, and 2.6-new-interface plugins. Added to that there are cretindesalpes' more recent versions of MVTools and dfttest...

In the longer term we need two just versions of each, a 2.5 compatible and a 2.6 new interface. I'm hoping cretindesalpes will provide 2.6 new interface versions resolving that issue. Then I'll provide just two packs, 2.5 & 2.6, and expect all MT users to switch to 2.6 and SEt's latest. I'm open to opinion about whether the different versions of the plugins should be renamed or not (as masktools does it). Seems to me there are potential problems either way. In any case I'm gonna wait a little before "officially" releasing these things...

[Boulder]

Thanks, I'll update at least NNEDI3 and MaskTools to your versions as soon as my current encode is done. I'm quite sure cretindesalpes will update MVTools soon as he's been quite active.

[markanini]

The updated 2.6 build and plugin pack seems to be a substantial improvement for me. I'm running lsfmod after smdegrain realtime in ffdshow on a i5-2500k at 3.2GHz on sub-SD material, before I couldn't do this smoothly.

[nhope]

Originally Posted by -Vit-

Here is a package of plugins for QTGMC using the latest Avisynth 2.6 interface...

Thanks very much for the updated plugins -Vit-! I see that you haven't included mt_masktools-25.dll in this package. With scripts such as this that use YUY2, I have been using mt_masktools-25.dll from your previous modded plugins package. If I use mt_masktools-26.dll the script runs really slowly and then Virtualdub crashes after a while.

(I do realise I could be using YV12 in that particular script, but that's not the point)

Also, thanks for pointing out previously that thSCD1 and thSCD2 are supported directly in QTGMC. Actually I found that it is in the MFlowFps line that I need them. I got success by dropping thSCD1 to 352 and thSCD2 to 110 from their defaults of 400 and 130.

[nhope]

Originally Posted by jfcarbel

Looking to take some footage from Panasonic HD Camera that is 1080 60i and deinterlace it to 1080 30p. I would preferably like to edit in Vegas and then render to x264 if possible.

Anyone have done with same type video with this deinterlacer and can suggest a process?

You could follow the workflow in my signature, which takes interlaced footage from the Vegas timeline right through to x264.

[kolak]

Originally Posted by nhope

Also, thanks for pointing out previously that thSCD1 and thSCD2 are supported directly in QTGMC. Actually I found that it is in the MFlowFps line that I need them. I got success by dropping thSCD1 to 352 and thSCD2 to 110 from their defaults of 400 and 130.

Yes- I have similar experience from interframe- I think default values are to high.

[SubJunk]

Originally Posted by kolak

Yes- I have similar experience from interframe- I think default values are to high.

The problem is that scene-change detection isn't something that any AviSynth tool (that I'm aware of) can do with good accuracy across many videos, including MVTools2. You can either have it so sensitive that it catches each scene-change but also detects action scenes as scene-changes, or you can make it insensitive so it doesn't detect many changes so it leaves high-action scenes alone.
The only way to get it perfect is to adjust the values per video or per set of scenes.
In InterFrame 1 it is less sensitive and in InterFrame 2 it is more sensitive. But of course, InterFrame 2 is just a beta and is not recommended for use yet. By the time it is ready for release it will have scene-change detection similar to version 1.

[kolak]

Originally Posted by SubJunk

The problem is that scene-change detection isn't something that any AviSynth tool (that I'm aware of) can do with good accuracy across many videos, including MVTools2. You can either have it so sensitive that it catches each scene-change but also detects action scenes as scene-changes, or you can make it insensitive so it doesn't detect many changes so it leaves high-action scenes alone.
The only way to get it perfect is to adjust the values per video or per set of scenes.
In InterFrame 1 it is less sensitive and in InterFrame 2 it is more sensitive. But of course, InterFrame 2 is just a beta and is not recommended for use yet. By the time it is ready for release it will have scene-change detection similar to version 1.

Hmm- funny enough- I have no problems with scene change detection in inteframe 2 Haven't used it that much, but up to now no problems.

[-Vit-]

Originally Posted by nhope

I see that you haven't included mt_masktools-25.dll in this package.

I did consider it, but it felt perverse to include a 2.5 plugin in a 2.6 pack (obviously it can't use the new interface). However, I expect you can still switch to the earlier modded masktools-2.5 for YUY2. The YUY2 pathway does present more plugin problems. It doesn't help that it relies on SSETools2 for which there isn't any source, which means it is probably not thread-safe (no mod, no 2.6 new interface version)

[mp3dom]

Uhmm, with latest AVS 2.6 MT version, and the above plugins, I'm getting a strange error.
"Access violation at 0x00003FA0 in fftw3.dll, attempting to write to 0x00000000".
QTGMC at line 467 (it's a FFT3DFilter call).
The fftw3 DLL is correctly placed in \System32.
The source is a 1080i60, YUY2 colorspace, Edimode as EEDI3+NNEDI3. Using YV12 doesn't change anything anyway (still the same error).
Any idea?
Thanks.

[-Vit-]

I regressed to an older version of fftw3.dll, the one that was originally expected to be used with fft3dfilter. Previously I just renamed the more recent libfftw3f-3.dll, but that really isn't appropriate.... But then again, maybe it is...

Try removing the fftw3.dll I just provided and copy/rename the libfftw3f-3.dll in its place. If that doesn't work, try the fftw3.dll from the modded plugins package in the first post. And please report back your results.

Anyone know the "correct" fftw3.dll to use with fft3dfilter?

[Terka]

Vit, do you plan update QTGMC with SVPflow?

[mp3dom]

Tried both ways, same error with little difference on the address:
"Access violation at 0x000C78B6, attempting to write to 0x00000078"

[HolyWu]

ftp://ftp.fftw.org/pub/fftw/fftw3win32mingw.zip works fine on my system.

[Nevilne]

I've always just kept both latest libfftw3f-3.dll and latest libfftw3f-3.dll renamed as fftw3.dll, seems to work with all my plugins.