Re: Strange LilyPond crash

[Edward Ardzinski]

I don't know if I'm stumbling on something similar, but I can't believe that
it's a large file issue - the piece is about 50 bars of mostly slow 7 with a
repeat unfolded, two voices and a 2 part drum staff, no lyrics, and done
entirely with 2.18.2

I got to the final dozen bars, and was compiling a score block for the midi
with the drums, and a pdf score without.  I added the final variable with
the coda, and got:

Starting lilypond-windows.exe 2.18.2 [Edski-2015-11-16 v4 test.ly]...
Processing
`c:/users/edward/appdata/local/temp/frescobaldi-cyoxhi/tmpcpyl1r/Edski-2015-11-16
v4 test.ly'
Parsing...
Interpreting music...[8][16][24][32]
Exited with return code -1073741819.

Eventually I added the drums, the pdf works fine.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Strange-LilyPond-crash-tp183610p184079.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Why does \fromproperty fail in instrumentName?

[Simon Albrecht]

On 24.11.2015 23:44, Thomas Morley wrote:

Reinhold’s final code is http://lsr.di.unimi.it/LSR/Item?id=467


Thanks, I’ll try that.

Yours, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [Best Practices] splitting and combining choral parts

[Simon Albrecht]

Hello Kieren,

first of all: Looks like a nice piece!
Second: offtopic nitpicks. There are some superfluous LyricExtenders 
there – I’d rather leave them out if they are very short. 
( …) And note the 
mid-air bar-numbers, where they are aligned with ScoreMarks. I’d move 
Bar_number_engraver to the topmost staff. And I like for long syllables 
to be increasingly left-aligned, for which I wrote a custom grob callback.
And finally on your actual point, an answer which is probably not the 
one you wanted to hear: :-)


I’d vote to keep with four staves, at least in this example. My model 
for engraving choral scores is the respective volume in the 1926 
Breitkopf & Härtel Brahms complete edition. It’s beautiful and excellent 
to read. It always uses a consistent number of staves for the music 
(which might also be due to the music), which I think gives more 
consistent looks and takes some difficulty (in finding the staff he 
should be singing from) from the singer. The other major point is that 
it doesn’t print ‘redundant’ lyrics, i.e. passages with equal rhythm and 
wording in multiple voices have the lyrics printed only once, mostly 
below the topmost of the staves. This is certainly a controversial 
feature, but IMO the clarity it adds to the score and the nudge to not 
only read one’s own voice are valuable, alongside with the gain on 
vertical space.
For this I also wrote a nice, easy-to-use solution, which you find 
applied to the version in the attachment.
Of course there are cases where one needs to go e.g. to eight staves, or 
have other changes in staff number – the best of orchestral score 
engravings show it. It _would_ of course be great to have a good 
mechanism for that in LilyPond, but it looks like a really involved task.


Other measures to obtain closer vertical spacing are shifting dynamics 
(a task for which I haven’t yet found a definite, if only personal 
solution yet – very complicated) – and narrower hairpins (My default 
stylesheet has \override Hairpin.height = 0.45).


I hope there is something useful for you amongst these ideas…

Yours, Simon

On 24.11.2015 16:14, Kieren MacMillan wrote:

Hello list,

I’ve posted this question several times before, but the discussion always got 
truncated or derailed… I’m hoping this time we can work this through to a 
solution.

Choral pieces tend to have both sections of polyphony (requiring 4 or more 
staves) and sections of homophony (requiring as few as 1 staff). I want to be 
able to arbitrarily break systems and have Lilypond Do The Right Thing™, by 
which I mean use the maximum number of systems when necessary, but combine 
voices and lyrics to 3 or 2 staves or even 1 staff where possible.

Bonus points if we can convince Lily to automagically [e.g., via an engraver?] 
put a user-definable markup indicating who is singing at a given moment, add 
splitting-or-combining arrows at the end(s) of systems, etc.

I’ve attached the first 17 measures of one of my original carols as an example 
we can work with/through. Is anyone out there willing to work with me to find 
the Best Practice here? I’m happy to do this on-list or off-, as appropriate.

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


\version "2.19.31"
\language "english"
\include "interpolate.ily"
\include "switch-lyrics.ily"

#(set-global-staff-size 15.5)

\paper {
  page-count = 2
  system-count = 5
  ragged-bottom = ##t
  ragged-last-bottom = ##t
  system-system-spacing = #'((minimum-distance . 18) (padding . 8))
}

\layout {
  \context {
\Voice
\consists "Melody_engraver"
\override Stem #'neutral-direction = #'()
  }
  \context {
\Staff
\name ChoralStaff
\alias Staff
\override DynamicLineSpanner.direction = #UP
\override Script.direction = #UP
\override TextScript.direction = #UP
\override TupletBracket.direction = #UP
\override TupletNumber.direction = #UP
  }
  \context {
\ChoirStaff
\accepts ChoralStaff
  }
  \context {
\type "Engraver_group"
\name ScoreMarks
\consists "Staff_collecting_engraver"
\consists "Axis_group_engraver"
\override VerticalAxisGroup.staff-affinity = #DOWN
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing =
#'((basic-distance . 1) (minimum-distance . 1) (padding . 2) (stretchability . 0))
\override VerticalAxisGroup.nonstaff-unrelatedstaff-spacing =
#'((basic-distance . 6) (minimum-distance . 6) (padding . 4) (stretchability . 0))
\override VerticalAxisGroup.nonstaff-nonstaff-spacing =
#'((basic-distance . 1) (minimum-distance . 1) (padding . 1) (stretchability . 0))
\consists "Metronome_mark_engraver"
\override 

Re: Why does \fromproperty fail in instrumentName?

[Thomas Morley]

2015-11-24 15:41 GMT+01:00 Robin Bannister :
> David Kastrup wrote:
>
>> In general, those variables seem to be defined only within titling
>> material.
>
>
>
> http://lists.gnu.org/archive/html/lilypond-user/2008-05/msg00426.html
>
>
> Cheers,
> Robin



Reinholds final code is
http://lsr.di.unimi.it/LSR/Item?id=467

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [Best Practices] splitting and combining choral parts

[Kieren MacMillan]

Hi Simon,

> I’d vote to keep with four staves, at least in this example.

For the record, I sometimes do that. One good example is “Go Thy Way”, a score 
of which you can see at 
.

But that’s a short a cappella piece, with just enough polyphonic differences 
(homophonic offsets, mostly) that it never makes sense to be in two staves for 
very long. “Wither’s Carol” is longer and more complex; it has instrumental 
parts (and/or a piano reduction); it alternates between a cappella, 
instrumental, and combined-forces sections, etc. Ultimately, sticking to four 
chorus staves doesn’t make much sense [in all score outputs], in my opinion.

By the way: the “Go Thy Way” score is “almost final”. That will give you a 
sense of the amount of stylesheeting and edition-engraver tweaking I do to my 
scores, to overcome Lilypond’s shortcomings (e.g., the BarNumber padding bug 
you saw in the “minimal” example I supplied for this thread).

I would do even more, but there’s a point of diminishing marginal utility: at 
some point, I’d rather compose a new piece than sit and tweak the engraving of 
an old one.  ;)

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [Best Practices] splitting and combining choral parts

[Simon Albrecht]

On 25.11.2015 00:03, Michael Gerdau wrote:

Last not least for vocal lines I always turn off autoBeam and manually
put beams to groups that are sung on a single syllable. For my singers
eyes that strongly helps to keep words and music in a proper flow.


It’s rather a question of rhythmic complexity; with long and/or 
oft-changing measures it helps to have normal beaming.


Yours, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Layout of a (piano) hand indicator

[Urs Liska]

Am 24.11.2015 um 22:39 schrieb Simon Albrecht:
> On 24.11.2015 18:49, Urs Liska wrote:
>> Hi all,
>>
>> please consider the attached image, especially the "half-bracket" at the
>> center. This is to indicate that this d' is to be played with the
>> left hand.
>>
>> Is there anything I could improve to the proportions and placement of
>> that sign?
>>
>> Any suggestions for improvement welcome. Suggestions for *not* improving
>> it even more ;-)
>
> I agree that it looks quite good, and that the vertical part should be
> shorter. Also, the horizontal part could be longer in my eyes.
> And I’d be very interested in how you did it :-)
>

I use a very simple \path. Originally I simply added it as a \markup and
used extra-offset to position it. But thanks to Abraham's blog post I
changed that to use a fingering indication. However, I'm not really sure
this is more reliable (for example against transposition):

So this is what it looks like now:

\set fingeringOrientations = #'(left)
 8

Urs

> Yours, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Strange LilyPond crash

[Thomas Morley]

2015-11-24 17:11 GMT+01:00 David Kastrup :
[...]
>
> Ticket created at: https://sourceforge.net/rest/p/testlilyissues/issues/4670/
>
> --
> David Kastrup

You already pushed it, so I tested Marc's files with a build including
your patch.
As far as I can tell, all works fine now.

Many thanks,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [Best Practices] splitting and combining choral parts

[Simon Albrecht]

On 24.11.2015 23:36, Kieren MacMillan wrote:

And I like for long syllables to be increasingly left-aligned

This is one of the many, many lyric-related problems in Lilypond. (See my 
numerous other posts and sponsorship offers on that topic.) I solve almost all 
of them post-hoc, using the edition-engraver.


>for which I wrote a custom grob callback.

I’d be happy to look at that, if you’re willing to share it.
(I have yet to find a callback that satisfies me in that regard.)


It’s in the ‘interpolate.ily’ file I already sent. I’ve found that it 
yields quite acceptable results, but I’m interested to hear your opinion.


Yours, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Layout of a (piano) hand indicator

[Noeck]

Hi Urs,

to me it looks pretty much optimal. To be more precise:

I like:
+ the top edge is at a defined position between the staff lines
+ it has round edges (as far as I can tell)
+ the distance from the note head/stem is good (positioning in general)

I find acceptable but other choices could also look good:
- the length of the vertical line (shorter?)
- it is hard to tell from the png how wide it is as even the stems have
different widths in the image. But I would probably make it a bit
thinner. About the thickness of a staff line. At most as thick as a stem.

Cheers,
Joram


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Layout of a (piano) hand indicator

[Simon Albrecht]

On 24.11.2015 18:49, Urs Liska wrote:

Hi all,

please consider the attached image, especially the "half-bracket" at the
center. This is to indicate that this d' is to be played with the left hand.

Is there anything I could improve to the proportions and placement of
that sign?

Any suggestions for improvement welcome. Suggestions for *not* improving
it even more ;-)


I agree that it looks quite good, and that the vertical part should be 
shorter. Also, the horizontal part could be longer in my eyes.

And I’d be very interested in how you did it :-)

Yours, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: cross-staff stems for only two of three staves

[Malte Meyn]

Hi Stephen,

thank you for your reply. (Please always reply to the list.)

I should have been clearer: I want three notes in three staves, all with 
stem up, and a stem only from the lower to the middle staff but not to 
the upper. (You suggested to omit the flag from the middle staff; that 
would be a good solution if I wanted the stem across all three staves.) 
Please have a look at the attached image (made with LilyPond and GIMP) 
to see what I mean.


Any other ideas?

Malte

Am 24.11.2015 um 22:32 schrieb Stephen MacNeil:

Since no one answered you I thought I would let you know I would just omit
them since it doesn't happen by default

%%%

\new PianoStaff \with {

\consists #Span_stem_engraver

\autoBeamOff

} <<

\new Staff {

e'8 f'

\crossStaff e'' f'' % not ok

}

\new Staff {

% both work omit leaves out printable space

% \omit Flag

% hide is more like transparent -- space is occupied

% \hide Flag

d'8 \crossStaff e' % ok

d'' \crossStaff e'' % ok

% to undo hide or omit

% \undo \omit Flag

% \undo \hide Flag

}

\new Staff {

\crossStaff c'8 d' % not ok

c'' d''

}









you could write a function that takes care of the undo for omits and hides
within a group ...{ }

HTH
Stephen

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Confused about output

[Shane Brandes]

After fiddling with this for hours i cannot figure out why the added
lyrics e and i drop below the bass as opposed to the voices they ought
to be associated with which is here "melody" and "mel" that live on
the soprano staff. What am I missing?

\version "2.18.2"

sopranoVoice =  {
  a2 <<
  \context Voice = melody \relative {
   c'
  }
   \new Lyrics { \set associatedVoice  = #"melody" \lyricmode {
   e }
  }<<
  \new Voice = "mel" \relative {
\stemDowna2
  }
  \new Lyrics \lyricsto "mel" {\set associatedVoice  = #"mel"
  i
  }
>>
>>
}

verseSopranoVoice = \lyricmode {
  a }

bassVoice = \relative c {
  f e
}

versebassVoice = \lyricmode {
 o u
}

sopranoVoicePart = \new Staff \with {
  instrumentName = "Soprano"

} { \sopranoVoice }
\addlyrics { \verseSopranoVoice }

bassVoicePart = \new Staff \with {
  instrumentName = "Bass"

} { \clef "bass"\bassVoice }
\addlyrics { \versebassVoice }

\score {
  <<
\sopranoVoicePart
\bassVoicePart
  >>
  \layout { }

}


regards,
Shane

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Suggestion for spacing pagenumber and barnumber

[Andrew Bernard]

Hi All,

How do you get the extra spacing under the page number? This has been eluding 
me.

Andrew


On 25/11/2015, 02:27, "Urs Liska" 
 wrote:

 I think it looks much better now. Somehow imagination evaded me ...


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Suggestion for spacing pagenumber and barnumber

[Kieren MacMillan]

Hi Andrew,

> How do you get the extra spacing under the page number? This has been eluding 
> me.

top-system-spacing

Hope this helps!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Strange LilyPond crash

[David Kastrup]

Edward Ardzinski  writes:

> I don't know if I'm stumbling on something similar, but I can't believe that
> it's a large file issue - the piece is about 50 bars of mostly slow 7 with a
> repeat unfolded, two voices and a 2 part drum staff, no lyrics, and done
> entirely with 2.18.2

Not the same bug, then.

> I got to the final dozen bars, and was compiling a score block for the midi
> with the drums, and a pdf score without.  I added the final variable with
> the coda, and got:
>
> Starting lilypond-windows.exe 2.18.2 [Edski-2015-11-16 v4 test.ly]...
> Processing
> `c:/users/edward/appdata/local/temp/frescobaldi-cyoxhi/tmpcpyl1r/Edski-2015-11-16
> v4 test.ly'
> Parsing...
> Interpreting music...[8][16][24][32]
> Exited with return code -1073741819.
>
> Eventually I added the drums, the pdf works fine.

