QTGMC Deinterlacing Script (v3.32)

[Taurus]

@ChibiBoi
I dont know why you are going for 23.976.
But anyway...Try this:
AVISource("sms vhs test.avi", audio=false).AssumeFPS(30000,1001)
converttoyv12(interlaced=true)
assumetff()
qtgmc(preset="medium")
selecteven()
srestore(frate=23.976)

or this

AVISource("sms vhs test.avi", audio=false).AssumeFPS(30000,1001)
converttoyv12(interlaced=true)
assumetff()
QTGMC(TR0=2, TR1=1, TR2=3, Rep0=0, Rep1=0, Rep2=0, Edimode="NNEDI3",edithreads=1,precise=true,truemotion=true)
srestore(frate=23.976)
Both slow as hell.
The edithreads are adjustable.
And maybe try an Avisynth MT version for speed.
The colours are bleeding and some halos in your source.
But this is another story.

[ChibiBoi]

@ChibiBoi
I dont know why you are going for 23.976.
But anyway...Try this:


or this

AVISource("sms vhs test.avi", audio=false).AssumeFPS(30000,1001)
converttoyv12(interlaced=true)
assumetff()
QTGMC(TR0=2, TR1=1, TR2=3, Rep0=0, Rep1=0, Rep2=0, Edimode="NNEDI3",edithreads=1,precise=true,truemotion=true)
srestore(frate=23.976)
Both slow as hell.
The edithreads are adjustable.
And maybe try an Avisynth MT version for speed.
The colours are bleeding and some halos in your source.
But this is another story.
Thanks, I'll try it. I did a test with preset="slow" for another tape, and the flickering seemed less prominent. The reason I tried to get it to 23.976 is because that's the original animation speed, but it was converted to 29.970 using blended fields and whatnot, so I wanted to get rid of those blendings. And as for haloing and bleeding, I'm not really too concerned with that :p I think I could get something to clean up the bleeding though (I'm worried a dehalo script will change the crispness of the subtitles)

[asdfen]

thank you
awesome script

[DJ-1]

Hi, I got a question regarding the version of ms redistributetable atl updates..
I have a Win7 64bit OS...
NO avisynth (as the Hybrid GUI(32bit) as its own avisynth.dll)

I'm importing PAL DVD (with just 1title/pgc/angle (as avisynth support DVD only in this way))

When trying to preview the clip (with QTGMC de-interlacing) b4 output I'm getting an "error loading eedi3.dll error code 0x36b1"

A possible fix is to install the ms 2005 or 2008 atl update, BUT my pc already has ms redistribute 2010, so do I still need the patched version.... Or does the 2010 version cover it?

I've tried in the relevant thread, but currently the Dev of Hybrid doesn't know what " error code 0x36b1" means for avisynth....

I'm just searching to try and find out if it's related to the atl patches or the eedi3.dll itself....

Thanks.

[StainlessS]

From MSDN
http://msdn.microsoft.com/en-gb/library/windows/desktop/ms681384%28v=vs.85%29.aspx

-------------------
ERROR_SXS_CANT_GEN_ACTCTX

14001 (0x36B1)

The application has failed to start because its side-by-side configuration is incorrect.
Please see the application event log or use the command-line sxstrace.exe tool for more detail.
-------------------

Perhaps the above will enable some W7 user to assist.

Application event log available on W7 via "[Right Click]Computer/Manage/Event Viewer" (if "My Computer" on Desktop) or,
Via Windows Explorer -- "[Right Click]Computer/Manage/Event Viewer"

EDIT: For a related problem with MS Office Access 2010:- http://support.microsoft.com/kb/2525435

EDIT: and the source for the previous link:http://forum.worldoftanks.com/index.php?/topic/133678-launcher-critical-error/page__st__20__pid__2102316#entry2102316

[Selur]

As the Hybrid author I have to say: I have no clue why it's not working for him.
I can't reproduce the problem on any of my Windows machines (Windows XP 32, Windows 7 32/64bit)
@DJ-1: do you use some personnel firewall or similar? (if so try if it helps to disable it) Last time a user had a problem which I couldn't replicate at all it turned out that his "ZoneAlarm Firewall Free" interfered with Hybrid to make it crash randomly. (couldn't reproduce that either by installing "ZoneAlarm Firewall Free" here, but it solved the problem for him, so my be you got a similar problem.

