I've been having issues with renders failing since updating to Windows 10 with the following error message:
After Effects error: Unable to allocate enough memory to render the current frame (1280x720 @ 16bpc). Either decrease the memory requirements for rendering of this frame, or install more RAM. (12805). For more information, see www.adobe.com/go/learn_ae_mem (7 :: 66)After Effects error: Timewarp out of memory. (4) (25 :: 60)
It failed less than half way through the render (at 01:58:22 of 04:10:00) after 2hr57 min. Also my project is set to 8bpc in project settings so why is the error saying its rendering in 16bpc (is this due to an effect)?
Using AE version:
AE CC2015.2 Version 13.7.1.6 (I'm not using Multiprocessing, in fact I don't even see it as an option in the Preference Menu?)
Plugins:
Magic Bullet Suite (12.1.4)
Render settings:
H264 Quicktime MOV with Audio (AAC), 100% quality, 8bpc
PC specs:
16GB RAM, Intel i7-4790, NVIDIA GeForce 720
Running Windows 10 (1511) 64bit with issues, or running Windows 8.1 (6.3 Build 9600) 64bit without issues.
Quicktime:
Version 7.7.9
I don't have any other applications running while using AE and rendering. The render will complete if I set the quality down to 70%, which I thought was weird because I would have assumed AE would need to store more information about each frame (and the frames either side) in order to make the compression. I've rolled back to Win 8.1 and using the same render settings, the render completed in 2hr32 with no error. I have also been able to output an uncompressed version in Quicktime Animation in 16bpc on Win 8.1 which I can't do on Win 10.
The footage is being loaded into AE as (uncompressed) image sequences, with a DOF pass, motion blur, colour correct - so there's quite a lot of stuff happening on each frame but its consistent through out the project. What I mean is it hasn't suddenly got to an intensive frame and given up, there's no difference between the frames it failed and the rest of the project. It's nothing it shouldn't be able to handle (and it's worked on Win 8.1).
I'm just confused as to why it would render OK on Win 8.1 but then be sluggish and fail on Win 10? And what may be a solution? It seems like an issue with the RAM not being made available again?