QTGMC Deinterlacing Script (v3.384)

[Cary Knoop]

Originally Posted by LigH

Why I think it's nonsense to have FullHD Telecine ... why would anyone produce that? I see no reason with modern TV sets which can easily adapt to many frame rates, and versatile consumer media supporting a variety. But if you say they exist, well ... then this is a fact I have to accept.

Good luck in sending a 1080p24 master for broadcast. They will likely tell you to telecine it first.

Also, some (older) cameras produce 1080PsF output which is telecined as well.

[LigH]

And the HEVC specs wanted to get rid of an interlaced mode ... sigh ... and x265 supports it again. Conservativism demands compatibility.

Well, it's not the fault of QTGMC. I'd agree to close this detour.

[DeafYakuza]

Thank you for many tips. But after the conversion I'm not satisfied with the output quality (mp4 AVC 1080p). There are to much pixels on screen than the original capturing (used via VLC by inverse telecine (film NTSC (IVTC)).

Look here:

https://mega.nz/#!92AnCSIL!-zJXEFEGV...M_M2YWxK9Sdyeo

LoadPlugin("C:\Windows\System32\TIVTC.dll")
AVISource("Source_my_Video.avi", audio=true)
AssumeTFF()
AssumeFPS(30000,1001)
ConvertToYV12(interlaced=true)
TFM()
TDecimate()
BilinearResize(1920,1080)

Does someone know which methods/functions should I to use to get the best quality for deinterlace?

[DeafYakuza]

Originally Posted by poisondeathray

If this is film content, it should be AssumeFPS(30000,1001) if it comes before TIVTC . That will result in 23.976 fps after TIVTC .

If you assume 24000/1001 before, you will end up with 19.something fps

You are right, I tried it to use assume 24000/1001 before and it was 18...fps. Now it's correct but the quality is not good.

[LigH]

Your screen has always pixels, and I hope it has a lot of them. Pixels are the hardware display units, not image artifacts. What you are complaining about, according to your linked image (you should have used an "image hoster" which allows to link the image, like frupic, tinypic, ingur, ... instead of mega) is a loss of resolution, but the reason is hard to know with one single partial screenshot. We would need a short video (best with some side panning) to analyze.

Oh, look, I wanted to put it on frupic, but it's already there...



If you look closely into the left part you will notice it's still combed. Whatever happened, IVTC in VLC did not fix it. And ffmpeg never appears in this workflow. In AviSynth it's TIVTC as well.

By the way, the TIVTC.dll does not belong into your Windows system directory (because Windows would not use it ever). It may be placed into your AviSynth plugins directory instead.

[poisondeathray]

Originally Posted by DeafYakuza

You are right, I tried it to use assume 24000/1001 before and it was 18...fps. Now it's correct but the quality is not good.

Maybe you should post a sample of the source

If it's really 3-2-3-2 ; this imples 3:2 pulldown and you should not deinterlace . Or clarify what you you mean by "it's templated by 3-2-3-2"

[VoodooFX]

Originally Posted by DeafYakuza

Alright... It looks this method should be correct, right?

Install Avidemux, drag & drop your video in Avidemux, search for a scene with movement, cut 10 seconds of that scene (mark start/end points with "A" & "B" buttons and save it), upload it to mega, post link here.

[DeafYakuza]

Ligh, okay, next time I will put the images to frupic - thanks!

Yeah, the file of TIVTC.dll was copied in Windows System32 and I changed it into avisynth plugin and it doesn't changed on quality.
Maybe I programed something wrong in the AvsPmod.


poison,

# Analyse-Script to watch for the field to field
AVISource("my_video.avi")
AssumeTFF()
Bob()

Here is a link to check the info of videosample:

Sample

[LigH]

Oooh ...

Actually, I do not really understand what's happening here. When I check the field pattern with Bob(), the result looks like it has been composed of badly upscaled SD resolution. And for some reason, TIVTC looks just the same, as if it returns only one of both fields.



Moderators: This discussion should be separated from the QTGMC thread.

[DeafYakuza]

We can post here further: https://forum.doom9.org/showthread.p...75#post1856075

[bruno321]

My QTGMC was not working correctly (it was giving a wobbly image), so I decided to update everything.

Currently, a simple

MPEG2Source("file.d2v", cpu=0)
QTGMC()

