Incorrect mapping of Drumset instruments when exporting to XML

Bytheburn commented 6 months ago

Issue type

Import/export issue

Bug description

When exporting XML (compressed or uncompressed) from MuseScore 4 (OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433) the drum mapping is completely out of wack (not just transposed). Tested by importing into Reaper. Exporting to midi the mapping is spot on: Github apparently won't let me attach the files xml or midi files so find attached zip... BRN-Kick+Snare+hiHat.zip

Steps to reproduce

Create one bar loop using Drumset.
Export it using Music Xml (compressed or uncompressed)
Import it into your Daw (Reaper in my case) 4) Play loop/examine midi to see mapping is all wrong 5) Do the same but Exporting to midi then importing to DAW and the mapping is correct

Screenshots/Screen recordings

MuseScore Version

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433

Regression

Choose option...

Operating system

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433

Additional context

No response

TeeDeeY commented 6 months ago

When I was using MusicXML from Musescore into Logic, I noticed a one-octave difference in drum set. I can’t remember exactly what I did, but in Musescore, first I changed the “drumset” into Timpani (from unpitched to pitched percussion). Then, I selected the entire Timpani staff and did a one octave move. I forgot if it was up or down, so I suggest trying both ways. Then, export to MXL. Then import into the third party program. If your third party program allows the drum set to be transposed, I would try that as well.

rettinghaus commented 6 months ago

Probably the same cause as in #21301 and #20283.

Bytheburn commented 6 months ago

"If your third party program allows the drum set to be transposed, I would try that as well"

That was the first thing I tried but, sadly, as you can see from the Reaper Screenshots, it's not just a transpose issue. Checking out the other comments (it's good to see such prompt responses from any community) it seems there may be workarounds and possibly it didn't happen in vs3 but it's defo a bug(?)

rettinghaus commented 6 months ago

@Bytheburn It seems that this is not an issue with MuseScore but with Reaper.

I investigated the exported file, and the MusicXML is exactly as in the specification:

<note default-x="743.20" default-y="5.00">
  <unpitched>
    <display-step>G</display-step>
    <display-octave>5</display-octave>
  </unpitched>
  <duration>1</duration>
  <instrument id="P1-I43"/>
  <voice>1</voice>
  <type>eighth</type>
  <stem>up</stem>
  <notehead>x</notehead>
  <beam number="1">continue</beam>
</note>

But looking at your screenshots Reaper seems to interpret the display-step and display-octave elements as actual pitch information. You should report this problem to them.

musescore / MuseScore