X-Keys hotkeys glitch

I am using an X-Keys24 keypad to operate the on-screen scoreboard and I keep getting a glitch at random times. It happens on both my windows 10 HP laptop and my iMac running High Sierra.

I map x-keys with the only keys we can use to change scores (this is another complaint) = and ]. I use a single = on a button to add 1 point. I use 2 = to add to points. And I use 3 = on the key to add 3 points. I do the same with the ] to add points for the other team.

Most of the time it works as intended, but sometimes the score gets stuck and wont stop glitching until I add another point. I'm attaching a short video to illustrate this.

Has anyone else experienced this type of issue with a hotkeys keypad? All of my other hotkeys (capturing replays, switching shots) work fine.

Thanks for any help.

22replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Do you see this using keyboard shortcuts on the computer keyboard?
    I wonder if there's an intermittent communication or timing issue.

    Reply Like
  • CraigS  It can't be done on the computer's own keyboard because I can only hit 1 = or ] at a time. I don't have any issues when increasing the score by 1 point, but I like being able to add 2 or 3 points without hitting the button 2 or 3 times. 

    Also, i have never experienced this issue when changing the score by 2 or 3 points in the editing area of the scoreboard when it's in Preview.

    Reply Like
  • Ben Cowart Perhaps there's an issue with X-Keys keypad communicating a given keystroke since this is happening on both your HP laptop and iMac.

    Reply Like
  • CraigS That did occur to me and I emailed the x-keys customer support, but they have not responded yet. 

    Reply Like
  • Ben Cowart Do post back when they respond.

    Reply Like
  • Ben Cowart  did you get this resolved? It sounds like it could be a timing issue and you may need to add a bit of delay between the keystrokes in the X-keys programming. 

    Reply Like
  • Ben Cowart We are certainly interested in how this resolves.

    Reply Like
  • X-keys was unable to figure this out. The only way I was able to use hotkeys to change scores was to use a single hotkey to add 1 point and press it 2 or 3 times depending on the basket made. That was the only scenario that didn't result in the glitch. Hopefully, wirecast will add hotkeys for 1, 2, 3, and 6 points to avoid this problem. And update their scoreboard options.

    Reply Like
  • Ben Cowart We may want to look into this on our end since there's keen interest in X-Keys here. 
     

    Fill out the form and maybe we can test to see where the issue might be. Mention that you contacted X-Keys and they haven't figured it out (yet). Explain how you're using it as that can help.
    Wirecast Support Form

    Reply Like
  • I will discuss this with our tech staff as well. There may be some things we haven't tried.  We're keen to get this working.

    Reply Like
  • Ben Cowart , please contact us again ( tech@xkeys.com ). We're eager to take another shot at fixing this. If you can include your programming file, that will be a big help.

    Reply Like
  • Dan Slider Thanks for helping us investigate this.

    Reply Like
  • CraigS , we're happy to help.  My guess is the X-keys is sending the keystrokes faster than Wirecast is reading them (since we can send them faster than a keyboard) and that we just need to insert some delays in key places to make it work. 

    Reply Like
  • We should have a new public beta of Wirecast 9 very soon to test on. It may better handle X-Keys input.

    Reply Like 1
  • FWIW, I just tested it here with the Wirecast 9 Beta we've been using and I can't reproduce the glitch.  

    Reply Like
  • Upon further review...  I can reproduce it now that I switched to the same scoreboard Ben is using in his video. 

    Reply Like
  • Ben Cowart , In my testing here, I have fixed the issue by adding a 100 Ms delay between the the keystrokes. This is what the programming looks like in MacroWorks. You can find the Delay function at the bottom of the functions list.

    Reply Like
  • Dan Slider You may want to test the new beta

    Reply Like
  • CraigS , thank you.  I will get that right now. 

    Reply Like
  • Dan Slider You're welcome of course. Curious to see if the delay is still needed.

    Reply Like
  • Results of my tests with the new Beta.  I can still reproduce the glitch with the keys that have no delay in the programming. I cannot reproduce the glitch with the keys where I have added the 100 MS delay.  

    Reply Like
  • Dan Slider Thanks for that!

    Reply Like
reply to topic
Like Follow
  • 4 mths agoLast active
  • 22Replies
  • 247Views
  • 3 Following