musescore / musescore/MuseScore

Braille Output: Anacrusis (Pic-Up bar) should be labelled 0.

Open
#28,343 0 comments 1 reaction 1 assignee View on GitHub

@shoogle is already working on this.

Since Jun 11, 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

When a score with an anacrusis is exported to Braille both the anacrusis and the first full bar are numbered in Braille as 1. The pick-up bar should be numbered 0 in Braille. If requested bar numbering is added to the Braille Live Braille View then this may effect that also.

STEPS:

  1. Create a score with a pick-up bar.
  2. Exclude the pick-up from the bar count so the score shows bar 2 as print bar 1.
  3. Go to File Export and select Braille.
  4. Notice the resulting Braille file when viewed in a Braille editor shows bar numbers down the left margin starting with 1 on the first line at the beginning of the right hand and then the numbering shows 1 again at the first full bar. The bar count is correct but the pick-up bar should be labelled as 0.
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

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.