[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
issues with musicxml2ly
From: |
Gilberto Agostinho |
Subject: |
issues with musicxml2ly |
Date: |
Sun, 9 Jun 2019 18:34:42 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 |
Hello bug-squad,
I ran into three issues when converting a .musicxml file generated with
MuseScore into LilyPond:
1) the .ly file outut by musicxml2ly seems to have a weird encoding and
outputs an error. There are many hidden characters which I had to remove
manually in order to compile the .ly file.
2) slur placement is not taken into account. The entry below has the
argument placement set to "below" but musicxml2ly outputs it as a
standard pair of ( ) instead of _( _)
<notations>
<slur type="start" placement="below" number="1"/>
</notations>
3) MusicXML contains information about al niente hairpins but music2xml
does not use those. Perhaps this feature could be added? This is how the
.musicxml looks like:
<direction placement="below">
<direction-type>
<wedge type="diminuendo" number="1" default-y="-75.00"/>
</direction-type>
</direction>
[...music under which the hairpin is...]
<direction placement="below">
<direction-type>
<wedge type="stop" niente="yes" number="1" relative-x="16.00"/>
</direction-type>
</direction>
Cheers,
Gilberto
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- issues with musicxml2ly,
Gilberto Agostinho <=