Braille Panel Output not following rules for Semiquaver Grouping

[jmwmusic]

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

[msviolafangirl]

As a braille and screen reader user, I can confirm this is an issue. Another related issue is how to enter whole notes and how to enter 16th notes in braille using the braille panel, as the braille symbols are the same, the difference is in how the notes are grouped.

[jmwmusic]

Could the issue of inputting 16th or whole notes be solved by MuseScore assuming it is a whole note if it is followed by a space. This would mean in large time signatures such as 4/2 and 3/2 it may be necessary to add the space and then backspace to complete the bar but this could be handled as a work around in documentation as it wouldn't affect many users. The only other scenario an exception would need to be made for is if the input is on the last 1/4 of the last beat of a bar then it would need to assume 16th. conforming to the above rules for grouping when relating to input might be even more complicated. But this basic concept of knowing the difference between 16th and whole is fairly fundamentally essential.