FORUMS: list search recent posts

Resolve Feature Requests (The "Too-Late-for-NAB" edition)

COW Forums : DaVinci Resolve

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
Mel Matsuoka
Resolve Feature Requests (The "Too-Late-for-NAB" edition)
on Apr 1, 2012 at 11:34:27 am

For whatever it's worth, here's a list of feature-requests/gripes about Resolve8 that I've been keeping a log of for the past year. I'm hoping some of these things will find their way into the next major release of Resolve.


• Easier ways to make node-connections:

Node connecting is way too difficult when the node graph is zoomed out, and you have a complex node-chain (an unfortunate drawback of the single-monitor UI convention). There is currently too much precision required to get a node connection to stick, and it sometimes feels like I'm playing "Cut The Rope" because I can never get the connection to stick on the first try.

My suggestion is to implement a node-connection paradigm similar to node-based compositing apps like Shake or Nuke. In Shake, you can easily connect the output of one node to the input of another simply by highlighting the 1st node, then Shift-clicking on the 2nd node. No need to hunt around for the connection point! In cases where a node can take multiple inputs, such as the Parallel node, it would be great if the default action would be to have the input automatically created and connected for you. This would be much more efficient than having to right-click on the target node, selecting "Add One Input", then going back to drag the connection to it from the source node.

Of course, a simpler alternative to all of this would be to just make the node connection targets more "fuzzy" in how precise you need to be in order to make a connection. But being a longtime user of node-based compositing apps, I would still really appreciate the speed and simplicity of having the "shift-click" method implemented in Resolve.

• External Matte frame offset:

This is a must if you're working with media that hasn't been "consolidated" or trimmed before importing into Resolve. If you need to create an external matte of a shot, of which only 20 frames of a 2 minute long source clip is being used, you should be able to bring in a matte of those 20 frames, and be able to line it up to the in point of the edit, without having to render out a 2 minute long matte clip, just so the matte lines up with the portion of the source clip that's actually being used. If you could offset an external matte, or better yet, auto-align the external matte based on matching timecode, it would be a huge workflow timesaver.

• "Master Frame Markers"

This is a marker you could set on a timeline clip to explicitly denote a frame which you'd always want to use as the master reference frame for the grade, without having to manually save stills for it.

When you select clips with a master-frame marker in the timeline, the cursor automatically snaps to that frame, so you don't have to search for it all the time (esp. useful with long clips where a key frame may happen in the middle or end of the clips). This feature would probably have to be in its own explicit timeline "mode" (like "Source" mode) so the cursor-snapping behavior doesn't get annoying for when you just want to navigate the timeline normally.

Master-frame markers could also be used to:

- Generate stills from all existing master-frame marker points
- Set Playhead locations
- Loading frames in Wipe mode
- Display the master frame as the clip's thumbnail, instead of the clips first frame.

• C-Sort/Source mode that actually works.

C-Sort mode is just barely usable in its current state. For it to be a truly useful feature, it must:

- Sort not only on source timecode, but also by reel. Putting the sources from a multi-day shoot into C-sort mode creates a jumbled mess of intermingled sources because the timecodes overlap.

- Play back shots in C-mode. When you toggle the timeline into C-sort mode, you'd expect the timeline to play back in C-mode, and NOT in A-mode, as Resolve8 currently does. The current behavior makes it impossible to play thru a string of shots that appear as consecutive c-sort clips.

• Rendering with source audio

It's kinda nuts that Resolve doesn't do this (though in fairness, Apple Color didn't do it too), but when grading dailies, it's a huge pain in the ass that source-clip audio doesn't get passed through to rendered Quicktime files. I assume that this is a vestigial limitation from Resolve's DPX based roots, but it's a shame that you can't easily use it for outputting one-light passes for RED files that can be directly used by offline editorial.

• Node labels

User defined labels for individual nodes, much like the existing labeling functionality with Stills. This can make complex grade management much easier. For example, It would be great to have a visible label on a node that says "Desat Reds" or "Un-clip highlights", so you can instantly see what a node is doing at that point of the node graph.

• Node grouping

Select a group of nodes and "nest" them in a self-contained, collapsed group, so the node graph doesn't become cluttered and confusing. This way, you can then treat a complex node-tree as a single entity, rather than as a confusing series of individual nodes. This would be similar to how Shake allows you to group a selected portion of the compositing node-tree into a single collapsible node.

Theoretically makes effects/looks "presets" much more manageable. You could just copy a single, collapsed node-group from one shot into another shot, and get an instant look by simply feeding a single input noodle into the node.

Would make fading between grades easier too (make the actual "group node" Post Mixing/Gain param keyframable), and would put an end to my Baselight envy :)

