Page 1 of 1

Blackmagic Keyboard bugs / Feature req

PostPosted: Mon Nov 11, 2019 11:32 pm
by PRESSRESET
Hi Resolve team/Forum,

Long time paying Resolve user and own/use tons of BMD hardware. Started on 12, and have been using it for end to end since 14. I've been pushing people towards Resolve as end to end since 15 beta, and the collab features just make it out of this world. My team moved to it end to end after 15 stable came out.

Fantastic. Great job. Keep it up.

I recently got the keyboard. It is also a fantastic piece of kit... with some caveats still, but awesome nonetheless.

16 update is great, but there are still a few things lacking, and the keyboard integration is still surface level. It needs to be deeper... badly.

Below are some bugs and some features that are kinda missing, and some deep integrations for the keyboard.

BUG SQUASH:

KEYBOARD BUG:
When trimming between the wheel/mouse/keyboard (because it doesn't have enough features yet to keyboard only) the trim tool will open, and spinning the wheel can sometimes cause the trim editor to just stay open and not close until you smash the trim editor key, or click outside.

KEYBOARD BUG:
On machines where NUMLOCK isn't engaged by default in BIOS (or on machines running Win10 it can sometimes just be disabled at boot no matter what, ignoring BIOS), NUMLOCK becomes disengaged hit/miss. There is no NUMLOCK on the keyboard to re-engage NUMLOCK... the way around this right now is to open the on screen keyboard, open the options, click to enable the number pad, then enable NUMLOCK.

KEYBOARD BUG:
Dynamic zooming when in JOG/SCRL on the Source Tape is wonky. When I am in SCRL, I expect to see the full waveform, because I intend to jump around. When I am in JOG, I expect to see the zoomed in waveform. The dynamic zooming thing is wonky and jarring, and half the time it doesn't disengage when I spin faster either or it will snap in and out. It makes finding stuff within the source tape more tedious than need be. This again, could be an option within Prefs (Dynamic Source Tape Zooming) or something like that, where it's manual on mode engagement, or it's fully dynamic on wheel speed.

FEATURES:

Media Management Feature: Media Management Right Click Menu
Capture.JPG
Why can't I right click menu here in the media pool?
Capture.JPG (13.21 KiB) Viewed 1586 times

As referenced in the photo above. It has always driven us COMPLETELY NUTS that you can't right click in the main window, not just in the tree to get the "Create Folder" etc right click menu. This is expected behavior in other file managers, and as heavy users of the Media Manager it drives me up the wall. I have to hunt the location inside the tree to the left, then right click, then select "Create Folder" or whatever other function I wish to complete.

Media Management Feature: Merging folders in Clone Tool:
Sometimes we receive cards or folders and have to offload them onto the network storage, not directly with the clone tool. This means that we need to pull the files from the folders across, which works great fine and dandy. However, the issue is that if the folder is updated, there is no way to merge the folder inside the clone. If you attempt to re-clone, it just Errors and all the files inside the cloned folder vaporize. If it detected that the hashes were the same, then checked if the folder had new data in it, why not ask us if we want to merge the folder? This is again, something that has happened repeatedly, where we Clone, then someone forgets you can't merge and it breaks huge parts of the project. Then we have to go back and re-link / Re-Clone an entire folder... which requires everyone to completely quit Resolve (and sometimes reboot) because the files and folders are locked.

Keyboard Features:

Feature: Whatever speed you need
    Please make the speed adjustable when in SHTL, and when SHTL is first moved on switching to SHTL then engaging PLAY/REV snap to 1x play speed unless we come to full stop, then add more twist. (Could be check box in Prefs "1x Playback on shuttle initiation" or something)

Feature: Remap EVERYTHING
    Remapping inside the keyboard for the "Resolve only" keys please please?

Feature: Add deeper key mods
    Allow for CMD or right shift as modifier for the left keypad, this way they can dual purpose, and (if you enable remapping) I can map them to jump between windows within the media pool.

Feature: Make CUT... CUT/BLADE
    CUT key on left keypad doesn't add a BLADE? It just removes the transition? Could be single tap+hold? (Could be checkbox in Prefs "CUT Key is BLADES")

Feature: TOP/TAIL Left Pad Enhancement
    If CUT is also BLADE, this means that IN/OUT white keys could be mapped to CUT HEAD/TAIL to allow JKL TOP/TAIL style trimming from the left keys. So, if I HOLD CUT then hit IN, it performs a BLADE+HEAD. That would make the left side much more feature rich and remove a huge amount of movement back to main keyboard. Otherwise, I am always forced to spin the wheel for the trim which takes longer than smashing a key sequence. Could also be double tap IN/OUT?

Feature: Scroll wheel everywhere
    Spin the wheel to scroll/move within the media management added? It's a giant scroll wheel. I want to SCROLL everywhere and NEVER touch my mouse again.

Feature: Positioning/Zooming/Rotating? SCROLL IT
    It would be awesome if, when anytime I needed to rotate/zoom/position anything like titles, images, mattes, etc all I had to do was smash a modifier key and spin the wheel for L/R movement on JOG and UP/DN on SCRL. THE KEYBOARD IS AWESOME I DON'T WANT TO TOUCH THE MOUSE AGAIN. (Please snap back to previously selected mode JOG/SCRL when keys released.)

Feature: Separate top row
    Separate top row number keys vs entry pad (if this is possible in hardware). This would allow multiple mapping types. So, say I want the NUMPAD to be just a num pad, but the top row, I want to map to switch tabs, 1 2 3 4 5 without modifier.

Feature: Wheel Track Volumes
    Track volume adjustment with the wheel on Edit page/Fairlight. I know you guys have the Fairlight stuff, and that's great, but for some usage, you only need max 4/6 channels to hammer out and let someone else deal with the audio. Being able to adjust track volumes by holding a modifier

Feature: Auto Ripple Mode
    Cut page is great for chopping things down from source tape, but when I jump from CUT PAGE to EDIT PAGE, I will go and spin the wheel for a TRIM IN/OUT it doesn't auto ripple and I am left with a gap. That's why I have the wheel? I know I have to jump into TRIM mode, but this is an extra step and I have to jump in/out of trim mode to perform the ripple. Maybe single tap+hold to engage? (Could be additional option option in Prefs)

There is a lot more I'd like to see, but I'll limit this one to these things as I could keep going on. There are also some more bugs I have found, but I did not write them down as I was hammering out edits.

Thanks again for rockin. Resolve just keeps getting better and better.

Re: Blackmagic Keyboard bugs / Feature req

PostPosted: Wed Nov 13, 2019 11:46 am
by studio1492
+1 to all you said. You can't describe it better.

The keyboard has a great potential, but currently its use is highly limited to specific functions that I will rarelly/never use, the choosed layout is unergonomic with the natural shape of the hands (specially the right hand area when placed over the jogwheel, the buttons should be adapted to the fingers positions). The hardware is mastodontic when placed on a populated desktop, and overall, still not customizable as one would expect.

Re: Blackmagic Keyboard bugs / Feature req

PostPosted: Thu Nov 14, 2019 7:27 pm
by PRESSRESET
studio1492 wrote:+1 to all you said. You can't describe it better.

The keyboard has a great potential, but currently its use is highly limited to specific functions that I will rarelly/never use, the choosed layout is unergonomic with the natural shape of the hands (specially the right hand area when placed over the jogwheel, the buttons should be adapted to the fingers positions). The hardware is mastodontic when placed on a populated desktop, and overall, still not customizable as one would expect.


I can see where they are going with it. IMHO, just needs deeper integrations. I am sure it will come, I just hope it starts to come sooner than later. I've been using it every day for over a week and still getting to grips with it. I can see clearly that they are fans of the Sony BKE tape editor keyboards. That's what it reminds me of. I wish they used Topre switches. There is a slight high pitched resonation which is generated by typing in the main keyboard area. Which, can be a little annoying hearing that ring all the time. It's a v1 product, and it feels like they released it a bit early vs the software to get more feedback on how exactly we want to see it integrated. It's also clearly made for truck/broadcast/news/syndicate editors/News Cutter/Edius converts... that end of the market. The things I am personally familiar with... not people switching from FCPX/PP who work on docs or cut internet shorts.

Overall, so far I am happy with it as a piece of hardware. I like the key layout, the actual typing feels great sans that ringing noise, the size of the "nubs" on the "home keys" F and J (sometimes because I can't feel them I start typing in the wrong spot with my right hand), and the placement of the arrow keys. My only real "aw man" wish is transport controls above the knob like on a BKE deck.

Re: Blackmagic Keyboard bugs / Feature req

PostPosted: Sun Feb 02, 2020 7:37 pm
by Dave Romero
I would like to add my vote to the feature request list here. I’m a long time Resolve Studio (MAC) user with extensive investment in BMD hardware. I’ve been using the editors keyboard for about a month and see huge unrealized potential for use from within the edit page.

BMD- keep up the good work!

Re: Blackmagic Keyboard bugs / Feature req

PostPosted: Wed Mar 11, 2020 9:02 pm
by SpitPics
+1 from me too!

Have you noticed any improvements after the 16.2 update?

Re: Blackmagic Keyboard bugs / Feature req

PostPosted: Wed Nov 24, 2021 1:50 am
by Paul Steinberg
Please fix the NUMLOCK bug