SEt's Avisynth 2.5.8 MT compiled for *X86_64*, Latest Build 4/16/2010

[Zerofool]

Hi, now that nnedi3 and eedi3 do have 64-bit experimental builds, I only need a 64-bit version of the plug-in "Average". I see it's been requested by Stephen R. Savage, but there's no progress as far as I can see. If someone can port the plug-in, that would be very nice.

I would also like to request a feature from Avisynth 2.6. The ConvertTo function has this "chromaresample" argument, which is very helpful for my needs (mostly RGB videogame footage), If it could be ported to this 64-bit build of Avisynth, that would be great, thanks in advance.
And godspeed to the project .

[LeXXuz]

Is there any known problem with the resizer in Avisynth x64?

I got lots of crashes in MeGui and after some more testing and checking with Vdub, it seems Avisynth x64 crashes on certain source resolutions for the resizer.

f.e.
1920x1080 autocropped in MeGui to 1916x1080 => any resizer => 1280x720 = crash

1920x1080 autocropped in MeGui to 1918x822 => any resizer => 1280x544 = crash

Same machine, same source files, same resolutions on Avisynth x86 work without any problems.

[zmaster]

Which version of AviSynth_MT do you use? Resizing works great in the version of 4/16/2010.

[Lyle_JP]

Originally Posted by zmaster

Which version of AviSynth_MT do you use? Resizing works great in the version of 4/16/2010.

Not really. Try resizing to a mod2 (not mod4) height.

[zmaster]

Lyle_JP,
Hmm... You can specify any particular case? I think resizing always works correctly.

Originally Posted by LeXXuz

1920x1080 autocropped in MeGui to 1916x1080 => 1280x720
1920x1080 autocropped in MeGui to 1918x822 => 1280x544

These situations I have reproduced. The desired result is achieved, no problem.

[asarian]

I still can't get this to work properly. :( I did everything in the readme.txt, to the letter, ran the avisynth64_install.cmd, but I can't even get this simple script to work (gits2.avs):

LoadCPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins64\ffms2.dll")
FFVideoSource("f:\jobs\gits2.mkv").ConvertToYV12()
MCTemporalDenoise(settings="low", useEEDI2=true)

And I call it as follows:

c:\x264\x264.exe --crf 14 --sar 1:1 --aud --nal-hrd none --level 4.1 --preset placebo --vbv-bufsize 70000 --vbv-maxrate 60000 --bframes 8 --aq-mode 2 --tune film --output "c:\video\gits2.264" "f:\jobs\gits2.avs"

(x264.exe is the 64-bit executable)

Nothing happens, for a long time. Then I get this error:

avs [error]: Script error: there is no function named "gradfun2db"
(MCTemporalDenoise.v1.4.20.avsi, line 700)
(f:\jobs\gits2.avs, line 6)

I am not even using "gradfun2db", nor have I set ENHANCE to true.

Please, tell me what I'm missing.

[kypec]

Originally Posted by asarian

I am not even using "gradfun2db", nor have I set ENHANCE to true.

Please, tell me what I'm missing.

MCTD "low" settings have enhance option enabled by default, try to set it false explicitly in your filter call.

[asarian]

Originally Posted by kypec

MCTD "low" settings have enhance option enabled by default, try to set it false explicitly in your filter call.

Good catch! Sadly, it keeps throwing the same error, even when I set it to 'medium'.

[AlekseiV]

The script seems to suggest setting GFthr to 1.0 to disable Gradfun2db:

enhance : Enable GradFun2DBmod post processing to enhance flat areas
GFthr   : Gradfun2db threshold [1.0=off,...]

[LeXXuz]

Originally Posted by zmaster

Lyle_JP,
Hmm... You can specify any particular case? I think resizing always works correctly.


These situations I have reproduced. The desired result is achieved, no problem.

Yep. Works with x86 version also without any problems.

I'm not sure which x64 version is installed. Have to see if it's from 4/16.

[asarian]

Originally Posted by AlekseiV

The script seems to suggest setting GFthr to 1.0 to disable Gradfun2db:

