Multikey Bigrams Issue on T4

datacyclist

I'm new to the twiddler4, the tuner works fine, I'm already up to speed, great device 🙂

I have a funny issue though: I've set up the tabspace layout (a lot of it from scratch) and I want

2L4L "so"
2M4L "es"
2R4L "is"

But those three combinations just don't work, they keep returning other letters.

Currently it's this, but it was different before deleting and re-adding these two-letter chords.

2L4L "o"
2M4L "e"
2R4L "t"

It's also only the 4L positions, all the other five positions (3L, 3M, 3R, 4M, 4R -- in combination with 2L, 2M, 2R) work fine.

datacyclist

Oh, it gets worse:

I have configured

3M4M "th"

but suddenly this returns an "en" which I have configured for "2M3R" (and it also works there).

3L4L is configured as "rs", but only returns an "r".

So there's more wrong than I thought at first, and it's not only with the 4L button.

The twiddler4 is connected via bluetooth to an android phone with a German keyboard layout (needed German umlaute which still work fine when sending the correct US-keyboard keys).

datacyclist

datacyclist Something's seriously wrong. I fiddled around with the mappings in the tuner and deleted all the two-character keystrokes that didn't get sent anyway.

I saved, exported the config, tried it: the deleted mappings were correctly gone, i.e. didn't generate keys or keystrokes. Just nothing happening as expected.

I then re-added all those two-character keystrokes, exported the cfg, tried it.
Result: the keystrokes were as wrong as before deleting and re-adding them. At least some consistency, I thought.

But funny enough, a keystroke which I hadn't touched at all was suddenly generating something else.
1M2L4M was mapped to "qu" before and worked fine before.
Now it is generating an "is" sequence (which is actually mapped to 2R4L, so one of those "4L" things I suspected originally to do something nasty).

Is that a twiddler-tuner issue? I don't really want to start creating a layout from scratch again, but I might try that.

Geoff

Hey, others have reported the same issue on multiple devices and layouts. I've a support ticket open since last Friday, no response yet. Reference number is 353271 if you want to log one and mention it.

datacyclist

Thanks for the hint -- I sent them another ticket request, citing the above description and also mentioning your ticket reference number. My ticket has the number #749839.

datacyclist

datacyclist Starting to debug this now anyway 🙂

Started with an empty new version6 config in the twiddler tuner.
Added the not-working-before keystrokes.
Nothing else (except the standard codes that get added automatically)
Result: the keystrokes work fine.
Adding more letters now, will report back.

datacyclist

datacyclist I'm back up to 129 of 175 chords I had originally, added them all incrementally and tested chords and keystrokes in between.

It still works.

I'll go all the way to my original configuration now, adding all the remaining chords. A bit tedious, but if it works in the end, that's okay for me.

Tony

Have you reviewed this already? https://www.mytwiddler.com/doc/doku.php?id=nonenglishchars

It could be an HID mapping issue by your host's locale setting.

The Twiddler sends HID codes and not actual letters. Your host's local could be seeing the HID code and the HOST mapping them to the letters assigned to the HID in the language table. If you are using a German local and the QWERTZ layout, the mapping is different from the English QWERTY layout and mapping. https://en.wikipedia.org/wiki/German_keyboard_layout

datacyclist

Thanks, but I already knew that, otherwise I couldn't have typed the German umlauts.

An "ä" needs to be sent as an apostrophe ' because that's the key which is in the ä position on the US layout.

And as a side note: how am I supposed to send the HID code for the key between the left shift and the y key in the German layout?

Tony

datacyclist
HID 64 , <
Shifted HID 64 , >
Altgr HID 64 , |

Source: https://stackoverflow.com/questions/9777286/sending-the-right-hid-keycode
Resource: https://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/translate.pdf

datacyclist

datacyclist Funny enough, after adding all the chords again (going up from 129, where everything worked, up to 175 chords) I get exactly the same problems as initially. So it's definitely one or more of some chords that cause problems. I'll report back.

datacyclist

Tony Thanks, I'll try that 🙂

Geoff

datacyclist I've an earlier thread about how going over 22 multi key outputs broke the tuner. No longer crashes the tuner, but could be relevant.

datacyclist

Geoff wtf, that seems to be it. I had trouble with 27 multi-key outputs, now I'm at 22 and everything works.

datacyclist

Geoff Ah, and sure enough I had the same feeling that you reported here: https://forum.mytwiddler.com/d/17-empty-macro-for-chord-b-at-5527a46 -- that after a certain number of additional chords (that are over the limit somehow) other chords/keystrokes get overwritten with parts of the next keystrokes. (nice hack there to find out about this, btw.)

Tony

datacyclist Can you send your config(s) to support@tekgear.com? We can check it out.

Tony

datacyclist
Please don't "hack". Report and we will look into it and address the issue.

If it is a "pointer" issue, as you indicated, the firmware needs to be updated.

datacyclist

Tony Yes, this feels like a pointer issue and @geoff was just testing things to maybe find out where the problem lies. Overwriting memory fields that end up in neighboring address areas is kind of a classic 🙂

Tony

Locked this thread as it is handled in this thread: https://forum.mytwiddler.com/d/21-multi-keystroke-entry-mismatch