[Tom Hawcroft] “I suspect my system specs are embarrassingly weak, 5 year old Dell laptop with 4gb RAM… but I haven’t had any problems previously with the preview stopping short, so I will suspect it’s either the file being stored externally, or that other applications were draining the memory.”
I’ll bet that you were using a lower resolution for your earlier previews; this requires less RAM than the full-res render.
If you share your comp settings (comp size and frame rate) and project bit depth, I can explain the math involved in the memory consumption a bit better.
[Tom Hawcroft] “It’s very useful to know that the pre-render format doesn’t really matter in terms of the preview, but would you say that full blown AVI (for a PC) is the best lossless format for this? I saw one tutorial recommending an image sequence.”
I like image sequences for a few reasons: you can easily re-start interrupted renders, you can easily re-render only a small portion of the total length, and you can process them externally with all kinds of other tools.
However, image sequences can also run a bit more slowly on mechanical hard drives (accessing many files versus accessing a single one).
The container should have no bearing on RAM consumption, though.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn]