musescore / musescore/MuseScore

No Braille input for drum kit

Open
#32,805 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accessibility braille input 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

Currently there does not seem to be any way to trigger input on the Braille panel for a multi instrument untuned percussion staff such as a drum kit. Neither using the assigned shortcut letters or the letters shown on output (closely related to midi assignment) seem to work with or without octave signs.

Suggest that these should be assigned to the letter name and octave mark they would be if they were written in bass clef, so bottom space A2, top space G3, etc. This is the most standard method used by transcribers (although the manuals do allow for the transcriber to choose their own mapping). These need to be fixed in output first (see #32804) so they match for both input and output. It probably makes sense for them to default to the 1st option of instrument for each of those line/space assignments, and automatically use the correct note head shape on the score without needing to input the note head symbols in Braille. If these are supported for Braille output they could show when it refreshes.

Input in Braille should follow the standard rules for voices and the use of the in-accord symbol the same as it does in regular staff notation, which already work correctly for output.

Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.7 beta

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

Start by reviewing the related output issue #32804 and the existing Braille input and output handling for regular staff notation. Done means drum-kit input follows the proposed bass-clef letter and octave mapping, uses appropriate noteheads and voice/in-accord rules, and stays consistent with Braille output.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.