[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
musicxml2ly stops making chords after some timing errors
From: |
Pavel Roskin |
Subject: |
musicxml2ly stops making chords after some timing errors |
Date: |
Sat, 06 Jul 2013 14:01:33 -0400 |
User-agent: |
Internet Messaging Program (IMP) H3 (4.1.4) |
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 about chords. The only workaround is
fixing the original musicxml file, which is tricky.
It the attached example, G and B in the second measure should be a
chord. Musescore shows them as a chord. But musicxml2ly generates
two consecutive whole notes.
The problem was observed with the actual SharpEye 2 output.
musicxml2ly is from the current development version of Lilypond.
--
Regards,
Pavel Roskin
chords.xml
Description: Text Data
lilypond.png
Description: PNG image
mscore.png
Description: PNG image
- musicxml2ly stops making chords after some timing errors,
Pavel Roskin <=