import .xml no longer works

[tohubohu38]

Issue type

Import/export issue

Description with steps to reproduce

pitch is no longer imported. Notes are all at the same pitch.

Supporting files, videos and screenshots

dfdf

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

musescore 4.5.1

Regression

Yes, this used to work in a previous version of MuseScore 4.x

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

[Jojo-Schmitz]

Sample .xml file needed, the .xml files I tried it with just worked

[tohubohu38]

un jardin extraordinaire.zip

[tohubohu38]

it doesn't work

[Jojo-Schmitz]

Confirmed!

For some reason it seems to get imported as a drum staff, but with a treble clef

[MarcSabatella]

It seems to be missing anything that could help identify what instrument it is meant to be. But drums are probably not the best fallback in that case

[Jojo-Schmitz]

(1.3, 2.3.2 and) 3.6.2 imports as "channel 1" and plays with piano sound , same for 4.3.2, while 4.4.4 imports it as woodwinds and plays accordingly (flute?), 4.5.1 - 4.6-dev imports it as triangle and plays as percussion.

Encoding software: REAPER 7.35/x64
The apparently problematic instrument/part list:

  <part-list>
    <score-part id="P1">
      <part-name>Piste 1</part-name>
      <score-instrument id="P1-C1">
        <instrument-name>channel 1</instrument-name>
      </score-instrument>
      <midi-instrument id="P1-C1">
        <midi-channel>1</midi-channel>
      </midi-instrument>
    </score-part>
  </part-list>

Changing instrument to Flute or Piano, or whatever brings the notes back to their pitches and plays OK

The chord symbols are imported as staff text, in all versions (well, my 3.7 imports them as chord symbols!?!)

[MarcSabatella]

The chord symbols are definitely expected to just be text - they aren’t encoded as Harmony elemwnts

[Jojo-Schmitz]

Yet they are 'infered' as chord symbols in my 3.7. I like it ;-)

[MarcSabatella]

How do you differentiate? Run every potential staff text element through the chord symbol parser to see if it's possible to understand it as a chord symbol, and if so, go ahead and import it as a Harmony element instead of staff text? I guess that means a staff text consisting of the word "am" would be seen as a chord symbol? Probably not a problem in practice...

[Jojo-Schmitz]

No idea. It doesn't recognize them all, like none of the slashed chord symbols. Doesn't seem to happen inside the MusicXML import

[tohubohu38]

I wrote the chords in text insertion

[Jojo-Schmitz]

OK. But this isn't the issue at hand here. The pressing issue is the mis-detection as a triangle staff

[tohubohu38]

ok it's important to fix the xml import because it's unusable whereas everything worked fine before :)

[Jojo-Schmitz]

(Also) Try to get Reaper to fix their MusicXML export, not properly naming the intended instrument is ... crap.

[MarcSabatella]

Definitely it would be good to try to address. But to be clear, it's not "unusual" because it's a somewhat incomplete MusicXML file, missing the instrument-sound tag that normally provides information about what instrument to use. It's very easily fixed within MuseScore by changing the instrument to anything pitched (piano, flute, etc - whatever you'd like to hear for playback).

Doing a little experimentation, it appears that in the absence of an explicit instrument-sound tag that would specify the instrument to use unambiguously, MuseScore is asttempting to guess what instrument to use from the instrument-name tag - which in this case is set to "Channel 1". If I change it to soemthing specific like Flute 1, I get an actual flute instrument. If I change it to random garbage, I get random garbage. I assume probably there is an algorithm that is desperately try to match, but either it is too eager to succeed and matching something inappropriate, or else the fallback when no match is found is not defined (should probably be piano).

And yes - as @Jojo-Schmitz says, also Reaper should fix their MusicXML output - or you should see if there is an option to include the instrument-sound tag.

[tohubohu38]

Could you tell me exactly what I need to ask REAPER cockos, please? I didn't quite understand.

[MarcSabatella]

Tell them that in their MusicXML export, they should include an instrument-sound element within their score-instrument elements so that importing programs have a way of knowing what instrument to use. The list of sounds is in https://www.w3.org/2021/06/musicxml40/listings/sounds.xml/. My understanding is that they shouldn't actually include the "sound" tags in their output - that file is just listing the values to use within "instrument-sound" tags.

[tohubohu38]

I have sent
1 chance in 10 that they will fix in my experience. We'll see. If you don't hear from me, they haven't fixed it.
Thanks