[Thor Metzinger]

Oh, trust me — I have put into the official requests, numerous times. But you never know – sometimes someone might stumble upon a post like this…and come up with a solution

[Thor Metzinger]

Just to put a conclusion on this–

The PNG 4Kx4K plates finally completed. 57 hours of Rendering through AME. 198 GB.

I redid another render just to see what would happen – this time using JPEG sequence @ 100%, 4Kx4K, 34,932 frames, Rendered in 9hrs 32min. 168 GB.

PNG was the issue. The format killed the processing. The JPEG sequence was accessing about 30-45% CPU and around 87 GB or RAM. Night and Day difference.

We are limited on the file format we can output, our slicing server for the dome will not read ProRes etc.

I was quite surprised that the PNG took so long since this was a pass-through render. Frame sequence source to Frame Sequence output…the PNG codec was the enemy here. I never realized the PNG was such a compressor-heavy file write. But now I know where the demons sleep!

[Thor Metzinger]

We are running CS6 AME — there is not a selection for GPU render– no dropdown menu to select a different render engine.

1. Source footage is Local PNG image sequences
2. Output is Local PNG iamge sequences
3. SATA 3 Harddrives 7200 PRM 2TB
4. SATA 3 Harddrives 7200 RPM 2TB

Looked at resources throughout the process – CPU usage was nearly ZERO the entire time…peaked at 3% usage. RAM 95%. Disk Activity was SUB-10mb/s and Network was 100kb/sec.

39412 Frames. Total
57 Hours of Rendering