musescore / musescore/MuseScore

Pasting a metronome marking into a tempo marking box does not honour the metronome marking in playback BPM

Open
#28,667 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P2 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. Open a score.
  2. Drag an 'Allegretto' tempo marking to the start. Playback speed shows that the tempo is 116 BPM.
  3. Drag a MM80 metronome marking from the palette to the start. Playback speed now shows that the tempo is 80 BPM
  4. Now double-click the metronome marking, select all and copy the marking. Delete the metronome marking
  5. Double-click the 'Allegretto' marking, and paste the metronome marking in afterwards

Expected behaviour:
Playback speed should now be 80 BPM

Actual behaviour:
Playback speed remains at 116 BPM

Supporting files, videos and screenshots

Image

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

4.5.2

Regression

I was unable to check

Operating system

macOS

Additional context

From a music typesetting point-of-view, it is preferable to have a (textual) tempo marking and a metronome marking incorporated into a single text object. Doing so ensures that spacing/kerning between text and MM do not change when the music is respaced, and gives us finer-grained control.

There are two suggestions here:

  1. Add a fix so that metronome markings incorporated into a tempo object are honoured
  2. Create a text object in the Tempo palette that incorporates both a word and a metronome marking, rather than splitting them out into two objects.
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.

Research direction

Start by reproducing the reported copy-and-paste sequence in MuseScore Studio and trace how tempo markings determine playback BPM. No source files, tests, or entry points are named in the issue; done means a pasted MM80 inside the Allegretto tempo object makes playback use 80 BPM, with coverage for that behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.