musescore / musescore/MuseScore

Can't input triplets or other tuplets with 6-key Braille entry

Open
#34,236 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue type

Accessibility issue (e.g. for keyboard-only or screen reader users)

Description with steps to reproduce

In 4.7.4 triplets are now displayed correctly in Braille. But there does not seem to be a way to enter them using 6-key entry in the Braille panel.

STEPS:

  1. With focus on an empty bar press Tab to move to the Braille panel.
  2. Press N to input notes.
  3. Press the following key combinations to enter a 4th octave mark followed by 3 crotchet C's. k fjkl fjkl fjkl.
  4. Now press sd (dots 23) for the Braile triplet sign. The screen reader does announce "tuplet 3" but the crotchet rest remaining in the bar does not change to 3 quaver rests and the triplet sign does not display.
  5. Now try to enter 3 triplet quaver C's fjk fjk fjk. Nothing is entered.

As MuseScore usually has the note length set before the triplet is used to break it into 3, the Braille input for the triplet will likely need to remain partial until all 4 signs have been entered and then display once the last triplet note enters. For combinations of a triplet with 2/3 1/3 it should resolve once 2 notes have been entered that add up to 3 of the smallest entered.

Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.7.4

Regression

No.

Operating system

Windows 11 with NVDA

Additional context

No response

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

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.

Research direction

Reproduce the report in the Braille panel using 6-key entry and the key sequences given, then trace the Braille note-entry path for tuplets. Done means triplet and other tuplet signs are accepted, the entered notes are represented with the correct duration, and the tuplet becomes visible at the appropriate point described in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
accessibility
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.