Could be a gc-related Heisenbug as well, but also could be something
else.  Hard to tell without more information.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Confused about output

[Malte Meyn]

Am 25.11.2015 um 02:19 schrieb Shane Brandes:

After fiddling with this for hours i cannot figure out why the added
lyrics e and i drop below the bass as opposed to the voices they ought
to be associated with which is here "melody" and "mel" that live on
the soprano staff. What am I missing?


You can use alignBelowContext. I must admit I didn’t really overlook 
your code structure so I didn’t use any variables. But it should be 
possible with your code structure too.


\version "2.18.2"

\score {
  <<
\new Staff \with {
  instrumentName = "Soprano"
} \new Voice = "soprano_v1" {
  a2
  <<
c'
\new Voice {
  \voiceTwo a
}
\new Lyrics \with {
  alignBelowContext = "soprano_l1"
} \lyricmode {
  i
}
  >>
}
\new Lyrics = "soprano_l1" \lyricsto "soprano_v1" {
  a e
}
\new Staff \with {
  instrumentName = "Bass"
} \relative {
  \clef bass
  f e
}
\addlyrics {
  o u
}
  >>
}

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Strange LilyPond crash

[Marc Hohl]

Am 24.11.2015 um 17:11 schrieb David Kastrup:

Marc Hohl  writes:


