musescore / musescore/MuseScore
Tempo markings for dotted notes displayed differently if set when creating score
Nobody has claimed this yet.
- 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.
- Create a new score.
- Select any combination of instruments.
- Click "Tempo."
- Click "Show tempo marking on score."
- Select a dotted note for the tempo marking.
- Click "Done."
- Check the tempo in the top right. Is the conversion correct?
- Select the tempo marking. There should be a space between the note and the dot.
- Delete the space.
- 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):
Removing the space fixes the playback tempo:
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.