avisynth filter recommendation

[manono]

Greyscale it afterwards:

Greyscale()#or

Tweak(Sat=0,Coring=False)

Edit: Sorry. Forgot it was in color.

[poisondeathray]

Are you using proper masktools version ?

If you have avisynth 2.5.x you use the "25" versions of the dll

If you have avisynth 2.6.x you use the "26" versions of the dll

[mmbwdpnz]

i have avisynth 2.5.x

[poisondeathray]

i have avisynth 2.5.x

yes... but do you have to correct masktools version? using the wrong masktools version commonly results in green frames . Just a guess at what might be happening

[mmbwdpnz]

no i dont im using the 26 versions of the dll

[poisondeathray]

no i dont im using the 26 versions of the dll

So did changing to the correct version fix the problem ?

[mmbwdpnz]

no im not sure if i did something wrong

[sanlyn]

i have avisynth 2.5.x

yes... but do you have to correct masktools version? using the wrong masktools version commonly results in green frames . Just a guess at what might be happening

The script calls for 2 different versions of masktools. FastLineDarken uses masktools v.1.5.6 or v.1.5.8 (I've used both), the other plugins use any version 2.5.x of masktools. The two dll's have different names and different command parameters, so there's not likely to be a conflict loading both at the same time.

[mmbwdpnz]

where can i get both versions?

[mmbwdpnz]

do i need to use QTGMC or is there something waaaaaayyyyyyyyyyy faster than it? is it even needed?

[poisondeathray]

do i need to use QTGMC or is there something waaaaaayyyyyyyyyyy faster than it? is it even needed?

it wasn't even called in themaster1's script (not used)

[sanlyn]

where can i get both versions?

MaskTools v1.5.8
MaskTools v1 dll, for older plugins that don't require MaskTools v2. Many of these older plugins are still being used.

MaskTools v2.0a48
Contains v2.5 and v2.6 dll's. Use v2.5 for Avisynth 2.5, or use v2.6 for Avisynth 2.6 -- don't use both.

The names of all 3 of the dll's are different.

[Selur]

do i need to use QTGMC or is there something waaaaaayyyyyyyyyyy faster than it?

btw. using Avisynth MT with setMTMode(2) speeds up QTGMC a lot,...

[jagabo]

do i need to use QTGMC or is there something waaaaaayyyyyyyyyyy faster than it?

btw. using Avisynth MT with setMTMode(2) speeds up QTGMC a lot,...

If you have a multicore PC. And if the filters you're using don't crash or otherwise screw up.

[Selur]

And if the filters you're using don't crash or otherwise screw up.

isn't that always true when using avisynth?

If you have a multicore PC.

it might be hard to find a PC that isn't multicore nowadays, but of course you are right.

+ the usage of Avisynth MT can even slow down the whole script so using it blindly can be a mistake

[mmbwdpnz]

i switched to avisynth MT, it is faster on QTGMC. I fixed the script as well its finally complete thanks for all your help

[mmbwdpnz]

the encode in megui is gojng to take a day and 5 hours?!

[Selur]

Depending on your settings, source (length, resolution, format) and cpu (and general hardware) that can be fast/slow/normal.
Accurate audio/video editing takes it time.
-> so no surprise there. x264 and QTGMC both got presets to easily influence the speed of the encoding and there are probably other aspects that might not be ideal (but might also influence the speed only marginally).

The main bottle necks are:
0. CPU power (often a problem)
1. decoder speed (rarely a real problem unless real time or faster encoding is needed)
2. filter selection and configuration (often a problem)
3. encoder selection and configuration (often a problem)
4. general Data transfer speed in your encoding environment (rarely a problem unless real time or faster encoding is needed)
...

Cu Selur

[jagabo]

Try a faster preset in QTGMC(). Like QTGMC(preset="very fast").

[mmbwdpnz]

that reduced the time in half, thanks

[jagabo]

There's also "super fast", "ultra fast", and "draft". Successively faster and less effective.