gives me a "there is no function named "msuper"". But I do have (the latest version of) mvtools2.dll in my plugins folder. What's going on?

[Groucho2004]

Originally Posted by bruno321

My QTGMC was not working correctly (it was giving a wobbly image), so I decided to update everything.

Currently, a simple

MPEG2Source("file.d2v", cpu=0)
QTGMC()

gives me a "there is no function named "msuper"". But I do have (the latest version of) mvtools2.dll in my plugins folder. What's going on?

Download AVSMeter from my sig, run "avsmeter avsinfo -log" and post the log file. Use pastebin or similar to post the log.

[bruno321]

Here's what it says:

[Groucho2004]

Originally Posted by bruno321

Here's what it says:

Update Avisynth -> https://github.com/pinterf/AviSynthPlus/releases

[bruno321]

Oh. I thought that the one available at https://sourceforge.net/projects/avisynth2/ was the latest one. The message the utility gives is a bit funny, seeing as the version installed is 2.6 and it tells me to upgrade to 2.6

Will try installing that one in a couple of days -- now I'm in the middle of an encode (which doesn't use QTGMC :P). Thanks for the advice.

[Groucho2004]

Originally Posted by bruno321

Oh. I thought that the one available at https://sourceforge.net/projects/avisynth2/ was the latest one. The message the utility gives is a bit funny, seeing as the version installed is 2.6 and it tells me to upgrade to 2.6

2.6.0.2 was a beta (or alpha, not sure) that did not even support interface version 6. The 2.6 release is 2.6.0.6. However, I'll update that error message to be more specific.

[StainlessS]

There was no beta series, was

2.6.0.2 Alpha 3, (25 May 2011)
2.6.0.3 Alpha 4, (14 Jan 2013)
2.6.0.4 Alpha 5, (18 Sept 2013)
2.6.0.5 RC1, (14 Jan 2015)
2.6.0.6 RC2, (31 Mar 2015)
2.6.0.6 RC3, (19 Apr 2015)
2.6.0.6 FINAL (31 May 2015)
---
2.6.1 Alpha 1, (17 May 2017)

Think Version 6 Header (AvisynthPluginInit3) came in with Alpha 4.

[bruno321]

OK, avisynth updated. Here's the log from AVSMeter:

https://pastebin.com/2hqZYevT

EDIT: OK, I should add that now QTGMC -is- working, but in the same faulty way as described here: https://forum.videohelp.com/threads/...after-srestore

EDIT2: Got it!! It was the bloody mt-masktools-26 which was preventing the newer masktools2.dll from loading.

Thanks for the help & thanks for AVSMeter! It really helped.

[hello_hello]

Originally Posted by bruno321

OK, avisynth updated. Here's the log from AVSMeter:

https://pastebin.com/2hqZYevT

EDIT: OK, I should add that now QTGMC -is- working, but in the same faulty way as described here: https://forum.videohelp.com/threads/...after-srestore

The AVSMeter log shows you have two versions of MaskTools2 (mt_masktools-26.dll) and an old version of SMDegrain.

You probably should remove any Avisynth 2.5 plugins beginning with "R" (you have multiple version of each anyway) and replace them with RGTools. There's an up to date requirements list here.

Did you use the XP specific versions of MaskTools2 and MVTools2?

You probably don't need SSE2Tools.dll anymore (and you have multiple versions).

The log file clearly shows you're missing dependencies for some of the plugins. As you update them, check the required dependencies, They'll either be listed on the plugin's wiki or specified in the readme file included in the download, or something similar.

msvcr71.dll and FFTW3.dll belong in the system32 folder. You should also have libfftw3f-3.dll in there (same file as FFTW3.dll, but some plugins expect different names).

I also spotted a couple of outdated plugins. There's newer versions of Average and nneid3.

I tried your sample from the VideoHelp thread and it's fine for me simply using the following. I'm running XP (QTGMC 3.358s).

QTGMC()
SRestore()

[bruno321]

Thanks for the tips -- as you were writing your reply, I updated my post above to show that I solved it. Nonetheless, what you write is useful. I have updated SMDegrain and replaced the R plugins with RGTools, will look at Average and nnedi3.

So I'm guessing that the plugins marked in yellow are those whose dependencies are not fully met? If everything is working OK for me now, would I gain something by meeting them?