"Pavel Roskin" wrote in message
news:20130706171855.91mxat93pycg440g-ceb...@webmail.spamcop.net...
Quoting pls :
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 yo
On 06.07.2013, at 23:18, Pavel Roskin wrote:
> Quoting pls :
>
>>> 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 co
Quoting pls :
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. t
On 06.07.2013, at 22:26, Pavel Roskin wrote:
> Quoting pls :
>
>> Hi Pavel,
>>
>> musicxml2ly does not like wrong timing information.
>
> That's understandable. What's not understandable is corrupting the rest of
> the output (I mean the lilypond input, not just the pdf).
>
>> The problem
Quoting pls :
Hi Pavel,
musicxml2ly does not like wrong timing information.
That's understandable. What's not understandable is corrupting the
rest of the output (I mean the lilypond input, not just the pdf).
The problem here is that SharpEye 2 obviously has issues with its
MusicXML e
oops, note f should be assigned to 1 and note d to
2 to fix the wrong stem direction.
On 06.07.2013, at 20:58, pls wrote:
> Hi Pavel,
>
> musicxml2ly does not like wrong timing information. The problem here is that
> SharpEye 2 obviously has issues with its MusicXML export. SharpEye 2
> expo
Hi Pavel,
musicxml2ly does not like wrong timing information. The problem here is that
SharpEye 2 obviously has issues with its MusicXML export. SharpEye 2 exported
the wrong duration value in the backup element in the first measure. It also
assigned the f (half note) to the same voice as d
musicxml2ly cannot recover from some timing errors. From that point,
it stops making chords for the remainder of the score.
This is a serious problem, as no adjustments to the broken measure
made in the musicxml2ly output would fix the consecutive output.
musicxml2ly loses information abo
