Quoting your PM:
davy_a wrote:Hey unfortunately I can't post a link on the forum, but Imma send you the link via private message. Hope it is working this time
https://drive.google.com/drive/folders/ ... sp=sharing
two fonts included, which have to be installed for making this project work. AND it is only the last fusion Clip which is causing the problems. The previous ones should be working fine.
cheers David
OK so I experienced the exact same problem on DR Studio 17.2.2 on macOS. The compositions work in Edit, but Deliver just won't start, and requires Resolve to be Force Quit.
Took me a while to figure it out, but I've got it:
1. Close Timeline1 (so you're looking at nothing)
2. Playback menu -> Timeline Proxy Mode -> Off
3. Open Timeline1, Deliver it
It appears that having Timeline Proxy Mode active is completely breaking Deliver somehow, at least in this project with Fusion comps. A strange and very annoying bug. I suggest reporting it to BMD in the main DaVinci Resolve forum.
The reason I gave step 1 - closing Timeline1 - is that the first time I tried changing Timeline Proxy Mode to Off I was looking at Timeline1, and switching Timeline Proxy Mode locked up Resolve. Another bug.
So that will get it rendering. Then the first render I tried failed for me early into the second Fusion comp. I changed Preferences to disable the option that stops renders on errors, and then it seemed to render OK (I cancelled before the end though as it was going to take ages - I got as far as part way through composition 5)
By the way, while looking through your comps, I noticed:
> Multiple merge nodes with only one input - you might want to clear these out as they're not doing anything
> Your Renderer3D nodes are set to Software - you will likely get better performance from switching these to OpenGL (the output image may change, so might require altering the scene and/or Renderer3D settings a little)
> On the last Fusion comp you're using multiple MediaIn nodes to load still images. I highly recommend swapping those out for Loader nodes, loading the same images direct from disk. Using MediaIn for images can drastically tank performance in Resolve's Fusion page (for more info:
Fusion page: Major performance issue with MediaIn v Loader)
If you're going to be working with compositions of this complexity, you may want to check out Fusion standalone. If you own Resolve Studio, you already have access to Fusion Studio 17. If you don't, then Fusion 9 standalone is still available for free. Either option will likely be more stable and perform better than the Fusion page in Resolve.
What you lose is the ability to easily add compositions to existing timelines with edited clips, but at least in this project, you're not doing that. Fusion standalone works fine for animating to a single audio track, as it has an option to load an audio track and play it in time to your composition.
Or you can design in Resolve, as you have here, then switch to Fusion standalone/Studio just for the final render of each composition. Render out in standalone, then import the renders into Resolve and put them in your timeline in place of the compositions, and do a final render to combine them together.
If you do need to stay in Resolve, I would recommend rendering each of the compositions separately. This could be done two ways:
A. Render in Individual Clips mode, with audio disabled. This will render out each individual clip (in your case, that's each Fusion composition) as a separate file.
B. Manually render them individually, eg by dragging the Fusion compositions into the Media Pool to create permanent clips from them, giving them unique names, then dragging each of them to their own separate timeline. Then make one render job for each each of those timelines.
In either option, you would render these separate clips to a high quality intermediate format like DNxHR HQ, so no quality is lost by rendering multiple times. Then import the rendered files, duplicate your master timeline, and put the newly imported files onto the duplicated master timeline in place of the Fusion compositions. Then render out that duplicate master timeline in standard Single Clip mode with audio enabled, to get your final deliverable. That final render will be very fast, as Fusion is not involved.
Rendering them individually means that any render error in one won't affect the rendering of the others, and it means Resolve and Fusion have a chance to clear their caches in between renders. This may reduce the time it takes to render overall, even though you have to do multiple renders. It also means a failure late in the process only breaks the file that was rendering at the time, and not any that completed successfully before that point, and you can then retry just that composition (and any after it), rather than starting from the beginning every time.
Sun Aug 15, 2021 6:42 am
maybe it works). 