Braille input new bar after in-accord sign does not reset to voice 1
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
Issue type
Accessibility issue (e.g. for keyboard-only or screen reader users)
Bug description
When inputting music using the Braille input feature, if you write music using multiple voices (called "in-accord" in braille terminology), the norm is to add voice 1, then the in-accord sign, then voice 2. This should repeat at each new bar.
Currently, when a new bar occurs, the voice remains voice 2. The in-accord sign in the second bar means that music is entered using voices 2 and 3 instead of 1 and 2. etc.
There seems no way to reset to voice 1 for each new bar, except to come out of the braille input window and select voice 1 manually.
Steps to reproduce
- Create a new score. We'll assume treble clef template. Key C major, time 4/4.
- Ensure the Braille input panel is active (in Preferences)
- Navigate to the braille window and enter the following braille music characters:
- Fifth octave C crotchet, C crotchet,
- Fourth octave G crotchet, G crotchet,
- in-accord
- Fourth octave E minim, F minim
that is:
⠨⠹⠹⠐⠳⠳⠣⠜⠐⠏⠟
or in key presses:
- J+L, F+J+K+L, F+J+K+L,
- K, F+D+K+L, F+D+K+L,
- F+D+L, S+J+K,
- K, F+D+S+J, F+D+S+J+K,
This bar works well and the music appears correctly in the print.
- For the next bar, enter almost exactly the same as above, but change the second C crotchet (⠹ - F+J+K+L), to B crotchet (⠺ - D+J+K+L).
Notice this time that the notes are being entered for voices 2 and 3 instead of voices 1 and 2.
(Note: technically, in the input of the second bar, the fourth octave sign before G crotchet is not needed, but it won't harm).
Screenshots/Screen recordings
No response
MuseScore Version
4.2.0
Regression
No.
Operating system
Windows 10
Additional context
When writing music in MuseScore's main score view, continuing to enter notes in several bars correctly maintains the same voice. It is arguable whether change voice commands should be used instead of the in-accord sign in the braille.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from musescore/MuseScore
-
engraving P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
community P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
regression nightly UX/interaction
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in musescore/MuseScore
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·