I very much welcome any effort in this direction. Sounds good.
But ... I have seen several attempts and announcements to better support MusicXML export for LilyPond over the years in this mailing list. And after a promising start and even usable first implementations very often the development slows down.

MusicXML export support for LilyPond seems to be a tricky thing to tackle and to maintain and debug. Many people (including me) will be tempted to say "Yes I want that NOW!" but in reality just let's wait and see, or - if you can - help coding and contributing.

MT




Op donderdag 12 maart 2026 om 10:11:55 +11:00:00 schreef Vaughan McAlley <[email protected]>:
This sounds great, Tina!

Personally, being able to reliably export one-part-per-line choral music would be a huge benefit for me. I usually import and export with MIDI, and it is the lyrics that have to be redone.

Vaughan


On Wed, 11 Mar 2026, 10:05 Tina Petzel, <[email protected] <mailto:[email protected]>> wrote:
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

Reply via email to