Add configuration item for midi-unpitched elements in MusicXML Import & Export

• Dec 6, 2015 - 20:41
Reported version
2.1
Type
Functional
Severity
S5 - Suggestion
Status
won't fix
Project
MuseScore

For unpitched instruments like used in the drum map, the midi-unpitched element specifies a MIDI 1.0 note number ranging from 1 to 128. Unlike the MusicXML specification, MIDI 1.0 note numbers are generally specified from 0 to 127 rather than the 1 to 128.

Although Musescore is doing the correct decoding / encoding of this element according to MusicXML specification, other Software like Guitar Pro encodes the elements of the drum map zero based, that is from 0 to 127.

It is requested to ad a configuration checkbox to allow switching between zero base and one-based mapping of midi-unpitched elements. The configuration shall be used for decoding and encoding of MusicXML files.

Comments

• Dec 7, 2015 - 03:00

Do I understand correctly that you request the addition of an option in MuseScore to adapt to a bug in GP and to export ill formatted MusicXML?

Reply

• Dec 8, 2015 - 07:25

Well, I guess that's the bottom line. There are surely enough arguments to reject this request, but think of it as a way to enhance connectivty between applications, which is the primary mission of MusicXML.

Instead of a check box it could be done as a configurable offset for midi-unpitched notes. The default if value is null / zero or missing resulting in correct [1...128] output according to MusicXML defintion. The GP bug could be circumvented configuring a value of '-1', resulting in [0...127].

Maybe this would be more transparent compared to a check box named "provide ill formed XML" ;-)

Reply

• Dec 16, 2015 - 22:17

I tryed, but the request was not filed as I don't have a GP license myself. I will ask my friend (the one I'm exchanging GP generated XML files with) to do so.

We meanwhile arranged with the situation and replace the midi-unpitched elements in a text editor, so don't waste your time with this request.

BTW: I get the "same" - or maybe just similar - problem when I import native *.gpx files. All drum sounds are wrong, however I didn't check if it's the same " midi note minus one" shift as for XML import.

Reply

• Dec 16, 2015 - 22:32

I just check between native gpx and GP generated MusicXML. The shifts are different.

GP MusicXML: bass drum sounds like triangle
Native *.GPX: bass drum sounds like some percussion drum, I don't know the name

I guess the gpx file is not shifted but simply uses a drum map different to General Midi.

Reply