Unrealistic expectations of Resolve 20.

+1 for customizable UI (grey on grey is the worst experience for my old eyes).
2) A patch panel that looks and operates like a patch panel. (Am I the last man standing who actually used a real patch panel back in the late 1950's?).
3) Some real-world help (with diagrams) for old sound men on how you get an ambisonic BFormatACN bed to give you something you can play back in 5.1/7,1/7.1.2 etc on your home theatre system).
4) A play back format within Resolve that does not use a sub-woofer. (4.0/6.0 etc. My ears tell me that even low frequency (bass) has sound positioning information, albeit small).

AI getting into auto-matting.

https://matanyone.com/
https://paperswithcode.com/paper/matany ... tting-with

The development of AI video is going exponential.

It is simple: Resolve is on the AI bandwagon big-time or they will be obsolete soon!

Some editing software, like Final Cut Pro, allows users to easily add elements to the timeline. A simple keyboard shortcut can bring up a solid, an adjustment layer, or a text element. I believe that being able to do this in the Edit page is necessary, or at the very least, being able to incorporate the SHIFT + SPACE functionality that we have in Fusion.

For some time now, I have been harbouring entirely unrealistic expectations for the Resolve 20 release, based purely on the fact that it's a big round number.

There. I've said it.

I'd like to see Blackmagic Design partner with the Blender Foundation and make the full version of Blender available as a page inside DaVinci Resolve. Is that asking too much?

I'd like to see Blackmagic Design partner with the Blender Foundation and make the full version of Blender available as a page inside DaVinci Resolve. Is that asking too much?

I don't think there need to be Blender inside of Resolve (RAM & VRAM requirements would explode), but definitely there could be some kind of bridge between the two, to have some crazy live connection between the two ?

I feel my expectations are very realistic, but whether or not they are enough of a priority to actually get done is another thing.

I still just want to be able to move clips around on the timeline without Resolve automatically deleting things (clips and transitions)... I don't think this an unrealistic expectation, especially since Resolve already has both of these solutions partially implemented already. Much of the work is already done, it just needs to be completed.
#1) Layered Video Editing: to overlap clips on the same track without deleting anything underneath.
viewtopic.php?f=33&t=176919
#2) Auto-Crossfade: automatically create a crossfade when overlapping clips and allow clips with crossfades to be moved while adjusting the length of the crossfade instead of deleting the crossfade.
viewtopic.php?f=33&t=179234

Publish to Edit Page in Fusion: A right-click menu option for individual controls, nodes and groups of nodes in Fusion to have the controls show up on the Edit page. I make too many custom effects in Fusion to make use of the macro export/import process. I just want a fast and simple way to get the controls for my custom Fusion effects on the Edit page. This would be prefect!
viewtopic.php?f=33&t=179069&p=1056389#p1056389

A Mouse Editor (like the Keyboard Editor) to customize the mouse wheel, mouse buttons, and modifiers. After over 3 years of using Resolve even the basic navigation with mouse wheel+modifiers for scrolling/zooming on the timeline still drives me nuts as it is completely opposite of what I find comfortable. I have customized the mousewheel modifiers for navigation in my other DAWs and I would love to be able to use those in Resolve as well.

These are my top priorities and they would drastically improve my overall experience using Resolve.

I feel my expectations are very realistic...

Well, the thread was intended to be about unrealistic expectations of a truly major new version, Sean! ;)
For what its worth though, personally, neither your number 1 nor number 2 desires are anything I have even the faintest interest in ever seeing implemented... which doesn't mean the devs shouldn't, won't or haven't already worked on implementing them, it just proves that whatever they do to make version 20 an iconic release (if or when that happens), it's highly unlikely they'll please us all. :)

it just proves that whatever they do to make version 20 an iconic release (if or when that happens), it's highly unlikely they'll please us all.

And for that reason it's easy to wish folks would lay off with the more idiosyncratic requests, "realistic" or not, so the focus would remain on the essential ones on which there's broad agreement. As in, the way the thread started: all the fixes the Edit page needs. Parties checking in with a new request virtually every day or a few times a week means they all get swamped.

