Blackmagic Forum

Trying out the 'Kick Ass Keyer' (https://www.steakunderwater.com/wesuckl ... f=6&t=3194) - which works really well in Fusion 9 standalone but always struggles in Resolve.

Even just a simple HD green screen takes a couple of minutes to get to pick a screen colour, then often gets into a 'not responding' blue spinning circle death spiral.

Is this something that will eventually be optimised in Resolve17 as the beta evolves? Or will the recommendation to use standalone Fusion on complex comps hold for the forseeable future?

R17b6 - win10 on z840 - 64GB Ram Nvidia M5000 GPU

That question may be better asked of the plug-in's developer.

Jim Simon wrote:That question may be better asked of the plug-in's developer.

It’s not a plug-in, as such, it’s a custom tool built with Fusion tools (if I understand it correctly). Dev says (in thread I linked to) that it’s RAM limitations in Resolve vs standalone.

So it’s really like a complex composition in one node. (Which is how it ‘kicks ass’ as a keyer)


Be good to know that BM were aware and agree it’s a reason to use standalone or something they will be optimising in future.

Here's two simple timelines - using fast noise generator - one has the KAK tool added, but not inserted into pipeline and loads very quickly.

The other has the KAK tool inserted into the pipeline and takes several minutes to load.

Be interested to know if *anyone* can open the KAK timeline quickly in R17b6 (you need Reactor installed - https://www.steakunderwater.com/wesuckl ... php?t=1775 - and KAK installed from within Reactor).

I feel like, even though it is a very intensive, it shouldn't completely beachball Resolve when the same tool is very usable, even on limited MBP, in Fusion standalone.

I get the same behaviour with your two timelines - one loads instantly, and the other took just over 3 minutes to load.