Export .xml from Digital Performer problem
Hi there,
I export .xml files from Digital Performer latest version, open it with Sibelius 7.5, no problem.
I open it with MuseScore 2 and I get the message you see on the attachment.
MuseScore does open the file anyway but what is called on DP "conductor track", which it holds tempo changes and markers, it is not imported properly and it is always 1 bar late. Unfortunately I don't know how to shift all those info on the right place.
Any idea? Thank you
Best
Danilo Madonia
http://www.danworks.it
| Attachment | Size |
|---|---|
| Screen Shot 2017-05-13 at 14.41.29.png | 43.05 KB |
Comments
Ciao Danilo, benvenuto.
Attaching the file would help ;-)
edit____
2? Not 2.1?
In reply to Ciao Danilo, by Shoichi
Ciao Sochi,
I've attached the file, I can actually see it.
Yep, v2.1 …
Just in case you cannot see it , here we go:
"Fatal error: line 3825 column 21 Content of element beam does not match its type definition:
String content is not listed in the enumeration facet …"
Whatever it means :)
Best
In reply to Ciao Sochi, I've attached the by danworks
You've attached a png file, not the xml file. But attaching the xml file would be helpful to investigate the error message in line 3825.
In reply to You've attached a png file, by kuwitt
Ok, got it :)
Tomorrow as soon as I'm studio I'll send you the .xml.
By the way, FYI every .xml file created with DP show this error.
Best
In reply to Ok, got it :) Tomorrow as by danworks
But open it with Sibelius and export as XML?
Regards.
In reply to But open it with Sibelius and by Shoichi
Yes, it would be interesting to have both: the xml file of digital performer and an exported xml file of the same file with Sibelius, to investigate, if it's is an export error of digital performer or an import error of MuseScore.
In reply to Yes, it would be interesting by kuwitt
Hi there,
here you have two .xml file of the same project:
#1 created with Digital Performer: it opens with MuseScore 2.1 showing a warning error message, but it flawlessly opens with Sibelius 7.5.
#2 is the very same .xml file created with DP, opened with Sibelius 7.5 and re-exported to .xml. Now MuseScore 2.1 doesn't show any problem to open it.
Hope it helps ...
Best
In reply to Hi there, here you have two by danworks
It seems DP uses '<beam number="1">start</beam>', where MusicXML expects/mandates '<beam number="1">begin</beam>', so this seems a bug in DP.
Looks like Sibelius is tolerating this silently (or doesn't do a proper evaluation at all) and correctly exports.
Attached a fixed xml
In reply to It seems DP uses '<beam by Jojo-Schmitz
Hello Jojo,
that's interesting. Would you think that MuseScore could find in the future a workaround to tolerate this issue a-la Sibelius, or should I contact MOTU folks and inform them about it?
By the way, if that's the only thing, for now can I edit the .xml and substitute that "start" string with the "begin" one, right? Thank you …
Best
In reply to Hello Jojo, that's by danworks
In MuseScore just ignore that error and load the file anyway.
MuseScore could partially fixed to accept "start" and understand/turn into "begin", although I believe it does that somehow anyway internally, but that wouldn't change that error message, as that is generated by the XML validator, which validates against the MusicXML standard and is run bevore MuseScore itself reads and interpretes the XML.
Reporting to the vendor of program producing that invalid XML is the only way to get this fixed for real.
In reply to Hello Jojo, that's by danworks
If DP is violating the standard, they should definitely be informed.
In general, we don't go out of way to accept all the various forms of incorrect MusicXML that could possibly exist - this would be impossible to maintain as there are probably hundreds of such errors to deal with. It is better to focus efforts on doing the best we can of supporting correct MusicXML.
In reply to If DP is violating the by Marc Sabatella
Hi there,
I'll definitely inform the MOTU guys, thanks.
Best