For what its worth though, personally, neither your number 1 nor number 2 desires are anything I have even the faintest interest in ever seeing implemented...

My top two requests are for a non-destructive editing experience on the timeline. The other editors I've used (multiple DAWs and two other video NLEs) have all worked this way (with the exception of my very first DAW Cakewalk Pro Audio 9, but that was 25-ish years ago and editors have evolved significantly since then). I'm exactly the opposite as I've never had any interest in destructive editing on the timeline. I don't want the editor deleting things without my explicit say so. I move clips and effects around all the time and I don't want clips, effects, or transitions being deleted from doing nothing more than move them. Having to tread on eggshells to keep Resolve from deleting anything is one of my biggest complaints about editing in Resolve, I'd like the ability to change it to be completely non-destructive. However, if you do want the destructive timeline behavior then the non-destructive functions can be turned off. Both options should be available.

1 - a true Motion Design Tool/Page
2 - a Single Nodal Page for Colorgrading and Compositing

Big yes to the Motion Design Tool/Page!!! Either deep integration with Autograph or Cavalry or a huge update to fusion.

My longest standing and still most desired ask:

please give me a setting that lets me ripple or roll on a per edit point basis simply by selecting one or both sides of the edit without any mode change.

Premiere does it with this setting:

preferences > Trim > Allow Selection tool to choose Roll and Ripple without modifier key

Related to this I wish there were a setting that restricted edit point selection to only one edit point per track. It’s extremely rare for me to roll or ripple simultaneously in more than one place on a track. It’s common for me to make complex edit point selections where I’m adding multiple edges. It sucks when there’s an edge that’s left over from a previous edit that I forget to clear and that selection breaks the whole move.

Plus, since undo doesn’t restore the selection I have to start all over again rather than just fixing the one little glitch.

Here’s a link to where we last discussed this and the usual suspects told me to forget everything I know and just do it Resolve’s way. Resolve’s CURRENT way is just way, way slower. But with a small tweak…

​https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=157598

1. I only want to be able to target tracks with the Data Burn In function.
Ideally, the Data Burn In would be available as an Effect as well.
(Requested long ago here: viewtopic.php?f=33&t=124158 ).
Without this, I find Resolve to not be usable in VFX intensive projects.

2. Much better scripting.

Ability to watch clips with 1 fx using BRAW and a 4090 at the full 24 fps

... not sure about that one, i have plenty of full resolution BRAW clips in a 4k timeline and I can pay back 50 frames per second with a 3090ti....

I want to say... it's your setup...

I don't disagree. I'm finding that performance issues are boiling down to cache. In the project I just finished, I have 1 TB of cache for a ~7:50 short. I only have about 600GB of footage and am only using 200GB of it at the very most. 2 clips have Fusion. I wouldn't be able to possibly edit a 30 minute movie with Resolve because that cache alone would fill my drive. There is definitely something very wrong with their cache system. I have, in fact, deleted the cache a couple times. Each time it rebuilds to about 1 TB.

Ability to watch clips with 1 fx using BRAW and a 4090 at the full 24 fps

... not sure about that one, i have plenty of full resolution BRAW clips in a 4k timeline and I can pay back 50 frames per second with a 3090ti....

I want to say... it's your setup...

I don't disagree. I'm finding that performance issues are boiling down to cache. In the project I just finished, I have 1 TB of cache for a ~7:50 short. I only have about 600GB of footage and am only using 200GB of it at the very most. 2 clips have Fusion. I wouldn't be able to possibly edit a 30 minute movie with Resolve because that cache alone would fill my drive. There is definitely something very wrong with their cache system. I have, in fact, deleted the cache a couple times. Each time it rebuilds to about 1 TB.

which kind of cache file are you rendering to?

Still want an OPTION to save/restore the playhead position with undo/redo.

Here’s a great example of an Avid tutorial using this feature - which exists in both Avid and both flavors of FCP.

