Chyron Duet Keyboard and Soarer's - how to?

[mlev6]

I recently picked up a Chyron Duet keyboard at an auction, did some research and got the Soarer's Converter.
keyboard is like this: https://deskthority.net/wiki/Chyron_Duet

so a nice many button keyboard and well-built.

I am new to reprogramming key-strokes.
by default, it seems according to hid-listen the two top eight row keys on the keyboard (row 1-8 and row Red-Black) are by default in system level act like if I was pressing alt1-8 and ctrl1-8 respectively...and that is causing a problem as I do not want those keys to be linked in any way to my default number keys on the keyboard 1 through 0, which are those above the letters row, if I want alt+1 I will just type alt+1 I want the extra keys in the top two extra rows of the keyboard to be unique.

I got Soarer's Converter PS2-usb and the computer running windows 10 now recognizes the keyboard and probably running default 102 US key on it.
So what do I need to program this keyboard? A teensy?

Thanks for the responses and help! I Never had to reprogram a keyboard before.

[Tactile]

I have a commercial keyboard which was originally set up to send two keystrokes on some of the keys. You might get some ideas from reading the story here.

[mlev6]

thanks!

it also looks like there are several "silent" keys currently in hid-listen. so they don't make a signal at all. like the three keys bellow the arrow keys on the keyboard (shift char, shift page, and shift row), any way to fix that?

[Tactile]

thanks!

it also looks like there are several "silent" keys currently in hid-listen. so they don't make a signal at all. like the three keys bellow the arrow keys on the keyboard (shift char, shift page, and shift row), any way to fix that?

More than likely those keys are... let's call them "extra modifiers" which are read by the keyboard controller which then changes some keyboard behavior. Because these keys are only read by the controller, the "signal" never leaves the keyboard. Nothing "outside" the keyboard can see these keys.

You can experiment with them, though, and maybe learn to use them. Play around pressing those keys or holding them down and see if they change any codes of the other keys.

[mlev6]

thanks!

it also looks like there are several "silent" keys currently in hid-listen. so they don't make a signal at all. like the three keys bellow the arrow keys on the keyboard (shift char, shift page, and shift row), any way to fix that?

More than likely those keys are... let's call them "extra modifiers" which are read by the keyboard controller which then changes some keyboard behavior. Because these keys are only read by the controller, the "signal" never leaves the keyboard. Nothing "outside" the keyboard can see these keys.

You can experiment with them, though, and maybe learn to use them. Play around pressing those keys or holding them down and see if they change any codes of the other keys.

so I am writing the .sc file after your layout where you shifted your F9/F10 keys but have some questions.

1.) why did you do the layer with f11 in your case?

"# SHIFT + RIGHT or LEFT arrow also presses F11 so we need to have F11 trigger
# a layer. The layer trigger itself absorbs the phantom keypress of F11
# then the shifted right/left arrows act normally"

2.) Also, in my case how do I ensure stuff like ctrl+s (save) etc still works, since the ctrl/alt keys ... both left and right ones, as most applications don't distinguish keymaps between a left or a right alt press and just treat it as an alt or ctrl press regardless because I am afraid if I program alt/ctrl to decouple and switch layers that will throw the default stuff like ctrl+s "save project" etc out of whack.

don't know if this helps or is too detailed, but other than my top rows being by default alt+1 through 8 and ctrl+1 though 8 respectively, the bottom three keys I mentioned as silent affect the arrow keys in similar fashion, ie. shift row+arrow key = alt+arrow key....kind of redundant.

And also I have an interesting key between my leftCtrl and leftAlt key (which is blank on the keyboard) but reads R00...undefined I guess...that jey could be potentially programmed into a default "windows" key or maybe a layer change key?

Here are my HID-listen readings for the keys in question.

"

left alt
r11 +E2 dE2
rF0 r11 -E2 uE2

left ctrl
r14 +E0 dE0
rF0 r14 -E0 uE0

