Gio @5 is missing my keystrokes

Hi,

At first I thought it was me, but it's happening way too much where the @5 misses my keystrokes. 

For example: An LD asks me to kill channels 201 thru 203.  I type it in and the whole set goes dark.  I look at my command line and it says 20 thru 203 Out.  Undo.. I type it again.

And it's not my hands, fat fingers or potato chip crumbs stuck in the keys.

I reached out to other @5 owners and I'm not the only one this is happening too.  I'm bringing it up here because it's making it very difficult to trust the commands I'm typing in.  Having used an Ion and Gio over the past decade I've never had a problem with keystrokes.  Well not since ETC changed the original keycaps from flat to curved.

If there's a way to investigate this I'm up for suggestions.  I can email my showfile or logs if that would help.

Thanks,
Jason

Parents
  • As a counter to this, as someone who has used Cherry MX Reds (or Zealio brand keyswitches with similar action to MX Reds), on all of my keyboards for the past 3 years, I haven't run into this problem as much as many people have complained about it.

    I believe this to be a muscle memory thing that will take some getting used to. Non enhanced Tis, non enhanced Gios, and original programming wings all had super heavy, mushy switches, which are quite the opposite of what are in the consoles now. (These switches were custom, IIRC).

    MX Reds have a 2mm actuation point and a 45g actuation force, which is considerably lighter than previous generation facepanels. Additionally, previous generation facepanels had switches with a tactile bump at the actuation point, so you knew when your key actuating, MX Reds are linear switches with no bump, which makes it much harder to know exactly when you've actuated a key. (IIRC, Ion Classics and Eos Classics had Cherry MX Blacks which were 60g actuation switches with no tactile feedback, like the MX Reds; the difference being the 15g actuation force difference, which is actually quite a bit).

    Jumping between consoles makes this harder, because you always have to be aware of how hard you're pressing each key, and whether it's being captured or not.

    This is why, in my personal opinion, lots of people seem to have problems with the updated facepanels.

Reply
  • As a counter to this, as someone who has used Cherry MX Reds (or Zealio brand keyswitches with similar action to MX Reds), on all of my keyboards for the past 3 years, I haven't run into this problem as much as many people have complained about it.

    I believe this to be a muscle memory thing that will take some getting used to. Non enhanced Tis, non enhanced Gios, and original programming wings all had super heavy, mushy switches, which are quite the opposite of what are in the consoles now. (These switches were custom, IIRC).

    MX Reds have a 2mm actuation point and a 45g actuation force, which is considerably lighter than previous generation facepanels. Additionally, previous generation facepanels had switches with a tactile bump at the actuation point, so you knew when your key actuating, MX Reds are linear switches with no bump, which makes it much harder to know exactly when you've actuated a key. (IIRC, Ion Classics and Eos Classics had Cherry MX Blacks which were 60g actuation switches with no tactile feedback, like the MX Reds; the difference being the 15g actuation force difference, which is actually quite a bit).

    Jumping between consoles makes this harder, because you always have to be aware of how hard you're pressing each key, and whether it's being captured or not.

    This is why, in my personal opinion, lots of people seem to have problems with the updated facepanels.

Children
  • A programmer should never have to think about "Am I hitting this key correctly?", not ever. If I press [Enter] on the console and it doesn't register, that's problem. Having to monitor the command line because I can't trust the consoles keys is a major problem. I know a Hog programmer that bashes on his keys until they break off, I'm not one of those kinds of typers.

    This isn't an issue of seasoned programmers not knowing how to type. As far as I can tell this is a defect in the @5 that I hope can be addressed in a firmware update.
Related