[Export Braille] Clef and Key signature disappear in case of long Tempo string

Open
#23,763 1 comment 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

braille export engraving needs info P2
Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

Goto File-Export-Braille
In case the Tempo string is longer than 20 characters, the Clef sign and the Key Signature don't appear on the Braille version of the score.
Example (see attached files): When Tempo string is "Modéré" , proper Clef sign and Key Signature are shown, when Tempo string is "Modéré mais sans lenteur et avec élan", Clef sign and Key Signature are not longer present.

Attached files:
Drill 8-3 Correct.pdf: Score with Modéré
Drill 8-3 Erroneous.pdf: Score with more than 20 characters
Drill 8-3 Correct.txt: (=exported .brf file, renamed to .txt) Braille translation showing clef sign and key signature
Drill 8-3 Erronious.txt: (=exported .brf file, renamed to .txt) Braille translation without clef sign and key signature
Drill 8-3.zip: all original .mscz and .brf included in zip archive.

Supporting files, videos and screenshots

Drill 8-3 Correct.pdf
Drill 8-3 Correct.txt
Drill 8-3 Erroneous.pdf
Drill 8-3 Erroneous.txt
Drill 8-3.zip

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

4.3.2 .241630832 rev 22b46f2

Regression

I was unable to check

Operating system

macOS Sonoma 14.5

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
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

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.

More from musescore/MuseScore

All issues in musescore/MuseScore

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.