musescore / musescore/MuseScore

Tempo markings for dotted notes displayed differently if set when creating score

Open
#28,550 7 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving 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

When setting a tempo marking with a dotted note as the beat while creating a score, a space is placed between the note duration and the dot. This space is not present if a tempo marking is inserted from the left panel, and it appears to prevent MuseScore from recognizing it as the tempo for playback.

  1. Create a new score.
  2. Select any combination of instruments.
  3. Click "Tempo."
  4. Click "Show tempo marking on score."
  5. Select a dotted note for the tempo marking.
  6. Click "Done."
  7. Check the tempo in the top right. Is the conversion correct?
  8. Select the tempo marking. There should be a space between the note and the dot.
  9. Delete the space.
  10. Check the tempo in the top right again.
Supporting files, videos and screenshots

Upon creating the score, there is a space between the quarter note and the dot, so the playback tempo is incorrect (dotted quarter note = 120 should mean that quarter note = 180; instead, it defaults to 120):
Image

Removing the space fixes the playback tempo:
Image

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

OS: Windows 11 Version 23H2 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.6.0-251490320, revision: github-musescore-musescore-1dccd0a

Regression

No.

Operating system

Windows 11

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

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.