musescore / musescore/MuseScore

Tuplet numbers sometimes disappear when polymeter change occurs

Open
#24,217 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving P3
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
  1. Create a new score with two staves.
  2. Set the time signature for the first staff to 6/8, and the second staff to 2/4.
  3. Change the time signature for the second measure of the first staff to 3/4.
  4. In this 3/4 measure, create three sextuplets, each with a duration of a quarter note.
  5. Merge each sextuplet into a single dotted quarter note.

Expected Behavior: Each dotted quarter note should display a small number 6 above it.
Actual Behavior: The number 6 appears above the first and third dotted quarter notes, but is missing from the second one.

Supporting files, videos and screenshots

image

What is the latest version of MuseScore Studio where this issue is present?

4.3.2 (4.4.0 for testing has this issue as well)

Regression

I was unable to check

Operating system

Windows 11

Additional context

Some may wonder why it's necessary to merge the sextuplets back into single notes. This is because these notes are intended to have tremolo applied to them in the final score. The original sheet music that I'm trying to transcribe looks like this:
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.