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

[bayex]

Seriously?!? This thread and all the filters within relate to 64 bit CPUs AND OSes ...

You can't run 64bit apps on a 32bit OS even if your CPU is 64bit ...

7ek
Avis dll files which I use 32-bit operating system setmtmode () to be active in the

[Livesms]

Update: I copied avisynth.dll and devil.dll to system32 on a Windows 2008 R2 setup, after which I imported avisynth.reg. I created a test script with the code "BlankClip().ConvertToYV12()". It does not load in either VirtualDub64 or x264. Both crash upon exit. VirtualDub64 gives an error message "AVI Import Filter error: (Unknown) 80040154".

The same problem.
Installed Avisynth_258, then unrar avisynth64_8-29-10.rar and installed avisynth64_install.cmd.
VDub says "AVI Import Filter error".
Opening any avs script before installing avisynth64_install.cmd - gives no error. x86 works fine.

CPU: Core i5-660, Windows 7 Ultimate x64.

[Livesms]

===

BTW - %PROCESSOR_ARCHITECTURE% with Windows 7 Ultimate + Core i5-660 returns " x86"

Need to comment "IF %PROCESSOR_ARCHITECTURE% == x86 (GOTO 32BIT)" in avisynth64_install.cmd

[nividia]

hi guys ...
is there a x64 build of Toon-v1.0-lite.dll yet ?

[travolter]

hi guys ...
is there a x64 build of Toon-v1.0-lite.dll yet ?

LOL I just entered into this post to ask same question ;)

Toon, toonlite or any line darkener is available in x64?

[GRKNGLR]

Hi,
When will new stable version be ready?

[Delerue]

===

BTW - %PROCESSOR_ARCHITECTURE% with Windows 7 Ultimate + Core i5-660 returns " x86"

Need to comment "IF %PROCESSOR_ARCHITECTURE% == x86 (GOTO 32BIT)" in avisynth64_install.cmd

Maybe checking if %WINDIR%\syswow64 exists (which exists only in x64 systems) is another solution. What you think?

[AlekseiV]

PROCESSOR_ARCHITECTURE will be "x86" if on x86 Windows or if an x86 program is asking, neither of which should happen on x64 with a batch file AFAIK.

If crazy you can use this to get accurate response without caring about process bitness:
reg query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" /f "AMD64" /e /d
it will set errorlevel to 1 if it finds no matches

[kypec]

PROCESSOR_ARCHITECTURE will be "x86" if on x86 Windows or if an x86 program is asking, neither of which should happen on x64 with a batch file AFAIK.

It happened to me as well, just because I was launching installation .bat file directly from my file manager (Altap Salamander) which is still available as 32-bit application only.

[kemuri-_9]

if you don't want to check the registry, you can also check
%PROCESSOR_ARCHITEW6432% to be amd64 if %PROCESSOR_ARCHITECTURE% is x86
this is the scheme of how windows handles keeping x64 environment variables around in x86 mode.

though, the bat still had numerous issues last i looked at it, since it required avisynth32's plugin directory to be in the registry, which is not guaranteed at all
(e.g. manual removing of the registry key or not having avs32 installed at all).
I'm not even sure the not working on XP x64 issue was fixed either.

[GRKNGLR]

I have AviSynth64 installed on my system but when I try to load a script on Veedub64, I receive an error which says I don't have "libfftw3l-3.dll".
Though I have downloaded the required files from ftp://ftp.fftw.org/pub/fftw/fftw-3.2.2-dll64.zip address and have placed them in my system32 folder, it's still the same. The script opens ok on Veedub64, but I can't take screenshots. BTW AvsP and AvsPmod never work. Is it because I have Avisynth64 installed? When I try to use FFT3DFilter, I receive an error saying that I don't have "FFTW3.dll". Though I have placed that folder in system32 adn SySWOW64, it is the same. What can I do?

[soulkeeper]

