One of my top feature requests for Resolve would have to be a visual keyboard mapping tool. The custom keyboard is such a personal thing to many editors that easy keyboard mapping is one of the first things many look for when switching to a new NLE. To find the right thing you’re looking for is something a visual keyboard mapper would solve.
A lot of mapping a new NLE keyboard is trial and error. This is a minor thing sure but it’s often these simple, unexpected behaviors that happen when trying to transition from one NLE to another that offers up a roadblock. Yes that would be an argument for just sticking with the default Resolve mapping but I am convinced that it can be better. The key in this case would of course be to begin with the Media Composer preset but then you have to search through the commands again to get some of the key Resolve features back like its unique Dynamic Trimming operations as that mode goes unmapped in the Media Composer preset that is included. “Go to” isn’t recognized in a keyboard search since go to appears under Playback menu and the actual go to IN and OUT command is only searchable by IN or OUT and not go to when you’re in the Keyboard Mapping tool. That’s great until you go to the keyboard mapping tool and type “go to” in an effort to change it. Be default Q is mapped to toggle between the Source/Timelne Viewer and W is mapped to Dynamic Trimming mode. If you begin with a Resolve mapping preset and want to go Avid-like the Q and W will be changed. It’s nice that you can change keyboard shortcuts on both a global level throughout the whole program and on a local level per page.Īnother example is the Go To command, as in Go To IN or Go To OUT … something you do hundreds or thousands of times in an edit. local mapping that is possible between the different Resolve pages. It probably has something to do with the GLOBAL vs. My first go-to mapping on a new NLE is to map the timeline zoom in to F12 and zoom out to F11. Putting aside how long it takes to sometimes load the keyboard mapping (Pro Tip: don’t close the Resolve > Preferences > User on the Keyboard Mapping panel as you might think Resolve has crashed next time you open the preferences) I just can’t get some commands to map. As I have tried to do this I’ve found the Resolve keyboard mapping tool to be … not very good.
Resolve doesn’t reinvent the editing wheel like Final Cut Pro X did so it should work. Resolve’s keyboard mapping isn’t greatĭigging into this paid edit job on Resolve makes me want to create my own custom keyboard mapping in keeping with the Keyboard Manifesto and really tailoring the keyboard to how I like to work. It tried some arrows in this one and placed some submenus at the bottom.
My apologies if this one seems a bit sloppier than those in the past as I pounded this one out rather quickly. I’ve tried to expand the submenus of most columns but there are a few that aren’t really relevant to creative editorial that I did not include. This cheatsheet focuses on the creative editorial tools so there are some menus missing, like the Fusion and Fairlight menus. Hopefully seeing them right in front of you can help learn them. Resolve has a lot of keyboard shortcuts and unlike Adobe Premiere Pro they aren’t buried deep in the keyboard settings, but rather right there in the menus. I’ve always found that creating these little cheatsheets and printing them out on a piece of paper is my favorite way of learning a new NLE. New submenus and commands have been added to existing menus and new menus themselves have been added as well.
With each new update to Resolve the menus have changed. And since I’m doing an webinar in July on craft editing in Resolve this is a timely post! This cheatsheet is focused on the Resolve editorial menus And why keep that to myself? Just as I did with Resolve 12 and Resolve 14 I’m posting it here for free. With that I thought it was time to once again update my handy, printable, 8.5 x 11 keyboard cheatsheet. Today is beginning an actual, real deal, paying client edit in #Resolve 15.