Newbie Problem - impossible to enter numbers in the sub-tracks (Chance, velocity,...)

[elode]

... and Alt+Y is obtained with the qwerty layout, even if the activated layout is not the qwerty layout.

[kjetil]

Ah, you're using Wayland, that's a different system, a different X implementation. I'll try and see if I can reproduce the problems in Wayland.

[kjetil]

... and Alt+Y is obtained with the qwerty layout, even if the activated layout is not the qwerty layout.

I've tried "fr bebo" under wayland, and it behaves differently than under X. It was impossible to add numbers in the velocity text there, so that has to be fixed. (Interestingly though, it worked when only using "fr" (without bebo) keyboard, which doesn't quite make sense).

But I can't reproduce that Alt + Y works as if the keyboard was QWERTY. Are you sure you haven't set the keyboard for velocity-text on/off to QWERTY_Y? You can check this under help -> edit keybindings. Just delete the line containing ra.showHideVeltext, if it's there.

[elode]

Ok, the situation at my place seems identical:
With Wayland,
- impossible to add numbers in the velocity text (possible with standard FR)

but :

- Also impossible to add letters (a to f) in the velocity text.

Alt+Y is ok in FR and BÉPO (no more problem here).

[kjetil]

Hmm, I didn't have any problems adding the letters a to f, except that I spent a very (VERY) long time finding the right keys in the "fr bepo" keyboard. You're using plasma with wayland? I'll check again, maybe I only tested a-f under that gnome-thing, not plasma.

[elode]

Well… it's a bit more complicated:

With the BÉPO layout:

- With radium_64bit_linux-7.5.76 version,
- I can type letters in Velocity Text, but not numbers.
- Alt+Y is ok.

- With radium_64bit_linux-7.5.77 version (the one you had sent me to do some tests),
- I can't type letters in Velocity Text, but numbers.
- Alt+Y is not ok. It's the US layout Alt+Y wich must be typed.

Phew! It’s disorienting!

[kjetil]

There is an alternative solution, namely to only use scancode (i.e. QWERTY) for keybindings, and only do the conversion from scancode->local name when displaying menus and so forth. However, then it would be difficult to document keybindings outside of the program + that common keybindings such as Ctrl+Z, and copy/cut/paste, would be at unusual positions for many users.

[elode]

Another idea to simplify and maybe make things easier to fix in the code:
Rather than following a "piano keyboard" type layout, enter notes using the corresponding letters on the user’s keyboard layout. To enter the notes with a sharp, add the 'shift' key as a modifier. To move up one octave: F2, to move down one octave: F1

Example:

Code: Select all

- a > A-3 (3 being the default octave).
- shift+a > A#3
- F2 + shift+a > A#4
- d > D4
- ...

It would remain quite simple as an input method, and even like for someone like me, simpler. And I suppose there would no longer be conflict problems as is currently the case.

I don’t know if this kind of thing would be easy to code, but if it is the case, I think it would be interesting to leave the choice to the user somewhere in the preferences.

What do you think?