musescore / musescore/MuseScore

Percussion Kit Changes w/ VDL and Muse Drumline causing notes to default to hit sounds on snare

Open
#27,205 2 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Mar 19, 2025.

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

Description with steps to reproduce
  1. Create a score with Marching Snare Drum.
  2. Change sounds in Mixer from MS basic to Either Muse Drumline or Tapspace Virtual Drumline.
  3. Go to area where drumset layout / drumkit layout is.
  4. Change the notehead design and/ or staff spacing on any snare drum, note. (I.E> Change Rim Shot to have a standard cross note head instead of an ornate X note head and move the note down 1 space.
  5. Place note that had a changed layout/design.
  6. Play
    Actual Behavior: Note that is meant to be a rim shot, or any other note that is not a normal snare hit that had it's notehead or staff position changed will playback as a normal snare hit unless the pre-programed design / layout is followed.
    Expected Behavior: sound that is meant to be played will be heard in playback as the intended sound while retaining the design and layout specifications I chose.
Supporting files, videos and screenshots

Playback issues.zip

What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.0-250721848, revision: github-musescore-musescore-7c55023

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Windows 11

Additional context

No response

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

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.