JKL keys seem to switch into a different mode in Color page

Several times my JKL shuttle has switched to something like a single frame mode while in the color page. Pressing J or L moves the playhead one frame rather than playing. Anyone know what I might have hit to cause this? Is it a bug or a feature I'm not understanding?


Sent from my iPhone using Tapatalk

a bug in b8, color page only

Rohit mentioned on LGG that's it's already sorted, but the fix needs to wait for the next release

[Rohit Gupta]

This is fixed in the GM released today!

Same or similar bug somehow re-appeared in the latest 15.1.0.024 release (studio mac). Initial jkl seems fine, successive switch to single frame and then sometimes again back to full play. Feels like a timing thing.
Its worse if you send jkl signals from a button box or controller.

I'm not seeing any weirdness in 15.1 on Windows 10.

Neither here on a Mac, where it existed too.

Maybe its typical to my system. Will play a bit further tomorrow , install on some other systems and see if i can pin it down to anything specific.
Maybe its just me. Entirely possible of course .

Did some more testing and is is limited to one of my 3 workstations and seems only to be affecting keyboard presses generated by controllermate. Using the actual keyboard has no issues. I had to adjust the timing/length of the single keypress (extend) for it to work again.
It only happened (repeatable) on the latest release so i guess some timings/process priorities have slightly changed in favor of resolve possibly affecting mapping software etc. So far have not seen any other effects so fingers crossed. I actualy dont use any keyboard presses besides jkl in any of my programming (luckily i guess) so lets see if nothing else pops up ....

edit : theory based on earlier issues and diff between workstations and why i only get it on 1 setup is that it may be related to the BM thunderbolt mini monitor i am using for my hero display , which has proven to introduce some timing/delay/reponse issues with peripherals (usb devices, other thunderbolt devices etc) that changed over the resolve releases from 12.5 to 15 . Anyway, just ignore me (unless you have similar issue of course)

I had this issue in 15.1 with our X-Keys 68 Jog/Shuttle but changed keyboard assignments to Avid, then back to Lightworks with a re-boot between then all fine.

AHAAAA so i am NOT crazy after all

Tnx

p.s. tried your trick with the avid assignment and back but did not work for me. I had to increase timing slightly.

Ps i also had it on my contour shuttle 2 , which has its own driver.
Had to change the jkl from single pulse action to press and hold mode to fix it. So its definately timing related and not limited to controllermate .
But it does seem aparantly very specific to the system itself as my macbook pro with exact same os, resolve version , same physical controllers,etc etc has no issues. So maybe its faster systems that have issues and slower not.... who knows. At least be aware if you notice anything like this.

Not sure if this is the same thing you guys are running into, but there is a bug where if you create a power window and then move it with your mouse. The JKL keys then switch to single frame mode until you switch to a different panel in the color page (ex. qualifiers) This is not a problem if you use the spacebar to initiate playback.

This bug is tested and present in 15.1 on windows

(RCP-926-72150)

Sound diffrent but as it involves the same jkl keys could be related in some deep programmatical way only BM can determine. Not sure what is so special on the jkl but over the history of betas etc a few times issues with these popped up and whee squashed.
But am sure it will be deald with at some point. No showstoppers but hindrence nevertheless

Same on a Mac.

I had this issue in 15.1 with our X-Keys 68 Jog/Shuttle but changed keyboard assignments to Avid, then back to Lightworks with a re-boot between then all fine.

On a different note, Craig, could you please share your configuration key positions in X-keys 68 jog/shuttle? I can't seem to find the old thread where you explained the logic of your configuration. Also, I am not sure, whether you posted on this forum or some other forum.

Thanks in advance.

I have not used the XK-68 in awhile, but here's a link to a diagram and the .cmate file I created last year when I was using it:

https://spaces.hightail.com/space/A2y8cTmQCr

This was for a 27" 2560x1440 display under Mac OS, and it worked fine in that system. Try as I might, I could never get the jog/shuttle knob to work in Resolve, but Universal's Skipper Martin cracked the formula on that and has a video on the subject:

...could you please share your configuration key positions in X-keys 68 jog/shuttle? I can't seem to find the old thread where you explained the logic of your configuration...

My X-keys is mainly set up for Lightworks with all popular transport controls configured for Resolve too so both popular Edit/Grade timeline transport controls use the same buttons and Jog/Shuttle wheel actions.

I have two button rows (in Blue - not shown) for Resolve specific control. You'll need to download an unzip the attachment, then extract and load the X-keys file and the DaVinci Keyboard shortcuts file. You can rearrange and modify to your delight. X-Keys ability to map 'mouse clicks' to specific backlit buttons makes it a very powerful tool. There is a video of the Jog/Shuttle in action using Lightworks and Resolve on the X-keys site.

X-Keys 68 Dec 17-crop.jpg (351.72 KiB) Viewed 4193 times

December 2017.zip

(12.57 KiB) Downloaded 73 times

Marc and Craig,
Thank you so much. I am considering upgrading from my Oxygentech panel to Micro and add this Xk-68 to it.
Let's see how the Jog-Shuttle performs.

I believe this is called completely hyjacking a thread no ?
Or is this also about issues with jkl.....

But now its busted anyway....

Let's see how the Jog-Shuttle performs.

Very unsatisfactory with all solutions i have seen (excluding my own), which all use navigation via keyboard shortcuts mapped to the knob, which is horrible, specialy on anything faster then super slow. Usefull for frame by frame small actions. Used it for 2 years as was all i had until i invested a few months time to build a proper solution for my 2 available custom controller kits, which is super smooth and a real jog shuttle feel at any speed. Not possible with controllermate or any basic macro program alone and works with own custom builld python code and open source libraries. Also it works only in edit,media page but not in color page unfortunately. For fairlight i use HUI protocol messages to drive a smooth jog/shuttle action. You can see it in action on my site (see signature) in the beatstep videos. For windows the hopcontrol tool beeing developed by another forum member would be able to be used to build/do similar (excluding the failight part)
Just my 2 cents

But now its busted anyway....
Very unsatisfactory with all solutions i have seen , which all use navigation via keyboard shortcuts mapped to the knob, which is horrible, specialy on anything faster then super slow. Usefull for frame by frame small actions. Used it for 2 years as was all i had until i invested a few months time to build a proper solution for my 2 available custom controller kits, which is super smooth and a real jog shuttle feel at any speed. Not possible with controllermate or any basic macro program alone and works with own custom builld python code and open source libraries. Also it works only in edit,media page but not in color page unfortunately. For fairlight i use reverse engineered HUI protocol messages to drive a smooth jog/shuttle action. You can see it in action on my site (see signature) in the beatstep videos. For windows the hopcontrol tool beeing developed by another forum member would be able to be used to build/do similar.

yes -- i also think, this kind of tasks have to be realized by proper means. using keyboard event injection is a very unsatisfying and inefficient workaround, which should only be seen as a last resort, if no other kind of access is available. but in case of resolve we should be able to solve this kind of demands in a more elegant way.

Let's see how the Jog-Shuttle performs.

Not so great with DaVinci as you would expect with simple keyboard mapping but absolutely superb with Lightworks as Jog/Shuttle has a true analogue VTR tape response and feel because LW was designed that way. As we Edit in the former and only Grade/Finish in Resolve, simple 'muscle memory' transport control is all that's needed.