BruceS wrote:I'm working on a Virtual Choir with 56 videos... and even with Use Proxies and Optimized media turned on... when it comes to render, the 4min video with everyone on screen takes nearly 8 Hours to render. Ugh. I realize I'm not on an optimal machine for editing a 4K video from 56 1080 clips, and I've pre-rendered all of them down to 560p to use as my source files to minimize the pixel bucket brigade (then rendered proxies at 1/4 size of that)
You've answered your own question. If you're "not on an optimal machine," then it's going to be a struggle from day one. Figuring out the
workflow for this kind of project is the real challenge. If you use really, really light-duty files -- like 720P DNxHD36 clips (or 422LT) -- you could do this on a lot of different machines. Then, once you lock the edit, you could conceivably link back to the original files and then (and only then) render.
Worst case, find a local computer vendor who will rent you a big machine for a day or two and do all the relinking and rendering on that.
If somebody had come to me and said, "hey, I have to run 56 videos for a 4-minute video," I would run screaming from the room... and we have a $20,000 system. The syncing alone would be a nightmare. If it were me, I'd do the thing in pieces and maybe do 12 at a time, then put them together in segments and as finished layers at the very end. There's a way to do it, but a lot of it boils down to methodology and workarounds, not around Resolve limitations per se. This would be tough on Avid or Premiere or FCPX, too.
In general, I'd tell you, "don't start working on a project until the software actually arrives." Worst case, I would've just bought a 16 license from a local vendor and done it all in that, and waited to get the Speed Editor (which is still a work in progress). When your living depends on having equipment and software that works, today, you have to deal with the current reality of stable versions and reliable hardware.