musescore / musescore/MuseScore
playback dynamics following arpeggiated chord are incorrect
@RomanPudashkin is already working on this.
Since Dec 9, 2023.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
General playback bug
Bug description
The first measure of my score is an arpeggiated whole-note chord. The second is a non-arpeggiated whole note chord.
Without the arpeggio marker, these chords play the same in terms of the volume, attack, and decay. With the arpeggio, the arpeggiated chord plays correctly, and the attack on the following chord seems correct, but it immediately drops in volume as if choked off (although that's not quite right as the rest of the decay continues normally, relative to the dropped volume).
Either undo-ing the apreggio marker or simply deleting it restores the correct playback of the following chord. All three arpeggio symbols (no arrows, up arrow, down arrow) have the same problem.
I initially encountered this on a complex score imported from MuseScore 3, but it was trivial to reproduce on a brand new MuseScore 4 document with just a grand piano staff.
- MacOS 12.6.6
- New install of MuseScore 4 without MuseHub (see https://github.com/musescore/MuseScore/issues/20344#issuecomment-1848646734)
- No other installs (no MuseSounds)
Steps to reproduce
- Create a new score
- Add a grand piano as the only instrument
- Add an arpeggiated chord, followed by a non-arpeggiated chord
- Play the score
Screenshots/Screen recordings
MuseScore Version
OS: macOS 12.6, Arch.: x86_64, MuseScore version (64-bit): 4.1.1-232071203, revision: github-musescore-musescore-e4d1ddf
Regression
Yes, this used to work in MuseScore 3.x and now is broken
Operating system
macOS 12
Additional context
MS Basic (I assume- I haven't installed or configured anything else and don't know anything about playback options, really)
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.