musescore / musescore/MuseScore
Repitch mode skips or gets stuck on grace notes
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
When using repitch mode, the cursor auto-advances to the next note, but it skips over grace notes that are before a regular note. Also, it seems to get stuck on grace notes after a regular note; the cursor remains on the note with the grace after, and can't advance past it.
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/a8621eaf-6c1b-40bf-b4fc-3f613d0d928b
What is the latest version of MuseScore Studio where this issue is present?
4.5.2, also in latest master
Regression
I was unable to check
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
Start by reproducing the issue in repitch mode with grace notes before and after regular notes, using the attached video as a reference. Trace the cursor's automatic note advancement and identify how grace notes are handled in both positions. Done means the cursor visits each intended note once and can advance past grace notes without becoming stuck, with regression coverage added if the relevant test area is found.
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
- 45/100