Will there ever be a Avisynth 64bit official build?

[djesteban]

Like the title says, will there ever be a Avisynth 64bit official build? Is this planned?
Also, if there's an unofficial build, where can I get it and if there's one, can it run alongside Avisynth 32bit?

Thanks

[IanB]

In the medium term, No. There is much MSVC ASM code with no C++ equivalent.

Squid80 did a partial port based on 2.5.6 and has ported some filters. They are available on his web site :search:

The independence relies on MS Windows64 WOW64 structures, so Yes, but the auto plugin directories can clash (or used to).

[thegame]

I was wondering this exact same thing,I am about to make the switch to Win7 Pro 64 bit and I need avisynth to work.

[Asmodian]

The 32bit Avisynth works very well in Windows 7 x64. All filters need to be 64bit to work with 64bit Avisynth (as well as whatever you use to encode the video). As many useful filters have not been ported to 64bit I like using the 32bit more at this time.

You can pipe the video from 32bit Avisynth to 64bit x264 pretty easily if you wanted to use 64bit x264.

[aegisofrime]

The 32bit Avisynth works very well in Windows 7 x64. All filters need to be 64bit to work with 64bit Avisynth (as well as whatever you use to encode the video). As many useful filters have not been ported to 64bit I like using the 32bit more at this time.

You can pipe the video from 32bit Avisynth to 64bit x264 pretty easily if you wanted to use 64bit x264.

Except that from my own experience, there's not much performance benefit of using 64-bit x264. Perhaps my Avisynth script is too complex.

[Snake91]

About 10% (imho it's a lot). And 64bit allow you to use much higher rc-lookahead values

[LoRd_MuldeR]

About 10% (imho it's a lot). And 64bit allow you to use much higher rc-lookahead values

You can use 64-Bit x264 with 32-Bit Avisynth just fine. All you need to do is piping the video from avs2yuv.exe (32-Bit) into x264.exe (64-Bit).

[saint-francis]

You can use 64-Bit x264 with 32-Bit Avisynth just fine. All you need to do is piping the video from avs2yuv.exe (32-Bit) into x264.exe (64-Bit).

I'm my tests it doesn't work well with complicated scripts. X264 x86 will actually encode faster for me with a complicated script since (I'm assuming) MT is more effective. I get an average of 70% CPU usage with a complicated script and the method described above where keeping it all 32 bit will usually yield an almost constant %100 usage.

[kemuri-_9]

I'm my tests it doesn't work well with complicated scripts. X264 x86 will actually encode faster for me with a complicated script since (I'm assuming) MT is more effective. I get an average of 70% CPU usage with a complicated script and the method described above where keeping it all 32 bit will usually yield an almost constant %100 usage.

depending on what you pipe with, it may not be applying the necessary methods to properly respect the script being possibly multi-threaded.
this would be a possible cause for such under-utilization.

[saint-francis]

depending on what you pipe with, it may not be applying the necessary methods to properly respect the script being possibly multi-threaded.
this would be a possible cause for such under-utilization.

Well, I have only used LM's too and the new x64 implementation in MeGUI.

[kemuri-_9]

Well, I have only used LM's too and the new x64 implementation in MeGUI.

seeing at how i don't use either of those, i wouldn't know if they have the aforementioned problem.
i do know that avs2yuv does not currently respect multi-threaded scripts properly though.
so if either of the mentioned implementations rely on avs2yuv, then multithreading is surely broken for that implementation.

[saint-francis]

seeing at how i don't use either of those, i wouldn't know if they have the aforementioned problem.
i do know that avs2yuv does not currently respect multi-threaded scripts properly though.
so if either of the mentioned implementations rely on avs2yuv, then multithreading is surely broken for that implementation.

I think they both do. I think that people were having issues with it in MeGUI though so they are using vfw4x264 ATM.

[kemuri-_9]

I think they both do. I think that people were having issues with it in MeGUI though so they are using vfw4x264 ATM.

ffmpeg built with --enable-avisynth will suffice just as much as it uses vfw as well.
though that's probably a bit larger to have around than vfw4x264