Log in

View Full Version : Avisynth 32bit vs 64bit


DarkT
10th September 2011, 20:45
Basically, in 64bit there's lots of filters which do not work. I couuuuld somehow work around that, but is it worth it?

I have win7/xp (dual boot) setup both as 64bit. I could go for it, but is the speed/whatever adventage significant?

Also - I have i7-950 cpu, so it's like 4 cores. So I intend to get avisynth_mt working. somehow. Would it be even better there with 64bit?

Some info from personal experience would be nice.

DarkT
11th September 2011, 06:48
Also I use 32 and 64 bit version both on the same system with a temp avi files encoded with a Lagarith Lossless Video Codec between stages. Some plugins work faster on 64 bit, some on 32 (because no assembler optimization).

So, if you have a filter-chain of say:

32bit filter
32bf
64bf
32bf
64bf

you would basically run like... avisynth32...64...32...64... (4 different times? like, also, 4 different scripts?)

DarkT
11th September 2011, 19:49
DarkT yes, different scripts. But in this case we should have a fast RAID0 disk to avoid recording time addition. In my case it is not a problem. I correct Full HD video, so in most cases I have only 1..5 fps per a step. 32/64-bit optimization is important to me (±4...6 processing hours in total per a project).


OCZ Agility 3 (sata 3 connection) *grins* I do not think it'll be a problem :) :) :).

Blue_MiSfit
14th September 2011, 08:43
You're going to have a lot of problems.

I'd suggest just running a lot of 32 bit scripts in parallel ;)

Derek

Dogway
14th September 2011, 11:02
DarkT, I use i7, too with HT enabled. In most cases we should specify SetMTMode(5,3/4). I don't know a cause, but this was my the first trouble with avisynth: I got permanent crashes with SetMTMode(5).
That's curious because on a friend's machine win7 x64 quad core setmtmode(5) worked on a 500 frames ffv1 encoding, anything else failed at some point. Using 2 threads, 3, 4, 6, 8....

Blue_MiSfit
14th September 2011, 11:37
I believe SetMTMode(5) will actually be slower than using no MT at all...

TheRyuu
14th September 2011, 15:46
Basically, in 64bit there's lots of filters which do not work. I couuuuld somehow work around that, but is it worth it?

You can work around it by sticking to 32bit. 64-bit is a hackjob and stability is an issue. While we're on the subject all the MT stuff can fall in the same category.

If you want to thread avisynth I suggest you look into something like ParallelEncoding.bat (https://privatepaste.com/a7e26f09c4).

On a side note, you mention it's 4 cores, are you using SMT (hyperthreading)? If not you should be, you gain about 25% in x264 with it. Also why are you dual booting Windows 7 and XP?

So, if you have a filter-chain of say:

32bit filter
32bf
64bf
32bf
64bf

you would basically run like... avisynth32...64...32...64... (4 different times? like, also, 4 different scripts?)

What?

DarkT
15th September 2011, 12:17
Huge lack of plugins... I suppose the sensible way is to go encoding everything you can with 64bit plugins into LAGERITH 1st pass. Then use 32bit plugins on the lagarith... So I suppose you just have to break shit down into more passes to be able to have both compatability as well as supreme speed. I guess... *shrugs*

I wonder which OS would encode faster. WIll check soon. winxp or win7.