can I install both 32 and 64bit avisynth?

[El Enmascarado]

I heard you can't use filters from 32bit in 64bit avisynth and viceversa, I want to know if I can install both versions or can't do that? what version do you recommend me as to what version has more and better filters, does 64bit avisynth allow faster encoding? or just better filtering? is this to be used with virtualdub only and used to create avis and mpgs only?

[sneaker_ger]

You can install and use both versions, but the only main advantage of AviSynth 64 bit is its ability to use more than 4 GB of RAM. Since this is only necessary for very crazy scripts and since AviSynth 64 bit is not really developed anymore and you have fewer pre-compiled plug-ins at hand, it is recommended to keep using AviSynth 32 bit.

[blubb444]

You can install and use both versions, but the only main advantage of AviSynth 64 bit is its ability to use more than 4 GB of RAM. Since this is only necessary for very crazy scripts and since AviSynth 64 bit is not really developed anymore and you have fewer pre-compiled plug-ins at hand, it is recommended to keep using AviSynth 32 bit.

Oh, I'm not even that much of an advanced AviSynth user, but just try to use either QTGMC or MCTemporalDenoise on a 1920x1080 with any settings higher than "very fast" or "very low".. even with 720x576 material I sometimes run out of RAM just with medium settings (VirtualDub seems to crash at around 1.4GB already). I always have to go through the tedious job of splitting up the video into smaller areas (sometimes up to 8) to avoid running out of RAM or getting glitches. I know that the MT() function does something similar, but as it is still all done in one script, it won't work. This forces me to work with lossless intermediates which I then have to stack together again... so 64bit would make a lot sense there (I have 16 gigs of RAM and a 8x4GHz processor).

[sneaker_ger]

There are some tricks to cope with the memory limitations. There's some discussion in the AviSynth 2.6 MT thread about VirtualDub and this:
http://forum.doom9.org/showthread.php?p=1602698#post1602698

Though most people would use something like avs2pipemod and x264.exe.

[blubb444]

Yeah, I use VDub for previewing only, for the final encoding step I use avs4x264mod and 64bit x264 but this crashes around the same amount of RAM.

[Groucho2004]

even with 720x576 material I sometimes run out of RAM just with medium settings
Odd. I just ran a test with QTGMC, PAL interlaced, 720x576:
SetMTMode(5,8)
LoadPlugin("DGDecode.dll")
Import("qtgmc.avsi")
MPEG2Source("test.d2v")
SetMTMode(2)
AssumeTFF()
QTGMC(Preset="Slow")

Here are the results with AVSMeter:
AVSMeter v1.46 by Groucho2004
AviSynth 2.60, build:Aug 28 2012 [18:17:07]
Active MT Mode: 2

Number of frames: 3408
Length (hh:mm:ss.ms): 00:01:08.160
Frame width: 720
Frame height: 576
Framerate: 50.000 (50/1)
Colorspace: YV12

Frames processed: 3408 (0 - 3407)
FPS (min | max | average): 64.37 | 104.47 | 81.36
CPU usage (average): 99%
Thread count: 41
Physical Memory usage (peak): 574 MB
Virtual Memory usage (peak): 625 MB
So, even with 8 threads (41 total) the peak memory usage is only 625 MB.

[SamKook]

In my experience, the problem isn't that a script uses too much RAM most of the time(unless you're using QTGMC with a 1080p source and want to max out your CPU, then there's no choices but to split the movie. 3 or 4 parts is enough with my overclocked i7-2600k for QTGMC at veryslow), it's that it starts to require more(or it leaks) at some point for some reason and then it won't be long before it crashes. I've never managed to identify why that is.

I've encoded a 1080p source using QTGMC at placebo and only 2 threads that used about 3.5GB of RAM without any crash(took 21 days though), but some DVD that was only around 800MB started to climb after a few hours until it crashed.

Sometimes, the same script with the same source will crash the first time, but work a second time without requiring any modifications.

A good value(achieved by trial and error since it's different for different systems) for SetMemoryMax will help a lot in achieving something stable.


Back to the original question: you have to install the 32bit version first using the installer to install the 64 bit one if I remember correctly since it uses the same install folder for the creation of the plugin folder so that answers that question.

The biggest problem with the 64 bit version is the lack of plugins and that they're often older versions than the 32bit ones, but if all you need exist in 64bit version and is up-to-date, then nothing is stopping you from trying it.

[blubb444]

Yeah, my bad, should've clarified better what relates to what. In fact, QTGMC only does trouble on HD material while MCTD already starts with SD.
QTGMC with very high settings on SD gets somewhat close to the limit though:
[Runtime info]
Frames processed: 2540 (0 - 2539)
FPS (min | max | average): 7.97 | 37.50 | 22.74
CPU usage (average): 97%
Thread count: 43
Physical Memory usage (peak): 854 MB
Virtual Memory usage (peak): 1267 MB
Time (elapsed): 00:01:51.720


[Script]
SetMTMode(3,14) #After some testing, I found 14 threads to give the best performance on my system
AviSource("20050818_175333.avi",pixel_type="YV12") #old DV file
SetMTMode(2)
QTGMC(Preset="Placebo", EdiThreads=2)
levels(16, 1.0, 255, 0, 255, coring=false, dither=true) #correcting the strange 16-255 camera levels to PC levels

With "slow" settings:
[Runtime info]
Frames processed: 2540 (0 - 2539)
FPS (min | max | average): 43.27 | 111.95 | 68.59
CPU usage (average): 98%
Thread count: 43
Physical Memory usage (peak): 616 MB
Virtual Memory usage (peak): 671 MB
Time (elapsed): 00:00:37.031


[Script]
SetMTMode(3,14)
AviSource("20050818_175333.avi",pixel_type="YV12")
SetMTMode(2)
QTGMC(Preset="Slow", EdiThreads=2)
levels(16, 1.0, 255, 0, 255, coring=false, dither=true)

Now HD with "slow" setting: (VDub, even the LAA version, crashes after advancing a couple frames manually at around 1.3GB)
AVS meter tries to load the script but terminates with a "Microsoft Visual C++ Runtime Error" at less than 1.2GB, this was the script:
SetMTMode(3,14)
DirectShowSource("20110104_164726.avi")
AssumeTFF()
SetMTMode(2)
QTGMC(Preset="Slow", EdiThreads=2)
levels(16, 1.0, 255, 0, 255, coring=false, dither=true)

Reducing the threads to 8 works but with a HUGE performance dip. I didn't feel like waiting 40 minutes for the script tu run to the end so I just copied the CLI text:
AVSMeter v1.46 by Groucho2004
AviSynth 2.60, build:Aug 28 2012 [18:17:07]
Active MT Mode: 2

Number of frames: 3984
Length (hh:mm:ss.ms): 00:01:19.680
Frame width: 1920
Frame height: 1080
Framerate: 50.000 (50/1)
Colorspace: YV12

Frame (current | last): 343 | 3983
FPS (min | max | average): 1.15 | 4.60 | 1.59
CPU usage (current | average): 68% | 72%
Thread count: 36
Physical Memory usage: 1095 MB
Virtual Memory usage: 1177 MB
Time (elapsed | estimated): 00:03:36.624 | 00:41:48.808

It was ~43 times slower than the same settings on SD, from the number of pixels and the somewhat lower CPU usage thanks to only being able to use 8 threads, one should expect it to be around 7 times slower.