Log in

View Full Version : Avisynth and Win7 64 bit compatible or not?


thegame
10th December 2009, 22:53
Hi,
I am planning on switching to Win 7 Pro 64 bit but have read both yes and no that avisynth works,now I know some of you here had to test this,so is Avisynth compatible with Win7 64 bit or not,I really hope it is.

Thanks in advance

Blue_MiSfit
11th December 2009, 01:56
Yes, of course it works fine - as do 99% of all 32 bit applications on Windows 7 x64.

I've been using it for about 6 months with no issues whatsoever. You can even use pipes and avs2yuv to make 32 bit AviSynth pipe to 64 bit x264 ;)

~MiSfit

kool
11th December 2009, 05:04
planing same move as thegame :p

Blue_MiSfit could you tell us where to start with, I mean do we need 64bit avisynth,meGUI,virtualdub and so on...

RunningSkittle
11th December 2009, 07:49
No, you can run 32bit (insert favorite app here). Welcome to 2009, pretty much everything 32bit works on windows x64.

tommy_vercetti
11th December 2009, 10:47
I confirm that it is working properly on Windows 7 x64 Ultimate, would a 64 bit Avisynth be more faster, just a query

kool
11th December 2009, 16:37
Hope I don't ask out of topic, but as long it related to 64Bit, I want to ask it here.

Do i need halli splitter when I use 64bit of ffdshow with 64bit of mpc-hc for playing files?

MadRat
12th December 2009, 07:18
Using 64bit Windows is tricky when it comes to encoding. I have XP Pro 64bit which is pretty much like a really, really stripped down version of Vista 64bit. What I normally do is encode using 32bit programs to a gigantic, lossless codec like lagrith, then do the final encode using all 64bit software. It's kind of kludgey but that's all I could come up with. If someone has a better suggestion I'm very open to it. I have no idea how I'll deal with x264 and megui.

osgZach
12th December 2009, 18:04
I don't even bother with an x64 encoding environment. Too complicated and I've heard the gains are somewhat minimal currently..

As for how to deal with MeGUI/x264 there is a thread on the forums somewhere, where you can get a version of x264 that should work fine with MeGUI without all those stupid unsupported tag errors, etc.

Although in my experience it still has to be the x32 version, as the x64 version will just lie and tell you it can't open your file for whatever reason.

Asmodian
12th December 2009, 23:44
I use 32bit avisynth with 64bit x264 using the pipe method in Win7 x64. It works very well and it a bit faster than using 32bit x264.

Lord Mulder has a great little program to make piping very easy too.

http://forum.doom9.org/showthread.php?t=144140

Blue_MiSfit
13th December 2009, 05:00
The easiest way is just using 32 bit avisynth and other encoding tools. They all run perfectly under x64.

I also use the 32 bit version of x264, and use Lord Mulder's GUI to automate 32 bit avisynth using pipes and avs2yuv to feed 64 bit x264. This gives a nice 10% boost when using slow settings :)

~MiSfit

stax76
13th December 2009, 05:24
How much boost does it give with medium settings?

TheRyuu
13th December 2009, 06:38
How much boost does it give with medium settings?

The slower the settings the more gain you'll get from using some kind of pipe to use 64bit x264.

The faster the settings the more overhead there is from using this pipe so your gain with 64bit x264 will go down the faster your settings get. I'm not sure where, or if there is even, a tipping point to where there is no benefit (or even negative benefit)?

Blue_MiSfit
13th December 2009, 11:44
As I said - you can expect roughly 10% when using slow / high quality settings.

~MiSfit

thegame
14th December 2009, 04:02
WOW thanks a lot for the replies guys,this is 1 of the major things I use and surely did NOT want to lose it by making the switch.

don't really understand the piping yet so I will start some reading.

again Thanks to all for the responses

Blue_MiSfit
14th December 2009, 10:11
Again, I suggest using Lord_Mulder's simple GUI to automate this process. You simply feed it an AviSynth script, specify encoding options, and it will automatically handle using avs2yuv and pipes to use the x64 executable if you're running on a 64 bit OS.

Ripbot264 is also a very powerful app that can do the same thing.

~MiSfit

kool
15th December 2009, 18:44
when there is solution for x264, how will Xvid work under 64bit?

osgZach
15th December 2009, 19:50
I'm not sure I understand what you are asking.

As it stands now, Xvid runs fine on x64 systems, and I think it can be multithreaded too.. So its got plenty of performance. I'm not sure if an x64 version exists, or if its even really warranted. I think Xvid may be approaching (if it isn't already) the end of its useful life, in practical terms. Its been super-ceded by x264 in a lot of areas, except low-end PC playback.

Blue_MiSfit
16th December 2009, 02:56
Yes, xvid is deprecated for most purposes IMO, with two notable exceptions

1) MPEG-4 ASP standalones
2) Extremly low end PCs

x264 is a far better choice in all other scenarios. Even slow PCs can handle H.264 if you use the "fastdecode" tuning. This disables CABAC and the in-loop deblocker - both of which hurt quality substantially, but improve decode performance quite a bit. Even with these limitations - I'd bet x264 can beat Xvid in the majority of cases.

If you still need to use Xvid and absolutely want to use the x64 version, there are definitely VFW builds floating around, and encxvid CLI builds as well - I would assume. Good luck finding them :)

Running 32 bit binaries will likely be much easier, IMO.

Just my two cents!

~MiSfit

mkv
3rd April 2010, 00:19
Can anyone upload own megui folder and avisynth folder on working windows7 x64...

all these configurations works on XP x86(32bit) perfectly.
http://www.imagebam.com/image/41883674656683
his error gives me no clue. any idea about that?

thanks.

osgZach
3rd April 2010, 01:13
Uploading our install folders won't do anything for anyone.

More importantly... Why is there no output video in the output field specified ?

Guest
3rd April 2010, 01:52
Why is there no output video in the output field specified ? Because his preview on open popped up the error.

osgZach
3rd April 2010, 03:06
hrmm... duh :stupid:

mkv
3rd April 2010, 14:30
Because his preview on open popped up the error.

WTF popped up error? can you explain?

osgZach
3rd April 2010, 14:38
When you open a file in MeGUI it automatically opens a preview window of the clip.

So the real problem here is not MeGUI (never was). It is that something in your script is not working correctly. Probably something to do with your DirectShowSource() call.

Post your script.

mkv
8th April 2010, 06:58
alright mates thx for the explaining.
here is the script content when I was successfully used on windows XP SP3
but it's not working on windows7 x64 ultimate

DirectShowSource("P:\777\source.m2ts", fps=23.976, audio=false, framecount=246713) #
crop( 0, 142, 0, -142)
LanczosResize(1920,800) # Lanczos (Sharp)
LimitedSharpenFaster(strength=40)
ConvertToYV12()

same script content, but given error has been changed right now.
error says:

AviSynth script error:
DirectShowSource:couldn't open file P:\777\source.m2ts:
Unspecified error
(P:\777\source.avs, line1)
http://www.imagebam.com/image/6f9c5075649873

also I tried to create avs script with using megui's avs script creator, I got different error.
error says:
Unable to render the file.
You probably don't have the correct filters installed.
http://www.imagebam.com/image/e4bffe75649876
I am using:
AviSynth 2.5.8,Haali Splitter (both of installed C:\Program Files (x86) directory)

FFDSHOW x64 (it's installed C:\Program Files\ffdshow)

mpc-hc.1782 x64

Blue_MiSfit
12th April 2010, 00:19
Try ffms2 instead of dss