Hi Tina,
thanks for sharing! I quickly tried with a minimal example and it
actually works :-)
A few suggestions from my part:
- Maybe you should consider a less generic and more descriptive name
for the file "export.ily". Something like "export-mxml.ily" ?
- Would it be possible to automatically create a default output
filename based on the input liypond filename? For example "example.ly"
would generate "example.musicxml" unless \musicXMLExport
"path/file.musicxml" is specified in the lilypond source.
- Would it be possible to have the most important features enabled by
default unless specified differently? What features are the most import
can be open to discussion. But there is too big a gap between
\musicXMLAll and the current behaviour. My little test showed to me I
did get some Staffs but no notes for example if I don't specify
anything. But as the list of features will grow in future releases
there should be an easy way to (de)select a subset of them.
Anyway, it looks promising. Keep up the good work.
MT
Op zondag 22 maart 2026 om 20:52:26 +01:00:00 schreef Tina Petzel
<[email protected]>:
Hej all,
as promised here is the first non-poc version of my musicXML export
module:
<https://codeberg.org/tinapetzel/ly-mxml>
Please feel free to try it out and to report bugs you’re encounting
and features you feel are missing.
Cheers,
Tina
