musescore / musescore/MuseScore
Pickup measure beats not "in sync" with Select>More>Same Beat
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
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
In 4/4 meter (nominal) with a one beat anacrusis (1/4 actual meter)
it's understood that the first note of the anacrusis is on the 4th beat of the measure.
But MuseScore Studio fails to comprehend that when selecting via Select>More>Same Beat.
NOTE: Perhaps this is related to the logic addressed in: https://github.com/musescore/MuseScore/issues/22080
Steps to replicate:
• download and open the example score
• command click the 4th beat in the first full measure
• choose Select>More>Same Beat
Unexpected result: MuseScore Studio does not select the first note in the anacrusis (i.e. beat 4).
Rather it selects nothing in the anacrusis, as if the anacrusis has no 4th beat.
Unsurprisingly there's a similar, converse error:
• using the example score
• command click the 1st beat in the first full measure
• choose Select>More>Same Beat
Unexpected result: MuseScore Studio selects the first note in the anacrusis.
In other words, the note understood to be on the 4th beat.
Supporting files, videos and screenshots
Here's a score that contains steps to replicate, and has the anacrusis and subsequent measure set up
https://musescore.com/user/35880724/scores/30346343
In which versions of MuseScore Studio is this issue present?
MS4.6.4 back thru MS3, and perhaps earlier.
Regression
No.
Operating system
macOS 13.7.8
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 opening the linked example score in MuseScore Studio and reproducing both Select > More > Same Beat cases with the one-beat anacrusis. Trace the selection entry point and beat comparison logic. Done means the anacrusis note is selected with beat 4 and not selected with beat 1, matching the reported expectations.
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
- 42/100