right alt
rE0 r11 +E6 dE6
rE0 rF0 r11 -E6 uE6

right ctrl
rE0 r14 +E4 dE4
rE0 rF0 r14 -E4 uE4

top1
r11 +E2 dE2 r16 +1E d1E rF0 r16 -1E u1E rF0 r11 -E2 uE2

top2
r11 +E2 dE2 r1E +1F d1F rF0 r1E -1F u1F rF0 r11 -E2 uE2

top3
r11 +E2 dE2 r26 +20 d20 rF0 r26 -20 u20 rF0 r11 -E2 uE2

top4
r11 +E2 dE2 r25 +21 d21 rF0 r25 -21 u21 rF0 r11 -E2 uE2

top5
r11 +E2 dE2 r2E +22 d22 rF0 r2E -22 u22 rF0 r11 -E2 uE2

top6
r11 +E2 dE2 r36 +23 d23 rF0 r36 -23 u23 rF0 r11 -E2 uE2

top7
r11 +E2 dE2 r3D +24 d24 rF0 r3D -24 u24 rF0 r11 -E2 uE2

top8
r11 +E2 dE2 r3E +25 d25 rF0 r3E -25 u25 rF0 r11 -E2 uE2

topRED
r14 +E0 dE0 r16 +1E d1E rF0 r16 -1E u1E rF0 r14 -E0 uE0

topMGTA
r14 +E0 dE0 r1E +1F d1F rF0 r1E -1F u1F rF0 r14 -E0 uE0

topBLUE
r14 +E0 dE0 r26 +20 d20 rF0 r26 -20 u20 rF0 r14 -E0 uE0

topCYAN
r14 +E0 dE0 r25 +21 d21 rF0 r25 -21 u21 rF0 r14 -E0 uE0

topYELLOW
r14 +E0 dE0 r2E +22 d22 rF0 r2E -22 u22 rF0 r14 -E0 uE0

topGREEN
r14 +E0 dE0 r36 +23 d23 rF0 r36 -23 u23 rF0 r14 -E0 uE0

topWHITE
r14 +E0 dE0 r3D +24 d24 rF0 r3D -24 u24 rF0 r14 -E0 uE0

topBLACK
r14 +E0 dE0 r3E +25 d25 rF0 r3E -25 u25 rF0 r14 -E0 uE0


leftBlank (between leftCTRL and leftALT)
r00


arrowUP
rE0 r75 +52 d52
rE0 rF0 r75 -52 u52

arrowRIGHT
rE0 r74 +4F d4F
rE0 rF0 r74 -4F u4F

arrowLEFT
rE0 r6B +50 d50
rE0 rF0 r6B -50 u50

arrowDOWN
rE0 r72 +51 d51
rE0 rF0 r72 -51 u51

shiftCHAR+arrowUP
r14 +E0 dE0 rE0 r75 +52 d52
rE0 rF0 r75 -52 u52
rF0 r14 -E0 uE0

shiftCHAR+arrowRIGHT
r14 +E0 dE0 rE0 r74 +4F d4F
rE0 rF0 r74 -4F u4F
rF0 r14 -E0 uE0

shiftCHAR+arrowLEFT
r14 +E0 dE0 rE0 r6B +50 d50
rE0 rF0 r6B -50 u50
rF0 r14 -E0 uE0

shiftCHAR+arrowDOWN
r14 +E0 dE0 rE0 r72 +51 d51
rE0 rF0 r72 -51 u51
rF0 r14 -E0 uE0

shiftPAGE+arrowUP
r14 +E0 dE0 r11 +E2 dE2 rE0 r75 +52 d52
rE0 rF0 r75 -52 u52 rF0 r14 -E0 uE0 rF0 r11 -E2 uE2

