DNG management inside of the LD is horrible. Tons of unnecessary I/O and the cache is 400% larger than it needs to be. Loaders can't be instanced, so any changes made to one LD can't be easily replicated in other LD's.
What would make more sense is to load in DNG images as mono int16 images and have a tool that did the development . This would allow much more efficient workflows.
Could just be another option for the various formats. Like for DNG, could add a third option in Color Processing of none . If you wanted to maintain 3rd party functions like for Red or Canon or whatever format, those could have their own tools or be modes for a universal tool.
Copy/paste between Fusion and Resolve, even if indirectly. Meaning, for example, a Resolve grade node should be able to be pasted into Fusion, even if the UI is different, so that rendering can be executed from either application. On the Resolve side, that would involve calling an instance of Fusion, but at least we'd have interoperability without the disk I/O.
With every Resolve release I hope there will be Python support. I would say it is about the time. Fusion Connect is not nearly enough, and Resolve users would benefit greatly as well (just look at the crazy stuff people do with scripting inside Vegas).
Fu 9 IMHO killed Generation , so there is only one path for conform and shot prep now. Fingers crossed.
when you import an alembic file, it would be great to have the option of turning off all the mesh you don't want at the start.
this can avoid the long wait for it to load a massive batch of nodes that you then need to go through meticulously in order to find that one you do want to have before you can eventually remove the ones you don't want.
if there is already a fast way to do this, please let me know!
A realtime feed from a blackmagic capture card. So I can do live composites and line-ups for the Director and DOP while on location.
E.g. frischluft lensfeed
Oh, yes! It's a no brainer from a BDP synergy standpoint. And Fusion is so fast at doing frame rendering, you could really see this being practical in on-set use or for someone doing say, stop motion.
I'm not sure what you'd need to have in place to make Fusion never stop rendering. There might be a straightforward way of doing that already. Everything is based around frames having one result that is cached, I've never tried to do anything else.