i use avisynth64 with mvtools2 x64(from the 1st post) in ffdshow in order to do frame interpolation...
there are 2 new versions of mvtools2 x86 since then (2.5.10.1 and 2.5.11) which contains important fixes for my use..
is it possible to have updated mvtools2 x64?

PS if i understand correctly each x64 plugin is "based" on it's x86 version and it's just ported to x64..

Thanks!

[Turtleggjp]

I'm having trouble getting this to work in Windows XP x64. Scanning quickly through this thread, it seems that it should work. The error I'm getting when trying to open a simple script in 64-bit VirtualDub is: "AVI Import Filter error: (Unknown) (80040154)"

My script is pretty simple:

Version()

And it works if I use a 32-bit version of VirtualDub, so at least 32-bit AVISynth is installed. I get this same error in 32-bit VirtualDub if I uninstall AVISynth, so it seems that it is an indication that 64-bit VirtualDub can't locate the 64-bit AVISynth DLL, or the correct registry entries are not there. I've gone over the install procedure many times, and everything seems to be where it needs to be. I've tried doing a fresh install of XP x64, installing SP2, and running Windows Update (based on things I read earlier in this thread). If I had a copy of Windows 7 handy, I'd try that too, but I really don't want to run Windows 7 if I don't have to.

Here's some other info:
Core2 Duo 3.16 GHz
4GB memory
32-bit AVISynth version: 2.5.8 (no MT version, but I did try that too with no luck)
32-bit VirtualDub: 1.9.6 (works)
64-bit VirtualDub: 1.9.10

I'd appreciate your help. I'd really like to start using 64-bit x264 for my encodes. I have 64-bit DGNV Tools and 64-bit x264. 64-bit AVISynth is the last piece of my puzzle. Thanks!

Matt

[kemuri-_9]

Make sure that the avisynth and devil dlls are in the System32 folder and make sure you have run the registry file that came with the installer.

that should be a bare minimum for getting it to work at all.
then there's some extra stuff if you want to have an autoload directory for avisynth x86_64 like there is for the x86 one.

btw, this is what i did with Squid_80's x86_64 avisynth build long before JoshyD made this thread. I'm also on XP x86_64

[Turtleggjp]

The files are there, and I had added the registry entries. I even went as far as to make copies of all the included DLL files and put them in the VirtualDub x64 folder. I noticed that once 32-bit AVISynth was installed, if I moved the avisynth.dll file out of the SysWOW64 folder, 32-bit VirtualDub would give the same error message. Putting the DLL file into the same folder as the 32-bit VirtualDub binary would allow it to work again. Having the DLL in there without having it installed did NOT work. That's what led me to think that in order to get the 64-bit version to work, there might be some additional registry entries that need to get added in. At least it is encouraging to know that it should work in XP x64.

Matt

[henryho_hk]

You may need to correct the plugin path in registry manually coz it may be generated as "plugins 64" (yes, there is an extra space in between).

[kemuri-_9]

the plugin path is only required to have the autoload plugin feature, it is not required to have avisynth work:
I've removed the plugindir2_5 registry entry because I find plugin autoloading annoying and avisynth still works here.

however, x264 does not rely on avisynth being registered in the registry to utilize it like apps that use it through VFW do (virtualdub).

