You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rendered normally with Lilypond, the result is this:
When converted to MusicXML using python-ly, the resulting MusicXML looks like this (rendered using MuseScore):
I can confirm that this visualization matches the underlying XML, I'm including the image only because it's easier to see the discrepancy. So, it appears that when converted to MusicXML, this piece produces the correct melody, but with two major problems (ignoring the double-bar line becoming a measure, which seems like a separate problem):
It contains none of the accompanying chord symbols.
There are additional measures beyond what is written that contain additional whole and half notes at the end of the piece (this is confirmed by looking at the raw XML). These notes seem to correspond to the roots of the chords that were specified in the chord block.
During conversion from ly to xml, the following repeated errors are reported (this is just a snippet, they appear repeatedly, presumably once for each chord symbol in the original):
...
Warning: ChordSpecifier not implemented!
'ParseSource' object has no attribute 'ChordSpecifier'
Warning: ChordItem not implemented!
'ParseSource' object has no attribute 'ChordItem'
Warning: ChordItem not implemented!
'ParseSource' object has no attribute 'ChordItem'
Warning: ChordSpecifier not implemented!
'ParseSource' object has no attribute 'ChordSpecifier'
Warning: ChordItem not implemented!
'ParseSource' object has no attribute 'ChordItem'
Warning: ChordItem not implemented!
'ParseSource' object has no attribute 'ChordItem'
Warning: ChordSpecifier not implemented!
...
The text was updated successfully, but these errors were encountered:
I appreciate this, as I'm interested in Chordnames export functionality as well.
I would add also that attempts to render notated polyphony (as opposed to chord sysmbols) via \chordmode input produces the same sort of undesired xml output as above. So, in lilypond,
\new Staff \new Voice \chordmode { g:7 }
will produce four pitches ( g, b, d, f) on the staff without a problem, but xml export is not yet capable of interpreting the same expression, it seems.
Here is a Lilypond file that produces a staff with a melody and annotated chord names above the staff:
Rendered normally with Lilypond, the result is this:
When converted to MusicXML using python-ly, the resulting MusicXML looks like this (rendered using MuseScore):
I can confirm that this visualization matches the underlying XML, I'm including the image only because it's easier to see the discrepancy. So, it appears that when converted to MusicXML, this piece produces the correct melody, but with two major problems (ignoring the double-bar line becoming a measure, which seems like a separate problem):
During conversion from ly to xml, the following repeated errors are reported (this is just a snippet, they appear repeatedly, presumably once for each chord symbol in the original):
The text was updated successfully, but these errors were encountered: