[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: musicxml2ly stops making chords after some timing errors

From: Phil Holmes
Subject: Re: musicxml2ly stops making chords after some timing errors
Date: Sun, 7 Jul 2013 10:58:58 +0100

"Pavel Roskin" <address@hidden> wrote in message news:address@hidden
Quoting pls <address@hidden>:

I don't care how the faulty markup looks. But MuseScore got the second measure right. It could recover and musicxml2ly could not.

that's because of the faulty MusicXML markup you provided. the first measure contained the duration of five quarter notes instead of four. that's why all the following measures were affected.

Oh well, this puts me between the rock and the hard place. musicxml2ly cannot deal with MusicXML errors reliably. On the other hand, MuseScore can read broken MusicXML but makes broken Lilypond output (missing braces).

One possible approach is to open and save MusicXML in MuseScore and then use musicxml2ly on the saved file. I checked it quickly, the chords are not lost, but I need to see if anything else is preserved.

I don't know how to persuade you that musicxml2ly could and should do better.

Pavel Roskin

Surely the correct approach is to ensure that the output from Sharpeye is correct. This can often be done by adding extra rests (which you subsequently delete/replace with spacers). Is Sharpeye warning of timing errors?

Phil Holmes
Bug Squad

reply via email to

[Prev in Thread] Current Thread [Next in Thread]