Resolve Fusion Workflow Confusion...

Hi all,

Is there a way to 'render out' the results from the Fusion tab to maintain the intractability of the Edit page?

I.e. If I use a computationally-expensive tool such as Defocus in Fusion window (or even some of the new Fusion Titles) performance in the Edit window during play-back deteriorates to a degree where it's unusable.

It's as expected tbh: I don't expect a complex Fusion node tree with motion blur to be rendered at the composition frame rate in real-time...

So what is the suggested workflow in R15 using the new Fusion window?

Thanks all!


(I've used Resolve and Fusion for a few years (well since Editing tools were properly added to Resolve actually))

select "cache fusion output"?

select "cache fusion output"?

I've tried enabling the fusion cache for the clip but it only seems to slightly alleviate the problem - it'll play back in a very choppy way, often skipping large sections, at-best about 50-60% of the normal frame rate.

The ui showing how much is being cached on the timeline reflects this too. It looks like a mix of red and blue spotted areas. Playing through this multiple times doesn't sort it.

I'm wondering why there's no "Perform Full Fusion Cache" option in the Fusion page tbh, and hence me wondering what the suggested workflow was meant to be.

At the moment I'm seeing how the integration could be very powerful - but as it currently is working im not sure I could think of a situation where I'd choose the Fusion page over the 'external' Fusion Clip option.

I've tried enabling the fusion cache for the clip but it only seems to slightly alleviate the problem - it'll play back in a very choppy way, often skipping large sections, at-best about 50-60% of the normal frame rate.

This also depends on your cache settings and drive performance. Have you tried using a lower bandwidth cache format, like DNxHR LB, for eg.?

Admittedly, I haven't played with this yet, haven't installed the beta. But I do hope there is some type of render functionality so that a cut can be played down in real time. This is a commonly found feature on NLEs that allows for complex, non-real time effects to be pre-rendered for playback.

I've tried enabling the fusion cache for the clip but it only seems to slightly alleviate the problem - it'll play back in a very choppy way, often skipping large sections, at-best about 50-60% of the normal frame rate.

This also depends on your cache settings and drive performance. Have you tried using a lower bandwidth cache format, like DNxHR LB, for eg.?

Yea I tried that too - it doesn't seem to cache the frames properly and seems to skip the same areas each time.

Still got my fingers crossed there'll be a force-render-cache option in the Fusion tab

Just to add that I've experienced similar issues: it not always caching properly, even when trying to "force" it. For now, the only workaround that works for me is to render it out via the delivery page. However, this method of course negates much of the benefits of the integration of Fusion to start with.

There are many things to dislike about Avid Media Composer, but the Render In to Out function sounds like the perfect solution to this problem. You just mark an In and Out on the timeline -- and force a render of every effect that lives in that range.

There are many things to dislike about Avid Media Composer, but the Render In to Out function sounds like the perfect solution to this problem. You just mark an In and Out on the timeline -- and force a render of every effect that lives in that range.

Something like that would indeed be appreciated.

I don't know what changed in the Fusion rendering engine during its incorporation with Resolve - but I can't shake the feeling that it's not feasible to expect even simple Fusion tools to render real-time at 24fps, never mind 60fps.

So given that's the situation - and given that real-time full-frame-rate rendering *is* a feature of the Edit page - surely we need a 'render Fusion output to cache' option?

got the same problem. very similar to the exact same caching-related problems with fusion standalone.

didn't try b2 yet though..

Bump. Old post, same issue on v17. I have a small node tree (planar tracker, paint node and a psd image.) It will not render no matter what settings I try. Have tweaked cache type and all render settings I can find. It will put green lines over 2-3 frames then stop and remove the lines. Stays red in the edit tab. Then presumably because of this none of the clips will play on the edit tab. I'll start on a clip with no effects at all and it'll play back at 0fps then will jump way ahead and play 1 frame and repeat until the timeline ends. It's weird though bc if I disable fx in edit, it still won't play back. This is just 1 raw file with a few cuts on it.

I've reinstalled Resolve and the studio driver, ran GPU and cpu stress tests with great results, am getting almost 500MB/s transfer between drives. Am using BM raw 4k files. Next step seems to be to trash the 2 week edit and revert to 16 which worked flawlessly. Seems 17 should work as well since it's out of beta. It has to be either my computer or Resolve but every test and every other resource-intensive program is working perfectly.

Does BM maybe offer a paid remote login tech support? Or maybe someone would be willing to dl the 1 file and my database to try to replicate the issue? I'll pay. I really need to get this edit working as I'm in the project deep $$.

Did you try VFX Connect? Anyway, you got a PM.