Am 24.11.2015 um 00:12 schrieb Thomas Morley:
[...]


So,
commit b416f10429d8d3881445d9000ff422dc67176df1
Author: David Kastrup 
Date:   Wed Jul 15 23:30:30 2015 +0200

  Issue 3693: Let Percent_repeat_iterator be unfazed by Timing changes

  There is still one shortcoming: the percent repeats will not contain any
  material apart from the percent itself.  In particular, no Timing
  changes will be repeated.  If there are meter changes or \partial
  commands inside of percent repeats, they need to occur in parallel
  passages outside of any percent repeat, if necessary in a separate
  "timing track".

is indeed the problem.


Thanks for your work on this issue!


And for me in creating it.


Hey, that's no problem at all – your work for LilyPond is just great, 
and the speed in which errors like these are corrected is just awesome!


Marc

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Layout of a (piano) hand indicator

[Urs Liska]

Hi all,

please consider the attached image, especially the "half-bracket" at the
center. This is to indicate that this d' is to be played with the left hand.

Is there anything I could improve to the proportions and placement of
that sign?

Any suggestions for improvement welcome. Suggestions for *not* improving
it even more ;-)

Best
Urs

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Layout of a (piano) hand indicator

[tisimst]

Urs,

On Tuesday, November 24, 2015, Urs Liska [via Lilypond] <
ml-node+s1069038n18406...@n5.nabble.com> wrote:

> Hi all,
>
> please consider the attached image, especially the "half-bracket" at the
> center. This is to indicate that this d' is to be played with the left
> hand.
>
> Is there anything I could improve to the proportions and placement of
> that sign?
>
> Any suggestions for improvement welcome. Suggestions for *not* improving
> it even more ;-)
>
> Best
> Urs
>
>
> ___
> lilypond-user mailing list
> [hidden email] 
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
> *gesang.png* (11K) Download Attachment
> 
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://lilypond.1069038.n5.nabble.com/Layout-of-a-piano-hand-indicator-tp184061.html
> To start a new topic under User, email ml-node+s1069038n...@n5.nabble.com
> 
> To unsubscribe from Lilypond, click here
> 
> .
> NAML
> 
>

I did a blog post about this very thing! You'll have to look back a ways
though in the archives (not lilypondblog). I probably wouldn't make the
vertical section quite so long.

Best

Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Layout-of-a-piano-hand-indicator-tp184061p184063.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Layout of a (piano) hand indicator

[Kieren MacMillan]

Hi all,

> I did a blog post about this very thing!



Hope this helps!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Table of Contents: 2 problems

[Simon Albrecht]

On 24.11.2015 14:30, David Sumbler wrote:

the snippet does not have a "version"
statement.


The LSR currently supports 2.18.

Yours, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Strange LilyPond crash

[David Kastrup]

Marc Hohl  writes:

> Am 24.11.2015 um 00:12 schrieb Thomas Morley:
> [...]
>>
>> So,
>> commit b416f10429d8d3881445d9000ff422dc67176df1
>> Author: David Kastrup 
>> Date:   Wed Jul 15 23:30:30 2015 +0200
>>
>>  Issue 3693: Let Percent_repeat_iterator be unfazed by Timing changes
>>
>>  There is still one shortcoming: the percent repeats will not contain any
>>  material apart from the percent itself.  In particular, no Timing
>>  changes will be repeated.  If there are meter changes or \partial
>>  commands inside of percent repeats, they need to occur in parallel
>>  passages outside of any percent repeat, if necessary in a separate
>>  "timing track".
>>
>> is indeed the problem.
>
> Thanks for your work on this issue!

And for me in creating it.

