Re: can bendAfter be made to skip over notes?
On 2020-10-26 10:54 pm, Aaron Hill wrote:
On 2020-10-26 7:37 pm, 98123981293 1293812397123 wrote:
Hi list,
I usually use the following snippet to handle glissandi across hidden
noteheads:
glissandoSkipOn = {
\override NoteColumn.glissando-skip = ##t
\hide NoteHead
\override Accidental.transparent = ##t
\override NoteHead.no-ledgers = ##t
}
is it possible to implement something similar for bendAfter? A quick
check
of the archives did not reveal anything relevant but please link me if
this
has already been covered. Pic attached with the line as I want it to
look
in green.
Thank you,
Kyle
The Glissando_engraver knows to look for glissando-skip, however no
such logic exists for Bend_engraver. It would be possible to re-write
the engraver and introduce a new bend-skip context property, however a
perhaps simpler option is to change the stencil for a glissando to
look like a bend:
[...]
Sorry, I pasted an old version of the code that did not handle the
vertical alignment properly:
\version "2.20.0"
bend-glissando-print =
#(lambda (grob)
(let* ((lnh (ly:spanner-bound grob LEFT))
(rnh (ly:spanner-bound grob RIGHT))
(lsp (ly:grob-staff-position lnh))
(rsp (ly:grob-staff-position rnh))
(dy (/ (- rsp lsp) 2))
(dot (ly:grob-object lnh 'dot))
(acc (ly:grob-object rnh 'accidental-grob))
(th (* (ly:grob-property grob 'thickness 1)
(ly:output-def-lookup (ly:grob-layout grob)
'line-thickness)))
(pad (ly:grob-property grob 'padding 0.5))
(cmx (ly:grob-common-refpoint
(ly:grob-common-refpoint grob lnh X) rnh X))
(cmy (ly:grob-common-refpoint grob lnh Y))
(lx (+ pad (max (interval-end (ly:generic-bound-extent lnh
cmx))
(if dot
(interval-end
(ly:grob-robust-relative-extent dot cmx
X))
(- INFINITY-INT)
(rx (- (min (interval-start (ly:generic-bound-extent rnh cmx))
(if acc
(interval-start
(ly:grob-robust-relative-extent acc cmx X))
INFINITY-INT))
pad))
(dx (- rx lx))
(sx (ly:grob-relative-coordinate grob cmx X)))
(ly:make-stencil
(list 'path th
`(quote
(rmoveto ,(- lx sx) ,(/ lsp 2)
rcurveto ,(/ dx 3) 0 ,dx ,(* dy 2/3) ,dx ,dy)))
(cons (- lx sx) (- rx sx))
(cons (+ (/ lsp 2) (min 0 dy)) (+ 0.5 (max 0 dy))
bendGlissando =
\tweak thickness #2
\tweak stencil #bend-glissando-print
\glissando
{ c''2. \bendGlissando
\once \override NoteColumn.glissando-skip = ##t
e'4 gis'1 }
-- Aaron Hill
Re: can bendAfter be made to skip over notes?
On 2020-10-26 7:37 pm, 98123981293 1293812397123 wrote:
Hi list,
I usually use the following snippet to handle glissandi across hidden
noteheads:
glissandoSkipOn = {
\override NoteColumn.glissando-skip = ##t
\hide NoteHead
\override Accidental.transparent = ##t
\override NoteHead.no-ledgers = ##t
}
is it possible to implement something similar for bendAfter? A quick
check
of the archives did not reveal anything relevant but please link me if
this
has already been covered. Pic attached with the line as I want it to
look
in green.
Thank you,
Kyle
The Glissando_engraver knows to look for glissando-skip, however no such
logic exists for Bend_engraver. It would be possible to re-write the
engraver and introduce a new bend-skip context property, however a
perhaps simpler option is to change the stencil for a glissando to look
like a bend:
\version "2.20.0"
bend-glissando-print =
#(lambda (grob)
(let* ((lnh (ly:spanner-bound grob LEFT))
(rnh (ly:spanner-bound grob RIGHT))
(lsp (ly:grob-staff-position lnh))
(rsp (ly:grob-staff-position rnh))
(dy (/ (- rsp lsp) 2))
(dot (ly:grob-object lnh 'dot))
(acc (ly:grob-object rnh 'accidental-grob))
(th (* (ly:grob-property grob 'thickness 1)
(ly:output-def-lookup (ly:grob-layout grob)
'line-thickness)))
(pad (ly:grob-property grob 'padding 0.5))
(cmx (ly:grob-common-refpoint
(ly:grob-common-refpoint grob lnh X) rnh X))
(cmy (ly:grob-common-refpoint grob lnh Y))
(lx (+ pad (max (interval-end (ly:generic-bound-extent lnh
cmx))
(if dot
(interval-end
(ly:grob-robust-relative-extent dot cmx
X))
(- INFINITY-INT)
(rx (- (min (interval-start (ly:generic-bound-extent rnh cmx))
(if acc
(interval-start
(ly:grob-robust-relative-extent acc cmx X))
INFINITY-INT))
pad))
(dx (- rx lx))
(sx (ly:grob-relative-coordinate grob cmx X)))
(ly:make-stencil
(list 'path th
`(quote
(rmoveto ,(- lx sx) 0.5
rcurveto ,(/ dx 3) 0 ,dx ,(* dy 2/3) ,dx ,dy)))
(cons (- lx sx) (- rx sx))
(cons (+ 0.5 (min 0 dy)) (+ 0.5 (max 0 dy))
bendGlissando =
\tweak thickness #2
\tweak stencil #bend-glissando-print
\glissando
{ c''2. \bendGlissando
\once \override NoteColumn.glissando-skip = ##t
e'4 gis'1 }
-- Aaron Hill
can bendAfter be made to skip over notes?
Hi list,
I usually use the following snippet to handle glissandi across hidden
noteheads:
glissandoSkipOn = {
\override NoteColumn.glissando-skip = ##t
\hide NoteHead
\override Accidental.transparent = ##t
\override NoteHead.no-ledgers = ##t
}
is it possible to implement something similar for bendAfter? A quick check
of the archives did not reveal anything relevant but please link me if this
has already been covered. Pic attached with the line as I want it to look
in green.
Thank you,
Kyle
On Mon, Oct 26, 2020 at 7:01 PM wrote:
> Send lilypond-user mailing list submissions to
> lilypond-user@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> or, via email, send a message with subject or body 'help' to
> lilypond-user-requ...@gnu.org
>
> You can reach the person managing the list at
> lilypond-user-ow...@gnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lilypond-user digest..."
> Today's Topics:
>
>1. Re: I ought to have a bar line here... (Aaron Hill)
>2. Re: I ought to have a bar line here... (Carl Sorensen)
>3. Re: I ought to have a bar line here... (Thomas Morley)
>4. Re: I ought to have a bar line here... (Carl Sorensen)
>5. Re: I ought to have a bar line here... (Thomas Morley)
>
>
>
> -- Forwarded message --
> From: Aaron Hill
> To: lilypond-user@gnu.org
> Cc:
> Bcc:
> Date: Mon, 26 Oct 2020 15:17:32 -0700
> Subject: Re: I ought to have a bar line here...
> On 2020-10-26 3:03 pm, Mike Dean wrote:
> > Hi Carl:
> > Is \include "english.ly" different from \language "english"?
> >
> > Part of my residing in the weeds is not being sure where \define
> > command
> > (and its relatives like \defineBarLine) ought to go...while the
> > compilation
> > didn't crash, the bar line construction was ignored in this case
> > Mike Dean
>
> \language "english" is preferred over \include "english.ly". The latter
> is a vestige of older LilyPond versions where the \language command did
> not exist, and the "english.ly" include files did more stuff. Now,
> "english.ly" is just a \version and \language statement.
>
> I think you can get away with \defineBarLine being inside music, but it
> would probably be poor practice. It is better to place all definition
> (or definition-type things) at the top-level. The only exceptions are
> things that specifically require scope, like \paper variables.
>
>
>
> As to why the bar line did not appear in your snippet, you redefined the
> bar twice in the same moment. Only use \bar once. In this case you
> would place the \bar command at the end of the alternative or at the
> beginning of the "Trio" section. As to which, that is probably personal
> taste.
>
>
> -- Aaron Hill
>
>
>
>
>
> -- Forwarded message --
> From: Carl Sorensen
> To: Mike Dean
> Cc: Lilypond-User Mailing List
> Bcc:
> Date: Mon, 26 Oct 2020 16:26:53 -0600
> Subject: Re: I ought to have a bar line here...
>
>
> On Mon, Oct 26, 2020 at 4:07 PM Mike Dean wrote:
>
>> Hi Carl:
>> Is \include "english.ly" different from \language "english"?
>>
>
> It's an old form that predates \language "english". I'm an old dog, so
> sometimes I forget the new tricks. At any rate, your snippet didn't
> include \language "english", so I had to fix it.
>
>
>>
>> Part of my residing in the weeds is not being sure where \define command
>> (and its relatives like \defineBarLine) ought to go...while the
>> compilation didn't crash, the bar line construction was ignored in this case
>>
>
> \define always goes at the top level -- outside of any other expressions.
>
> The other change I had to make in order to avoid errors was to replace #f
> with "" as the third element in the \defineBarLine list. The documentation
> allows the use of #f, but it threw an error and I changed it to "",
> which worked. That was a successful guess on my part.
>
> Carl
>
>
>
>
> -- Forwarded message --
> From: Thomas Morley
> To: Carl Sorensen
> Cc: Mike Dean , "lilypond-user@gnu.org" <
> lilypond-user@gnu.org>
> Bcc:
> Date: Mon, 26 Oct 2020 23:34:44 +0100
> Subject: Re: I ought to have a bar line here...
> Hi Carl,
>
> Am Mo., 26. Okt. 2020 um 23:04 Uhr schrieb Carl Sorensen <
> c_soren...@byu.edu>:
> >
> > Try this:
>
> > \defineBarLine ".|:-|." #'("|." ".|:" "")
>
> Though, \defineBarLine ".|:-|." #'("|." ".|:" #f) _should_ work as well.
>
> It's a bug in 'ly:bar-line::calc-anchor' in bar-line.scm, triggered by
> the RehearsalMark requiring an anchor.
> The anchor-calculating procedure compares the span-glyph using
> string=? which bombs out if span-glyph is not a string.
> One should likely use equal? here.
>
> I'll check that more thoroughly and probably ut up a patch.
>
> Cheers,
> Harm
>
>
>
>
>
> -- Forwarded message --
> From: Carl Sorensen
> To: Thomas Morley
> Cc: Carl
Re: I ought to have a bar line here...
Am Mo., 26. Okt. 2020 um 23:47 Uhr schrieb Carl Sorensen
:
>
>
>
> On Mon, Oct 26, 2020 at 4:35 PM Thomas Morley
> wrote:
>>
>> Hi Carl,
>>
>> Am Mo., 26. Okt. 2020 um 23:04 Uhr schrieb Carl Sorensen
>> :
>> >
>> > Try this:
>>
>> > \defineBarLine ".|:-|." #'("|." ".|:" "")
>>
>> Though, \defineBarLine ".|:-|." #'("|." ".|:" #f) _should_ work as well.
>>
>> It's a bug in 'ly:bar-line::calc-anchor' in bar-line.scm, triggered by
>> the RehearsalMark requiring an anchor.
>> The anchor-calculating procedure compares the span-glyph using
>> string=? which bombs out if span-glyph is not a string.
>> One should likely use equal? here.
>
>
> Thanks, Harm! Sometimes it's almost as good to be lucky as to be good. You
> are absolutely right, of course, and were I not too lazy to do so, I'd have
> looked up the line where the actual error was. Instead I just saw that #f
> didn't work, so I changed to "",
Patch's up
https://gitlab.com/lilypond/lilypond/-/merge_requests/483
Cheers,
Harm
Re: I ought to have a bar line here...
On Mon, Oct 26, 2020 at 4:35 PM Thomas Morley
wrote:
> Hi Carl,
>
> Am Mo., 26. Okt. 2020 um 23:04 Uhr schrieb Carl Sorensen <
> c_soren...@byu.edu>:
> >
> > Try this:
>
> > \defineBarLine ".|:-|." #'("|." ".|:" "")
>
> Though, \defineBarLine ".|:-|." #'("|." ".|:" #f) _should_ work as well.
>
> It's a bug in 'ly:bar-line::calc-anchor' in bar-line.scm, triggered by
> the RehearsalMark requiring an anchor.
> The anchor-calculating procedure compares the span-glyph using
> string=? which bombs out if span-glyph is not a string.
> One should likely use equal? here.
>
Thanks, Harm! Sometimes it's almost as good to be lucky as to be good.
You are absolutely right, of course, and were I not too lazy to do so, I'd
have looked up the line where the actual error was. Instead I just saw
that #f didn't work, so I changed to "",
Also, Mike, while my comment about \define always going at the top level,
that same thing is NOT true in general for functions of the form
\defineXXX. I can't think of any cases where it causes problems to put
them at the top level. But it's not strictly required, and the use of
\defineBarLine inside the music expression was not the cause of the errors.
I just wanted to clear up my possibly confusing statement.
Thanks,
Carl
Re: I ought to have a bar line here...
On Mon, Oct 26, 2020 at 4:07 PM Mike Dean wrote: > Hi Carl: > Is \include "english.ly" different from \language "english"? > It's an old form that predates \language "english". I'm an old dog, so sometimes I forget the new tricks. At any rate, your snippet didn't include \language "english", so I had to fix it. > > Part of my residing in the weeds is not being sure where \define command > (and its relatives like \defineBarLine) ought to go...while the > compilation didn't crash, the bar line construction was ignored in this case > \define always goes at the top level -- outside of any other expressions. The other change I had to make in order to avoid errors was to replace #f with "" as the third element in the \defineBarLine list. The documentation allows the use of #f, but it threw an error and I changed it to "", which worked. That was a successful guess on my part. Carl
Re: I ought to have a bar line here...
Hi Carl,
Am Mo., 26. Okt. 2020 um 23:04 Uhr schrieb Carl Sorensen :
>
> Try this:
> \defineBarLine ".|:-|." #'("|." ".|:" "")
Though, \defineBarLine ".|:-|." #'("|." ".|:" #f) _should_ work as well.
It's a bug in 'ly:bar-line::calc-anchor' in bar-line.scm, triggered by
the RehearsalMark requiring an anchor.
The anchor-calculating procedure compares the span-glyph using
string=? which bombs out if span-glyph is not a string.
One should likely use equal? here.
I'll check that more thoroughly and probably ut up a patch.
Cheers,
Harm
Re: I ought to have a bar line here...
On 2020-10-26 3:03 pm, Mike Dean wrote: Hi Carl: Is \include "english.ly" different from \language "english"? Part of my residing in the weeds is not being sure where \define command (and its relatives like \defineBarLine) ought to go...while the compilation didn't crash, the bar line construction was ignored in this case Mike Dean \language "english" is preferred over \include "english.ly". The latter is a vestige of older LilyPond versions where the \language command did not exist, and the "english.ly" include files did more stuff. Now, "english.ly" is just a \version and \language statement. I think you can get away with \defineBarLine being inside music, but it would probably be poor practice. It is better to place all definition (or definition-type things) at the top-level. The only exceptions are things that specifically require scope, like \paper variables. As to why the bar line did not appear in your snippet, you redefined the bar twice in the same moment. Only use \bar once. In this case you would place the \bar command at the end of the alternative or at the beginning of the "Trio" section. As to which, that is probably personal taste. -- Aaron Hill
Re: I ought to have a bar line here...
Ah, success! (Carl: you probably took out the barline repeat I had at the
Trio, but it just now dawned on me to do that)
Thanks for your help!!!
Mike Dean
On Mon, Oct 26, 2020 at 3:03 PM Mike Dean wrote:
> Hi Carl:
> Is \include "english.ly" different from \language "english"?
>
> Part of my residing in the weeds is not being sure where \define command
> (and its relatives like \defineBarLine) ought to go...while the
> compilation didn't crash, the bar line construction was ignored in this case
> Mike Dean
>
>
> On Mon, Oct 26, 2020 at 2:56 PM Carl Sorensen wrote:
>
>> Try this:
>>
>>
>>
>> \version "2.20.00"
>>
>> \include "english.ly"
>>
>> \defineBarLine ".|:-|." #'("|." ".|:" "")
>>
>>
>>
>> {
>>
>> \repeat volta 2 {
>>
>> d2 d8 c d e | f4 f8. e16 d2 | e2 e8 d e f | g4 g8. f16 e2 |
>>
>> a4 a8. g16 f8. g16 a8. f16 | g4 g8. f16 e8. f16 g8. e16 |
>>
>> g4 a8. g16 f8. f16 e8. e16 | d4 g8. g16 g4 r8 g, |
>>
>> c4. g8 c4 d | e4. c8 e4 f | g e f d |}
>>
>> \alternative {
>>
>>{c c8. c16 c4 r }
>>
>>{c c8. c16 c4\mark "Fine" r \bar ".|:-|." }
>>
>> }
>>
>>
>>
>> \break
>>
>> \mark "Trio" a4.-\p r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16 gs8. e16 |
>>
>> a4 c b e | d8. c16 b8. c16 b2 |
>>
>> a4. r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16 gs8. e16 |
>>
>> a4 c b e | a,4 a8. a16 a4 r |
>>
>> }
>>
>>
>>
>> Carl
>>
>>
>>
>>
>>
>> *From: *lilypond-user > gmail@gnu.org> on behalf of Mike Dean
>> *Date: *Monday, October 26, 2020 at 3:30 PM
>> *To: *"lilypond-user@gnu.org"
>> *Subject: *Re: I ought to have a bar line here...
>>
>>
>>
>> Still stumped
>>
>> \version "2.20.0"
>>
>> {
>>
>> \alternative {
>>{c c8. c16 c4 r }
>>{c c8. c16 c4\mark "Fine" r
>> \markup \vspace #1
>>
>> \defineBarLine ".|:-|." #'("|." ".|:" #f)
>> \markup \bold \typewriter "\".|:-|.\""
>> \bar ".|:-|." }
>> }
>> \break
>>
>> \repeat volta 2 {
>> \bar ".|:"\mark "Trio" a4.\p r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16
>> gs8. e16 |
>>
>> }
>>
>> has generated the following errors
>>
>> *Starting lilypond-windows.exe 2.20.0
>> [March-of-the-Russian-Imperial-Guard.ly]...*
>>
>> Processing `C:/Users/Mike
>> Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly'
>>
>> Parsing...
>>
>> C:/Users/Mike
>> Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:27:1
>> : error: markup outside of text script or \lyricmode
>>
>>
>>
>> \markup \vspace #1
>>
>>
>>
>> C:/Users/Mike
>> Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:30:1
>> : error: markup outside of text script or \lyricmode
>>
>>
>>
>> \markup \bold \typewriter "\".|:-|.\""
>>
>>
>>
>> Interpreting music...[8][16][24]
>>
>> C:/Users/Mike
>> Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:36:55
>> : warning: barcheck failed at: 1/2
>>
>> \bar ".|:"\mark "Trio" a4.\p r16 e a8. e16 gs8. e16
>>
>> | a4. r16 e a8. e16 gs8. e16 |
>>
>>
>>
>>
>>
>> So maybe I'll have to draw it in the PDF, since I seem to be at the point
>> that my understanding of LilyPond is enough to get me stuck in the weeds?
>>
>>
>>
>> (the first of Aaron's suggestions did not generate a bar line before the
>> Triowould enclosing the piece in two separate pairs of braces be
>> useful?)
>>
>>
>> Mike Dean
>>
>>
>>
>>
>>
>> On Sun, Oct 25, 2020 at 7:19 AM Aaron Hill
>> wrote:
>>
>> On 2020-10-25 6:25 am, Christian Masser wrote:
>> > Aaron Hill schrieb am So., 25. Okt. 2020,
>> > 04:38
>> >
>> >> You have to use a special bar line type when it breaks across a line:
>> >>
>> >>
>> >> \version "2.20.0"
>> >> \paper { indent = 0 line-width = 3\cm ragged-right = ##f }
>> >>
>> >> \markup \bold \typewriter "\".|:-||\""
>> >> { R1 \bar ".|:-||" \break R1 }
>> >>
>> >
>> > Out of pure interest: does anyone know why this seems to be "in the
>> > wrong
>> > order"? Why does the ". |:" of the second line come in front of the
>> > "||"
>> > which - viewed from a musical standpoint - should happen before?
>>
>> Near as I can tell, the naming convention is "primary-secondary". Only
>> a bar line breaking across a line will show both styles. Otherwise, it
>> is the style before the hyphen that is used.
>>
>>
>> -- Aaron Hill
>>
>>
Re: I ought to have a bar line here...
Hi Carl:
Is \include "english.ly" different from \language "english"?
Part of my residing in the weeds is not being sure where \define command
(and its relatives like \defineBarLine) ought to go...while the compilation
didn't crash, the bar line construction was ignored in this case
Mike Dean
On Mon, Oct 26, 2020 at 2:56 PM Carl Sorensen wrote:
> Try this:
>
>
>
> \version "2.20.00"
>
> \include "english.ly"
>
> \defineBarLine ".|:-|." #'("|." ".|:" "")
>
>
>
> {
>
> \repeat volta 2 {
>
> d2 d8 c d e | f4 f8. e16 d2 | e2 e8 d e f | g4 g8. f16 e2 |
>
> a4 a8. g16 f8. g16 a8. f16 | g4 g8. f16 e8. f16 g8. e16 |
>
> g4 a8. g16 f8. f16 e8. e16 | d4 g8. g16 g4 r8 g, |
>
> c4. g8 c4 d | e4. c8 e4 f | g e f d |}
>
> \alternative {
>
>{c c8. c16 c4 r }
>
>{c c8. c16 c4\mark "Fine" r \bar ".|:-|." }
>
> }
>
>
>
> \break
>
> \mark "Trio" a4.-\p r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16 gs8. e16 |
>
> a4 c b e | d8. c16 b8. c16 b2 |
>
> a4. r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16 gs8. e16 |
>
> a4 c b e | a,4 a8. a16 a4 r |
>
> }
>
>
>
> Carl
>
>
>
>
>
> *From: *lilypond-user gmail@gnu.org> on behalf of Mike Dean
> *Date: *Monday, October 26, 2020 at 3:30 PM
> *To: *"lilypond-user@gnu.org"
> *Subject: *Re: I ought to have a bar line here...
>
>
>
> Still stumped
>
> \version "2.20.0"
>
> {
>
> \alternative {
>{c c8. c16 c4 r }
>{c c8. c16 c4\mark "Fine" r
> \markup \vspace #1
>
> \defineBarLine ".|:-|." #'("|." ".|:" #f)
> \markup \bold \typewriter "\".|:-|.\""
> \bar ".|:-|." }
> }
> \break
>
> \repeat volta 2 {
> \bar ".|:"\mark "Trio" a4.\p r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16
> gs8. e16 |
>
> }
>
> has generated the following errors
>
> *Starting lilypond-windows.exe 2.20.0
> [March-of-the-Russian-Imperial-Guard.ly]...*
>
> Processing `C:/Users/Mike
> Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly'
>
> Parsing...
>
> C:/Users/Mike
> Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:27:1
> : error: markup outside of text script or \lyricmode
>
>
>
> \markup \vspace #1
>
>
>
> C:/Users/Mike
> Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:30:1
> : error: markup outside of text script or \lyricmode
>
>
>
> \markup \bold \typewriter "\".|:-|.\""
>
>
>
> Interpreting music...[8][16][24]
>
> C:/Users/Mike
> Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:36:55
> : warning: barcheck failed at: 1/2
>
> \bar ".|:"\mark "Trio" a4.\p r16 e a8. e16 gs8. e16
>
> | a4. r16 e a8. e16 gs8. e16 |
>
>
>
>
>
> So maybe I'll have to draw it in the PDF, since I seem to be at the point
> that my understanding of LilyPond is enough to get me stuck in the weeds?
>
>
>
> (the first of Aaron's suggestions did not generate a bar line before the
> Triowould enclosing the piece in two separate pairs of braces be
> useful?)
>
>
> Mike Dean
>
>
>
>
>
> On Sun, Oct 25, 2020 at 7:19 AM Aaron Hill
> wrote:
>
> On 2020-10-25 6:25 am, Christian Masser wrote:
> > Aaron Hill schrieb am So., 25. Okt. 2020,
> > 04:38
> >
> >> You have to use a special bar line type when it breaks across a line:
> >>
> >>
> >> \version "2.20.0"
> >> \paper { indent = 0 line-width = 3\cm ragged-right = ##f }
> >>
> >> \markup \bold \typewriter "\".|:-||\""
> >> { R1 \bar ".|:-||" \break R1 }
> >>
> >
> > Out of pure interest: does anyone know why this seems to be "in the
> > wrong
> > order"? Why does the ". |:" of the second line come in front of the
> > "||"
> > which - viewed from a musical standpoint - should happen before?
>
> Near as I can tell, the naming convention is "primary-secondary". Only
> a bar line breaking across a line will show both styles. Otherwise, it
> is the style before the hyphen that is used.
>
>
> -- Aaron Hill
>
>
Re: I ought to have a bar line here...
Try this:
\version "2.20.00"
\include "english.ly"
\defineBarLine ".|:-|." #'("|." ".|:" "")
{
\repeat volta 2 {
d2 d8 c d e | f4 f8. e16 d2 | e2 e8 d e f | g4 g8. f16 e2 |
a4 a8. g16 f8. g16 a8. f16 | g4 g8. f16 e8. f16 g8. e16 |
g4 a8. g16 f8. f16 e8. e16 | d4 g8. g16 g4 r8 g, |
c4. g8 c4 d | e4. c8 e4 f | g e f d |}
\alternative {
{c c8. c16 c4 r }
{c c8. c16 c4\mark "Fine" r \bar ".|:-|." }
}
\break
\mark "Trio" a4.-\p r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16 gs8. e16 |
a4 c b e | d8. c16 b8. c16 b2 |
a4. r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16 gs8. e16 |
a4 c b e | a,4 a8. a16 a4 r |
}
Carl
From: lilypond-user
on behalf of Mike Dean
Date: Monday, October 26, 2020 at 3:30 PM
To: "lilypond-user@gnu.org"
Subject: Re: I ought to have a bar line here...
Still stumped
\version "2.20.0"
{
\alternative {
{c c8. c16 c4 r }
{c c8. c16 c4\mark "Fine" r
\markup \vspace #1
\defineBarLine ".|:-|." #'("|." ".|:" #f)
\markup \bold \typewriter "\".|:-|.\""
\bar ".|:-|." }
}
\break
\repeat volta 2 {
\bar ".|:"\mark "Trio" a4.\p r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16 gs8.
e16 |
}
has generated the following errors
Starting lilypond-windows.exe 2.20.0 [March-of-the-Russian-Imperial-Guard.ly]...
Processing `C:/Users/Mike
Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly'
Parsing...
C:/Users/Mike
Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:27:1<0>:
error: markup outside of text script or \lyricmode
\markup \vspace #1
C:/Users/Mike
Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:30:1<1>:
error: markup outside of text script or \lyricmode
\markup \bold \typewriter "\".|:-|.\""
Interpreting music...[8][16][24]
C:/Users/Mike
Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:36:55<2>:
warning: barcheck failed at: 1/2
\bar ".|:"\mark "Trio" a4.\p r16 e a8. e16 gs8. e16
| a4. r16 e a8. e16 gs8. e16 |
So maybe I'll have to draw it in the PDF, since I seem to be at the point that
my understanding of LilyPond is enough to get me stuck in the weeds?
(the first of Aaron's suggestions did not generate a bar line before the
Triowould enclosing the piece in two separate pairs of braces be useful?)
Mike Dean
On Sun, Oct 25, 2020 at 7:19 AM Aaron Hill
mailto:lilyp...@hillvisions.com>> wrote:
On 2020-10-25 6:25 am, Christian Masser wrote:
> Aaron Hill mailto:lilyp...@hillvisions.com>>
> schrieb am So., 25. Okt. 2020,
> 04:38
>
>> You have to use a special bar line type when it breaks across a line:
>>
>>
>> \version "2.20.0"
>> \paper { indent = 0 line-width = 3\cm ragged-right = ##f }
>>
>> \markup \bold \typewriter "\".|:-||\""
>> { R1 \bar ".|:-||" \break R1 }
>>
>
> Out of pure interest: does anyone know why this seems to be "in the
> wrong
> order"? Why does the ". |:" of the second line come in front of the
> "||"
> which - viewed from a musical standpoint - should happen before?
Near as I can tell, the naming convention is "primary-secondary". Only
a bar line breaking across a line will show both styles. Otherwise, it
is the style before the hyphen that is used.
-- Aaron Hill
Re: I ought to have a bar line here...
Still stumped
\version "2.20.0"
{
\alternative {
{c c8. c16 c4 r }
{c c8. c16 c4\mark "Fine" r
\markup \vspace #1
\defineBarLine ".|:-|." #'("|." ".|:" #f)
\markup \bold \typewriter "\".|:-|.\""
\bar ".|:-|." }
}
\break
\repeat volta 2 {
\bar ".|:"\mark "Trio" a4.\p r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16
gs8. e16 |
}
has generated the following errors
Starting lilypond-windows.exe 2.20.0
[March-of-the-Russian-Imperial-Guard.ly]...
Processing `C:/Users/Mike
Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly'
Parsing...
C:/Users/Mike
Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:27:1
<0>: error: markup outside of text script or \lyricmode
\markup \vspace #1
C:/Users/Mike
Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:30:1
<1>: error: markup outside of text script or \lyricmode
\markup \bold \typewriter "\".|:-|.\""
Interpreting music...[8][16][24]
C:/Users/Mike
Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:36:55
<2>: warning: barcheck failed at: 1/2
\bar ".|:"\mark "Trio" a4.\p r16 e a8. e16 gs8. e16
| a4. r16 e a8. e16 gs8. e16 |
So maybe I'll have to draw it in the PDF, since I seem to be at the point
that my understanding of LilyPond is enough to get me stuck in the weeds?
(the first of Aaron's suggestions did not generate a bar line before the
Triowould enclosing the piece in two separate pairs of braces be
useful?)
Mike Dean
On Sun, Oct 25, 2020 at 7:19 AM Aaron Hill wrote:
> On 2020-10-25 6:25 am, Christian Masser wrote:
> > Aaron Hill schrieb am So., 25. Okt. 2020,
> > 04:38
> >
> >> You have to use a special bar line type when it breaks across a line:
> >>
> >>
> >> \version "2.20.0"
> >> \paper { indent = 0 line-width = 3\cm ragged-right = ##f }
> >>
> >> \markup \bold \typewriter "\".|:-||\""
> >> { R1 \bar ".|:-||" \break R1 }
> >>
> >
> > Out of pure interest: does anyone know why this seems to be "in the
> > wrong
> > order"? Why does the ". |:" of the second line come in front of the
> > "||"
> > which - viewed from a musical standpoint - should happen before?
>
> Near as I can tell, the naming convention is "primary-secondary". Only
> a bar line breaking across a line will show both styles. Otherwise, it
> is the style before the hyphen that is used.
>
>
> -- Aaron Hill
>
>
Re: OOoLilyPond: new repository
Ooops... Hi Andrew (where did I grab the name "Martin"?) Sorry...
Re: OOoLilyPond: new repository
Hi Martin, Am 25.10.2020 um 16:17 schrieb lilypond-user-requ...@gnu.org: >Hi Klaus, I will be opening the newly revivified openLilyLib repository in the next couple of weeks. I'm sorry I have not been able to do it instantly! It would be great if you could come back over there. I am trying hard to unify the OLL project so that we don't have the balkanisation and fragmentation of LilyPond into many individual git repos. I feel this makes it hard for end users. Tell a beginning user they have to fetch from five or six git repos and they likely won't stay with it long. Please don't feel pushed or criticized in any way. Thanks for taking over the maintainership! OOoLilyPond has never been an OLL package and therefore always has been somewhat out of place in the repo. In the past, Urs already thought about placing it somewhere else. Or course I will stay on board and continue my work on anaLYsis. Cheers, Klaus
Re: architecture document?
Tom Sgouros writes: Hello all: I've recently started using Lilypond and so far it's great. I don't think I'm saying anything surprising by observing what seems to be a close family resemblance to TeX. Did it start out as TeX macros and diverge? I wonder if there is a document out there that might talk about the design choices made in putting Lilypond together that might compare and contrast it with TeX? Lessons learned? Thank you, -Tom My opinion is a silly one without any facts or evidence: For projects, there might exist a level of difficulty-plus-complexity-plus-diversity-plus-peculiarity beyond which, *in practice*, every successful solution for that project must necessarily be peculiar, difficult, diverse, and complex, and the people who complete it will invariably turn out to be diverse, complex, difficult, and peculiar. And: For such a project or its solution or its people, every attempt to reduce the overall magnitude of one of those twelve characteristics (e.g. complexity of the project, difficulty of the solution, etc) will also cause unpredictable increases among the other eleven characteristics, unless each of them is correctly anticipated and successfully mitigated. And sometimes despite the mitigation, too. Or maybe: Extrapolation works better when it’s applied to one graph at a time. :) -- David R
