QTGMC Deinterlacing Script (v3.32)

[WorBry]

Thanks Boulder. I'll look at that.

I think I might have edited-in my last question after you posted:

Originally Posted by WorBry

And, sorry for my ignorance (I've been out of the game for a good while), but how does one run multiple one-thread encodes simultaneously on a single PC?

And my query about the modded vs regular filter set? Just want to be sure.

[Boulder]

I run 4 VirtualDub instances with each of them processing their own part of the video (using Trim to set the parts). I encode all parts to intermediate files with a lossless codec (FFV1 found in ffdshow) for easy joining and no quality loss. Of course, it requires a substantial amount of hard disk space especially with HD video.

Personally I use the regular filter set apart from the MaskTools build which is the one that was adapted to the latest API.

[WorBry]

OK, thanks. I wondered if you were maybe farming out to multiple PC's. Obviously a bit tedious, marking the trim set points and re-splicing, but probably quite efficient from the encoding perspective. On my new PC, MT-AVISynth processing speeds up QTGMC about 3-fold. It would be interesting to see how 4 simultaneous instances of non-MT encoding compares.

[SamKook]

Originally Posted by WorBry

It would be interesting to see how 4 simultaneous instances of non-MT encoding compares.

That's exactly what I plan to test very soon since an earlier conversation here made me realize that it might be better for HD movies.

I just have to finish reinstalling everything I need since I changed my OS drive and make sure everything in my batch file still work fine with the newly installed everything.

Instead of virtualdub, I personally use mencoder to encode to a temporary FFV1 file, but both work fine in a batch script so you only have to write one once and splitting everything will be easy as pie next time.

[Boulder]

For some reason, I didn't think of mencoder (ffmpeg). It would definitely be easier to use after the script is setup once. In 64-bit OS, it's also possible to pipe the Avisynth script output into a 64-bit build of ffmpeg for slightly increased performance, similar to the x264 way.

[kolak]

Originally Posted by WorBry

OK, thanks. I wondered if you were maybe farming out to multiple PC's. Obviously a bit tedious, marking the trim set points and re-splicing, but probably quite efficient from the encoding perspective. On my new PC, MT-AVISynth processing speeds up QTGMC about 3-fold. It would be interesting to see how 4 simultaneous instances of non-MT encoding compares.

Another way is to use mp_pipeline- there is big overhead but it runs stable even on 12 cores systems (assuming you have 12GB+ RAM)

[WorBry]

Me no, just 8GB RAM....for now.

[Octo-puss]

Avisynth+ is apparently getting MT support before end of the year.

[SamKook]

It would seem that MT is still faster, but it might be due to the encoders difficulty to balance themselves the more instances are running at the same time since there's always a couple that are much slower than the rest. Maybe others would be better at it.
And they don't always manage to catch up speed when other close which explain the time for the 6 instances single threaded.

The format is: Instances x number of threads(1=no mt calls)
It's not quite a fair comparison since the more instance there are, the more frames need to be encoded since I add 50 on each side and the sample was only 3997 frames, but it's a real world test for my usage.

Test mencoder_4x2: 0:18:37.37
Test mencoder_8x1: 0:21:53.60
Test mencoder_4x1: 0:24:43.94
Test mencoder_6x1: 0:56:35.42
Test mencoder_3x2: 0:18:38.59

[horrormaster34]

Getting the following error: "Cache: Filter returned invalid response to CACHE_GETCHILD_CACHE_MODE. 136310928
(QTGMC-3.32.avsi, line 776)
(QTGMC-3.32.avsi, line 386)

I'm using AviSynth 2.6 MT with the Modded Plugins Package

[LigH]

Every once in a while, the same question with the same error message, just in different threads: mt_masktools-26.dll had to be updated even once more.

[horrormaster34]

That fixed that, but now I get an error about nnedi3: arg 0 must be a clip!
(QTGMC-3.32.avsi, line 721)
(QTGMC-3.32.avsi, line 510)

Also end up with an error on another filter for something else not QTGMC related.

[WorBry]

I'm considering the implications for processing of YUY2 video sources in AVISynth - specifically files in the Cineform HD format, which (as AVISource) output only to YUY2.

The consideration then is whether it would be better to convert to YV12 from the start of processing, or to (try and) stay in YUY2 color-space throughout, before finally converting to YV12 for rendering to target format.

'Better' in this context would imply avoidance of unnecessary internal color space inter-conversions, yet taking into consideration the relative re-sampling efficiencies of YUY2 and YV12 color-space when it comes to processes such as rescaling.

As regards QTGMC; following the script through, it appears that for YUY2 input the only conversions that take place are between interleaved YUY2 and a planar 4:2:2 variant (is that technically YV16 or another variant?). I was wondering – is this inter-conversion completely lossless or are there potential sampling inefficiencies involved? And if there are, would these be anymore or less significant than converting the source to YV12 prior to processing? Relative processing speed is less of a consideration – assuming both inputs receive the benefit of MT support?

Thanks

[LigH]

Originally Posted by horrormaster34

nnedi3: arg 0 must be a clip!

Then please provide more details, details, details ... I suspect here an issue with the script sequence before calling QTGMC, which probably keeps assigning the video outputs to variables and thus leaves "last" unassigned, and then a call of QTGMC() follows without refering to any explicit clip variable.

[DarkSpace]

Originally Posted by horrormaster34

now I get an error about nnedi3: arg 0 must be a clip!

I had that once. As it turned out, my nnedi3 file had somehow become corrupted or otherwise unusable, and replacing it with this one completely solved the issue.

By the way, my test back then was only BlankClip(pixel_type="YV12").nnedi3(), so I don't think this error is related to QTGMC itself.

[trevorjharris]

QTGMC runs fine with avisynthmt 2.6 dated 15-5-2012. but removegrainsse2 crashes with versions dated 9-3-2013 and 28-9-2013. Is the there a version of removegrainsse2 which works with lastes avisynthmt?

Thanks

[LigH]

Did you already try to set a specific MT mode (4..6 instead of 2) for this plugin only? Or does it already crash while loading the script, and if, with which kind of error message or dialog?

[trevorjharris]

Originally Posted by LigH

Did you already try to set a specific MT mode (4..6 instead of 2) for this plugin only? Or does it already crash while loading the script, and if, with which kind of error message or dialog?

I am using qtgmc version 3.3
The error message is

Avisynth open failure
Avisynth: access violation at 0x00001433 in C:\Program Files (X86)\Avisynth 2.5\plugins\RemoveGrainSSE2.dll, attempting to read from 0x00000000
(qtgmc.avsi line 764)
(qtgmc.avsi line 790)
(qtgmc.avsi line 387)
(E:\3D Bluray\tenerife\qtgmc.avs, line 13)

The script is

SetMemoryMax(4000) # Optional line. Leave it out at first. See below for value M
#SetMemoryMax(400) # Optional line. Leave it out at first. See below for value M
SetMTMode(5, 6) # See below for value X
#SetMTMode(5, 3) # See below for value X
avisource("tenerife2fs.avi", audio=false)
SetMTMode(2)

assumetff()
#separatefields()
#info
#converttoyv12(interlaced=true)
#converttoyuy2()
QTGMC( Preset="slow", fpsdivisor=2, 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

The crash occures on opening. As I said earlier version of avisynthmt 2.6 worked.

[LigH]

Originally Posted by trevorjharris

SetMemoryMax(4000)

You are kidding, right? Even for an LAA process, allowing almost 4 GB for a 32 bit process is ... optimistic.

Originally Posted by trevorjharris

SetMTMode(5, 6)
...
QTGMC( Preset="slow", fpsdivisor=2, EdiThreads=3 )

6 QTGMC threads multiplied with 3 EDI threads are 18 threads, each using RAM for its own copy of the EDI plugin, and if it is NNEDI, it needs quite a lot. Try to be more modest...

[Reel.Deel]

Originally Posted by trevorjharris

I am using qtgmc version 3.3
The error message is

Avisynth open failure
Avisynth: access violation at 0x00001433 in C:\Program Files (X86)\Avisynth 2.5\plugins\RemoveGrainSSE2.dll, attempting to read from 0x00000000....
...The crash occures on opening. As I said earlier version of avisynthmt 2.6 worked.

Let me guess. Are you using the "2.6 plugin package provided in the first post"? If so those plugins are no longer compatible with the latest AviSynth 2.6 Alpha5 MT [2013.09.28].

Here's some on my older posts on that very subject.

Originally Posted by Reel.Deel

All of -Vit-'s 2.6 plugins seems to work with AviSynth 2.6 Alpha3 MT [2012.05.16].
With newer builds I get access violations and similar errors...

Originally Posted by Reel.Deel

Those plugins included in that package are no longer compatible with AviSynth 2.6 alpha4/5. Read here for more details.

I had the same problems some time ago, use the 2.5 plugins and everything will be ok.
Currently, I'm using -Vit-'s modded 2.5 plugins package and the updated MaskTools with Avisynth 2.6 Alpha5 MT [2013.09.28] and everything is running well so far.

--------
The first post seriously needs an update with the correct information.
It baffles me how many people are having this problem. Sometimes the answer is just a few pages back. :/