musescore / musescore/MuseScore
The diminuendo (text/hairpin) does not work if a dynamic mark doesn't exist at the end
@zacjansheski is already working on this.
Since Aug 6, 2024.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
General playback bug
Description with steps to reproduce
Steps to reproduce
- Create/open the score with a wind/string instrument
- Enter any note within the available range
- Add the aa dynamics to the note you just entered.
- Add a diminuendo stud after the introduced dynamics
- Click Play.
Expected behaviour
It was expected that the loudness would decrease, but this did not happen. (Even if the volume has changed, it is only by some microns, which is clearly not enough, especially at a slow tempo.)
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/baa57ac2-b035-4469-a699-cfbda69eb7fb
What is the latest version of MuseScore Studio where this issue is present?
MuseScore Studio version (64-bit): 4.3.2-241630831, revision: github-musescore-musescore-22b46f2
Regression
I was unable to check
Operating system
Windows 11
Additional context
It has nothing to do with whether the notes are tied or not. The bug works regardless of this.
https://github.com/user-attachments/assets/496e4694-2592-40ca-9be9-2c4614bd5901
I didn't just put "in a number of cases" in the title of the issue. In some cases, the diminuendo works fine (for example, if it is notated immediately after the crescendo). To be honest, I didn't have enough time to analyze in detail all the situations in which this bug can work. It is possible that along with the diminuendo, the same thing may happen with the crescendo.
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.