musescore / musescore/MuseScore

Tuplet (triool) becomes “orphaned”, floats in the measure and does not affect rhythm in 3/4

Open
#33,885 4 comments 0 reactions 2 assignees View on GitHub

@zacjansheski is already working on this.

Since Jun 23, 2026.

awaiting reply from user engraving needs testing
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:

Image

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:

  1. Create a new 3/4 score
  2. Insert a new empty measure
  3. Select the rest on beat 3
  4. Enter note input mode
  5. Choose eighth note
  6. Enter one eighth note
  7. Select it
  8. 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
Image Image
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
Image
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.