musescore / musescore/MuseScore
Tuplet (triool) becomes “orphaned”, floats in the measure and does not affect rhythm in 3/4
@zacjansheski is already working on this.
Since Jun 23, 2026.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Engraving bug (incorrect score rendering)
Description with steps to reproduce
Titel:
Tuplet (triool) becomes “orphaned”, floats in the measure and does not affect rhythm in 3/4
Beschrijving:
In a 3/4 measure, when creating a triplet of eighth notes, MuseScore sometimes creates a tuplet that is not attached to any note or rest.
The tuplet:
• floats freely and can be moved anywhere
• does not attach to a note (no red dotted line)
• does not change the rhythmic duration
• causes the measure to auto fill with rests as if the tuplet does not exist
• prevents deleting notes or rests inside the measure
• disappears only when deleting the entire measure
This happens even in a completely new, empty measure, in Voice 1, with correct cursor placement.
This results in a “ghost tuplet” that corrupts the measure.
Steps to reproduce:
- Create a new 3/4 score
- Insert a new empty measure
- Select the rest on beat 3
- Enter note input mode
- Choose eighth note
- Enter one eighth note
- Select it
- Press “Tuplet → Triplet”
→ MuseScore creates a tuplet that is not attached to the note
Expected:
The tuplet should attach to the selected eighth note and replace beat 3 with 3 eighth note triplet notes.
Actual:
The tuplet floats, does not affect rhythm, and corrupts the measure.
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
4.7.3‑260608135 (Windows 11)
Regression
I was unable to check
Operating system
WINDOWS 11
Additional context
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.
Assessment
This issue has not been assessed yet.