Cu Selur

Ps.: the avisynth.dll Hybrid is using is the normal Avisynth 2.6 MT dll.

[Taurus]

"I'm getting an "error loading eexi3.dll error code 0x36b1"
This is a typo, right?
The real name should be "eedi3.dll".
Better post your whole script.

[Selur]

That was a typo he made. :) (Hybrid calls eedi3.dll, otherwise it wouldn't work for me too ;))

[Selur]

Problem is that eedi3.dll depends on some vcomp dll -> can someone upload a eddi3.dll together with the vcomp.dll it requires?

[Taurus]

Problem is that eedi3.dll depends on some vcomp dll -> can someone upload a eddi3.dll together with the vcomp.dll it requires?
I have a working version of eedi3 and many vcomp.dll's :(:o
Where can I upload the files for you?
Please not mediafire.
Edit:
Aaah, I forgot to mention this is on WinXp32bit.

[Selur]

@Taurus: send you a pm

related question: will it be enough to put the vcomp.dll next to eedi3.dll or does it have to be inside the windows/system32 folder?

-> seems like the only way to get is running is to install:
http://www.microsoft.com/en-us/download/details.aspx?id=3387 (Visual Studio 2005 runtime)
and
http://www.microsoft.com/en-us/download/details.aspx?id=5638(Visual Studio 2005 runtime SP1)
->would be cool if someone could compile eedi3 in with a newer version installing 2005 runtime when we are nearly @2013,...
(copying the vcomp.dll from the 'Visual Studio 2005 runtime SP1' leaves me with interlockedIncrement and interlockedDecrement missing from the kernel32.dll, seems like eedi3.dll tries to load windows/system32/kernel32.dll, shouldn't it load windows/syswow64/kernel32.dll ??)

[SEt]

Here is rebuild of eedi3 without OpenMP: http://www.mediafire.com/?hthznhnhe5h59g5

[Selur]

Works without a problem. THANKS SEt!!

[Maxiuca]

I have a problem with the way motion blur is being applied.

I've noticed the problem on a real-life footage I'm just working with. I've created a test sequence to look further into it and try to find a parameter responsible, but so far no luck.

The test footage is basically a static background with an object moving across it.

Here is a frame from that test footage:
http://fixafilm.eu/temporary/doom9/orginal.jpeg

The deinterlace step is (of course :) ) fine:
http://fixafilm.eu/temporary/doom9/deinter_shutter_0_crop.jpegLink to full image (http://fixafilm.eu/temporary/doom9/deinter_shutter_0.jpeg)

The problem starts when I want to add motion blur.
The blur itself looks really nice but the problem is the area where it's being applied. It looks like the motion (used to determine which area to blur) is calculated from both fields, so the blur is also being applied to area with motion on the other field so in the end it creates a "ghost". This ghost is usually next to the moving object, so over some backgrounds it will give a "smearing" effect.

Here is the same frame, but with motion blur on:
http://fixafilm.eu/temporary/doom9/deinter_shutter_180_crop.jpg
Link to full image (http://fixafilm.eu/temporary/doom9/deinter_shutter_180.jpeg)


So I was wondering whether it is possible to calculate the motion for the motion blur from only one field?

I've read the manual very thoroughly, spent a lot of time doing the tests but haven't found a corresponding switch.

[2Bdecided]

I asked the folk on the Sony Vegas forum (http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=754540&Replies=10) and the general consensus is that 50i @ 1/50 or 60i @ 1/60 equates to a 180 degree shutter angle.
I wish I'd spotted this sooner. IMO the people you asked on the Sony Vegas forum didn't know what they were talking about. A 360 degree shutter (mechanically impossible btw!) captures everything. 1/50th 50i captures everything. 1/50th 50i is a 360 degree shutter. 1/60th 60i is a 360 degree shutter.

1/120th 60i is a 180 degree shutter.

1/48 at 24p is also a 180 degree shutter.

The shutter relates to the individual moments in time that you capture. For interlaced footage, these individual moments are fields. For progressive footage, these individual moments are frames. It's really not that complicated (when you get it right!).

Cheers,
David.

[nhope]

... The shutter relates to the individual moments in time that you capture. For interlaced footage, these individual moments are fields...

Not sure about that, David. My Sony Z1's shutter defaults to 1/60 at 60i. By your theory that makes it as 360 degree shutter. I've always assumed it's actually only open half the time (i.e. 180 degree equivalent), but I've never tested it. In other words, at least in Sony's case, I suspect the shutter relates to frames, not fields.

It doesn't really help that 50i and 60i should probably be called 25i and 30i.

[2Bdecided]

Not sure about that, David. My Sony Z1's shutter defaults to 1/60 at 60i. By your theory that makes it as 360 degree shutter. I've always assumed it's actually only open half the time (i.e. 180 degree equivalent)Well then it's not 1/60th is it, because there is no one in the world who argues about the definition of seconds (or fractions there of), or the durations of fields in 60i video - the two are identical (to within 1000/1001 ;) ) and if a camera says "1/60th" when it means "1/120th", it is simply wrong.

However, I suspect it's absolutely correct. Many video cameras default to 1/50th for 50i and 1/60th for 60i - i.e. 360 degree shutter, or (as near as damn it as you can manage easily) Nyquist temporal sampling - i.e. not leaving anything out. It avoids stutter. Cheaper cameras often shorten the shutter to combat lots of light, leading to strobing.

It doesn't really help that 50i and 60i should probably be called 25i and 30i.I think all sensible people know that both mean the same thing. Some may wish to argue about which is more correct, but that's a different matter. There is no confusion, since there is no video format with 12.5 interlaced fields per second, nor one with 100 interlaced fields per second (though some old CRTs ran their displays at this rate!).

Cheers,
David.

[kolak]

Hehe- BBC guys say 25i (or even i25 if I remember correctly)- I don't know in what sense this is better than 50i. For me 50i makes more sense then 25i. 25p is 25 frames/sec, so 50i is 50 fields/sec. 25i makes no sense, as we should be talking about fields, not frames in case of interlaced signals.

[Selur]

25i = 25 interlaced frames :D
I like this notation more since it always indicates frames per seconds and not one time fields and one times frames. ;)

