musescore / musescore/MuseScore
[Musicxml export] - Missing textline end
Open
Nobody has claimed this yet.
community
MusicXML
P3
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Import/export issue
Bug description
Steps to reproduce
Please see mov 10 bar 64, Musescore bar 601. Here beat 2 has "allargando" in both instruments. However, the end of the line is lost in piano part due to an offset, thus in beat 2 of a half chord. This should be included with an offset.
Screenshots/Screen recordings
No response
MuseScore Version
4.2
Regression
No.
Operating system
Windows
Additional context
No response
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 MusicXML export with the attached cui kaleidoscope.zip, focusing on mov 10 bar 64 and MuseScore bar 601 where “allargando” appears in both instruments. Inspect how the piano part handles the textline end and its offset. Done means the exported piano textline includes the end at the correct offset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100