• Qualifiers

More edge blur intensity!

Feather/Softness "bias". Give more control over which side of the matte gets more or less blur/feathering. I thought Shrink would be able to do this well, but Shrink seems to be doing the same kind of operation that is found in "Matte Choker" type filters in After Effects. This often leads to clumpy, "electronic" looking qualifications, made especially worse by the fact that you can't infinitely blur qualifiers enough to offset the harshness of the Shrink operation.

• Add Grain/Noise

While I disagree with others who feel that Resolve needs a full blown plugin architecture, I definitely think it at least needs some way of adding film grain or noise to grades. Clients request this ALL the time during grading sessions, and it's a bummer that I always have to tell them that we have to wait until I bring the rendered grades back into FCP before adding grain to shots.

• Optical blurs/defocusing

This is another one of those things that clients ALWAYS ask for. Gaussian blurs/defocusing is so passé. It would be a huge win if we could apply realistic optical defocusing to shots, especially in a qualifier or Window.

• Re-use/linking tracking data

It's wasted effort to have to re-track an object more than once. If you've already generated tracking data for a CPW, for example, that same tracking data should be made available for use by the LPW, PPW or PCW within the same node.

It would be even better if you could pipe "live" tracking data from one node into another node (much like using Expressions in AE, Nuke or Shake. Copying and pasting from node-to-node is an acceptable workaround, but imagine how much more efficient it would be if you could live-link data like this throughout the entire node-graph? Perhaps via a "Track Data Input/Output" node connector?

• Rendering secondaries in handles

I griped about this problem before in detail on the Cow (, but rendering with handles in Resolve is all but useless, in my opinion, because any secondary correction you make on a clip (qualifier, tracked window, etc) will disappear or "pop" to a defaulted state as soon as you start rendering into the handles.

At the very least, Windows should just keep the last known track point when rendering through a handle, or even better, should auto-interpolate the general motion that it was currently making (much like Shake's awesome "KeepSlope" animation curve option)

Don't re-enable manually disabled nodes when toggling grades on & off

• Labeled still pages

Or maybe folders within still pages to organize scenes, look etc.

• Playback/loop timeline range

Set specific i/o points on timeline and play/loop-thru only the shots within that range (I know you can do this on the Resolve control-panel, but it's such a basic need that it's a tad bit annoying that it's unavailable to those unwilling to spend $30,000 on the Resolve panel)

• Auto-conform/import RED offline .mov transcodes to original R3D files during EDL/XML import stage

IOW, integrate "R3D collecting" capability into the conform/media pool, so you don't have to load in unnecessary R3D files into the mediapool in order to conform an offline/proxy RED sequence

• "Render modified shots" Option

Have an option in the Render page to only render shots that have had their grades modified since the last time the Session was rendered. This saves you from having to manually re-render selected shots individually (esp. useful in FCP XML roundtrip renders, since you apparently cannot queue selected clips in the Batch Render queue when in this output mode)

• More extensive/configurable mappings for 3rd party control surfaces

There are a ton of options that are hard-mapped on my EclipseCX panel that I dont want/need. User-configuration of mappings is critical)


• Dynamically Disabling REDRocket card

There needs to be a way to selectively disable the REDrocket card so that you can fall back to the software-based debayer, when you need to access non-Rocket-enabled parameters like DRX.

• Option/shortcut to temporarily disable Window outline overlay on playback

Maybe shift+spacebar, and have it re-enabled when you hit stop. This would be great if you prefer to work with overlays turned on, but you don't want to have to keep toggling it on/off for playback

• Index/Table of Contents in the PDF Manual (!!!)

• "Difference" mode as a Wipe Type

Would be useful for eyematching repo's to offline references

• Remember the last-selected shot when opening up projects

On big film projects, it'd be nice to pickup where you last left off, without having to remember/search for it manually

• DV resolution support

As much as I hate DV, clients ALWAYS want you to use old DV footage for their documentaries

• Faster response of the Jog wheel on the JLCooper EclipseCX panel

It takes way too many revolutions of the Jog wheel to move a simple split-screen across the frame

• Auto-delete all grade Versions which are not currently active

• BIGGER Still-store thumbnails (for the love of God, please!!!!)

• Remove Full pathname from "Source File Name" burn-in option (I only want to burn in the actual source filename, not the fully qualified path)

Return to posts index

Peter Chamberlain
Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
on Apr 1, 2012 at 1:00:09 pm

Thank you for the extensive and clearly detailed list. We appreciate your support and will continue to add to Resolves many features based on all the feedback we receive. I hope to see you all at NAB.
Thanks again.

Return to posts index

Boris Tivchev
Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
on Apr 1, 2012 at 2:01:55 pm

Could I just add... The ability to choose and set a default version would be of huge help when loading a new XML into the project.


Return to posts index

Gabriele Turchi
Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
on Apr 1, 2012 at 6:54:38 pm

Peter don't forget the huge list i sent you months ago ... :)
That was ahead of time for V9 release ... :)

Anyway , now that we are talking ,
i am not going to re-write Huge lists but quick priorities (the ones while working i miss the most often )

-OFX plugin Support (to implement maaaany features from 3rd party without stressing you about everything guys..)

-NEW GUI that use a second Monitor to accommodate (eventually( node tree and still store (so having space for bigger Curves and bigger Dynamics tab (or tabs that expand full screen with a click of a button (like adobe product (pressing ~ to expand and collapse))

-Better quality speed changes (so i can actually render out the XML conform)

-Skin Soften tool (mist is old ) and a nice soften tool can resolve quite few problems in terms of color-skin work

-color Temperature and Tint controls (it's so easy when i use it the one in red SDK tab)

-Improved Keyer : better key refine tools (is a bit incredible how SMOKE can pull much cleaner color qualification )

-Save dynamics on Stills (based on TC values (so if the TC does not match (because apply the still color to a different shot , the dynamics gets discarded )

-R3D SDK settings version independent (i still vote for this one )

Off course i have many more , as anybody else , but this ones are the ones that i care the most .

Hope someone at BMD will agree on some of those .

thanks for listening


Davinci Resolve Control Surface
Cubix desktop 4
2 Red Rockets
HP Dreamcolor
Panasonic 58PF Plasma

Return to posts index

Dmitry Kitsov
Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
on Apr 1, 2012 at 7:58:25 pm

Agreed on many of your points. Would also like the ability to grab stills for a group of selected clips on a timeline. Right now we either have an ability to grab one or to grab all.

Return to posts index

Knut Jansohn
Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
on Apr 1, 2012 at 9:57:04 pm

Hi there,

what i miss most:

  • Please let me do everthing on the gradingmonitor, what now is to do on the viewer. Simply switching the cursor between grading and GUI like in baselight. This will also give more space for gui

  • synchronice gui/third party control devices

  • Configurable window-setting for GUI. And storable window-cofiguration like in baseligth and make that mapable to keybord

  • Something like a dkey. Just sampling desired colors from an area defined with the cursor and make unlimeted qualified spaces in the rgb-cube

  • enhanced keyframe handling: edit left/right, copy keyframes, show all keyframes for the tracker

  • direct select of node with a keystroke, direct select of node-output to the gradingmonitor selectable over menue so that it's mapable

  • less limited powerwindows: let me modify circle by adding curvpoints. Ad gradient / edge shape. 'Unlimeted' shapes in a node, say two circles...and let them merge with boolean operation. And please let me control the shapes with the spheres. Another great thing is: let me create two shapes and then generate a gradient between inner an outer shape for easy creating spots.

  • direct accsess to the clip rawsource. Rightclick and selecting from the contextmenue is not funny for often needed actions

  • Let me ad any video and key from other tracks to nodetree input
    (like hdr)

  • Markers! Please let me set markers in the timeline which i can stepp throu with ease

  • Howerver i like the resolve pretty much :)
    It is really fast and affordable and seems to be developed furthermore.
    Thanks BM!

    All the best.


    Return to posts index

    Robbie Carman
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 12:00:48 am

    I did a list a week or two ago that Mel (the OP) commented on. I have a about 4 more versions of it.

    In my opinion software can't be everything to everyone. Peter, Rohit and the rest of the of the team have done an AMAZING job. Truly I don't know when these guys have down time. Can the product improve - yes and I know this team is doing that every day.

    Robbie Carman
    Colorist and Author
    Check out my new Books:
    Video Made on a Mac
    Apple Pro Training Series DVDSP
    From Still To Motion
    An Editors Guide To Adobe Premiere Pro


    Return to posts index

    Mike Most
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 12:46:41 am

    I don't disagree with your sentiments, but you're basically telling DaVinci to make Resolve into Baselight (8 out of the 9 things you mentioned are descriptions of specific Baselight features).That's not sensible and it's not a goal. Every manufacturer has a different approach to their system and different ideas as to how to present the functions that users want. Baselight is Baselight, Resolve is Resolve. If you want Baselight, well, then use Baselight. But just as I don't expect Blackmagic to turn Resolve into an Avid, you probably shouldn't expect or even suggest that they should turn it into a Baselight. I think you can safely assume that Resolve's developers are very, very familiar with and aware of what Filmlight does. But they have their own ideas as well. That's what makes competition, and that's what produces better products by all manufacturers.

    While I agree that better keyers and matte cleanup tools would be nice, a number of the things you state are already in the product, provided you use the full DaVinci panel set. That is also the case with Baselight, as certain functions are only available from the Blackboard. I've made my own suggestions to Blackmagic as well (I'd REALLY like to have the Offset controls mapped to the fourth trackball on the new Tangent Element panels, as they are on the DaVinci panels.........), but one needs to let go of the notion that one product should be exactly like another. It shouldn't, and it won't.

    Return to posts index

    Knut Jansohn
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 10:36:46 am

    Sorry if it received that way.
    I didn't intend to ask turning resolve into baselight!
    The curvetool didn't do that and other new features will not too, altough they possibly similar present in baselight (or other applications). Resolve has its advatages beside!
    These features are usefull for me and I would be glad to see them similar in resolve.
    Obviously the most ergonomic operating is provided by the first party boards.
    But regardless for low budget it would be helpfull if more functions could be assigned to third party devices.

    Return to posts index

    Mike Most
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 3:28:26 pm

    Even with the full control surface, Resolve is very appropriate for "low budget." It costs less than 1/3 what a base Baselight system does, and 1/10 of what a Pablo does. Unless you're really talking about "no budget," in which case you shouldn't be comparing it to things like Baselight that cost over 10 times more (if you're not buying the Resolve control surface).

    I really wonder if the guys at Blackmagic get a bit frustrated at how quickly they've made so many people forget how much this stuff cost only 12 months ago, and the rather unreasonable level of demands and complaints that's engendered....

    Return to posts index

    Knut Jansohn
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 4:34:38 pm

    Maybe my style is insufficient. If so, I have to appologize.

    Resolve gives a sensational way for the price. That is beyond all question.

    However BM develops it further on. And customers tell what they would like to see. I don't see these wishes as unreasonable demands.
    And even if we are 'no budget-customers' with say a wave and a Mac - what is wrong with thinking about more ergonomics etc.?

    And don't forget that BM itselfe declaires Resolve as "The world's most advanced color correction solution for Mac, Windows and Linux!". There isn't an addendum like 'for its price'

    Return to posts index

    Mike Most
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 4:59:03 pm

    Well, can you name one other color grading product that's available on the Mac, Windows, and Linux other than Speedgrade? And I would contend that in that context, Blackmagic's statement is generally true.....

    Return to posts index

    Knut Jansohn
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 5:08:38 pm


    You are kidding, right?

    I don't have the impression that they mean it along this line.

    Return to posts index

    Gustavo Bermudas
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 6:03:28 pm

    [Mike Most] "I really wonder if the guys at Blackmagic get a bit frustrated at how quickly they've made so many people forget how much this stuff cost only 12 months ago, and the rather unreasonable level of demands and complaints that's engendered...."

    Well, they certainly are not victims when you introduce a product such as Resolve that used to cost around $250K as a free one. They obviously've had to see this coming, we all did.

    Return to posts index

    Rohit Gupta
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 8:49:46 am

    "• Remove Full pathname from "Source File Name" burn-in option (I only want to burn in the actual source filename, not the fully qualified path)"

    Why don't use the Source Clip Name? It will get the source filename, not the fully qualified path.

    Return to posts index

    stig olsen
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 10:10:31 am

    For power grades, I would like to have a list of names instead of thumbnails. Its getting very messy with all that thumbnails. Maybe it is a good thing, but there should be an option I think.

    Return to posts index

    Paul Jay
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 10:21:29 am

    While we're on it:

    Still RAW support ( Color Grading Stills with a Control Surface is so much nicer than Lightroom )

    Lets make Resolve a Finishing tool. More editing functionality.
    Resolve has the potential to be the next Smoke and more.....

    Return to posts index

    Ernest Ratliff
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 2:25:09 pm

    All I want is AVC-Intra support.

    Return to posts index

    Mel Matsuoka
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 2, 2012 at 9:10:28 pm

    Please, no!

    The reason why Resolve is so awesome is because it's not trying to be a finishing tool.

    Smoke already exists, and is the best in breed for what it's intended focus is. I'd rather purchase a tool that was designed and optimized from the ground up for a specific task, rather than having an amalgam of different "cool things" that don't do any one thing particularly well (i.e Final Cut Pro and 3rd party plugins) If you need to grade stills, Lightroom exists and excels for exactly that focus, and is better than Resolve could ever reasonably hope to be, considering that it's designed for realtime film/video grading.

    I think a more reasonable request would be for Adobe to support control-surfaces within Lightroom. Then again, I have a hard time seeing how this would work, considering how deep and precise Lightroom's controls are compared to any video grading app. Color correcting stills is a different type of workflow that I imagine would be very frustrating to perform using a control surface.

    I agree it would certainly be convenient to be able to import camera Raw stills into Resolve. But it would also be "convenient" for it to load in native projectfiles from Apple Motion like Final Cut does. I just don't think it's particularly reasonable for Resolve to dedicate any sort of effort to try and make it happen, considering how esoteric such workflows are.

    Of course, I could be proven wrong about all this in 2 weeks at NAB :)

    Return to posts index

    michael stirling
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 3, 2012 at 12:37:56 pm

    The nightmare reconform I am embarking on today (mention in another thread) would be to have grade versions ripple through from other cuts

    I could see how this wouldn't help in all circumstances (ie. when you are versioning an ad for example) so suggest this:

    Right click on a Session in the timeline management window/gives option to reconform this session/ xml loader dialog - loads a new session with grading decisions intact.

    Oh, and render sound of course :)


    Return to posts index

    Neil Sadwelkar
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 3, 2012 at 6:47:55 pm

    I'd like to propose...

    Support for titles and other objects with Alpha and which can be linked to an XML. Imagine, you can master out a graded programme with subtitles, and even opening titles, lower thirds and other supers.

    While we are at it, some rudimentary compositing, even simple DVE moves inherited from an XML would do nicely too.

    And, pass-through for audio embedded in a video clip. Great for dailies.

    DPX standard log to Lin conversion like Apple Color can do.

    Neil Sadwelkar
    twitter: fcpguru
    FCP Editor, Edit systems consultant
    Mumbai India

    Return to posts index

    Nichole Kizer
    Re: Resolve Feature Requests (The "Too-Late-for-NAB" edition)
    on Apr 3, 2012 at 10:41:10 pm

    Might I also add...
  • The capability to see what Event #'s are queued in the "Render Queue".

  • Ability to choose Event Numbers BEFORE filename in all rendering options.

  • To control the .R3D debayer quality in the Render window (in addition to the config. panel).

  • The ability to TYPE in TimeCode to locate/slip certain clips in the Timeline and Conform windows.

  • Ability to acess the "Gallery" in the Color Panel for easier/faster finding and applying of grades.

  • ------------------------------------------------
    Nichole Kizer
    Colorist, Motion Designer
    631 north 1st avenue suite 201
    phoenix, arizona 85003
    602-253-2630 office | 602-254-3431 fax

    Return to posts index

    << PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
    © 2018 All Rights Reserved