Quote:
Originally Posted by LigH
Well, you used AVSMeter 2.6.2 (x86), so, a 32-bit process.
AVSMeter64 will run a 64-bit process.
Yet ... if you have LAA binaries, utilizing above 2.0 and up to 3.5 GB RAM should not cause so much speed penalty, that's a different issue (bold guess: maybe using a plugin which is not really LAA compatible, thus system calls occur a lot to try to prevent issues?).
|
I'm a bit puzzled by your post. What makes a plugin LAA compatible? LAA
only applies to the calling executable (AVSMeter, x264, VDUB, ...). Setting that linker flag in Avisynth.dll or plugins is pointless.
I have no idea why Avisynth+ doesn't exit gracefully with a proper out of memory message, I guess it's a plugin misbehaving in combination with multi-threaded AVS+.