Cannot export to lilypond

You should save files in MuseScore's own format. See [[nodetitle:export]] for details. Lilypond import is very experimental.

If there is a developer interesting in improving Lilypond import in MuseScore then we'll leave this active. Otherwise maybe we should close as "won't fix" to keep the list of bugs manageable.

I guess the bug report was not about lilypond import but export. The lilypond file created with MuseScore attached to the main issue can't be processed by lilypond.
Regarding import, my opinion is that it should be remove from the import list option.

I guess there will be no usable lilypond import in the near future and i removed "*.ly" form the import option list.

For a lilypond export bug it is more helpful to include the original MuseScore file (.mscz or .mscx). Better yet are you able to narrow it down to a particular score element that is causing the problem?

It turns out there's lots of elements that are causing problems:

• Staff text that includes "#" needs quotation marks around it in lilypond (Fixed in r.2026)
• The 8va signs should be exported as "set-octavation" but were misspelled "set-octaviation" (Fixed in r.2026)
• When a dynamic marking and 8va sign occur on the same note the dynamic marking should be first (Bug filed )
• Instrument names that include non-ASCII characters can cause errors when exported to lilypond (needs more investigation).

[duplicate comment]

Hi,
I have improved lilypond export at little. The file exported from your mscore-file will now be compiled by lilypond. There are however some unsolved issues. (Rome was not built in one day; Ars longa, vita brevis)
* Ottava: lilypond export looks for the anchors of the ottava-brackets/lines. You have, so far as I can see, stretched the lines far beyond the notes to which the start and end of the line is anchored. To take account of the extension of the lines in mscore in addition to the anchor-notes is a project of the future. This appertains also to hairpins and other lines.
* grace-notes immediately after new timesignatures, repeat-signs and other barlines makes erroneous and unpredictable results. This is a bug in lilypond, and for now I will not try to remedy it in lilypond-export. See lilypond notation reference chapter 1.2.6 for lilypond 2.12.1.
* multiple dynamics on one note is discarded by lilypond. The remedy is to insert an invisible rest, and attach the second dynamic to this. This means that the length of the measure is extended, and so this invisible rest must be inserted in all the other staffs in the same measure. There is no fast way to program this in exportly, so the solution to this must be postponed for now.
* lyrics still not implemented.
Regards, Olav Gundersen

When I try to save Cronicas.mscz as a LilyPond file MuseScore crashes.

(Tested using r. 2348 nightly, Windows XP)

hi,
sorry for that, I uploaded the file to early. It was so on linux too.
In r2351 compiled on ubuntu, it exports the mentioned file without crash. But there are difficulties with flageolets seemingly anchored to the uppermost staff, and then dragged down to one of the lower ones, at approx bar 13.
Olav Gundersen

It still crashes for me on r.2351 nightly, Windows XP.

Export of Cronicas.mscz no longer crashes in r. 2415 nightly (Windows XP)

The root cause of octava lines anchoring to the wrong note is a result of a MuseScore bug: http://www.musescore.org/en/node/2846

Lyrics are implemented now.

I open new bug reports for a couple remaining issues I spotted:

• LilyPond: Fermatas over full measure rest not exported (Cronicas: m. 35)
• LilyPond: Staff text and dynamic on same note (Cronicas: m. 1 violincello, and m. 32 violincello)

Automatically closed -- issue fixed for 2 weeks with no activity.