musescore / musescore/MuseScore
MusicXML import: Pickup measure not correctly recognized
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
MusicXML Import
Bug description
Pickup measure not correctly recognized on MusicXML import
Steps to reproduce
Importing the attached MusicXML file
Sunnyside Of The Street.zip
results in the first measure, which is a pickup measure,to get the number 0:
Exclude from meeasure countit not tickedAdd to measure numberis set to-1
Unlike when importing it into M3.6.2, which behaves correctly here:
Exclude from meeasure countit tickedAdd to measure numberis set to0
Screenshots/Screen recordings
See above
MuseScore Version
4.0.0, 4.0.1, 4.0.2 and latest build from master
Regression
Yes, this used to work in Musescore 3.x and now is broken
Operating system
Windows 11
Additional context
Stems from https://musescore.org/en/node/348410
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 with the MusicXML import path and reproduce the issue using the attached Sunnyside Of The Street.zip file, comparing its first pickup measure with MuseScore 3.6.2. Done means the imported pickup measure is excluded from the measure count and its added measure number is 0, as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100