This made sound silly but . . . what is the point of Render to RAM? If you make a small change don’t you need to render the whole thing again anyway? If that is the case aren’t you better just rendering to your hard disk as a movie format?
Thanks.
This made sound silly but . . . what is the point of Render to RAM? If you make a small change don’t you need to render the whole thing again anyway? If that is the case aren’t you better just rendering to your hard disk as a movie format?
Thanks.
Render to Ram does essentially the same thing as clicking “play” and letting it cache your timeline.
I rarely use it, however if you have pretty layer heavy composites, and not a whole lot of RAM, it can do a better job of compressing it for storage on the RAM.
RAM has the huge advantage over saving it to your HD of having bandwidth potentially in the hundreds of MB/s as opposed to 20 or 30 from a 7200rpm hard drive.
Ah right, thanks.
I guess if you have complex workspaces and not much RAM (a gig of DDR like I do) then maybe there’s not a lot of use for it . . .
Depending on the composite Render to RAM caches everything in one layer. Hitting Play caches the indivual layers also, this is only useful if you have got a lot of RAM.
One advantage of Render to RAM is that you can save the render instantly by File> Save Ram Player as. The compare operator feature is also quite useful.
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.