Hello Pondies, just to have you know, I am working on a system for exporting musicXML. I have done a rough sketch recently for a project I was doing (the singers wanted musicXML for rehearsing parts). Once I have time I will hopefully tackle a proper implementation and put into some sort of git hosting thingy. The small 900 lines of code sketch I have works quite nicely already for sufficiently simple music, but is not too cleaned up. But I think it can be turned into quite a nice and extensible system.
My goals here are: * The system should not necessarily be super perfect, but super stable. No non-experimental inputs should lead to totally unusable results (of course only to the extent to which musicXML can encode things, after all the Lilypond language is much more expressive than musicXML) * It should be clean, well structured and easy to understand * It should be easily extensible So far none of the solutions that exist satisfy these conditions. They tend to produce corrupeted structures for fairly non-complex stuff, are very hard to actually understand and thus quite hard to extend. Will probably rewrite the proper code on weekend and share for inspection and input. Cheers, Tina
signature.asc
Description: This is a digitally signed message part.