[Poutnik]

I use the latest SET's MT Avisynth 2.6, but the testing plugin pack for AVS 2.6 give me Memory read access violation errors for most of plugins.
( I.e. when I replaced the affected plugin one by one, it occurred again and again at some other plugins from the package ).

Currently I use Plugins from Vit's Modded package.

[Didée]

coded_frames/coding_type/number_of_samples. 25i25, 25i50, 30i60, 30i24, all confusion gone.

But hey, it would be too boring if everyone knew what everyone else is talking about. Confusion and misunderstanding keeps people busy.

[LigH]

is it ok to use this version (3.33)

i'm asking as it's not here which is making me think perhaps not to use it.

http://www.spirton.com/uploads/QTGMC/QTGMC-3.33.avsi

Most probably yes. As far as I understand the changes, they are more than just "cosmetic".

[bcn_246]

# --- LATEST CHANGES ---
#
# v3.33
# - Increased maximum value for Rep0, Rep1 and Rep2 to 7 (from 5). Higher values help with flicker on static detail, potential for minor motion blur
# - Bug fix for the fact that Bob always outputs a BFF clip regardless of field order of input (thanks ajp_anton)
# - Improved generation of noise (NoiseDeint="Generate") for noise bypass / EZKeepGrain
# - Minor change to denoising

I've been using it for ages, not seen any issues...

[trevorjharris]

I cannot get QTGMC 3.33 to run multithreaded without crashing in mt_masktools-26.dll. I have a HP Z800 with dual xeon X5660 (6 core) and 48gb of memory and I am using virtualdub.. I removed all traces of my previous avisynth and installed avisynth 2.6 alpha 4. I then installed avisynth 2.6 MT dated 16-5-2012 and the latest plugins pack posted by vit. This is the script I used:

SetMemoryMax(400) # Optional line. Leave it out at first. See below for value M
SetMTMode(5, 6) # See below for value X
avisource("00218.avi")
assumetff()
converttoyv12(interlaced=true)
SetMTMode(2)
QTGMC( Preset="fast", EdiThreads=3 ) # Choose preset based on overall speed/quality you want. See below for value Y
selecteven()
#Distributor() # This line may or may not be necessary, try removing it and see if you get more speed

I have tried the other plugins pack without success. Please can anyone help.

