musescore / musescore/MuseScore
Pickup measures show wrong rests when the Actual duration is modified
Open
Nobody has claimed this yet.
P3
regression MS4
UX/interaction
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
- New score for Flute, Time signature 4/4, with a pickup measure (1/4) created with the Wizard.
- Create two more incomplete measures (Actual duration : 1/4 and 1/8) in the following measures
Expected result: display of a quarter rest (as when creating the score) and a 8th rest
- Works as expected with 4.3.2
- Malfunctions as of version 4.4.0 (See GIF below)
Supporting files, videos and screenshots
What is the latest version of MuseScore Studio where this issue is present?
4.4.0
Regression
Yes, this used to work in a previous version of MuseScore 4.x
Operating system
Windows 10
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
Reproduce the issue in MuseScore Studio 4.4.0 using the reported Flute score, 4/4 time signature, 1/4 pickup measure, and following measures with Actual durations of 1/4 and 1/8. Compare the displayed rests with version 4.3.2; done means the quarter and eighth rests remain correct after changing Actual duration.
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