musescore / musescore/MuseScore

Braille Panel Output not following rules for Semiquaver Grouping

Open
#20,153 2 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

accessibility P2 UI
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UI bug (incorrect info or interface appearance)

Bug description

As the same symbol is used in Braille for semibreves and semiquavers the context quickly shows which is which. However, when there are full beats of semiquavers only the first one should be shown as a semiquaver and the rest as quavers. This is similar to beaming groups of semiquavers into beats in print.
So for example:
8 semiquavers in 3/4 followed by a crotchet will actually be Brailled as – semiquaver, quaver, quaver, quaver, semiquaver, quaver, quaver, quaver, crotchet.
This makes the group of 4 semiquavers much easier to quickly see the beat grouping.

However, this is not done if there is a quaver or quaver rest in the next cell after the group.
So if the 8 semiquavers were followed by two quavers only the first group could be grouped in this way giving:
Semiquaver, quaver, quaver, quaver, 4 semiquavers, 2 quavers.

Note: It would be essential to check carefully the exceptions are all covered if updating this so there can be no misinterpretation of what are semiquavers and what are quavers. Currently it seems a bit odd, but with all semiquavers being Brailled as semiquavers there is no issue with confusion.

Steps to reproduce
  1. Create a bar full of semiquavers.
  2. The live Braille panel shows them all as semiquavers.
  3. Actual output should be that the first of each beat is a semiquaver and the rest are shown as quavers that the reader understands to be subsequent semiquavers in a grouped beat.
Screenshots/Screen recordings

No response

MuseScore Version

4.1

Regression

No.

Operating system

Windows 10 with NVDA

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.