Chord symbols input

• Sep 30, 2022 - 19:43

OS: Linux Mint 21, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-3140861968, revision: a78c972

When i input chord symbols, [TAB] doesn't move forward a measure? Commands [SPACE] and [;] work fine.

Greetings, Pentatonus

Comments

• Sep 30, 2022 - 21:40

Correct, Tab probably never should have been used for that purpose since it has special meaning with respect to accessibility (it navigates UI elements). It's been replaced by the shortcut used for moving between measures elsewhere in the program: Ctrl+Right.

Reply

• Sep 30, 2022 - 22:49

I'm all for accessibility features ... but not when they interfere with my accessibility.

For instance:

• Regarding the Tab keystroke I understand that accessibility designates Tab to navigate UI elements. But I would sorely miss using Tab to advance to the next measure (for chord symbols, lyrics, etc.) Using Ctrl+Right causes me to let go of the mouse or bring my left hand to the right side of the keyboard, or use both hands for the keystroke. Given that there's no one here with accessibility needs, I'd like an option for Tab measure advance. Is that flexibility in the cards?

• When in the Mixer I don't need a spacebar press to toggle the last setting, such as solo. I want the Spacebar's non-Mixer function: to start/stop playback. Trips me up half the time!

Will users be able to disable MuseScore accessibility keystrokes across the board with MuseScore defined non-accessibility defaults in their place?

Thanks!

Scorster

Reply

• Sep 30, 2022 - 23:23

"There's no one here with accessibility needs" - !? Define "here". There are very many MuseScore users with accessibility needs. I guess they are not "here" in sense of having a voice in this thread. Is that what you're saying?

Anyhow, certainly, if you file a suggestion for a new feature to GitHub to allow any given command to be redefined that currently is not, that could happen someday. Right now, rest of the chord symbol navigation commands - senmicolon for next beat, Ctrl+7 for advance by whole note, etc - are all customizable. I think only the functions performed by Space (next note or beat) and Ctrl+Right (next measure) are not, but no reason they couldn't be if someone were to request it and someone were to volunteer to implement it.

Regarding the Mixer, are you saying space doesn't work as expected for you in MuseScore 4 builds? If so, best to file an issue on GitHub for that as well. But if you're talking about the bug in MuseScore 3, that's fixed in MuseScore 4 as far as I can tell. That was just a bug; it was not something intended for accessibility.

Not sure what you mean about "across the board". Tab, Space, Left/Right/Up/Down, Enter, and F6 are the main keys with special universally-recognized accessibility functions. But none of them create any sort of conflict with anything in MuseScore except the use of Tab in chord symbol edit mode, and F6 to open the selection filter. The latter has no default shortcut currently, but you can add one through Edit / Preferences / Shortcuts as usual. As far as I know, the "next measure" command in chord symbol edit mode is the only command that's now reserved and not customizable. So there isn't any "across the board". It really is just about this one command, and shouldn't be a big deal to allow it to be customized.

Reply

• Oct 1, 2022 - 00:13

Marc wrote >> There's no one here with accessibility needs" - !? Define "here". There are very many MuseScore users with accessibility needs. I guess they are not "here" in sense of having a voice in this thread. Is that what you're saying?

My opening statement expressed my understanding of the importance of accessibility so I'm surprised you interpreted my statement to mean, "No MuseScore users rely on accessibility features."

By "here" I meant here using my computer. To be as precise as possible, there's no one here that uses my computer that has accessibility issues. Thus I would like to turn off accessibility features when they hamper my workflow or preferred keystrokes. I cited two use cases in my initial post.

scorster

Reply

• Oct 1, 2022 - 00:44

Sorry for the misunderstanding! For the record, your opening statement sounded more than a little like, "One of my friends is Black, but...", so it actually didn't help provide the necessary context for "no one here". Which in turn ended up sounding like "there's nobody around" from the famous Eddie Murphy "White Like Me" sketch on SNL:

https://www.youtube.com/watch?v=l_LeJfn_qW0

Anyhow, obviously, huge misunderstanding, so sorry again, and hopefully you get a laugh out of seeing the skit :-)

Anyhow, the rest of the post stands - other than this, I don't think you'll find any particular compromises to the overall user experience made for accessibility reasons - and on the contrary, many of the features originally introduced for accessibility are great usability improvements for everyone.

Reply

• Oct 1, 2022 - 00:22

Hi Marc,

I haven’t tried MS4 yet. Probably will do so in two or three weeks.

Marc wrote [no keystrokes] create any sort of conflict with anything in MuseScore except the use of Tab in chord symbol edit mode

Marc wrote there isn't any "across the board". It really is just about this one command, and shouldn't be a big deal to allow it to be customized.

Thanks. Good to know.

scorster

Reply

• Oct 1, 2022 - 17:28

Actually, I just discovered what is likely a bug, but a convenient one here perhaps, so I won't report it:

You can actually redefine the "Go to next measure" shortcut to be Tab if you like, and if you do that, it also works in chord symbol edit move. Looks like you can use anything that isn't otherwise a legal text character (so, you can't use backtick which is the first thing I tried).

Reply

Do you still have an unanswered question? Please log in first to post your question.