Lee Reichel wrote:I wanted to add I have a GTX1070/8 GB. I rendered the same video and native or Nvidia makes no difference. I am rendering H.264...
My suggested workaround: don't render to H.264. Render to a mezzanine format like DNxHD or DNxHR. Once you have that file, run it back through Resolve or another program and then create the H.264 from that file. I bet it will go considerably faster (or at least consistently).
I think when you're hitting the computer with XAVC S compressed video (which I believe is an H.264 variant), and you're putting titles on top of it, and you're running at 60fps, and you're in 4K, and you're rendering H.264 out of the computer, that's a lot of stress all the way around. Massive hardware (CPU, RAM, GPU, I/O, etc.) might be enough to reduce this problem, but you're trying to leap over a very big wall.
I generally try to consider the intended distribution chain of the project, and then adjust the workflow accordingly to match the available schedule and budget we have to work with. For example, I'd avoid 60fps unless the client demanded it, knowing that 30fps/29.97fps is going to be fine if it's just online or broadcast TV. I'd create 4K transcodes for all the XAVC files provided it was a very high-quality codec like ProRes 444 or DNxHR HQX, and I'd only render to mezzanine files. I try to pick my battles and avoid slowdowns in Resolve if at all possible, provided it has zero effect on picture quality.
We do try to work entirely in 4K with 4K source material, even when rendering out to HD, because I'm convinced it scales better than putting the 4K in an HD timeline. I admit, the differences are small, but I've gotten caught by this a few times and learned from those lessons. (The good news is, as we used to say in the 1980s, "it's not a mistake if we caught it before the show ships.")