Voices 1&2 exchange places when exported to LilyPond

• Nov 8, 2010 - 17:33
Type
Functional
Severity
S4 - Minor
Status
won't fix
Project

Operating System: Windows XP-sp3
MuseScore Version: 0.9.6.3, LilyPond Version: 2.12.3

In the attached piece something breaks the voice 1 / voice 2 association between MuseScore and LilyPond with the result that when imported into LilyPond all voice 1 notes have their stems pointing down and voice 2 notes have their stems pointing up - resulting in overlapping stems and multitudinous "clashing note column" warnings.

I tried exchanging voice 1 and voice 2 notes before exporting (in the hope that the transfer would swap them back) but it did not work any better. It may be that this particular piece messes up because both voice 1 and voice 2 start on the same note?

In any case in order to get LilyPond's voice 1 and voice 2 stems pointing the right way I found it necessary to explicitly and manually add "\voiceOne" and "\voiceTwo" commands within each voice's note-string parentheses {}.

Attachment Size
TheChristmasChildPiano.mscz 4.49 KB

Comments

In order to achieve more comprehensive support for voices in LilyPond export, do you have any idea what the adeste.mscx demo score would look like as a .ly file? Can LilyPond do this (i.e. have one voice in some measures but multiple voices in other measures)?

Your score is simple because there are two voices per staff for every measure for the full length of the score. However this is more of an exception rather than the norm for solo instruments such as the piano.