Wed Jan 13, 2021 3:46 pm
Are you using. Resolve Studio or the free version? (If you have a Resolve Studio key it works with Fusion Studio v17 -- in beta, which has less overhead than Resolve Fusion.) As Kel said, you can turn on some optimizations in Fusion Studio that might more effectively use your CPU. (Plus Fusion Studio doesn't have the overhead of Media, Color, Edit, etc, that Resolve has. On the other hand, if Fusion Studio's input is not as convenient as a MediaIn in Resolve.)
Do you have overly-large assets that are part of things? For example, you could have an 8MB TIFF of which you're only using part and you're scaling it up with Transform. Or a 4K video where you're zoomed in and only using part in an HD comp. You might use a Resize instead of a Transform to resize an asset. The idea is to use assets that are as small as possible to still get the results and quality you want. If you're forcing Fusion to keep 4x or 16x the information that will ultimately make it onto the screen, it will take much longer and be more likely to crash.
Not only might it be more likely to crash, it might waste lots of CPU/GPU cycles processing excess data, or you might see the opposite: seemingly very little CPU and GPU usage because both CPU and GPU are waiting on data being swapped around. (Particularly the GPU which will probably have less VRAM than your CPU has RAM.)
Even in Resolve Fusion it's possible to use Saver nodes to output EXR sequences (I think) and then use a Loader to import that part of your node graph and not have to re-render it if you make tweaks downstream.
Last edited by
wfolta on Thu Jan 14, 2021 3:13 pm, edited 1 time in total.
Resolve Studio 17 latest, Fusion Studio 17 latest, macOS Big Sur latest, MacBook Pro 2020 64GB RAM and Radeon Pro 5600M 8GB VRAM