musescore / musescore/MuseScore
MIDI export puts rehearsal marks into lyrics
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Import/export issue
Description with steps to reproduce
- Create a new file, add some notes
- Create a rehearsal mark on a bar that has notes at the start
- Export MIDI with default settings
- Observe that the lyrics on the note starting immediately after the rehearsal mark have been replaced by the text of the rehearsal mark
Supporting files, videos and screenshots
2025-09-08 Rehearsal mark in MIDI lyrics.zip
A sample MuseScore Studio file, plus the resulting MIDI file.
What is the latest version of MuseScore Studio where this issue is present?
MuseScore Studio version (64-bit): 4.5.2-251141402, revision: github-musescore-musescore-ac9d3bc
Regression
No.
Operating system
OS: Windows 11 Version 2009 or later, Arch.: x86_64
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the attached sample MuseScore Studio file and MIDI output, following the export steps in the report. Trace the MIDI export path to determine why a rehearsal mark replaces lyrics, then verify that lyrics remain unchanged while rehearsal marks are exported appropriately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100