Avisynth and virtualdub 32bit, going OOM

[tsk1979]

I am making a timelapse.

I have various sequences ranging from 450-700 frames.

So I just go with
a1=imagesource(...)
a2=imagesource(...)
.
.
Then I dissolve a1,a2.... and so on

I am seeing that when processing longer sequence (700 images of 1080P) size, it goes OOM.

I'm using 32bit because I need MSU deflicker plugin.
I am not sure if I am hitting the 2GB limit too. It seems odd that ImageSource will hit the memory limit.

Machine is Xeon i7 1231v3 and RAM is 16GB. I also have a Nvidia medium end graphics card(not that it matters).

Any idea I can figure out how much memory did my process request? Did it request more than 2GB?

Alternatively, I can assemble a video in 64bit and then run deflicker by reading that video in and then reading it out, but that is going to degrade quality(unless I go for uncompressed video(which will be massive running into many GBs)

Reading that video in 32bit is going to give me more problems I guess.

Those who do timelapse with 4000-5000 frames, how do you do it?

[LigH.de]

AVSmeter should help you discovering the memory consumption.

AviSynth has indeed some trouble handling hundreds of clip variables. It is probably preferable to read all images as one sequence first, then change the framerate with an interpolating function; unfortunately I don't remember right now which one will be best suited, just believe to remember that the AviSynth kernel FPS functions (specifically ConvertFPS) may have limits up to which framerate ratio they will apply blending, which seemed paradox to me.

MFlowFps of MVTools v2 is a lot more elaborate, trying to interpolate frames with motion compensation, may return a much smoother result when it works flawlessly.

There may be more plugins useful for timelapses which I don't know.