musescore / musescore/MuseScore

Softer dynamic affects passage with stronger dynamic in Musesounds solo brass.

Open
#21,522 2 comments 0 reactions 1 assignee View on GitHub

@matthewreadbass is already working on this.

Since Feb 14, 2024.

MuseSounds P1
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Muse Sounds bug

Bug description

When using Musesounds solo brass, soft dynamics affect the playback of preceding notes, sounding down a lower dynamic level despite the absence of hairpins or cresc./decresc. text. This behavior occurs when the passage has a rest in between, where the passage connecting to the note with the new dynamic is affected.

Steps to reproduce
  1. Open this score: https://drive.google.com/file/d/1S_msEKYnrmd6ogpJAFjzec-oZlqd5iii/view?usp=sharing
  2. Press play
  3. Observe that the passage in measure 3 plays significantly different despite having the same dynamic as measure 1. It seems to be affected by the dynamic marking in measure 4. The same things are occurring to measures 6 and 7.
Screenshots/Screen recordings

OBS recording of the bug:

https://github.com/musescore/MuseScore/assets/102687285/ebce1772-9a84-4226-9326-a3e0c6aaa650

(Apologies for the lower audio quality. I compressed it to fit into github import)

MuseScore Version

4.2.1

Regression

I don't know

Operating system

Windows 11

Additional context

I do not recall hearing this in previous versions of Musescore 4.x, but I don't have previous versions of Musesounds to confirm.

For clarification, the bug is reproducible despite reproduction steps needing to open an example score.

UPDATE: Upon further testing post-OBS recording, I can confirm that Musesounds Bass Trombone, Cimbasso, and Tuba is also affected by this bug.

None occur with MS Basic.

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.