>> Now it would be nice I'd could come up with a tiny example...
>>
>> Though, very strange things happen, like:
>>
>> assume file-1.ly with
>>
>> foo = { some-music }
>> buzz = { some-other-music }
>>
>> and
>>
>> file-2.ly with
>>
>> \include "file-1.ly"
>> \score {
>><<
>>\new Staff \foo
>>\new Staff \buzz
>>>>
>>
>> compiling file-2.ly causes a segfault.
>> commenting \new Staff \buzz still causes a segfault
>> additional commenting(!) buzz = { some-other-music } in file-1.ly,
>> and the segfault disappears!!!
>> But it's not consistent! It depends what else is defined in those files.
>
> Yep. Moreover, if I removed some notes from buzz, the segfault
> disappeared, but adding one single note causes Lilypond to crash,
> and we talk about scores with 3-5 pages or even less.

Garbage collection errors tend to behave somewhat erratically.

Ticket created at: https://sourceforge.net/rest/p/testlilyissues/issues/4670/

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: Layout of a (piano) hand indicator

[Mark Stephen Mrotek]

Urs,

V 2.18 has a snippet at:
http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-keyboards#staff_002dchange-lines

Mark

-Original Message-
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org 
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Urs 
Liska
Sent: Tuesday, November 24, 2015 9:50 AM
To: lilypond-user 
Subject: Layout of a (piano) hand indicator

Hi all,

please consider the attached image, especially the "half-bracket" at the 
center. This is to indicate that this d' is to be played with the left hand.

Is there anything I could improve to the proportions and placement of that sign?

Any suggestions for improvement welcome. Suggestions for *not* improving it 
even more ;-)

Best
Urs



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [Best Practices] splitting and combining choral parts

[Kieren MacMillan]

Hi Simon,

> first of all: Looks like a nice piece!

Thanks! You can hear it at , if 
you’re interested.

> Second: offtopic nitpicks. There are some superfluous LyricExtenders there – 
> I’d rather leave them out if they are very short

I include all LyricExtenders, until the layout is finalized; only then can I 
possibly know whether they’re “too short”.  :)

> And note the mid-air bar-numbers, where they are aligned with ScoreMarks. I’d 
> move Bar_number_engraver to the topmost staff.

That’s a whole separate Lilypond bug, which I deal with using the 
edition-engraver. Note also that your solution is insufficient, since the 
topmost staff will periodically disappear and reappear (frenched score).

> And I like for long syllables to be increasingly left-aligned

This is one of the many, many lyric-related problems in Lilypond. (See my 
numerous other posts and sponsorship offers on that topic.) I solve almost all 
of them post-hoc, using the edition-engraver.

> for which I wrote a custom grob callback.

I’d be happy to look at that, if you’re willing to share it.
(I have yet to find a callback that satisfies me in that regard.)

> I’d vote to keep with four staves, at least in this example.

Thanks for the vote…  :)

But I’ll be outputting at least four different scores for this piece: full 
score (U.S. letter), vocal score (U.S. letter), and vocal score (octavo). I am 
trying to reduce the number of pages, both to keep page turning to a minimum, 
and because many customers will be downloading PDFs and printing their own (and 
I want to minimize their printing costs).

Additionally, I find unnecessary redundancy in scores irritating as both a 
conductor/performer and as an aesthete. My goal is always to include the bare 
minimum information to get the job done as efficiently and elegantly as 
possible.

> It _would_ of course be great to have a good mechanism for that in LilyPond, 
> but it looks like a really involved task.

I don’t think so… We have \quoteDuring, and \divisi, and a number of other 
great features. I was just hoping I didn’t have to roll my own solution, 
without any extra eyes.

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [Best Practices] splitting and combining choral parts

[Michael Gerdau]

Hie Kieren and Simon,

> first of all: Looks like a nice piece!

Yes :)

> Second: offtopic nitpicks. There are some superfluous LyricExtenders
> there – I’d rather leave them out if they are very short.

I agree on that one.

> And I like for long syllables
> to be increasingly left-aligned, for which I wrote a custom grob callback.

I'm torn between liking it and not liking it...
...will have to look at it some more time :)

> I’d vote to keep with four staves, at least in this example.

I again agree. I find switches between the number of staves for short
periods (i.e. a few bars this, a few bars that and another few bars some
other way) confusing and it takes too much of my precious attention
when performing.

> The other major point is that
> it doesn’t print ‘redundant’ lyrics, i.e. passages with equal rhythm and
> wording in multiple voices have the lyrics printed only once, mostly
> below the topmost of the staves. This is certainly a controversial
> feature,

Yes, it definitely *IS* controversial :)

I'm a bass singer. if you really wish to leave out the redundant lyrics
then do so for all other voices but bass ;)

Seriously :
If you wish to leave out lyrics then at least put them between soprano
and alto and between tenor and bass. That way each voice has lyrics
adjacent to the music.

I find the distance between lyrics and music in Simon's version too
close. To my eyes it appears cramped and makes it less easy to read
during performance.

Last not least for vocal lines I always turn off autoBeam and manually
put beams to groups that are sung on a single syllable. For my singers
eyes that strongly helps to keep words and music in a proper flow.

I'm sure from a keyboard player's perspective this is different. I know
as a violinist I would want autoBeam on as well :)

Find attached my preferences applied to the original score.

Kind regards,
Michael
--
 Michael Gerdau   email: m...@qata.de
 GPG-keys available on request or at public keyserver\version "2.19"
\language "english"

#(set-global-staff-size 15.5)

\paper {
  page-count = 2
  system-count = 5
  ragged-bottom = ##t
  ragged-last-bottom = ##t
  system-system-spacing = #'((minimum-distance . 18) (padding . 8))
}

