musescore / musescore/MuseScore

Different time signatures with the same total rhythmic duration may incorrectly be treated as equivalent for repeat courtesies

Open
#32,179 0 comments 0 reactions 1 assignee View on GitHub

@ajuncosa is already working on this.

Since Jul 16, 2026.

engraving P2
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. Open the attached test score.
  2. Add a time signature (e.g. 4/4) to the bar following the end repeat barline.
    RESULT: time signature and appropriate repeat courtesy is added as expected.
  3. Undo, then attempt to add a 3/4 time signature at the same place. Notice that total rhythmic duration (3/4) is the same as is being repeated to (6/8).
    RESULT: The 3/4 time signature is not added.
  4. Open Format > Style > Clefs, key and time signatures > Clefs, key & time signatures at repeats and jumps and uncheck At repeats, only show changes before the barline.
  5. Repeat step 3.
    RESULT: Now the 3/4 time signature and appropriate repeat courtesies are drawn as expected.
  6. In the Style dialog, check At repeats, only show changes before the barline.
    EXPECTED: No change to the notation (because the time signatures for the repeat and the subsequent measures are different).
    ACTUAL: A single 3/4 time signature is drawn before the repeat barline.
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/406e8144-0a60-42fb-be82-0e036dbbb0ba

In which versions of MuseScore Studio is this issue present?

4.5.0-latest nightly

Regression

No.

Operating system

Ubuntu 24.04.4 LTS

Additional context

This appears never to have worked correctly.

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.