| ||||||||||
| Hi, It's important to know that the project rendering bit depth is unrelated to the bit depth of the file format you're saving as. You can save an 8 bit tiff, a 16 bit tiff or a floating point tiff regardless of whether you render at 8,16 or 32 bpc. You will get a warning message if you want to save a 16bit tiff while only rendering at 8 bit, but AE won't stop you from doing it. If you use multiple output modules you can even save all 3 versions at the same time, with only minimal increase in the overall rendering time (not that there's any reason to do this, but know that you can...) The rendering process is what takes up the time. Outputting the rendered frame is negligible. How much slower it is to render at 16 or 32 bit compared to 8 bit depends on the project, plugins, and the amount of ram in your machine. In some cases rendering at 16 bit is not too much slower than 8 bit, but unfortunately rendering at 32bit is much slower again. In your case, if you tried rendering 32bpc with 8 instances of BG render, I would suggest that you're running out of ram and this is slowing down your entire machine. When you work at 16 bpc, you're effectively halving the amount of stuff that can be stored in the image cache, and if you render at 32bpc then you're reducing the effective size of the image cache to a quarter. AE can quickly run out of memory, and then things will slow to a crawl. You may get better results by turning on multiple processing instead of using BG render, and allocating each CPU at least 2GB ram. Or if your project uses lots of ram, you may even get better results without multiple processing and simply rendering within After Effects. But basically - saving a 16bit (trillions) tiff file is unrelated to the time it takes to render something. -Chris On 28/04/2012, at 2:30 AM, Rick wrote:
|
