#Keyboard layout editor professional#

If a keyboard supports multiple physical layout of keys, then the KLE JSON definition will contain the 'default' layout as well as all the layout options. Most LAYOUT_*() macros in QMK use some row,col naming convention so translation into the KLE JSON should be straight-forward. Thus, the mapping that is usually done by a LAYOUT_*() macro in QMK is instead stored in the key objects in the KLE JSON. The mapping from physical layout to switch matrix layout is defined by the top-left legend of the key, using row,col format.

Use legend color #000000 for all legends.

Use key color #cccccc for alphas, #aaaaaa for modifier keys and #777777 for accents (i.e.

Rotated keys are allowed but layout options for rotated keys is not supported.

Horizontal and vertical gaps are allowed (for separation of rows, columns, blockers, etc.).

(KLE's 'Raw data' tab contains JSON with missing ' around property names.) In KLE, save as a JSON file and then copy the contents of the JSON file into the keymap property of the. Unfortunately, copying and pasting the other way does not work. The user can copy the value of the keymap property into the 'Raw data' tab of Keyboard Layout Editor, i.e. json that VIA uses, only the KLE JSON within the keymap property. Keyboard Layout Editor will not load the. The labels property is used to name the layout options. This contains the switch matrix coordinates for each key, and optionally information about layout options. It optionally requires definition of layout options - alternative physical arrangements of keys, such as different bottom rows, split right shift, etc.Įverything inside the keymap property is KLE JSON data, which can be edited using Keyboard Layout Editor. But currently, is, IMHO, someting far to be a milestone or a new Hit, proposing a JKL centerred layout.VIA requires a definition of both the physical arrangement of keys and the mapping of those keys to the switch matrix.

So perhaps we will like to hear a brainstorm about a more efficient and ergonomic layout, and perhaps even BMD maybe be the first interested to mark a milestone and propose a truely eficient keyboard layout for Davinci Resolve.Īfter then, the Davinci Resolve Editor Keyboard will be a milestone and a Revolucion as a new standard for the video edition industry. Perhaps as a legacy keyboard layout on years to come I dont' see any future to the JKL centered keyboard layouts on video editing.

#Keyboard layout editor professional#

This is the future, and the original idea of a computer keyboard as an archetype.īMD should consider how many professional and commited editors are using their own layouts, then examine what those layouts have in common that surpases the default Apple JKL proposal keys for video, which is far from being an ergonomic method.

You don't need to be a pianist, nor a professional videogamer. A non-ergonomical keyboard layout.Īs editor for years I'm working with a custom layout based on a smart WASD keys Shift-CTRL-ALT-CMD keys (like professional videogamers use), which allows you to edit the whole Davinci Resolve project without moving your wristl, using ONLY your LEFT HAND (the right hand is the mouse, or joogwheel), and whithout moving your eyes to the keyboard, as every funcion is in one of your four left hand fingers, as fifth finger strokes SHIFT CTRL+ALT+CMD. And this is the keyboard layout proposal from Black Magic Design.

and I waste a lot of energy/time to do move my arms and whistls around the keyboard. I am using the new Resolve Editor Keyboard for a week, and I'm in the urge of share with all of you that I've the NEED of customize it, as the JKL layout is not ergonomic.