shiftPAGE+arrowRIGHT
r14 +E0 dE0 r11 +E2 dE2 rE0 r74 +4F d4F
rE0 rF0 r74 -4F u4F rF0 r14 -E0 uE0 rF0 r11 -E2 uE2

shiftPAGE+arrowLEFT
r14 +E0 dE0 r11 +E2 dE2 rE0 r6B +50 d50 rE0 rF0 r6B -50 u50
rF0 r14 -E0 uE0 rF0 r11 -E2 uE2

shiftPAGE+arrowDOWN
r14 +E0 dE0 r11 +E2 dE2 rE0 r72 +51 d51
rE0 rF0 r72 -51 u51
rF0 r14 -E0 uE0 rF0 r11 -E2 uE2

shiftROW+arrowUP
r11 +E2 dE2 rE0 r75 +52 d52
rE0 rF0 r75 -52 u52
rF0 r11 -E2 uE2

shiftROW+arrowRIGHT
r11 +E2 dE2 rE0 r74 +4F d4F
rE0 rF0 r74 -4F u4F
rF0 r11 -E2 uE2

shiftROW+arrowLEFT
r11 +E2 dE2 rE0 r6B +50 d50
rE0 rF0 r6B -50 u50
rF0 r11 -E2 uE2

shiftROW+arrowDOWN
r11 +E2 dE2 rE0 r72 +51 d51
rE0 rF0 r72 -51 u51
rF0 r11 -E2 uE2

"

Thank you for tips on how to proceed with the remapping!

[Tactile]

thanks!

it also looks like there are several "silent" keys currently in hid-listen. so they don't make a signal at all. like the three keys bellow the arrow keys on the keyboard (shift char, shift page, and shift row), any way to fix that?

More than likely those keys are... let's call them "extra modifiers" which are read by the keyboard controller which then changes some keyboard behavior. Because these keys are only read by the controller, the "signal" never leaves the keyboard. Nothing "outside" the keyboard can see these keys.

You can experiment with them, though, and maybe learn to use them. Play around pressing those keys or holding them down and see if they change any codes of the other keys.

so I am writing the .sc file after your layout where you shifted your F9/F10 keys but have some questions.

1.) why did you do the layer with f11 in your case?

"# SHIFT + RIGHT or LEFT arrow also presses F11 so we need to have F11 trigger
# a layer. The layer trigger itself absorbs the phantom keypress of F11
# then the shifted right/left arrows act normally"

....

SHIFT worked normally - both right & left
Arrow keys all worked normally
But if you pressed either SHIFT + LEFT or RIGHT arrow, the controller would add F11
So I had to get rid of that F11 keypress

.....

I'll return later for the rest of your questions - got stuff on the barbecue right now

[mlev6]

Ok I am making a lot of progress in terms of remapping, I decoupled the top rows by making LCTRL and LALT trigger new layers and mapping those rows to extra FUNCTION  keys.

Now I have a problem of remapping the blank key just to the right of my LSHIFT key on the Duet keyboard....it gives me r00 in hid-listen. I want to set it as my windows/gui key. Is there a code for that?

Thanks!

[Tactile]

Ok I am making a lot of progress in terms of remapping, I decoupled the top rows by making LCTRL and LALT trigger new layers and mapping those rows to extra FUNCTION  keys.

Now I have a problem of remapping the blank key just to the right of my LSHIFT key on the Duet keyboard....it gives me r00 in hid-listen. I want to set it as my windows/gui key. Is there a code for that?

Thanks!

That might be just a do-nothing placeholder. That's a spot where an ISO keyboard (Europe - Germany, Norway, England, etc.) have a key but US ANSI don't. ANSI usually enlarge the left shift to fill in that spot. They might have done it this way so they didn't need different keycaps for US/Europe. For the US market just pop a blank keycap there & program that key to do nothing.

They couldn't just add a larger left shift key because they would also need a stabilizer for that new 2U left shift, which might mean a different plate, and so on...

So you can see why a company might choose to just make that key blank.