Re: MusicXML issue

Dear Christina,




I have to agree with Adrian.




All existing sheet-music-editors have inconsequences in their musicxml-exports. However, lot’s of the time it’s not the problem of the editing-software itself, it’s the person who is using the software in a wrong way to input his content. When this “engraver" is using a “text”-tool while he/she should have been using the “fingering”-tool, nobody can do anything about it until somebody invents an unambiguous UX-toolbox for common mistakes like this :-)




How do we (try to) solve this?

Over the last couple of years we have been developing our file-import-process in multiple steps. The first step we like to call our “Sanitizer”. It “validates” the imported musicXML and tries to detect and solve inconsequences based on the semantical meaning of all items it contains.




If you like to try it yourself, please visit http://www.musicxmlsanitizer.io. It actually is our first step for importing a musicxml-file into neoScores. It is in continuous development so please come back regularly. It’s our intention to expand this “service” to become some kind of musicxml-validator like the w3c Markup Validation Service https://validator.w3.org/




Unfortunately the fingering-issue can’t be solved directly from just an xml-file because there simply isn’t enough data to be sure it’s a fingering.




All the best,





Bob Hamblok

M bob@neoscores.com
T +32 476 74 78 42
W www.neoscores.com













On Monday, Aug 10, 2015 at 5:05 PM, Adrian Holovaty <adrian@holovaty.com>, wrote:
On Sat, Aug 8, 2015 at 9:59 AM, No-C-Notes Music <xinamusic@no-c-notes.com> wrote:
My question is if MusicXML export is the same for all software and apps that use it?  Is the MusicXML export the same from Sibelius as it is from Finale?





(Hollow, weary, world-worn laughter)




No, the MusicXML generated by Sibelius is not the same as it is from Finale.. It's often quite different, frustratingly. Same goes for the MusicXML generated by MuseScore and Notion -- they are all different.




This is the number one pain point in dealing with MusicXML. A large part of my own MusicXML importer (for Soundslice) deals with smoothing over the vendor differences.





The issue I have is with fingering, that it is linked to the printed score as <notations> <technical> and not a note <note> in the music software I am using.  When there are two or more notes played together, the fingering MusicXML treats it as a print location instead of a <note> type such as <pitch> or <type>.




Is this because of the software I am using or is it the MusicXML?  Or do I need to create a new <note> schema in my music notation software that will export fingering as part of <note>, and if I do does it need to belong to the W3C??






I've been wrestling with MusicXML fingering differences quite a bit over the last month. Several applications put fingerings in <words> elements -- losing the semantics of fingering -- which I believe is what you're running into.




In my experience, MuseScore does the best job here: it associates fingerings with the individual notes, so when you have stacked fingerings (two or more notes played together), it does the right thing. I haven't been able to get Sibelius or Finale to do the right thing here; generally they use <words> elements for fingering.




Hope this is helpful,

Adrian




--

Adrian Holovaty

Soundslice: https://www.soundslice.com/


Personal: http://www.holovaty.com/