Go about 90 seconds in to see what I mean.

Still want an OPTION to save/restore the playhead position with undo/redo.

+1

also for "dumb" moments when i jump to the start/end or a marker or anywhere by accident.

Exactly!

My unrealistic expectation is an AI edit button - you press it and it automatically edits, grades and exports. It then also books you a holiday to the Maldives.

Now that’s an excellent unrealistic expectation!

Am currently wishing there was a user or project preference to keep timeline clip selection synced between all pages... so if I select a clip in the Color page timeline then that same clip will be selected if / when I switch to Edit page and vice versa etc. At present, broadly speaking, every page retains and reverts to its own previously active selection, though the actual behaviour between certain pages is not entirely consistent.

Note: Both behaviours (page specific selections vs synced selections) have their uses, so make it a preference that can be changed as necessary.

Right now I believe the media, edit, cut, and I thought color pages share a common selection.
Are Fairlight and Fusion the odd men out? If so that sounds more than happenstance than explicit design.

Right now I believe the media, edit, cut, and I thought color pages share a common selection.

With respect to timeline clip instance selections, currently, every page preserves its own unique selection memory... except the Deliver page, which does the opposite. ;)

Select any clip or clips on the timeline in the Cut page and then switch to the Edit page... the active selection doesn't persist; whatever was selected previously (on the Edit page) will be selected instead (or nothing, if nothing was previously selected)... change the Edit page selection to something new and switch back to Cut page... that new selection doesn't persist, instead the selection is back to whatever clip or clips were previously selected in the Cut page. Same holds true when switching between any pages that have a timeline view: Cut, Edit, Color and Fairlight... but not for Deliver. Switch from any page to Deliver and suddenly there's no selection at all, regardless of what may have previously been selected in Deliver... but wait, theres more... select something on Deliver page and then switch to the Edit page... the Deliver page selection persists! ... switch back to Deliver though, and hey presto the selection is gone again (as is the Edit page selection).

More specifically, Cut, Edit, Color and Fairlight each have their own selection memory which is always restored when switching to that page, except when switching from Deliver to Edit. Meanwhile, the Deliver page has no selection memory at all. When you switch to Deliver (from any page) there is always no selection. When switching from Deliver to Cut, Color or Fairlight then the previous selection memory is restored as normal.. but meanwhile the Edit page selection memory will have been replaced with whatever was just selected in Deliver (or wiped if nothing was selected in Deliver). Because the Edit page selection memory is synced to the Deliver page selection... but not the other way round (because, as noted, the Deliver page has no selection memory).

All in all, it's a bit of a hot mess really... but as much as I'd like to see the selection memories working more consistently across all pages, what I really want is an option to turn this memory behaviour completely off (across all pages), so my active clip selection doesn't ever change when switching pages.

Ah! I meant the playhead. Sorry about that!

Well, i got my wish in 19.1.4

Apple ProRes encode support on Windows and Linux.

Well, i got my wish in 19.1.4

Apple ProRes encode support on Windows and Linux.

Now I believe in god
Fantastic news

I only want one thing... customizeable interface! Move, size windows wherever I want.

That really is an unrealistic expectation. Sorry!

I only want one thing... customizeable interface! Move, size windows wherever I want.

That really is an unrealistic expectation. Sorry!

Sadly, you are probably correct.

It’s a philosophical preference they seem to have. Which can be ok as long as what they provide can comfortably accommodate the workflows people are using.

It’s a philosophical preference they seem to have. Which can be ok as long as what they provide can comfortably accommodate the workflows people are using.

Unfortunately, nearly every single thing Blackmagic has setup in Resolve is the polar opposite of what I find comfortable to use. So I don't think they will ever set things up in a way that is comfortable for me, which is why I don't want them to try. All I want is more flexibility/customization so that I can set things up exactly the way I want and others can do the same for themselves as well. So for those who like Resolve just the way it is, they can leave it... but I would turn Resolve upside down and inside out if I could and as long as I could export/import my settings I'd only have to do it once. Then I'm happy.

