#Two-letter one-handed chords do not output if chorded perfectly

1 messages Β· Page 1 of 1 (latest)

lapis niche
#

Summary:
When trying to chord words that have two letters in them, if the chord is input perfectly, the word won't output. This applies to the following circumstances:

(1) chords that have two letters and are on only one hand;
(2) chords that use the DUP key plus one other letter from either hand.

Technical details:
I have tested this using the CC1 with CCOS 1.0.0, 1.0.1 and 1.0.4-beta.
I've tried playing around with press and release tolerances, debounce and other settings in the GTM to no luck.
I've also tried getting a can of compressed air and blowing it into all the switches. My CC1 is now a little cleaner, but, otherwise, it had no effect.

Further description:
So when I say "perfectly", I mean when the inputs for the two-letter chord are both pressed and released simultaneously. The issue does not arise if both inputs are pressed at a slight delay. I'm very confident that this isn't user error as it can be recreated using ridiculously high press and release chord tolerances too. The issue I have with this bug is that as I'm getting better at chording, the chords are actually going through less often.

Example chords for me would be these:

Left hand only - me (m + e), we (w + e), our (o + u), or (o + r).
Right hand only - after (a + f), that (t + h), as (a + s).
DUP + letter (left or right hand) - say (s + DUP), no (n + DUP), off (o + DUP).

Video:
Here's a video showing the two-letter chords not outputting whenever the inputs are pressed at exactly the same time:

https://drive.google.com/file/d/14sYYmQuoAjROccei9EMTpf7S0LkilXdC/view?usp=share_link

You can see at the start that my chord tolerances are very high at 150 ms. You can also see that the individual letters are actually showing up, so there's no issue with the inputs not going through. And on the right side of the screen, you can see that the keys are being pressed simultaneously, which you can also hear from the sound of the switches.

Let me know if there's any more information I can provide!

median pike
#

Thank you for the video and further explanation. I think there have been others who have experienced this and it's interesting because I haven't personally been able to reproduce.

Could you confirm if you, too, don't have any issue at all if trying this while in spurring mode?

lapis niche
dusk geyser
# lapis niche Summary: When trying to chord words that have two letters in them, if the chord ...

also an issue on the LITE ... it also happens with 3 and 4 letter chords if you hit it fast and all the keys at exactly (as near as possible) the same time. it seems like the best way to keep the speed up is to chentry 2 characters and roll into 3, rarely an issue if the chord has 4 chars. ... since I'm using a Lite I have not messed with spurring. I've noticed there is a nice sound and rythm to successful chording . If my chord makes the correct sound it gets detected. Not even punnyLOL.

lapis niche
dusk geyser
#

I concur ... lol but really I agree ... simultaneous strikes results in one or more keys getting missed

lapis niche
#

Oh, I have no issue with the keys getting missed. As you can see in the video, each key is being inputted, but for some reason, the chord just doesn't get output.

dusk geyser
#

ive been (5xbn) trying to pay close attention and most of the time the keys are not missed ... they are output just not chorded. occassionally they do seem to get missed
I've noticed if I pause however so briefly at the bottom of the stroke and then release it seems to catch the chord. a variety of things can mitigate it but it totally interferes with the way I would like to use the keyboard. because I don't trust the output I have to watch it very closely and re-chord the misses. the degree to which this slows me down is significant. I'm not super fast but it cuts my speed to about 1/3 of my peak if the problem is not happening. I don't think it happened much if at all pre ccos and I've considered going back again but I really want the other features ccos offers so I'm just hoping we can figure out the cause and fix it.

#

the the the the hththt the the the the the hththt the hththt the the the the the htht htht the the the the the the the htht ht the the the ht the the the htht ht ht typical

#

the ones it caught are just those I failed to strike perfectly

lapis niche
median pike
#

and for me I don't seem to notice it at all, leading me to think I am the one with bad chording habits πŸ˜„

dusk geyser
lapis niche
#

An adaptation, I suppose haha

lapis niche
proud wave
#

Same here, it's very annoying because correctly performing the 2-letter chord doesn't work, but when "rolling" the 2 letters in a normal word, while typing character entry, will output the chord.

median pike
#

I.. think last night I may have actually started to notice myself failing some chords because of this

dusk geyser
median pike
lapis niche
dusk geyser
median pike
#

Well, it's got visibility don't worry, we will get it figured out

dusk geyser
#

I didn't know it was contageous πŸ˜› now I have to tell all my keys I've been with other keys LOL

median pike
#

LOL

dusk geyser
# median pike LOL

I noticed @dapper smelt is key-vorcing Lite in favor of One. I probably would too if I could, I mean look at that hourglass.

void horizon
#

I was bored at work meeting and was able to reproduce it.

#

I set my chord and press tolerance to 255ms, so it is impossible to mis-chord.

#

My settings:

#

I had tested with o + u == our and n + s == namespace.

#

The chord failure happens at around the 10th to 15th time in a row.

#

I have a gut feeling maybe debouncing is interfering with chording?

#

With no debouncing, I know my o and s keys start bouncing.

#

Perhaps this is why it is hard to reproduce, this does not crop up on devices with fresh, new switches.

lapis niche
#

Interesting, thanks for the additional perspective. It happens to me much more often than that. When I'm practicing on Charatyping, and a two-letter chord comes up, I'm always hyper-vigilant and have to be extra careful to purposely roll the chord; otherwise, it won't work maybe half the time.

#

I might play around with debounce settings again, but I don't think that had any effect last time

median pike
#

We are working towards what looks to be a promising update to fix this one. Hope to have it available for our beta testers to test soon!

lapis niche
#

Amazing. Thanks for the heads-up πŸ™‚

lapis niche
#

So no matter how hard I try, I can no longer replicate this bug in the new beta release. Seems 100% fixed now!

bitter abyss
lapis niche
#

#open-beta-testing message

void horizon