enhance : Enable GradFun2DBmod post processing to enhance flat areas
GFthr   : Gradfun2db threshold [1.0=off,...]

So, this is interesting. Seems basically GradFun2DB is always on by default then. Didn't know that (I usually have a second line following with a separate GradFun2DB command). I just thought GradFun2DB was a function of ENHANCE.

Now, who do I suck up to to have GradFun2DB ported to 64-bit? :) Seriously, if someone were to do so, then MCTemporalDenoise could finally run with all the trimmies in 64-bit (where it solidly belongs).

[LaTo]

Originally Posted by asarian

So, this is interesting. Seems basically GradFun2DB is always on by default then. Didn't know that (I usually have a second line following with a separate GradFun2DB command). I just thought GradFun2DB was a function of ENHANCE.

Now, who do I suck up to to have GradFun2DB ported to 64-bit? Seriously, if someone were to do so, then MCTemporalDenoise could finally run with all the trimmies in 64-bit (where it solidly belongs).

Set fixband=false in MCTD.

[asarian]

Originally Posted by LaTo

Set fixband=false in MCTD.

Thanks for letting me know the official way.

But, erm, any chance you'll compile GradFunDB for 64-bit one day?

[AlekseiV]

Avisynth 8-29-10 with DGDecode_mpeg2source post-processing and SetMTMode(2) has bad artifacting for me.
If cpu=1 or 2, small white dots occasionally appear. Hard to spot in a still frame.
If >2, lots of green or white things often appear. See here or here (cpu=4 and cpu=6)
Shows up even in a script consisting only of:

SetMTMode(2,4)
return DGDecode_mpeg2source("Dresden.d2v", info=3, idct=5, cpu=6) #tested: idct=3|5, cpu=1-6

They're non-deterministic, reloading the script and requesting the same frame causes different artifacts (or none)
It works fine with SetMTMode(3) or just disabling post-processing.
Has anybody else seen this?

[asarian]

Just want to thank everyone involved (to no small degree, Kemuri) for porting all this stuff to 64-bit. :) I can now run a full MCTemporalDenoise job, complete with GradFun2DB and SupTitle plugin, all in 64-bit. No more mucking around with avs2yuv.exe, and hope it still all fits into memory.

[kypec]

Finally succeeded to install that x64 build on my Win 7. The culprit was to execute all scripts and registry editing from inside "cmd.exe", otherwise the enviroment was configured like 32-bit and though the import of registry keys appeared good, they were never really written into proper place!

Quick benchmark of simple AVS scripts utilizing MCTemporalDenoise(settings="medium") on 1920x800 source [no MT at all I remind you] returned following results:

• 32-bit avs2avi.exe = 0.97 FPS
• 64-bit avs2avi64.exe = 1.13 FPS

for E8400 @ 3.0GHz that I've in my office.
~17% speedup is not that much but I believe MT will boost the performance even more once I run it at home i7-920 @ 2.66GHz.

[cweb]

I just installed this 64 bit build, and I'm looking right now for a 64-bit version of hdragc... hoping someone ports it someday

Edit: What's needed to port these plugins actually? Is there any documentation available or examples?

[AlekseiV]

You need the source code, for one. Since HDRAGC is closed-source, the author would need to rewrite any x86-only code and recompile for x64.

[cweb]

Originally Posted by AlekseiV

You need the source code, for one. Since HDRAGC is closed-source, the author would need to rewrite any x86-only code and recompile for x64.

I've got the source I think of an older GPLed version dated 2005, at least that's what it says...
I just installed visual studio 2008 with the x64 tools.

[cweb]

Originally Posted by cweb

I've got the source I think of an older GPLed version dated 2005, at least that's what it says...
I just installed visual studio 2008 with the x64 tools.

I built hdragc for x64 and got it to load but it kept adding green frames every now and then.. so I gave up on it.. for now at least.

This is avsrecursion.dll which I built for 64 bits too.. I didn't test it but here it is just in case. No guarantees that it works..

http://www.filesonic.com/file/25354761/AvsRecursion.rar