musescore / musescore/MuseScore

Bass Clarinet (Muse Sounds) Specific Incorrect Playback/Pitch

Open
#23,123 4 comments 0 reactions 2 assignees View on GitHub

@sampleeditor is already working on this.

Since Jun 11, 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

Bass clarinet playback plays the wrong pitch (half step up) when attempting to play with the following conditions:

  1. The note is concert Eb4 (works with any other instrument as long as bass clarinet is the MuseSound used in the mixer)
  2. A piano dynamic marking is added
  3. The note in question is played either after a rest or is the first note played by the user hitting play.

The playback is normal if other notes precede it, so this issue is only occurring after silences (either rests in the score or because the playback has just been started).

Additionally, if the bugged note is followed by another pitch, the correct pitch is heard briefly before moving to the second note.

I have only found this issue in the bass clarinet. Playback for the same notes is correct for other MuseSounds instruments when changed in the mixer.

Steps to reproduce

With the Bass Clarinet Muse-Sound selected in the mixer:

  1. Notate a concert Eb4
  2. Notate the note with a piano dynamic
  3. Have rests precede the note in question, or start the playback directly from this note.
  4. Hit Play
Screenshots/Screen recordings

https://github.com/musescore/MuseScore/assets/156558407/b80a7e9a-3496-45ad-b606-2d753c1acd64

MuseScore Version

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.1-241490900, revision: github-musescore-musescore-026c26b

Regression

I don't know

Operating system

Windows 11

Additional context

No response

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.