+1 for customizing. It may make it back on my desk if this was the case.
dimsum wrote:I also have a ShuttleXpress, a Stream Deck, and a mouse with customisable buttons and I've been investing a lot of time learning all the functions of the speed editor, and right now, besides the jog wheel, it actually feels like a downgrade for multi-track editing and splitting tracks compared to my old setup.
Similar here, but a programmable keyboard instead of SD (yeah, more stuff to remember). Only thing I really used/liked on the Speed Editor was the wheel... otherwise it was a big waste of space (especially with the way the USB cable sticks out the back).
I get that maybe it's meant to replace a regular keyboard for the Cut page, and maybe that's useful to someone, sometimes, but I just don't grok it. I do admit I was also instantly turned off by the mushy key switches with no feedback (and yes they can apparently be replaced, but that's more moneys on something with questionable usability to begin with).
jamedia wrote:It would make sense if the 2nd and 3rd row of camera buttons could be re-configured.
Heck, it would make sense if one could at least use the camera buttons in Edit mode. But no, they only work in Cut, with the specific way multicam tracks are set up there. Which I tried but don't use (the "old way" multicam in Edit is weird enough as it is). Never mind that the numbers row or keypad on a regular keyboard isn't exactly difficult to operate (or remember) either.
And yeah, why are the keys in reverse order to camera arrangement on multiview? They keycaps would be easy to re-arrange, but that's pointless w/out re-programming.
jamedia wrote:(at the same time the put in the control to turn off the bluetooth.)
Or how about an on/off switch? I unplugged the thing to put it away, but some of the lights were still on from when DR was active, and they stayed on until (apparently) the battery drained out.
ctrevatt wrote:Heck, if you had an SDK for the panel and those controls, I'd gladly give the above a shot.
Heck yea. But not holding breath here... seems all very hush-hush. I've had no luck even finding info on hacking the input protocols, never mind anything official. Even DR's own documented "TCP transport" protocol doesn't work right (
viewtopic.php?f=12&t=141436).
-Max