\layout {
  \context {
\Voice
\consists "Melody_engraver"
\override Stem #'neutral-direction = #'()
  }
  \context {
\Staff
\name ChoralStaff
\alias Staff
\override DynamicLineSpanner.direction = #UP
\override Script.direction = #UP
\override TextScript.direction = #UP
\override TupletBracket.direction = #UP
\override TupletNumber.direction = #UP
  }
  \context {
\ChoirStaff
\accepts ChoralStaff
  }
  \context {
\type "Engraver_group"
\name ScoreMarks
\consists "Staff_collecting_engraver"
\consists "Axis_group_engraver"
\override VerticalAxisGroup.staff-affinity = #DOWN
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing #'((basic-distance . 1) (minimum-distance . 1) (padding . 2) (stretchability . 0))
\override VerticalAxisGroup.nonstaff-unrelatedstaff-spacing #'((basic-distance . 6) (minimum-distance . 6) (padding . 4) (stretchability . 0))
\override VerticalAxisGroup.nonstaff-nonstaff-spacing #'((basic-distance . 1) (minimum-distance . 1) (padding . 1) (stretchability . 0))
\consists "Metronome_mark_engraver"
\override MetronomeMark.font-size = #2
\override MetronomeMark.font-series = #'normal
\override MetronomeMark.Y-offset = ##f
\override MetronomeMark.padding = #2
\override MetronomeMark.break-align-symbols = #'(time-signature key-signature)
\override MetronomeMark.non-break-align-symbols = #'(paper-column-interface)
\consists "Text_spanner_engraver"
\override TextSpanner.font-size = #2
\consists "Mark_engraver"
\override RehearsalMark.Y-offset = ##f
\override RehearsalMark.outside-staff-priority = #75
\override RehearsalMark.font-size = #2
\override RehearsalMark.break-align-symbols = #'(time-signature key-signature)
\consists "Time_signature_engraver"
\override TimeSignature.stencil = #point-stencil
  }
  \context {
\Score
\remove "Metronome_mark_engraver"
\remove "Mark_engraver"
\accepts ScoreMarks
\override TimeSignature.style = #'()
\override BarNumber.font-size = #2.5
\override BarNumber.padding = #2
  }
}

  GLOBAL  

\header {
  title = "Wither’s Carol"
}

WithersCarol_global = {
  %%  v. 1
\key d \major
\tempo "Brightly" 48
\time 2/4
\partial 8 s8
s4*2
\time 4/4
s4*4
\time 2/4
s4*2*3
\time 4/4
s4*4
\time 2/4
s4*2*2
\time 7/8
s8*7
\time 2/4
s4*2
\time 4/4
\tempo \markup "Relaxing slightly"
s1*2
\tempo "Like a madrigal" 4€
s1
\time 9/8
s8*9
\time 4/4
s2
\tempo \markup "poco rit."
s1
\tempo \markup "regain tempo"
s2 s1
\bar "||"
}


  VOICES  

Re: [Best Practices] splitting and combining choral parts

[Michael Gerdau]

> > Last not least for vocal lines I always turn off autoBeam and manually
> > put beams to groups that are sung on a single syllable. For my singers
> > eyes that strongly helps to keep words and music in a proper flow.
> 
> It’s rather a question of rhythmic complexity; with long and/or
> oft-changing measures it helps to have normal beaming.

I understand that argument and it has its merrit.

However in my experience such complex rythms aren't found too often in
choral music and certainly not in the piece at hand. IMO the advantage
of \autoBeamOff more often outweights the disadavantage but I'm happy
to agree to disagree.
[Note that my whole argument is from a singer's perspective, not an
instrumentalist]

Kind regards,
Michael
-- 
 Michael Gerdau   email: m...@qata.de
 GPG-keys available on request or at public keyserver

signature.asc
Description: This is a digitally signed message part.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Automatically transforming a FiguredBass line into a sequence of chords ?

[Richard Shann]

The fundamental problem you will hit here is that a figured bass is
ambiguous, it only hints at the harmonic sequence, you have to make
judgements about how frequently the chords should be changing, and where
"obvious" changes have been omitted. (So an artificial intelligence
approach would be needed to do it by computer).
FWIW there is a set of Figured Bass exercises by Handel which I've
packaged with Denemo - you can play the chords and they are installed on
a staff above the bass notes. You can use this "Play Chords over Bass"
command for any score - I've used this to provide a guide realization
for accompanists who don't read from the figured bass directly. Then you
can take the LilyPond output for that staff. But you do have to be able
to play from the figures yourself for this, albeit as slowly as you like
- it waits for you to play the bass note before listening for the
chord(s).

Richard

On Mon, 2015-11-23 at 23:56 +0100, Michael Gerdau wrote:
> Hi list,
> 
> does someone know of a function or snipped that automatically transforms
> some music together with a FigruedBass line into a sequence of chords
> like illustrated in the example below ?
> 
> %%%
> \version "2.19.31"
> 
> bcMusic = \relative {
>   c2 c | c c | c c | c c |
> }
> 
> bcFigures = \figuremode {
>   \override Staff.BassFigureAlignmentPositioning #'direction = #DOWN
>   \bassFigureExtendersOn
>   \set figuredBassPlusDirection = #RIGHT
>   \set figuredBassAlterationDirection = #RIGHT
>   <5 3>2 <5 3> | <6 5+ 2>4 <6 4! 2> <6 4! 2>2 | <6\! 5> <6 5> |
>   <9 4>4 <8 3>4 <8 3>2
> }
> 
> \markup { "Is there a function that transforms this FiguredBass line..." }
> <<
>   \new Staff {
> \clef bass \bcMusic
>   }
>   \new FiguredBass \bcFigures
> >>
> 
> result = \relative {
>   2  | 4  2 |
> | 4  2 |
> }
> 
> \markup { "...automatically into this sequence of chords ?" }
> \new Staff { \clef bass \result }
> 
> \markup { "(hoping I got it right manually :)" }
> 
> %%%
> 
> Kind regards,
> Michael
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: function to replace notes by rests

[David Kastrup]

Marc Hohl  writes:

> Am 23.11.2015 um 21:41 schrieb Malte Meyn:
>> Am 23.11.2015 um 10:46 schrieb Marc Hohl:
>>> As the file is a bit lengthy, I think of a way to just redefine
>>> \xNotes to change every note to its corresponding rest, instead of
>>> rewriting the whole file (or using sed or any other external script).
>>>
>>> Has anyone a scheme routine at hand that does exactly this job?
>
> Malte,
>
>> I wrote this but it doesn’t work well in relative mode:
>>
>> \version "2.19.30"
>>
>> notesToRests =
>> #(define-music-function (music) (ly:music?)
>> (music-map
>>  (lambda (m)
>>(if (eq? (ly:music-property m 'name) 'NoteEvent)
>>(make-music 'RestEvent
>>  'duration (ly:music-property m 'duration))
>>m))
>>  music))
>>
>> \relative {
>>c' d e f \notesToRests { g a b2 g8 c } f e c2
>> }
>
> Thanks or sharing! The drawbacks in relative mode are neglectable,
> I'll use absolute mode.

\version "2.19.30"