[LigH]

You may try using mt_masktools-25.dll as you only need YV12 anyway, it is probably more stable. And you may want to reduce the number of tasks as you will probably multiply 3×EDI with 6×QTGMC.

[trevorjharris]

Thanks for your help.
Actually I seem to have found an answer. I set virtualdub to be large address aware and it is much more stable. This seems to be my optimum setup:

SetMemoryMax(1000)
SetMTMode(5, 4)
avisource("00218.avi", audio=false)
assumetff()
converttoyv12(interlaced=true)
SetMTMode(2)
QTGMC( Preset="slow", edithreads=2)
selecteven()
#Distributor()

I find it rather odd that I have to setmtmode to such a low value as I have 24 threads available. CPU usage is only about 16% and I get 5 fps from an hdv clip. If I increase the threads I get over 80% usage but it runs alot slower.

I think it is about time avisynth and all its filters were 64bit and avoid all this sillyness.:)

[LigH]

If it were so easy to port the AviSynth source to 64-bit with a stable result, it were already done. Instead, its "coding style" (cough) seems to be the reason why it doesn't finish...

[Selur]

I find it rather odd that I have to setmtmode to such a low value as I have 24 threads available.
Your problem is probably that the memory the threads need combined with the SetMemoryMax are simply cracking the limit of RAM 32bit Avisynth can handle,...

[Mystery Keeper]

Offtopic, but I agree. AviSynth AND its plugins need to be made x64 aware. Right now even if I use x64 AviSynth and plugins - they crash at reaching 4GB memory load.

[trevorjharris]

A couple of questions:

Please can some one tell me if there is any difference in using FPSDivisor=2 or selecteven() to get the original frame rate.

The other concerns color spaces.

I am using DebugMode frameserver which delivers YUY2 and compressing with cineform which also uses YUY2, so I am using QTGMC in YUY2 mode to avoid conversions. My ultimate destination is Blu-ray which is YV12.

My question is will I loose quality if I use QTGMC in YV12 mode by converting to YV12 before deinterlacing. I have always felt that it is best to minimise color space conversions but I have wondered if deinterlacing in YUY2 might give better quality.

Thankyou for your help.

[LigH]

FPSDivisor belongs to the Motion Blur feature; SelectEven instead removes each second output frame regardless of the used features.

YUY2 represents Chroma Subsampling 4:2:2; YV12 represents Chroma Subsampling 4:2:0. Indeed, the vertical chrominance resolution is higher in YUY2. If you have enough time and available RAM, a late conversion may keep a little more quality until the end, at the cost of 4:3 required memory per cached/processed video frame and time to process so much more data; if you can recognize the difference, is another topic.

[Pulp Catalyst]

hi, with 3.32 or 3.33 script,

the following works fine, never get a crash

global MeGUI_darx = 123
global MeGUI_dary = 92
SetMemoryMax(1024)
SetMTMode(5,4)
LoadPlugin("D:\Program Files (x86)\MeGUInew\tools\dgindexnv\DGDecodeNV.dll")
DGSource("E:\Working\qi4nlowk.vns\War03.dgi",fieldop=0)
SetMTMode(2,2)
QTGMC( Preset="Slow" )
SelectEven()
#deinterlace
crop(6, 0, -10, 0)
#resize
#denoise



however when using Progressive mode, i always (ALWAYS) get a crash around the 50-80% of the encoding process,

the following script is what i use

global MeGUI_darx = 123
global MeGUI_dary = 92
SetMemoryMax(1024)
SetMTMode(5,4)
LoadPlugin("D:\Program Files (x86)\MeGUInew\tools\dgindexnv\DGDecodeNV.dll")
DGSource("E:\Working\qi4nlowk.vns\War03.dgi",fieldop=0)
SetMTMode(2,2)
QTGMC( Preset="Slow", InputType=1 )
#deinterlace
crop(6, 0, -10, 0)
#resize
#denoise



now i use Avisynth MT 2012.08.28 although i have also tried 2012.05.16 to no avail,

i have tried several different DVD's all the same

i have also tried a combination within the script

SetMTMode(5,4)
5,2 and 5,6 nothing

SetMemoryMax(1024)
512 and 1536

weird why it ALWAYS works with using the first method, but the other method always fails (crash)

