Large Drum Kit not retaining entire drum map

[chunga2020]

Issue type

Opening/saving issue

Description with steps to reproduce

1. Create a Drum Kit (Large) instrument
2. Enter some music
3. Save and quit
4. Return to the score
5. Repeat Steps 2–4 until the Drum Kit mapping is that of a minimal kit. I haven't figured out precise causes.

Expected behavior: the drum kit should retain the mapping of the large kit
Actual behavior: the kit mapping becomes that of the "Drum Kit (Minimal) instrument"

If I view the Staff Properties for the drumset staff, the instrument is still identified as "Drum Kit (Large)". Attempting to use the Instruments menu to reassign the large kit results in MU4 crashing.

I also unzipped the score and peeked at the source code, confirming that the mapping was not just a visual error.

Supporting files, videos and screenshots

batcountry.zip

Sorry for the large score; trying to recreate this is proving difficult, and this is the only score that I currently have on hand demonstrating the issue.

This score is a transcription of an Ultimate Guitar "Official" tab; I do these transcriptions to be able to see a full score for context while practicing. Below is a snippet of said tab's drum part, with multiple toms clearly notated in beats 2 and 3 of each bar.

Back to the MU score, notice that the playback of bar 22, beats 2 and 3, has the sounds of the toms from the large kit, as expected, but the notation is wrong. Entering drum input mode shows only the drums from the minimal kit.

Curiously, switching from Muse Sounds to MS Basic playback returns the "large kit" mapping, and vice versa—not that it does anything for the score, which has already been messed up.

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

OS: Arch Linux, Arch.: x86_64, MuseScore Studio version (64-bit): 4.6.0-250690300, revision: github-musescore-musescore-f32615b

Regression

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

Operating system

Arch Linux, kernel 6.13.5-arch1-1

Additional context

For the Regression data: I used to modify the default drum mapping so that each tom was on its own space, and I never had any issues with the drum map reverting. I have not done that is some time, however, so I chose the best answer I could.

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

[zacjansheski]

I'm guessing this has to do with the MuseSounds "Drum Kit" being selected rather than the "Big Kit"

Is your Muse Percussion Library up to date? (What version do you have?)

I don't reproduce a crash on replacing instrument either, if that is reproducible it might be worth opening a separate issue for that.

[chunga2020]

My Muse Percussion library is at version 0.6.1

[zacjansheski]

And you are unable to assign the "Big Kit" instrument, did you manually assign the "Drum Kit" as some point?

[chunga2020]

I started it as a "Drum Kit (Large)", and so it used the "Big Kit" sounds by default, as expected. However, I'm not a huge fan of the instrument volume balance in the "Big Kit", especially for the style of the music (hard rock), so I used the Mixer to assign the "Drum Kit" sounds instead, which I found more appropriate.

[zacjansheski]

That kit only has 3 toms. Hence the remapping

[chunga2020]

Understood. Dug through the MS Basic kits and found one that sounds good enough. Sorry to take up your time.