> Pedro: > I see. data exchanging is allways good, that's for sure. anyone knows > how is the read/write support for MusicXML in finale, sibelius, and > others?
Both of the two mentioned can import and export musicXML with Recordare's "Dolet" plugin (technically the transformer for Sibelius uses macros, so it's not really a plugin.) And there are a couple other ones. Check http://www.recordare.com/software.html for others. Lilypond is also on the list of the ones which can use musicXML as input. I have to admit that it is only partially true: xml2ly xslt stylesheets convert between previous versions of both musicXML (somewhere 0.7) and Lilypond (somewhere 1.7). A python xml2ly converter (using the python SAX interface) was also built, with which I successfully converted 2/3 of the musicXML test suite files (by using convert-ly --from=1.9.3 of course). > I haven't look at MusicXML in ages, so I don't know how it's doing now. > i'd curious to know if it saves "tweeks" or just the "basic" data > representation. MusicXml is 1.0 now for a year. Michael Good of Recordare actively works on 1.1 in these days. Some of the proposed features are (from the musicXML mailing list): harp pedal diagrams scordatura tunings fanned beam color for individual items etc.etc there are other changes I couldn't get... For the 1.0 there's a "MusicXML elements, attributes, and entities in alphabetical order" - if it makes some sense - at here: http://www.recordare.com/xml/musicxml-index.html -- rpd _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