notesToRests =
#(define-music-function (music) (ly:music?)
   (make-relative (music) music
(music-map
 (lambda (m)
   (if (eq? (ly:music-property m 'name) 'NoteEvent)
   (make-music 'RestEvent
 'duration (ly:music-property m 'duration))
   m))
 (ly:music-deep-copy music

\relative {
   c' d e f \notesToRests { g a b2 g8 c } f e c2
}

-- 
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: function to replace notes by rests

[Marc Hohl]

Am 24.11.2015 um 09:52 schrieb David Kastrup:
[...]

Even better, thanks a lot!



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: function to replace notes by rests

[Robin Bannister]

Marc Hohl wrote:


Now I need a midi file that contains the "normal" notes only:


Skips would be quiet too.


notesToSkips =
#(define-music-function (music) (ly:music?)
(skip-of-length music))


Cheers,
Robin

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: function to replace notes by rests

[Marc Hohl]

Am 24.11.2015 um 10:43 schrieb Marc Hohl:

Am 24.11.2015 um 09:52 schrieb David Kastrup:
[...]

Even better, thanks a lot!


Well, nearly there. Is it possible to use this function only within a 
certain Staff?


If I write

xNote =
#(define-music-function (music) (ly:music?)
   (make-relative (music) music
(music-map
 (lambda (m)
   (if (eq? (ly:music-property m 'name) 'NoteEvent)
   (make-music 'RestEvent
 'duration (ly:music-property m 'duration))
   m))
 (ly:music-deep-copy music

\include "myfiles.ily" % <- \mel and \text defined here

\score {
  <<
\new Staff {
   \new Voice = "mel" { \mel }
}
\new Lyrics \lyricsto "mel" { \text }
\new Staff \with { midiInstrument = "alto sax" } { \mel }
  >>
  \midi { }
  \layout { }
}

the lyrics are displaced because the "spoken" notes are replaced 
globally with rests. This is a feature for proofreading only,

if there is no easy way, I'll comment out the first staff with the lyrics.

Marc





___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Suggestion for spacing pagenumber and barnumber

[Kieren MacMillan]

Hi Urs,

> how would you suggest to handle this unpleasant situation
> between the barnumber and the pagenumber?

Bar number italic + page number bold + more spacing, e.g.,



That seems very clear to me (which is why I do it that way).

Hope this helps!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Table of Contents: 2 problems

[David Sumbler]

On Tue, 2015-11-24 at 14:47 +0100, David Kastrup wrote:
> David Sumbler  writes:
> 
> > I have experimented with elements from the all the suggestions made -
> > thanks to all.  One thing that has been confirmed is that my
> > understanding of how to use markup commands is pretty poor.
> >
> > I still have not managed to solve all of the problems.  I tried to test
> > Graham's suggestion of a modification of part of Nicolas Sceaux's
> > book-titling snippet.  But when I try to compile the whole snippet
> > (which has a demo at the end of it) I get an error.
> >
> > I am using Lilypond 2.19.30; the snippet does not have a "version"
> > statement.  The error I am getting stems from the fact that in the
> > snippet the procedure 'collect-music-for-book' is always called with 2
> > arguments: (collect-music-for-book parser (make-music # # ...)).  When I
> > look in the lily-library.scm in my current Lilypond installation, I see
> > that it should only have 1 argument, e.g.
> > (collect-music-for-book (make-music # # ...)).
> >
> > I have tried putting an old version number at the top of the snippet
> > (e.g. "version" 2.16.1) and running convert.ly, but no significant
> > changes are made to the file.
> >
> > How can I get this snippet to work?
> 
> I presume you are talking about snippet 368?
> 
> Putting on old version number at the top of the snippet and running
> convert-ly works here.  Do you have the wrong convert-ly perhaps?
> 
> I get as diff (from 2.18.0)
> 
> differences between files attachment (lsr368.diff)
> --- /tmp/Snippet  2015-11-24 14:39:21.482732193 +0100
> +++ - 2015-11-24 14:44:36.648156076 +0100
> @@ -1,3 +1,4 @@
> +\version "2.19.32"
>  %% http://lsr.di.unimi.it/LSR/Item?id=368
>  %% see also 
> http://www.lilypond.org/doc/v2.18/Documentation/snippets/paper-and-layout 
>  %% see also http://nicolas.sceaux.free.fr/
> @@ -236,7 +237,7 @@
> (set! odd-label-header-table
>   (cons (list label text display-1st)
> odd-label-header-table))
> -   (collect-music-for-book parser
> +   (collect-music-for-book
>   (make-music 'Music
>'page-marker #t
>'page-label label)
> @@ -246,7 +247,7 @@
> (set! even-label-header-table
>   (cons (list label text display-1st)
> even-label-header-table))
> -   (collect-music-for-book parser
> +   (collect-music-for-book
>   (make-music 'Music
>'page-marker #t
>'page-label label))
> @@ -266,23 +267,23 @@
>  %%% Utilities for adding (no-)page breaks, toplevel markups
>  %%%
>  #(define (add-page-break parser)
> -  (collect-music-for-book parser 
> +  (collect-music-for-book 
> (make-music 'Music
>  'page-marker #t
>  'line-break-permission 'force
>  'page-break-permission 'force)))
>  
>  #(define (add-no-page-break parser)
> -  (collect-music-for-book parser 
> +  (collect-music-for-book 
> (make-music 'Music
>  'page-marker #t
>  'page-break-permission 'forbid)))
>  
>  #(define (add-toplevel-markup parser text)
> -  (collect-scores-for-book parser (list text)))
> +  (collect-scores-for-book (list text)))
>  
>  #(define (add-toc-item parser markup-symbol text)
> -  (collect-music-for-book parser
> +  (collect-music-for-book
> (add-toc-item! markup-symbol text)))
>  
>  
> @@ -302,7 +303,7 @@
>(format #f "~a-~a" major-number minor-number
>  
>  #(define-public (add-rehearsal-number parser)
> -   (collect-scores-for-book parser
> +   (collect-scores-for-book
>  (list (markup #:huge #:bold (rehearsal-number)
>  
>  
> @@ -314,50 +315,50 @@
>  #(define *use-rehearsal-numbers* (make-parameter #f))
>  
>  useRehearsalNumbers =
> -#(define-music-function (parser location use-numbers) (boolean?)
> +#(define-music-function (use-numbers) (boolean?)
>(*use-rehearsal-numbers* use-numbers)
> (make-music 'Music 'void #t))
>  
>  bookTitle =
> -#(define-music-function (parser location title) (string?)
> +#(define-music-function (title) (string?)
> (*book-title* title)
> (make-music 'Music 'void #t))
>  
>  chapter =
> -#(define-music-function (parser location title) (string?)
> +#(define-music-function (title) (string?)
>(increase-rehearsal-major-number)
> -  (add-page-break parser)
> -  (add-toc-item parser 'tocChapterMarkup title)
> -  (add-even-page-header-text parser (string-upper-case (*book-title*)) #f)
> -  (add-odd-page-header-text parser (string-upper-case title) #f)
> -  (add-toplevel-markup parser (markup #:chapter-title (string-upper-case 
> title)))
> -  (add-no-page-break parser)
> +  (add-page-break (*parser*))
> +  (add-toc-item (*parser*) 'tocChapterMarkup title)
> +  (add-even-page-header-text (*parser*) 

Re: Why does \fromproperty fail in instrumentName?

[Robin Bannister]

David Kastrup wrote:


In general, those variables seem to be defined only within titling
material.



http://lists.gnu.org/archive/html/lilypond-user/2008-05/msg00426.html


Cheers,
Robin

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ‘Kerning’ a clef

[Kieren MacMillan]

Hi Simon,

> Thanks, that’s good.

Glad to hear it.

> There are two issues, though:
> – the \tweak version spills over to the next clef

That seems like a straight-up bug…

> and
> – the vertical position of the beam changes:

Hmmm… I’ll be interested to hear if that’s considered a bug. Once a grob has no 
X-extent, it mathematically has no Y-extent either, right? So it shouldn’t 
affect the vertical spacing.

Sounds like a “feature” to me…

=)

Cheers,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

[Best Practices] splitting and combining choral parts

[Kieren MacMillan]

Hello list,

I’ve posted this question several times before, but the discussion always got 
truncated or derailed… I’m hoping this time we can work this through to a 
solution.

Choral pieces tend to have both sections of polyphony (requiring 4 or more 
staves) and sections of homophony (requiring as few as 1 staff). I want to be 
able to arbitrarily break systems and have Lilypond Do The Right Thing™, by 
which I mean use the maximum number of systems when necessary, but combine 
voices and lyrics to 3 or 2 staves or even 1 staff where possible.

Bonus points if we can convince Lily to automagically [e.g., via an engraver?] 
put a user-definable markup indicating who is singing at a given moment, add 
splitting-or-combining arrows at the end(s) of systems, etc.

I’ve attached the first 17 measures of one of my original carols as an example 
we can work with/through. Is anyone out there willing to work with me to find 
the Best Practice here? I’m happy to do this on-list or off-, as appropriate.

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info



WithersCarol_example.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Why does \fromproperty fail in instrumentName?

[Simon Albrecht]

Hello everybody,

help is appreciated with the following minimal example:

\version "2.19.31"
\header {
  test = "test"
}
\new Staff \with {
  instrumentName = \markup\fromproperty #'header:test
} { 4 }


TIA, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Why does \fromproperty fail in instrumentName?

[Simon Albrecht]

On 24.11.2015 13:16, Jacques Menu wrote:

Hello Simon,

Succeeds with 2.19.32.


Huh. Not for me (Ubuntu 14.04, 64bit).
~ Simon



JM


Le 24 nov. 2015 à 13:10, Simon Albrecht  a écrit :

Hello everybody,

help is appreciated with the following minimal example:

\version "2.19.31"
\header {
  test = "test"
}
\new Staff \with {
  instrumentName = \markup\fromproperty #'header:test
} { 4 }


TIA, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Why does \fromproperty fail in instrumentName?

[Jacques Menu]

Hello Simon,

Succeeds with 2.19.32.

JM

> Le 24 nov. 2015 à 13:10, Simon Albrecht  a écrit :
> 
> Hello everybody,
> 
> help is appreciated with the following minimal example:
> 
> \version "2.19.31"
> \header {
>  test = "test"
> }
> \new Staff \with {
>  instrumentName = \markup\fromproperty #'header:test
> } { 4 }
> 
> 
> TIA, Simon
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Table of Contents: 2 problems

[David Sumbler]

I have experimented with elements from the all the suggestions made -
thanks to all.  One thing that has been confirmed is that my
understanding of how to use markup commands is pretty poor.

I still have not managed to solve all of the problems.  I tried to test
Graham's suggestion of a modification of part of Nicolas Sceaux's
book-titling snippet.  But when I try to compile the whole snippet
(which has a demo at the end of it) I get an error.

I am using Lilypond 2.19.30; the snippet does not have a "version"
statement.  The error I am getting stems from the fact that in the
snippet the procedure 'collect-music-for-book' is always called with 2
arguments: (collect-music-for-book parser (make-music # # ...)).  When I
look in the lily-library.scm in my current Lilypond installation, I see
that it should only have 1 argument, e.g.
(collect-music-for-book (make-music # # ...)).

I have tried putting an old version number at the top of the snippet
(e.g. "version" 2.16.1) and running convert.ly, but no significant
changes are made to the file.

How can I get this snippet to work?

David



On Sat, 2015-11-21 at 11:56 +, David Sumbler wrote:
> I have not used a Table of Contents before, and I am having some
> difficulty in getting the result I want.  I have 2 problems.
> 
> 1) I would like to have a dotted line between the title and the page
> number in each line.  But if I use
> 
> tocItemMarkup = \tocItemWithDotsMarkup
> 
> then there does not seem to be a way of formatting the text the way I
> want to (larger font etc.).
> 
> As an alternative I have tried defining tocItemMarkup including
> 
> \fill-with-pattern #1 #RIGHT .
> 
> This results in a space between the dots
> and the page number; I get a similar result with
> \fill-with-pattern #1 #CENTER .
> 
> 2) The table of contents appears at the top of a page which already has
> a couple of paragraphs of text on it.  This page is defined as a
> separate \bookpart, and has its own \paper block setting a wider
> 'inner-margin' and 'outer-margin' than I use for the actual scores.
> 
> I would like the table of contents to have wider margins still, but a
> second \paper block on the same page does not work, and changing
> 'indent' effectively only increases the right margin.  I have tried
> experimenting with a \hspace before and after the contents of the line,
> e.g.
> 
> tocItemMarkup = \markup \fontsize #5 \fill-line {
>   \hspace #1 { \fill-with-pattern #1 #RIGHT .
>   \fromproperty #'toc:text \fromproperty #'toc:page } \hspace #1 }
> 
> but this just doesn't work.  (Please forgive my feeble attempts at using
> markup, which I still find rather cryptic!)
> 
> David
> 



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Table of Contents: 2 problems

[David Kastrup]

David Sumbler  writes:

> I have experimented with elements from the all the suggestions made -
> thanks to all.  One thing that has been confirmed is that my
> understanding of how to use markup commands is pretty poor.
>
> I still have not managed to solve all of the problems.  I tried to test
> Graham's suggestion of a modification of part of Nicolas Sceaux's
> book-titling snippet.  But when I try to compile the whole snippet
> (which has a demo at the end of it) I get an error.
>
> I am using Lilypond 2.19.30; the snippet does not have a "version"
> statement.  The error I am getting stems from the fact that in the
> snippet the procedure 'collect-music-for-book' is always called with 2
> arguments: (collect-music-for-book parser (make-music # # ...)).  When I
> look in the lily-library.scm in my current Lilypond installation, I see
> that it should only have 1 argument, e.g.
> (collect-music-for-book (make-music # # ...)).
>
> I have tried putting an old version number at the top of the snippet
> (e.g. "version" 2.16.1) and running convert.ly, but no significant
> changes are made to the file.
>
> How can I get this snippet to work?

I presume you are talking about snippet 368?

Putting on old version number at the top of the snippet and running
convert-ly works here.  Do you have the wrong convert-ly perhaps?

I get as diff (from 2.18.0)

--- /tmp/Snippet	2015-11-24 14:39:21.482732193 +0100
+++ -	2015-11-24 14:44:36.648156076 +0100
@@ -1,3 +1,4 @@
+\version "2.19.32"
 %% http://lsr.di.unimi.it/LSR/Item?id=368
 %% see also http://www.lilypond.org/doc/v2.18/Documentation/snippets/paper-and-layout 
 %% see also http://nicolas.sceaux.free.fr/
@@ -236,7 +237,7 @@
(set! odd-label-header-table
  (cons (list label text display-1st)
odd-label-header-table))
-   (collect-music-for-book parser
+   (collect-music-for-book
  (make-music 'Music
   'page-marker #t
   'page-label label)
@@ -246,7 +247,7 @@
(set! even-label-header-table
  (cons (list label text display-1st)
even-label-header-table))
-   (collect-music-for-book parser
+   (collect-music-for-book
  (make-music 'Music
   'page-marker #t
   'page-label label))
@@ -266,23 +267,23 @@
 %%% Utilities for adding (no-)page breaks, toplevel markups
 %%%
 #(define (add-page-break parser)
-  (collect-music-for-book parser 
+  (collect-music-for-book 
(make-music 'Music
 	   'page-marker #t
 	   'line-break-permission 'force
 	   'page-break-permission 'force)))
 
 #(define (add-no-page-break parser)
-  (collect-music-for-book parser 
+  (collect-music-for-book 
(make-music 'Music
 	   'page-marker #t
 	   'page-break-permission 'forbid)))
 
 #(define (add-toplevel-markup parser text)
-  (collect-scores-for-book parser (list text)))
+  (collect-scores-for-book (list text)))
 
 #(define (add-toc-item parser markup-symbol text)
-  (collect-music-for-book parser
+  (collect-music-for-book
(add-toc-item! markup-symbol text)))
 
 
@@ -302,7 +303,7 @@
   (format #f "~a-~a" major-number minor-number
 
 #(define-public (add-rehearsal-number parser)
-   (collect-scores-for-book parser
+   (collect-scores-for-book
 (list (markup #:huge #:bold (rehearsal-number)
 
 
@@ -314,50 +315,50 @@
 #(define *use-rehearsal-numbers* (make-parameter #f))
 
 useRehearsalNumbers =
-#(define-music-function (parser location use-numbers) (boolean?)
+#(define-music-function (use-numbers) (boolean?)
   (*use-rehearsal-numbers* use-numbers)
(make-music 'Music 'void #t))
 
 bookTitle =
-#(define-music-function (parser location title) (string?)
+#(define-music-function (title) (string?)
(*book-title* title)
(make-music 'Music 'void #t))
 
 chapter =
-#(define-music-function (parser location title) (string?)
+#(define-music-function (title) (string?)
   (increase-rehearsal-major-number)
-  (add-page-break parser)
-  (add-toc-item parser 'tocChapterMarkup title)
-  (add-even-page-header-text parser (string-upper-case (*book-title*)) #f)
-  (add-odd-page-header-text parser (string-upper-case title) #f)
-  (add-toplevel-markup parser (markup #:chapter-title (string-upper-case title)))
-  (add-no-page-break parser)
+  (add-page-break (*parser*))
+  (add-toc-item (*parser*) 'tocChapterMarkup title)
+  (add-even-page-header-text (*parser*) (string-upper-case (*book-title*)) #f)
+  (add-odd-page-header-text (*parser*) (string-upper-case title) #f)
+  (add-toplevel-markup (*parser*) (markup #:chapter-title (string-upper-case title)))
+  (add-no-page-break (*parser*))
   (make-music 'Music 'void #t))
 
 section =
-#(define-music-function (parser location title) (string?)
-  (add-toc-item parser 'tocSectionMarkup title)
-  

Re: Why does \fromproperty fail in instrumentName?

[Jacques Menu]

I’m on Mac OS X 10.11.1, 64 bit too.

JM


> Le 24 nov. 2015 à 13:35, Simon Albrecht  a écrit :
> 
> On 24.11.2015 13:16, Jacques Menu wrote:
>> Hello Simon,
>> 
>> Succeeds with 2.19.32.
> 
> Huh. Not for me (Ubuntu 14.04, 64bit).
> ~ Simon
> 
>> 
>> JM
>> 
>>> Le 24 nov. 2015 à 13:10, Simon Albrecht  a écrit :
>>> 
>>> Hello everybody,
>>> 
>>> help is appreciated with the following minimal example:
>>> 
>>> \version "2.19.31"
>>> \header {
>>>  test = "test"
>>> }
>>> \new Staff \with {
>>>  instrumentName = \markup\fromproperty #'header:test
>>> } { 4 }
>>> 
>>> 
>>> TIA, Simon
>>> 
>>> ___
>>> lilypond-user mailing list
>>> lilypond-user@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Suggestion for spacing pagenumber and barnumber

[Urs Liska]

Hi list,

how would you suggest to handle this unpleasant situation between the
barnumber and the pagenumber?

Thanks
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Why does \fromproperty fail in instrumentName?

[David Kastrup]

Simon Albrecht  writes:

> On 24.11.2015 13:16, Jacques Menu wrote:
>> Hello Simon,
>>
>> Succeeds with 2.19.32.
>
> Huh. Not for me (Ubuntu 14.04, 64bit).

In general, those variables seem to be defined only within titling
material.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Suggestion for spacing pagenumber and barnumber

[Urs Liska]

Thanks,

I think it looks much better now. Somehow imagination evaded me ...

Best
Urs

Am 24.11.2015 um 15:26 schrieb Kieren MacMillan:
> Hi Urs,
>
>> how would you suggest to handle this unpleasant situation
>> between the barnumber and the pagenumber?
>
> Bar number italic + page number bold + more spacing, e.g.,
>
> ...
>
> That seems very clear to me (which is why I do it that way).
>
> Hope this helps!
> Kieren.
> 
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info 
> ‣ email: i...@kierenmacmillan.info 
>

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user