Guides and rules (for possible pages)
Presets transforms (edit and cut Page)
Diamonds keyframes (fusiion page)
Speed graph (fusion page)
Shortcuts for parameters on inspector (fusion page)
Remix tool (like a premiere)

+100

I dreamt that v20 was released today, but I woke up before I could read about the new features.

My highly unrealistic expectations are:
1. A simple cache/prerender node in fusion

Right click any 2d node in fusion "Cache to disk"...

My highly unrealistic expectations are:
1. A simple cache/prerender node in fusion

Right click any 2d node in fusion "Cache to disk"...

Thanks for the suggestion, sometimes im wondering am I using a different version of davinci resolve, am I doing something completely wrong or do people recommend this feature without using it themselves? I dont use the standalone fusion, because I need some of the resolve fusion features, maybe thats why. (This is not directed at you, I know you just wanted to help, but more the tutorials on youtube or discord chats ive been in, I hope it doesent come off as offensive, I simply dont understand how people can recommend it. If its on me I would be more than glad to find out)

But for me in its state in davinci resolve fusion its unusable:
1. Its slower than before caching, even when using intense effects like particle simulations, or the cached files get lost and its not using them anymore, that might also be whats happening. (I tried everything I could think of: caching directly the prender, on a brightness contrast after, enabling lock cache, trying different formats like png or jpg, testing it on a different PC with a different SSD, making sure I have enough disk space).It happens so much that there is no point in using it, even though it would be a great feature, because savers and loaders take a lot more time to set up and force you to take organization of the files into your own hands, which can get really messy if you cache files a lot.

In my opinion fast and easy caching is really important in a nondestructive application, because processing all the effects, while allowing for flexibility is taxing for your computer. There is obviously ram caching, but for more intense comps a disk cache with manual control over what is being cached is useful. After effects has precomping and now disk cache also for example, not saying after effects runs smoother than fusion in general, but that helps it a lot. I heard here is also disk cache in the color page, so its definitly an important feature, that should be as good as possible in fusion too, for the same reasons.

2. There is no way to save defaults, because one solution for me has been to use jpg or png instead of raw, to make it run a bit faster atleast. If we would have it as a node, you could save defaults or make presets so you can have different format setups for different cases. Also when enabling png or jpg it says it wont auto update the cache.

3. If it was a node, you could easily place it somewhere else in your nodegraph and it would be way more organized, then having a tiny icon in my opinion. You could access all the format settings and the render button way faster and easier in the inspector, then right clicking and going through menus or typing in the file format everytime manually.

Im wondering, shouldnt cache to disk theoretically be as fast as media ins or loaders atleast, because theoretically thats whats its doing after its rendered: just loading in image sequences? If it was that fast, it would be incredibly useful for quickly caching AI effects, renderer3D, USD or Particles so you can add more effects to them, while having smooth playback. If they can fix the cache to disk how it is right now, that would also be great, but maybe it would be better to redo it and make a new node for it, thats why I requested it. If you have any ideas what might help I would really apreciate it!

Does anyone know how to fix this issue!? we have vertical in the color tab now but whats the use if its still just as small as it was before!? is there a fix for this that i am missing!?

IMG_4500.jpg (74.24 KiB) Viewed 814 times

I dreamt that v20 was released today, but I woke up before I could read about the new features.

I was off by 2 days.

3. If it was a node, you could easily place it somewhere else in your nodegraph and it would be way more organized, then having a tiny icon in my opinion. You could access all the format settings and the render button way faster and easier in the inspector, then right clicking and going through menus or typing in the file format everytime manually.

It's not a complete solution but here you go. It's a node based renderer that will let you save things like frame type, frame ranges and the ability to solo the saver so that you don't have to use the nuclear, "render all savers" button.

Saver with Ranges

Screenshot 2025-04-13 134137.png (100.39 KiB) Viewed 561 times

Code: Select all

