|
From: | Mats Bengtsson |
Subject: | Re: bar command |
Date: | Sun, 19 Feb 2006 19:54:43 +0100 |
User-agent: | Internet Messaging Program (IMP) H3 (4.0.4) |
If you had included also the next bar, it would have been obviouswhy this happens, namely that the next bar is the beginning of a repeat. Imagine first the situation where there is no line break
here, then the bar line would have to be a "|:" to show the start of the repeat. This explains why the "|:" of the repeat overridesthe "||" you have inserted manually (I don't understand why you also specified the "|:" manually, it's done automatically by the \repeat command). At line breaks, LilyPond has a built-in rule saying that if a "|:" happens at a line break, then it should print an ordinary bar line at the end of the first line and the "|:" at the beginning of the next line.
However, since your situation isn't that uncommon, there is actually a solution. Unfortunately, I cannot find it in the documentation, though. The trick is to specify \bar "||:"
directly after the \repeat command. This will translate into a "||" before the line break and "|:" at the beginning of the next line. To summarize, use: ... \grg f8 e8 c8 \grg c8 d8 e8 \break \repeat volta 2 { \bar "||:" \grg f4. _\markup { return to 3rd part } ... /Mats Quoting Stuart Lowe <address@hidden>:
Hi Folks,I'm doing a harmony for a 6/8 jig. All the parts have eight bars and are repeated,save for one, which has eight bars but is to be played only once. the part in question looks like: \grg f4. _\markup { return to transition - once over } ( f4.) \hdblg g4. ( g4. ) \dblA A4. ( A4. ) f8 e8 f8 \dbld d4 e8 \break \grg f4. ( f4. ) \hdblg g4. ( g4. ) e8 A8 e8 A8 f8 e8 \grg f8 e8 c8 \grg c8 d8 e8 \bar "||" \breakThe problem is that the generated (pdf) file does not show the ' \bar "||" ' - it only comes out as a single bar line.Note that I'm using a multiple (different) \bar commands within the score (attached) and perhaps this is what is causingthe problem.I'm using GNU LilyPond 2.6.4 on Fedora Core release 4. The bagpipe.ly file is standard except for the additionof some embellishments I've added. Any thoughts would be much appreciated. Regards, Stu. -- Stuart Lowe | Toronto, CAN | key ID on keyserver | Skype stuart.loweFedora Core release 4 (Stentz) GNU/Linux kernel 2.6.11-1.1369_FC4 on i686 localhost3.localdomain15:57:50 up 15 days, 5:22, 5 users, load average: 0.35, 0.49, 0.58
[Prev in Thread] | Current Thread | [Next in Thread] |