so you should be able to use avisynth with x264 x86_64 as long as it and the devil dll are in your System32 folder (technically as long as they're in the PATH, but System32 would be the best spot).

though the fact that it doesn't work with virtualdub does make it harder to preview the script...

You will probably need to check and make sure the registry values went in correctly.

so manually open the 64bit regedit (NOT the 32bit version) (doing it from a standard x64 cmd prompt or the run command will be the correct one)
and verify that all the values in the registry file are actually in the registry.

all 3 values are important, the first is to register avs as an AVIFile (so anything that uses VFW api on it will try and use avisynth)
and the latter two are to register avisynth as a valid application/service per se - so the first value works.

if they are in correctly, then i'm not sure what the problem would be... all i could say at that point is "try the windows cure-all - restarting if you haven't already"

[Turtleggjp]

When I've been running regedit, I have been doing so from the Run command in the start menu. It sounds like I was opening the right version. I had been checking to see if the registry entries were there, as well as trying to figure out exactly what they all meant.

I will try running 64-bit x264 on that version() script and see if that works.

@kermuri, have you installed SP2 and all the updates from Windows Update too?

[Turtleggjp]

No go on x264:

D:\Documents and Settings\Administrator>E:\Apps\x264.1745.x64.exe -o E:\apps\version.mp4 e:\apps\Version.avs
avs [error]: failed to load avisynth
x264 [error]: could not open input file `e:\apps\Version.avs'

I even tried putting all the DLLs right next to the x264 binary:

DirectShowSource.dll
MT.dll
avisynth.dll
DevIL.dll

with no change. These are the DLLs from the 8-29-10 release in this thread. @kermuri, what version are you using?

[kemuri-_9]

i have the 8-29-10 release.
i have SP2, tho i haven't done windows updates for about a month.

Strange, it should work with the scenario you're providing...

hmm... i have visual studio installed, do you have the visual studio 2008 runtime installed? this may be required...

overall, it does look like you can absolutely not use the avisynth.dll as it can't be loaded for some particular reason,
you can try a small test program (http://kemuri9.net/dev/avs/test_avs_load.7z) that will actually output the error code from the loadlibrary call on it to see what the problem is (you'll likely need to google the error code).
I suspect that it may indeed be the visual studio 2008 runtime if you don't have it installed.

[Turtleggjp]

Update:

I found a copy of Windows 7, and I installed 64-bit Ultimate version. No serial number, no activation, just installed it. The result: it worked! :angry: (yes, I'm angry. I don't want to have to run Windows 7 just for this)

I didn't copy any DLL files into the system32 folder or anything, I just used the copies that I had put in the folder with the x264 x64 binary. I came right back to XP x64, didn't change anything, just ran the same command from the command line, and it still doesn't work here.

I do not have Visual Studio 2008 anything installed. Is the runtime library you mentioned free to download? I have a feeling that may be the key to this...

EDIT: I think I found it here (http://www.microsoft.com/downloads/en/details.aspx?familyid=BD2A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en). I installed that, rebooted, and it still doesn't work. I'll see what I can find out with that last link you posted.

EDIT2:
Running the 64-bit version of that little program gives this:

E:\Apps>E:\Apps\testavsload64.exe
unable to load avisynth, error code = 14001

Running the 32-bit version gives this:

E:\Apps>"D:\Documents and Settings\Administrator\My Documents\Downloads\testavsload32.exe"
can load avisynth without issues

[henryho_hk]

Try installing those Visual Studio/C Redistributable 2005 2008 2010... SP1 SP2 SP3..... x86 x64.... etc.

[kemuri-_9]

hmm.
error 14001 that's a vague error that usually ends up referring to visual studio runtime/manifest issues.

hmm... ok, i did what i should've in the first place: run dumpbin/dependency walker on avisynth.dll and devil.dll and see what they're importing from other dlls.

results:
avisynth.dll itself does not require anything outside of normal windows libraries and devil.dll

devil.dll requires Microsoft visual studio 2005 runtime (the x64 version) to be installed in addition to normal windows libraries.

so install this (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=eb4ebe2d-33c0-4a47-9dd4-b9a6d7bd44da)

[Turtleggjp]

Ok, got it. I'll install that tonight when I get home. Hopefully that will do it then. Thanks so much for your help!

[Tuik]

Hey people, can you give me some help?

Hey, i don't know what happen but now i'm getting this error when opening the avs script (a simple DirectShowSource("video.mkv")) on megui 64:

---------------------------
AviSynth error
---------------------------
AviSynth script error:

DirectShowSource: RenderFile, the filter graph manager won't talk to me
(C:\Users\Admin\Documents\Encodes\script.avs, line 8)
---------------------------
OK
---------------------------

I'm using DirectShowSource with Haali Media Splitter and CoreAVC Pro installed.

Also i'm using avisynth64_4-16-10 version and in MPC x64 the movie opens well (not the .avs but the HD source since the .avs opened in MPC gives the same error). Maybe it's something wrong with avisynth no?

[Turtleggjp]

devil.dll requires Microsoft visual studio 2005 runtime (the x64 version) to be installed in addition to normal windows libraries.

so install this (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=eb4ebe2d-33c0-4a47-9dd4-b9a6d7bd44da)

SUCCESS!! That did it. I tried encoding my version.avs script using 64-bit x264, and it worked, just like in Windows 7 x64. I'm now going to do a clean install to see if SP2 and all the updates are necessary or not.

Perhaps this requirement should be added to the first page for those few others trying to run this on XP x64. Also, is it possible in the future that this requirement will be dropped? I can't exactly wave the bloatware flag over a little 3MB download, but it would be nice if this was no longer required, since it never has been for 32-bit AVISynth.

Thanks again Kemuri!

Matt

EDIT: After doing my clean resinstall, the first thing I did was install that runtime library (before drivers, updates, even 32-bit AVISynth). Once I did that, 64-bit x264 could use the 64-bit avisynth.dll, so it definitely seems that it is required for use in XP x64. Windows 7 didn't need it, and I did not test Vista.

[travolter]

There is any bug with assumefps()?

Im trying to change fps and create slowmotion videos with assumefps(10) (I use this line in x86 and works), but its not working in avisynth x64 (the video is not slowed down.. its like it loses frames).

If its confirmed bug.. there is any workarround for continue working on x64 and do slowmotion?

[henryho_hk]

I've modified the install and uninstall cmd batches to fix the plugins64 directory name generation and tidy up the codes. Please enjoy.

[Hagbard23]

@JoshyD: Is still something going on in here, or is it like you have no time to maintain the project any further? That would be a damn pity, because i really liked this project.

Please give a sign from yourself... ;)

[zmaster]

Hi!

I just want to say that many users (myself included) eagerly awaiting the development branch x64 plugins. Current status makes the possibility of using AviSynth x64 somewhat limited.

[AlekseiV]

@JoshyD: Is still something going on in here, or is it like you have no time to maintain the project any further? That would be a damn pity, because i really liked this project.

Please give a sign from yourself... ;)Last update was only 3 months ago. Not even close to dead.

[Didée]

Alas, the last update is buggy. (Aug 24 build)

I have been wondering why so many scripts are crashing upon script loading. Tested plenty of plugins, but couldn't find the culprit.

Today I found something:

In the 08-24 build, TemporalSoften() is broken.

More precisely: the scenechange detection is broken.

Works: clip.TemporalSoften(3,4,5) # RGB / YUY2 / YV12 colorspaces

Crashes: clip.TemporalSoften(3,4,5,6,2) # YUY2 / YV12 colorspace. (RGB never did support scenechange detection anyway.)


That's what I call a showstopper.

[Prettz]

I'm just about done with the YV12 version of a new 64-bit FluxSmooth, completely rewritten for SSE2 and SSSE3. I had to obtain the Intel compiler, due to needing inline assembly, before I could even make sure it compiles, so I still need a bit more time before it's ready for testing and feedback. I'm going to post a new thread for it when I'm ready.

[tormento]

Even a MedianBlur_x64 would be very nice. Anyone skilled enough?

Please ;)

[AppleA]

Its.dll is useful plugin for vfr(Variable Frame Rate) source.
And we can easily get chapter file.
Could someone please compile a 64-bit Its.dll?
There appears to be a source code in the 7z file.
http://www.avisynth.info/?plugin=attach&refer=%A5%A2%A1%BC%A5%AB%A5%A4%A5%D6&openfile=Its086.7z

[jpsdr]

Latest version, PointResize don't work/crash on 1080p YV12 video.

[blausand]

Hey there,
i appreciate that, after clicking through the devasted areas of

AviSynth.org,
there: /mediawiki, /avisynth3, German pages etc.
SourceForge.net
QUITE some forum.doom9.org threads,
and, finally, some absolutely uncommented indexOf in
members.optusnet.com.au/squid_80
for AviSynth x64,


i finally find some sign of life here, in this very thread. Brave developers! Really.
Thank you for sissiphossing all those lines of x86 code to x86-64, thanks for struggling through the pains and wonders of Windows Media Foundation Whatsoever.

As everybody knows, some major media production software vendors have finally managed to release 64bit versions of their video editing software - where we so much loved to directly open our RGB32-formatted AVS-output into.
And i think right now it is time to plan some changes to the FRONTpages of Avisynth. It is just evident that a software without noticeable signes of life on it's homepage is -yes- DOOMED to die.
Let's talk about updating those wiki-pages.
NOW.HERE. (http://forum.doom9.org/showthread.php?t=158527)

[Wilbert]

And i think right now it is time to plan some changes to the FRONTpages of Avisynth. It is just evident that a software without noticeable signes of life on it's homepage is -yes- DOOMED to die.
Let's talk about updating those wiki-pages.
NOW.
Go ahead, talk :) I know nothing about x86-64, nor have the time to do much at the moment. Perhaps it's best to open a separate thread about it.

[blausand]

Did so here (http://forum.doom9.org/showthread.php?t=158527).
Sorry for repeating part of the previous post there.
Even more sorry for inconvenience in this very thread.

[osgZach]

Its.dll is useful plugin for vfr(Variable Frame Rate) source.
And we can easily get chapter file.
Could someone please compile a 64-bit Its.dll?
There appears to be a source code in the 7z file.
http://www.avisynth.info/?plugin=attach&refer=%A5%A2%A1%BC%A5%AB%A5%A4%A5%D6&openfile=Its086.7z


That links is busted for some reason.. Here

http://www.avisynth.info/?%A5%A2%A1%BC%A5%AB%A5%A4%A5%D6

Maybe this one will work.. otherwise just google ( Avisynth, "its.dll" ) to bring up a result for the Japanese page, it was easy enough to find.

Anyway... is there english documentation for this? WHAT does it do? I'm always interested in VFR stuff, and I think I heard of this DLL before when I got into using YATTA, but I couldn't find it back then..

[Stephen R. Savage]

That links is busted for some reason.. Here

http://www.avisynth.info/?%A5%A2%A1%BC%A5%AB%A5%A4%A5%D6

Maybe this one will work.. otherwise just google ( Avisynth, "its.dll" ) to bring up a result for the Japanese page, it was easy enough to find.

Anyway... is there english documentation for this? WHAT does it do? I'm always interested in VFR stuff, and I think I heard of this DLL before when I got into using YATTA, but I couldn't find it back then..

IT is a combination field matching and decimation filter. It's briefly mentioned in the Yatta manual as one of the three metric sources. From the source, it appears to have automatic VFR detection and timecodes output. As for whether it's any good... I don't know, I've never used it.

[osgZach]

IT is a combination field matching and decimation filter. It's briefly mentioned in the Yatta manual as one of the three metric sources. From the source, it appears to have automatic VFR detection and timecodes output. As for whether it's any good... I don't know, I've never used it.

Automatic VFR detection? Would be interesting to play with :p

Wish someone around here had made a filter like that to see how well it works.

Although I suppose our current tools do the job pretty well. Still would be a neat idea.

[AppleA]

Its.dll is different from It.dll or itvfr.dll.
Its.dll is support filter to make vfr file.
Its.dll can't do automatic VFR detection.

Its.dll Usage

Its( def, tpr, fps, debug, posx, posy, chapter , output )

def [strig]
set definition file pass
tpr [string]
set TMPGEnc(ver 2.5xx) projectfile pass
this is capable to be abbreviated.
fps [int default=-1]
set output fps
=-1:120pfs(mixed fps)Delete frame stripped mode
=0:120fps(mixed fps)
=24:24fps
=30:30fps
it should use exavi_vfr.auo to set 120fps
debug [bool default=false]
=true:show debug infomation
=false:don't show degub infomation
posx,posy [int default=0]
set pixel value for debug infomation position
chapter [string]
set generated chapter file pass
chapter file is output quickly after initialize
output [string]
set generated timecode pass
timecode is output quickly after initialize
if chapter file pass is seted, only extension is ok

example
------ foo.avs -------------------------
OpenDMLSource("baz.avi")
AssumeFrameBased().ComplementParity()
its(debug=false, def="foo.def", fps=-1, posx=300, chapter="bar.xml", output=".tmc" )
return last
-----------------------------------------

construction for definition file

definition file is SHIFT-JIS or UTF-8.
set a instruction evry a line.
comment line take off #.
substitution line homologize function name InverseTelecine plugin or deinterlace plugin.
example
set [24] tfm = 'TFM(order=1,mode=1,PP=1,slow=2).tdecimate()'
set [24] it = 'IT(ref="TOP")'
set [30] it = 'IT(fps=30,ref="TOP")'
set [30] td = 'TDeint(order=1,field=1,slow=2,mode=0)'
set [24] tmpgenc = tpr<"c:\foo.tpr">

string is bracketed off ' '," ",` ', { }.
[24],[30],[60],[48],[20],[10],[12],[15] set fps.
[24] it is differentiated [30] it.

default behavior set on range set line(later discussion).
default 24 = it
default 30 = td

range set line
set handling like that.

0-99999 [24]:command / function name

range is set startframe-endframe.
if startframe only, range is startframe only.
[24] set fps.
command make a choice frame after doubleweaved frame.
It should set field order before Its.
frame number is 0(0a), 1(0b), 2(1a), 3(1b), 4(2a), 5(2b), ...
there are some command.
on_a(on), on_b, off_a(off), off_b, dup_a(dup), dup_b, null_a(null), null_b , tpr<"foo.tpr">, <10010>, (5,0,3)、chapter=

here, on is output, off is delete, dup is frame copy, null is drop.
tpr<> is TMPGEnc project, <10010> is frame choice pattern.
(5,0,3) is choice 0th frame nad 3rd frame every 5 frames.
max cycle is up to 30.
chapter=string set chapter at first frame for range.

mode set line
default fps set like
mode fps_priority=24
mode fps_priority=30
set chapter character.[default: "SHIFT_JIS"]
mode chapter_charset = SHIFT_JIS
mode chapter_charset = UTF-8

keyframe set line
example

keyframes {
100 "OP"
200
300 A Part
400
500
600
700 'B Part'
800
900
1000 Trailer
}

character after num set chapter.


about debug infomation
frame=80(100 80<+0>) 24fps (for fps=24)
frame=100(100 100<+0>) 30fps (for fps=0/30)

definition file example

set [24] it = 'IT(ref="TOP")'
set [24] xx = 'DoubleWeave().a60224()'
set [24] /01 = <01010> #01frame is strip for 2:3pulldown source.
set [24] /12 = <10010> #12frame is strip for 2:3pulldown source.
set [24] /23 = <10100> #23frame is strip for 2:3pulldown source.
set [24] /34 = <00101> #34frame is strip for 2:3pulldown source.
set [24] /40 = <01001> #40frame is strip for 2:3pulldown source.
set [24] decimate = 'tdecimate()'
set [24] tfm = 'TFM(order=1,mode=1,PP=1,slow=2).tdecimate()'
set [24] tfm2 = 'TFM(order=1,mode=1,PP=6,slow=2).tdecimate()'
set [30] td = 'TDeint(order=1,field=1,slow=2,mode=0)'
set [30] tddefo = 'tdeint(order=1,field=1,tryWeave=true,slow=2)'
set [30] td2 = 'tdeint(order=1,field=1,tryWeave=true,slow=2,emask=last.TMM(order=1,field=1))'
set [30] fs ='doubleweave().selectodd()'
set [30] pp = <10>
set [60] eedi = 'separatefields().MT("""EEDI2(field=3)""",threads=8,splitvertical=true)'
mode fps_priority = 24
default 24 = tfm2
default 30 = td
default 60 = eedi
keyframes{
4434"OP"
7427"A-Part"
23307"B-Part"
40130"ED"
42842"Trailer"
}
0- 7426 00:04:07[24] /01
7126[24]dup_a
7426[24]dup_a
7427- 7665 00:00:07[24] /01
7666- 8264 00:00:19[60] eedi
8265-23306 00:08:21[24] /23
23307-42841 00:10:51[24] /01
42842-44039 00:00:39[24] /01

[miker3x]

windows 7 does not open .rar what program due we use to open avisynth.

[Chikuzen]

windows 7 does not open .rar what program due we use to open avisynth.

just use 7zip (http://www.7-zip.org/), winrar (http://www.rarlab.com/), or something you like.

[GRKNGLR]

I wouldn't like to ask about it but has AVS64 really died? The last release (test release) came at the end of August. No new releases or plugin updates since then. Can anyone make a clear explanation about it?

[nividia]

Any plan to do a x64 build of Toon,Toonlite ..etc or any line darkener is available in x64 ?

[Stephen R. Savage]

I wouldn't like to ask about it but has AVS64 really died? The last release (test release) came at the end of August. No new releases or plugin updates since then. Can anyone make a clear explanation about it?

There was only ever one developer, and he has disappeared. As far as I know, the original (2010-04) build still works, minus a few bugs. Overall, I'd say that the main reason AVS64 died was simply a lack of interest. Plugin developers had no interest in 64-bit, and nobody really bothered to contribute to the project.

Known bugs in 2010-04 AVS64:

The src_* parameters to Point/Bilinear/Bicubic resize cause an exception
XMM registers are clobbered ("PTS < 0" message in x264)


Known bugs in 2010-08 AVS64:

The src_* parameters to Point/Bilinear/Bicubic resize cause an exception
TemporalSoften crashes when the scene change detection is used


Plugin writers maintaining 64-bit versions:

tritical: eedi3 and nnedi3
manao: mt_masktools
kemuri-_9: ffmpegsource


In the interest of maintaining whatever information is available about this (hopefully not) dead fork, please contribute anything you might know that I have not summarized above.

[GRKNGLR]

Thank you very much for your answer, Stephen R. Savage. Too bad, coz we liked AVS64 a lot... A few questions then... When will AVS officially support x64? I mean, will the 2.6 or any later version officially support x64? The April release is stable but the August release has resizing bugs. The developer of AVS64 is missing and I'm really wondering where he is now. One last thing; where can I find the x64 versions of nnedi3 and eedi3?
Kind Regards

[Stephen R. Savage]

Thank you very much for your answer, Stephen R. Savage. Too bad, coz we liked AVS64 a lot... A few questions then... When will AVS officially support x64? I mean, will the 2.6 or any later version officially support x64? The April release is stable but the August release has resizing bugs. The developer of AVS64 is missing and I'm really wondering where he is now. One last thing; where can I find the x64 versions of nnedi3 and eedi3?
Kind Regards

64-bit support is not planned for Avisynth 2.6, nor any future version. There is simply no interest in it.

eedi3: http://bengal.missouri.edu/~kes25c/eedi3_64.dll
nnedi3: http://bengal.missouri.edu/~kes25c/nnedi3_64.dll

They require the MSVC runtimes (not sure which ones) to run.