Blackmagic Forum

In v14 I used F16, F17, F18 and F19 on my OSX keyboard to switch between the 4 DR pages.
Quick and easy as those keys are unused in Sierra.

Now in V15b2 I get an error as DR interprets F18 and F19 as A and B which are already used.

The keyboard viewer is showing that the OS is interpreting the key presses correctly.

No combination of FN, SHIFT, CONTROL, OPTION or COMMAND keys will get me F18 or F19

Its a small thing but annoying.

As a workaround, you can override Resolve's assignments using OS X's Keyboard Preference Pane and assigning new bindings in the Shortcuts tab, as I have for various Fairlight functionality.

For some reason this issue only affects F17, F18 and F19.
F13, F14, F15, F16 function as expected and don't require this workaround.

Thanks for that tip.

Unfortunately I still get A and B when I press F18 and F19.

Resolve is misinterpreting the key presses.

I am using the keyboard viewer and it shows the F keys responding properly.

Furthermore I can use the keyboard viewer to issue keystrokes and DR 15 still sees and B instead of F18 and F19

Hi Jack,

Reynaud's explanation works for me. You need to type the EXACT MENU NAME in the OSX Keyboard mapping.
It's not Resolve creating the issue.... it's OSX.

Peter, if OSX is the problem why does it work correctly when I go back to V14?

This problem in V15 affects the F17, F18 and F19 keys.

It does not matter which menu shortcut I try to set, these keys show as @, A and B.

Can anyone with the large wired Mac keyboard with these F keys please try to verify this bug.

Jack Swart wrote:Peter, if OSX is the problem why does it work correctly when I go back to V14?

This problem in V15 affects the F17, F18 and F19 keys.

It does not matter which menu shortcut I try to set, these keys show as @, A and B.

Can anyone with the large wired Mac keyboard with these F keys please try to verify this bug.

Yes, I had the same issue with the large wired Mac keyboard until I followed Reynaud's fix. Now it works as expected.

Peter, while that works I found a better way.

Export the keyboard shortcuts as a text file.

Edit the commands as you need them, ensuring there are no duplicates.

Re import as a new keyboard shortcut file.

Really simple...and it works.

Jack Swart wrote:Peter, while that works I found a better way.

Export the keyboard shortcuts as a text file.

Edit the commands as you need them, ensuring there are no duplicates.

Re import as a new keyboard shortcut file.

Really simple...and it works.

Hey Jack, this is from forever ago, but in Resolve 18 this is still happening. F19 can not be assigned as Resolve interprets it as "B". I tried your method and unfortunately it still interprets F19 as B, even though F19 does show as assigned in the keyboard shortcuts manager. Bummer!! Does this method still work for you?