musescore / musescore/MuseScore

Braille Output: No need to mark end of Hairpin immediately before another dynamic mark

Open
#28,320 1 comment 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

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

This effects both the Braille export feature and the output in the Live Braille panel. Currently the live Braille panel is also showing the end in the wrong place (see 25203) so the below behaviour is best seen by using the export feature.

Assume some music such as:
hairpin crescendo, then some crotchet notes and the end of the hairpin; next bar, diminuendo hairpin, some notes and the end of the hairpin.
In braille it is not necessary to show the end of the crescendo hairpin in this case as it is immediately followed by another dynamic mark.

Similarly, if the diminuendo hairpin was instead another dynamic, such as forte.

  1. Crescendo hairpin immediately followed by diminuendo hairpin:
    Expected output:
    ⠼⠙⠲
    ⠁ ⠜⠌⠇⠄⠜⠉⠐⠹⠱⠫⠻ ⠜⠙⠐⠳⠻⠫⠱⠜⠲ ⠐⠽⠣⠅

Actual output:
⠁ ⠜⠌⠇⠼⠙⠲ ⠜⠉⠐⠹⠱⠫⠻⠜⠒ ⠜⠙⠐⠳⠻⠫⠱⠜⠲ ⠐⠽⠣⠅

  1. p crescendo hairpin followed by forte:
    Expected output:
    ⠼⠙⠲
    ⠁ ⠜⠌⠇⠄⠜⠉⠐⠹⠱⠫⠻ ⠜⠋⠐⠳⠻⠫⠱ ⠽⠣⠅

Actual output:
⠁ ⠜⠌⠇⠼⠙⠲ ⠜⠉⠐⠹⠱⠫⠻⠜⠒ ⠜⠋⠐⠳⠻⠫⠱ ⠽⠣⠅

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.