musescore / musescore/MuseScore

playback dynamics following arpeggiated chord are incorrect

Open
#20,387 1 comment 0 reactions 2 assignees View on GitHub

@RomanPudashkin is already working on this.

Since Dec 9, 2023.

playback regression MS3
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.

Steps to reproduce
  1. Create a new score
  2. Add a grand piano as the only instrument
  3. Add an arpeggiated chord, followed by a non-arpeggiated chord
  4. Play the score
Screenshots/Screen recordings
Screen Shot 2023-12-09 at 12 15 59 PM
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

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.