Issues with Displaced Tempo Markings When Making Parts

Open
#29,765 1 comment 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

engraving needs review
Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce
  1. Open file.
  2. Open all parts, and scroll to measure 52 (try it in the contrabasses, violoncellos, violas, violins, and violins (2) parts, as well as the clarinets and harp I and II parts).
  3. At measure 52, there is a "Meno Mosso (q=66)" that must be placed properly above the staff. Place it correctly if you can on each of the parts.
  4. As you continue past the strings parts, notice how any mistake that results in the tempo locking to a place other than m. 52 results in the tempo marking being significantly displaced on ALL of the parts, even if you fix it immediately afterward.
  5. Notice that cmd+z/ctrl+z/undo do not have any effect. The tempo markings do not return to their original positions, even if other actions are undone.

Quartal_harmony_is_actually_peak.mscz.zip

Supporting files, videos and screenshots

Please watch this video:

https://www.youtube.com/watch?v=_i8kpaqdFFQ

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

OS: macOS 15.5, Arch.: arm64, MuseScore Studio version (64-bit): 4.5.2-251141402, revision: github-musescore-musescore-ac9d3bc

Regression

No.

Operating system

MacOS Sequoia 15.5

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
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

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.

More from musescore/MuseScore

All issues in musescore/MuseScore

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.