{
   Tools = ordered() {
      RangeSaver_1 = Saver {
         CtrlWZoom = false,
         CustomData = {
            Path = {
               Map = {
                  ["Setting:"] = "Macros:\\"
               }
            },
         },
         Inputs = {
            Blend = Input {
               Value = 0,
               Expression = "iif(time < renderFrameIn, 0, iif(time > renderFrameOut, 0, 1))",
            },
            ProcessWhenBlendIs00 = Input { Value = 0, },
            Clip = Input {
               Value = Clip {
                  Length = 0,
                  Saving = true,
                  TrimIn = 0,
                  ExtendFirst = 0,
                  ExtendLast = 0,
                  Loop = 1,
                  AspectMode = 0,
                  Depth = 0,
                  TimeCode = 0,
                  GlobalStart = -2000000000,
                  GlobalEnd = -2000000000
               },
            },
            OutputFormat = Input { Value = FuID { "OpenEXRFormat" }, },
            ["Gamut.SLogVersion"] = Input { Value = FuID { "SLog2" }, },
            renderFrameIn = Input { Value = 10, },
            renderFrameOut = Input { Value = 20, }
         },
         ViewInfo = OperatorInfo {
            Pos = { 5170, 2458.5 },
            Flags = {
               ShowPic = true
            }
         },
         UserControls = ordered() {
            renderFrameIn = {
               INP_Integer = true,
               INP_MinAllowed = 0,
               LINKID_DataType = "Number",
               ICS_ControlPage = "File",
               INPID_InputControl = "ScrewControl",
               LINKS_Name = "Render Frame In",
            },
            renderFrameOut = {
               INP_Integer = true,
               INP_MinAllowed = 0,
               LINKID_DataType = "Number",
               ICS_ControlPage = "File",
               INPID_InputControl = "ScrewControl",
               LINKS_Name = "Render Frame Out",
            },
            SOLO = {
               LINKS_Name = "Solo",
               ICS_ControlPage = "File",
               BTNCS_Execute = "    \n        function check_selected(tool)\n            return tool:GetAttrs('TOOLB_Selected')\n        end\n\n        function check_enabled(tool)\n            return tool:GetAttrs('TOOLB_PassThrough')\n        end\n\n        local comp = fu:GetCurrentComp()\n        local selectedSavers = comp:GetToolList(true, \"Saver\")\n        local allSavers = comp:GetToolList(false, \"Saver\")\n\n        comp:StartUndo(\"Solo Saver\")\n        \n        for _, currentSaver in pairs(allSavers) do\n            if not check_selected(currentSaver) then\n                currentSaver:SetAttrs( { TOOLB_PassThrough = true } )\n            end\n        end\n        \n        for _, sel in pairs(selectedSavers) do\n            if check_enabled(sel) then\n                sel:SetAttrs({ TOOLB_PassThrough = false})\n            end\n        end \n        comp:EndUndo()\n    ",
               LINKID_DataType = "Number",
               INPID_InputControl = "ButtonControl",
               INP_Default = 0,
            },
            RENDER = {
               LINKS_Name = "Render",
               ICS_ControlPage = "File",
               BTNCS_Execute = "rfi = ActiveTool.renderFrameIn[comp.CurrentTime] \n rfo = ActiveTool.renderFrameOut[comp.CurrentTime] \n composition:Render(true, rfi, rfo, 1)",
               LINKID_DataType = "Number",
               INPID_InputControl = "ButtonControl",
               INP_Default = 0,
            }
         }
      }
   },
   ActiveTool = "RangeSaver_1"
}

I made this up a few years ago and it's now my standard rendering process. Throw a Loader right after this and you have a complete caching solution like you're looking for. At some point I'll try and wrap the two into one node so that it works like Nuke or Houdini. Always holding out that somebody at Blackmagic that actually makes stuff in Fusion will get around to one of the most obvious omissions in the entire program. After all, they now have cryptomattes natively so who knows!

Thanks for sending this!
I already made something similar myself, but I like the options your version has. And yes I agree quality of life is something they could definitly work on. I heard now that they updated some of the code, they will go all in, but who knows if that also affects fusion that much.