any ideas why this could be happening, really appreciate it the feedback,

for the time being, i've resorted too LimitedSharpenFaster(), which is OK really..... but not sure if I'm missing out by NOT using QTGMC for progressive sources?

[Mole]

I also usually get crash in the middle or at the end when using InputType=1.

My remedy is to use SetMTMode(5,0)

It won't be multithreaded, but at least it'll finish 100%, albeit slowly.

[yup]

Pulp Catalyst!
SetMTMode(5,4)
and after
SetMTMode(2,2)
useless number threads set at first call SetMTMode
try
SetMTMode(5,2)
and after
SetMTMode(2)
and report
Go to Win7 x64 or add memory and use LAA. When I am upgrade my PC to Win7 x64 QTGMC became more stable.
yup.

[Pulp Catalyst]

my combinations have already came close to that, and SetMTMode(2) is not that much difference to SetMTMode(2,2) but i put two in to keep the number even

i'm on x64 with 8gb, but i have a strong feeling that this crash is not memory related,

but i'm not skilled enough to analyse the script to see what differs in operation when using InputType=1 as opposed to without this line, for example does Input=1 run an extra plug-in that maybe responsible for not playing nice?

[LigH]

As far as I remember, the number of threads must not be set in any call of SetMTMode except the very first. At least it should not change the number of threads again in later calls. I am not sure if it may cause instability trying so, only a look into the AviSynth-MT source code will prove if it is safe or unsafe to even try.

