You're very likely hitting this issue:
Fusion page: Major performance issue with MediaIn v LoaderPutting still images on a timeline and then going into Fusion will access each image with a MediaIn node. MediaIn nodes cannot cache in RAM, so the still image is copied over and over to the GPU on every frame. When many still images are involved this can very quickly cause out of VRAM errors. Resolve/Fusion has many problems with VRAM caching.
Normally the workaround is to replace the MediaIn with a Loader node, and then everything works great. But a Loader can't access timeline media, so things are more complicated in your case.
Possible quick solution: go into each Fusion comp, and in its MediaOut node, go to Settings -> Frame Render Script and enter this script:
- Code: Select all
if time % 20 == 0 or time == comp.RenderEnd then fu:PurgeCache() end
This will purge the RAM and VRAM cache every 20 frames, and also on the last frame of the composition. This might allow enough VRAM to be available for all the separate Fusion comps to work OK. Make sure you do it for every separate Fusion composition involved.
If that doesn't help, what you could do is forget the timeline, and just make a single Fusion Composition. In that composition, make Loader nodes to load all your still images direct from disk (one per still image, so 16 in total), and then re-create the timeline in Fusion. Ie using Merge or Dissolve nodes to comp one image over the previous one, and re-create the cross-dissolve transition you were previously doing on Edit.
Then drop that Fusion Composition on a timeline and render it. That should render fine with no VRAM problems.
I could advise more specifically if you show a screenshot of your Edit timeline, and an example of the Fusion comps you're currently making.