I really like the feel of the K3 in my hand. The weight, the buttons, etc. I really want to like this thing.
I created a mapping for the K2 that assigns multiple functions to almost all keys, which can be accessed using the Shift and Layer keys. The Latch Layer function must be disabled. Unfortunately, the mapping does not work with the K3 (LED feedback), and after hours of analysis, I figured out why.
When I assign a key twice, let’s say I assign D4 (orange) to Quantize and D7 (green) to Headphone Cue. When Quantize is activated and I activate Headphone Cue, D7 lights up. When I deactivate D7 again, I want D4 to light up because D4 is active. Or, if D4 and D7 are active and I deactivate D4, I still want D7 to light up. I applied this principle to the other buttons as well, and it worked well with the K2. It doesn’t work with the K3 because it remembers the value of the buttons, and if there is no change in value, you can’t just make the button light up again. In my example: D4 (orange) has the value 127, now D7 is activated with 127 and the button lights up green, I deactivate D7 and then send the command D4 127 “only for the LED, since Quantize is already active,” the LED will not light up because the state D4 127 already exists.
I can get it to work if I send D4 126 first and then D4 127. However, this makes the whole mapping much more complicated, and I hope that this behavior is not related to the hardware, because then it will not be possible to fix it. In order for my and your mappings to work the same as with the K2, the K3 must not remember the values of the LED, or it must parse them again (LTP latest takes precedence) if it receives the same value again. I hope that this problem can be fixed.