AviSynth Wiki: Multithreading functions (http://avisynth.org/mediawiki/Internal_functions/Multithreading_functions)

threads: Number of threads to use. Set to 0 to set it to the number of processors available. It is not possible to change the number of threads other than in the first SetMTMode. Default value 0.

[Pulp Catalyst]

didn't make any difference, tried several more different combinations, also changed masktools versions, and tried several backdated avisynth versions.... all to no avail unfortunately,

it's not a major issue mind, as like i said above QTGMC works really well in default mode "QTGMC( Preset="Slow" )
SelectEven()" and it was designed for interlaced material in mind, in fact i can't recollect ever having a crash with it when using it for interlaced material, i guess i'll just have to accept that when it comes too progressive material i can't use it!

looking forward to the day though that the mess behind avisynth is once and for all settled... there seems to be a lot of branches now...

i have a lot of hope though in this new vapoursynth.... looks promising (of course all the old plugins would have to be ported.... and most of the developers aren't around no more.... getting hold of permissions will be a near impossible task for some of them)

but the extensive support behind vapoursynth is really starting to come into it's own now, been following it for a long time.... to rewrite a foundation such as avisynth.... my hat goes off!

[nhope]

A couple of questions:

Please can some one tell me if there is any difference in using FPSDivisor=2 or selecteven() to get the original frame rate.

I don't think there is a difference. I used to use selecteven() and now I use FPSDivisor=2. If in doubt do a test with each and A/B compare them in 2 tracks in your NLE while looking at the NLE's waveform scope. I suppose FPSDivisor=2 might be doing a selectodd() though.

I am using DebugMode frameserver which delivers YUY2 and compressing with cineform which also uses YUY2, so I am using QTGMC in YUY2 mode to avoid conversions. My ultimate destination is Blu-ray which is YV12.

My question is will I loose quality if I use QTGMC in YV12 mode by converting to YV12 before deinterlacing. I have always felt that it is best to minimise color space conversions but I have wondered if deinterlacing in YUY2 might give better quality

Are you using Sony Vegas? That works internally in RGB, so I always frameserve out of it in RGB24. See the posts from Frameserver author Satish in this old thread (http://www.sonycreativesoftware.com/forums/showmessage.asp?forumid=4&messageid=301018).

So if you frameserve in YUY2 then Frameserver is just doing a conversion. I prefer to do such a conversion later in AviSynth. If Cineform will handle YV12 then I would convert to YV12 in AviSynth before deinterlacing.

I do use YUY2 instead of YV12 if I am re-interlacing later the script for DVD using Weave, because of this (http://forum.doom9.org/showthread.php?t=161011).

If you are using another NLE such as Premiere Pro then the above might be irrlevant to your case since it's not necessarily delivering RGB to Frameserver. See the Frameserver usage instructions (http://www.debugmode.com/frameserver/usage.htm).

[trevorjharris]

My workflow is now:

Use mvctoavi to convert mvc to cineform.
Use virtualdub and qtgmc to deinterlace and change to 23.976 to cineform.
Use firstlight to mutiplex left and right into a cineform 3d file.
Edit in Premiere Pro and export as cineform 3d.
Import to Vegas Pro and render avc and mvc file.
Import to DVD Architect Pro.

Cineform is YUY2 10 bit so after deinterlacing 10 bit YUY2 is preserved till Vegas Pro. It is a great pitty the qtgmc is only 8bit.

I am coming to the conclusion that it best to deinterlace before editing. When I tried editing interlaced video in Vegas and I got some horible artifacts. I suspected the Vegas was deinterlacing and reinterlacing to render. I have since learned that you must not set vegas interlace method to none when editing interlaced video. Premiere pro is a much better editor than Vegas as it can use YUY2 and up to 32 bits. I use Vegas just for encoding MVC.

It is very important to make make Virtualdub "Large Address Aware" particularly on 64bit machines. Since doing this I have not had a single crash from qtgmc.

[2Bdecided]

Anyway, any chance of correcting the shutter angle?
http://forum.doom9.org/showthread.php?p=1611626#post1611626

[bcn_246]

I use the latest SET's MT Avisynth 2.6, but the testing plugin pack for AVS 2.6 give me Memory read access violation errors for most of plugins.
( I.e. when I replaced the affected plugin one by one, it occurred again and again at some other plugins from the package ).

Currently I use Plugins from Vit's Modded package.

I found exactly the same thing. Have .NET v4.5, Visual C++ 2005/2008/2010 (x86 & x64) installed.

Have reverted to the original -Vit- mod pack and havn't had any issues (except with masktools - had to revert to the standard a48 in order to get any support for YV16/YV24.

[Mole]

When using FPSDivisor=2

Does it discard the frames before or after the denoise routines?

There may be a difference regarding how temporal noise is processed if the denoise routines are performed after the decimation.

[dioxin]

Hi! In some anime there's such artifacts as they can fix it?
http://s1.ipicture.ru/uploads/20130130/T2wRZuw2.pnghttp://s1.ipicture.ru/uploads/20130130/axaZXOOI.png

[LigH]

Do not try to deinterlace Anime with QTGMC. Anime has no continuous interlacing. Motion prediction will fail.

[Mole]

Did you crop before using QTGMC? If so, you must either crop by 4 pixels, or use crop after QTGMC.

For example, crop top 6 pixels is not good, you must crop 4 or 8.

You will get effect like that if you crop before QTGMC.

[TheSkiller]

This effect is due to either upsampling the chroma in a progressive fashion while the frame was actually showing interlacing (before IVTC or deinterlacing) or because the field order of the chroma – but not the luma – was swapped by cropping beforehand.

You cannot fix it afterwards without nuking the chroma, it's screwed up.

[kolak]

I use TFM to find progressive frames and than QTGM for deinterlacing, but sometimes progressive frames are detected and processed by QTGMC (no way to make TFM 100% accurate).

Deinterlacing is more important, but are there any settings in QTGMC, which would help to keep other frames more as source?

[mastrboy]

I use TFM to find progressive frames and than QTGM for deinterlacing, but sometimes progressive frames are detected and processed by QTGMC (no way to make TFM 100% accurate).

Deinterlacing is more important, but are there any settings in QTGMC, which would help to keep other frames more as source?

Read the "manual" on the Sourcematch parameter.

[kolak]

SourceMatch is to slow for HD even with very fast preset.

[simcut]

Had a quick question, does it matter what order you put things in the avs script, for example if I put the crop info before the QTGMC line, or the SelectEven before/after the QTGMC line? whats the correct structure?

An example of how I have it right now is:-

# Set DAR in encoder to 16 : 9. The following line is for automatic signalling
global MeGUI_darx = 16
global MeGUI_dary = 9
LoadPlugin("C:\Program Files (x86)\MeGUI_2153_x86\tools\dgindexnv\DGDecodeNV.dll")
DGSource("D:\Encode\SATA 1\Test.dgi",fieldop=0)
AssumeTFF()
crop(0, 2, 0, -2)
QTGMC( Preset="Medium" )
SelectEven()

is that okay?

Thanks in advance