musescore / musescore/MuseScore

No 8va shown in Braille Output

Open
#28,899 2 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Jul 25, 2025.

accessibility braille export braille view needs review
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
  1. Create a bar of music with 4 C5 crotchets.
  2. Select beats 3 & 4 and add an 8va.
  3. Notice that the Braille in the Live Braille panel shows the 4 C's (dots 1789) and the 5th octave mark is in front of the first C (dots 46) and 6th octave mark in front of the 3rd C (dots 56). But notice that the 8va is not shown (345, 3456, 125 , 1236, 1). This would usually also have a termination mark where it ends. Neither are present.
    Although the octave marks are correct for the notes it is much easier to see the start and end of a line in Braille than it is to listen to all of the description on every note. Only in Braille can a blind user skim through quickly looking for this start/end.

This is the sort of thing that ideally long term might have some options of what is to be displayed or not in the Braille, similar to those for transcribing in SMB.

Supporting files, videos and screenshots

N/A

What is the latest version of MuseScore Studio where this issue is present?

4.5.2

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.