I will try, thank you so far. Will reply later.
Hello riban,
was able to connect to webconf and took the necessary changes. System is up and running now. I need to check out the keyboard/mouse handling ;-).
3 Likes
I use keyboard and mouse a lot via VNC which should be a similar experience to your HDMI. I also plug a keyboard into my touch-only RPi5 + screen unit when I have to (like when its touch stops working which I believe is a touch hardware issue that I am negotiating with the supplier).
By default the key mapping is logical (to me) if you know the reason for it. On a standard UK QWERTY keyboard, the < > keys are near the bottom right. These are mapped to the nudge up / down of the 4th encoder (SELECT on V4). Modifier SHIFT makes them act as 3rd encoder. Ctrl makes them act as the 2nd encoder and SHIFT+CTRL makes them work as the 1st encoder. The 4 keys directy above these are I, K, O, L which are mapped to the switches on the 4 encoders (1st switch = I, 2nd switch = K, 3rd switch = O, 4th switch = L) so that they mimic the location on a V4. The Numeric keypad also has logical mapping but I rarely use that (although I did buy a wireless nemric keypad to implement and test this).
This default key binding (that can of course be changed in webconf) allows control with one hand hovering over those 6 keys and another hand pressing the shift/ctrl modifiers. It works well for me and I now have the muscle memory for this to be second nature.
Ha, thanks. Unfortunately I´m on German keyboard layout, which I have to map completely different.
After playing a bit with the keyboard, I can control some functions, also the knob values up and down. The knob buttons do not work. Instead, the key input freezes for a while, then returns to normal function. Also the âSelectâ function is not working, when mapped to âEnterâ key for example. I have cleared the full mapping list via webconf and try to implement one key after the other.
You donât want action SELECT. You want ZYNSWITCH 3.
You donât want parameter 3 with your arrow actions.
Hi,
Iâm glad youâve got now a running Zynthian. Have fun.
Iâve tested with Pi3 and Pi4 again and everything was running fine, so, it looks like your issue was very âPi5 relatedâ. I guess you have use this in audio settings for jackd parameters
This setting is working too on my Pi3 with an up to date Oram
Hi @riban,
the parameter 3 on the arrow events was added by the Zynthian itself by actvating Profile V5. The arrows work as expected. I tried this profile to make V5_ZYNPOT_SWITCH working, but it does not work. The top entry âSELECTâ is also not working. I think I have to learn a bit with the keyboard settings.
Oops! Typo in my previous comment (now corrected). CUIA SELECT is not the required action. This is a very common mistake that users make so maybe we should think how to mitigate it. If you want to emulate the press of the 4th encoder (SELECT on V4) then you need ZYNSWITCH 3 which binds the key to the action associated with the 4th (zero based index, hence param = 3) switch which is hardcoded as the V4 SELECT switch. You can do similar with other ZYNSWITCH values. The first four (0âŚ3) are hard coded to the encoder shaft switches of a V4. The rest are defined in Wiring Layout. A slight confusion is that wiring layout shows switches 1, 2, 3⌠but ZYNSWITCH references these with parameter 4, 5, 6⌠I would like to simlify this and make all the trigger mapping consistent and configured in a similar way - but not todayâŚ
[Edit] I donât know what mechanism would change the key binding to add param 3 to the arrow buttons. The CUIA arrow actions ignore parameters so these are harmless but should not be there. I would be interested to know the workflow that adds them.
Hi, thanks for the information. I will try this evening for the different switches.
With âSELECTâ I mean the âYes/Selâ Key action on a V5 kit. It confirms a previous selected action, like âEnterâ or âReturnâ event on a computer keyboard. But it is not working in the key binding list right now, when mapped to space or enter key. Or I maybe use the wrong event. On V5 the âyesâ button generates the necessary event without problems. Also the knob switches can send the confirming event to enter the previous selection.
Read my previous comment. The CUIA command, SELECT is not the CUIA command you want.
OK, thanks for open my eyes⌠
OK, I´m moving forward. The ZYNSWITCH works so far.
1 Like