[LilyPond] Bar lines and repeats appear prematurely

• Jun 23, 2011 - 12:19
Type
Functional
Severity
S4 - Minor
Status
by design
Project

Hi,
when I export to Lilypond format, the bar lines and repeat marks
I insert (from the bar line palette) move and appear one bar too early.
Exporting to MusicXML first and then converting to lilypond format
via musicxml2ly works fine.
MuseScore 1.0 on Ubuntu and Nightly Build r4414 Windows 7 both
show the bug.
I have attached a small example.

Thanks!
dj

Attachment Size
barline-test.mscz 1.61 KB
barline-test.ly 2.97 KB

Comments

To be more accurate, the bar line does appear at the end, but there's a duplicate one in the bar before (see image ).

It's might be hard to know if some bugs are a fault of Lilypond, or MuseScore.

Using MuseScore 1.1 and Lilypond 2.14.2 - Mac 10.6.8.

Actually, it appears twice in the same bar (not in the previous one) - I didn't look at it closely.

After doing some tests, a score with an anacrusis and:

Multi-voice rests - no extra bar line.
Deleted multi-voice rests - extra bar line.

I think any other score has problems.

Attachment Size
Rests Intact.zip 38.09 KB
Rests Deleted.zip 37.8 KB

With Nightly Musescore 2.0 build 5262 most problems disappear. All repeat marks correct, even codas! Only the problem with the doubled end bar remains.

The bug is also present in MuseScore 1.2 Revision 5470.

I have confirmed in the Lilypond output source that the problem is on MuseScore's end.

MuseScore also misplaces repeats in LilyPond's output when the repeats are supposed to fall in the middle of a measure.

The attached file "30b.xml" renders fine in the MuseScore interface. Printing it in the MuseScore interface produces the correct output, as shown in "musepdf.pdf". The Lilypond output is shown in "30b.ly" and a PDF copy in "lilypdf.pdf". The LilyPond source clearly shows the repeat beginning and ending in the wrong place, as confirmed by the LilyPond PDF output.

Attachment Size
30b.xml 56.08 KB
musepdf.pdf 19.81 KB
30b.ly 5.68 KB
lilypdf.pdf 67.21 KB

Thank you, lasconic.

I have looked at musicxml2ly and will probably begin using it. But MuseScore does provide the option of saving a file to LilyPond's format, so my expectation, as a user, is that said option will work. Especially when every other aspect of that export option seems to be fully functional. I appreciate the work-around, but I don't think it's really a solution.

I notice that one of the previous commentors says that this is fixed in MuseScore 2, but the bug is still marked as unresolved. Hence, my visit here.

I installed the 2.0 nightly build (windows) in order to get this problem solved, but the current revision (15c1263 from 2013-03-29) does not even provide a lilypond export possibility.