Re: One staff, two voices
On Sun, Oct 28, 2012 at 3:25 AM, Daniel Rosen wrote: >[...] > This is the first time I've answered a question on the list That's great! I find your answer clear and helpful - hopefully Mark will like it, too :) > but I don't think I'd be out of line by asking you to use tiny examples in > the future. +1 (I agree) see also http://www.lilypond.org/tiny-examples.html cheers, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Changing program defaults
On Sun, Oct 28, 2012 at 7:40 AM, Daniel Rosen wrote: > That's really OK in my case--no one else I know uses LilyPond. :-P You never know what will happen in the future :) Anyway, i wouldn't do it. Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: A documentation suggestion, was: Problem with remove bar number/ why I'm not upgrading to the new stable version
+1 for updating documentation. On Sat, Oct 27, 2012 at 3:05 PM, james wrote: > Perhaps there is a much simpler solution. Notation reference, 1.3.1 is where > I got the example which I have been using since at least 2.12, because > centering such a new dynamic is probably rarer than having it left-aligned, I > think it would be useful to note that there's an easy way of doing this. A > minor change from the example in the documentation. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problem with remove bar number/ why I'm not upgrading to the new stable version
On Sun, Oct 28, 2012 at 2:18 AM, Kevin Patrick Barry wrote: > Dear LilyPond users, > > I have found the recent debate about the difficulty of using LilyPond > interesting and would like to offer my experience, as someone who has > been using it for about six months. I apologise if this is a bit > long. Not at all, thanks for your feedback! I'm crossing fingers for your project :) Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Modified laissez vibrer ties
On Sun, Oct 28, 2012 at 7:28 AM, Daniel Rosen wrote: > Is there a way to extend laissez vibrer ties so that they stop just short of > the barline, > as in the attached example? I can't seem to find a way that doesn't involve > manually adjusting control points. You may consider using a trick: create ties attached to hidden notes. See http://lilypond.org/doc/v2.14/Documentation/notation/inside-the-staff#hidden-notes hth, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Modified laissez vibrer ties
I did consider that; the problem is those ties go _over_ the barline instead of stopping just short, so they'd still need to be adjusted manually. DR -Original Message- From: Janek Warchoł [mailto:janek.lilyp...@gmail.com] Sent: Sunday, October 28, 2012 3:31 AM To: Daniel Rosen Cc: lilypond-user@gnu.org Subject: Re: Modified laissez vibrer ties On Sun, Oct 28, 2012 at 7:28 AM, Daniel Rosen wrote: > Is there a way to extend laissez vibrer ties so that they stop just > short of the barline, as in the attached example? I can't seem to find a way > that doesn't involve manually adjusting control points. You may consider using a trick: create ties attached to hidden notes. See http://lilypond.org/doc/v2.14/Documentation/notation/inside-the-staff#hidden-notes hth, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Modified laissez vibrer ties
On Sun, Oct 28, 2012 at 8:44 AM, Daniel Rosen wrote:
> I did consider that; the problem is those ties go _over_ the barline instead
> of stopping just short, so they'd still need to be adjusted manually.
Not if you scale the durations:
{ r2 2*7/8 ~ \hideNotes q2*1/8 \unHideNotes R1 }
but i admit that it doesn't look perfect.
Janek
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Modified laissez vibrer ties
On 28/10/12 17:28, Daniel Rosen wrote:
> Is there a way to extend laissez vibrer ties so that they stop just short of
> the barline, as in the attached example? I can't seem to find a way that
> doesn't involve manually adjusting control points.
You can change the default length of LV ties to make them longer, though
they won't adjust their length to scale to the next barline:
\version "2.16.0"
#(define ((alter-lv-tie-curve offsets) grob)
(let ((coords (ly:semi-tie::calc-control-points grob)))
(define (add-offsets coords offsets)
(if (null? coords)
'()
(cons
(cons (+ (caar coords) (car offsets))
(+ (cdar coords) (cadr offsets)))
(add-offsets (cdr coords) (cddr offsets)
(add-offsets coords offsets)))
xlv = \override LaissezVibrerTie #'before-line-breaking = #(lambda (grob)
(set! (ly:grob-property grob 'control-points)
(if (= UP (ly:grob-property grob 'direction))
((alter-lv-tie-curve '(0 0 0.75 0.7 2.25 0.7 3 0)) grob)
((alter-lv-tie-curve '(0 0 0.75 -0.7 2.25 -0.7 3 0)) grob
\relative c' {
\xlv
c1 \laissezVibrer c
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: custom voiceStyle
Ofcourse, thank you David. Changed my template to Voice instead of Staff
and everything works like a charm!
Thanks for all the help and kind regards, Gagi
On 27 October 2012 10:55, David Kastrup wrote:
> Gagi Petrovic writes:
>
> > Allright, so the problem seems to be something else. When i use your
> > exact code it does work (see directMacro.png). But i'd like to use it
> > via my "template.ly" file which is in the
> > "/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/ly"
> > directory. So i could do something like
> >
> > \version "2.14.2"
> > \include "template.ly"
> >
> > \new Staff {
> > \relative c'' {
> > <<
> > \new Voice {\voiceOne d2~\( d8[es] as16[f g8]\) }
> > \new Voice {\voiceTwo \diamond d2~ d2 }
> >>> \oneVoice
> > }
> > }
> >
> > and then somehow i get the result you see in templateMacro.png..
> > my "template.ly" consists of
> >
> > cross = \override Staff.NoteHead #'style = #'cross
> > xcircle = \override Staff.NoteHead #'style = #'xcircle
> > diamond = \override Staff.NoteHead #'style = #'diamond
> > triangle = \override Staff.NoteHead #'style = #'triangle
> > mensural = \override Staff.NoteHead #'style = #'mensural
> > notehead = \override Staff.NoteHead #'style = #'default
> >
> > among other things. This always works perfectly, but not when i am
> > using multiple voices in one staff.
> >
> > Any ideas of what the problem could be are appreciated greatly. Thank
> > you and kind regards, Gagi
>
> If you are overriding Staff.NoteHead, it should not come as much of a
> surprise that as a result all noteheads in a Staff as opposed to just
> the noteheads in a Voice are getting changed.
>
> --
> David Kastrup
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
--
+31 6 1259 8681 |
LinkedIn
| gagipetrovic.nl
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Modified laissez vibrer ties
Daniel Rosen writes: > I did consider that; the problem is those ties go _over_ the barline > instead of stopping just short, so they'd still need to be adjusted > manually. I tried using normal ties to invisible notes after the barline and tweaking to-barline in order to have them stop short. I have not been able to make to-barline have any effect, though. Huh. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: A documentation suggestion, was: Problem with remove bar number/ why I'm not upgrading to the new stable version
Janek Warchoł writes: >> On Sat, Oct 27, 2012 at 3:05 PM, james wrote: >>> Perhaps there is a much simpler solution. Notation reference, 1.3.1 >>> is where I got the example which I have been using since at least >>> 2.12, because centering such a new dynamic is probably rarer than >>> having it left-aligned, I think it would be useful to note that >>> there's an easy way of doing this. A minor change from the example >>> in the documentation. > > > +1 for updating documentation. Would make sense for the bug squad to register the proposal. I don't think it would be suitable in the proposed form but that does not mean we should ignore it. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: One staff, two voices
Hi Janrek,Thanks for pointing to the Tiny Examples section. Didn't know this existed, good idea. In programming it is a common method to squeeze your problem to something as small as possible. Also a good start for any regression test.But the top part of the example shown uses an include-file. That is not "tiny", anything can happen there. So I would add to the rules for a tiny example no use of include files.And the page tells about an example? What example you want:- what this example of a problem produces (everyone can grab the code and see for himself, but showing it right away is much, much faster for everyone)- what the author wants to happen (likes something not accomplished but desired)- or both (my preference)And how does one place an example there? (and remove when not valid anymore, for example if your tiny tie-problem -- which is ugly indeed! -- is solved in a next version, this example may be updated with the text "Solved" and removed in the next run.)Regards,Wim.P.S. My tiny example:Wanted attached in a small example (not realized), code I think should produce it:\version "2.16.0"{ \key f \major \time 4/4 \slashedGrace { \stemDown d'32[ c'] } \stemUp f32[c' f' g' a' g' f' c']}On 28 Oct 2012, at 08:19 , Janek Warchoł wrote:On Sun, Oct 28, 2012 at 3:25 AM, Daniel Rosen wrote:[...]This is the first time I've answered a question on the listThat's great! I find your answer clear and helpful - hopefully Markwill like it, too :)but I don't think I'd be out of line by asking you to use tiny examples in the future.+1 (I agree)see also http://www.lilypond.org/tiny-examples.htmlcheers,Janek___lilypond-user mailing listlilypond-user@gnu.orghttps://lists.gnu.org/mailman/listinfo/lilypond-user___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Changing program defaults
Daniel Rosen writes: > That's really OK in my case--no one else I know uses LilyPond. :-P And at the next update things change, and then somebody else _does_ ask you for it, willing to help with things, and so on and so on. Then you try asking here on the list for some fine-polishing of a score, and nobody can reproduce your layout. Janek has engaged half his choir in entering some scores. Having a standard setup really has advantages. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: A documentation suggestion, was: Problem with remove bar number/ why I'm not upgrading to the new stable version
On Sun, Oct 28, 2012 at 11:09 AM, David Kastrup wrote: > Janek Warchoł writes: >> +1 for updating documentation. > > Would make sense for the bug squad to register the proposal. I don't > think it would be suitable in the proposed form but that does not mean > we should ignore it. Forwarded to bug-lilypond. Bug Squad, please look at "A documentation suggestion, was: Problem with remove bar number/ why I'm not upgrading to the new stable version" thread on -user. Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond on the cloud
Dear Marek, many thanks, its wonderful! Francois 2012/10/28, Marek Klein : > Hello, > > 2012/10/28 Francois Planiol > >> Well the question was Lily in the cloud with integrated editor. Where >> should I go? >> F >> > > Have you tried lilybin.com? > HTH > > Marek Klein > http://gregoriana.sk > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Changing program defaults
Daniel Rosen wrote > That's really OK in my case--no one else I know uses LilyPond. :-P one should probably also mention -dinclude-settings="file" which is for such purposes (s. http://lilypond.org/doc/v2.17/Documentation/usage-big-page#advanced-command-line-options-for-lilypond )! Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Changing-program-defaults-tp135433p135472.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
Function for rendering key textually in 3 languages
Hi all,
I'd like to have a function to translate a key signature into the
textual representation of that key in 3 languages.
For instance, I'd write this in my score:
header {
piece-key = "c#"
}
and the rendering would look like this:
\markup {"Cis moll." \italic { "Do dièse mineur." } "C sharp minor."}
The logic I'm trying to implement, is (in pseudo-code):
1. key format = []
2. IF is lowercase THEN key is minor ELSE key is major.
3. If accidentals are added, they pertain to the key name
How should I proceed?
Best regards,
Olivier
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Changing program defaults
I'll bear that in mind going forward--I appreciate the warning. DR -Original Message- From: David Kastrup [mailto:d...@gnu.org] Sent: Sunday, October 28, 2012 6:44 AM To: lilypond-user@gnu.org Subject: Re: Changing program defaults Daniel Rosen writes: > That's really OK in my case--no one else I know uses LilyPond. :-P And at the next update things change, and then somebody else _does_ ask you for it, willing to help with things, and so on and so on. Then you try asking here on the list for some fine-polishing of a score, and nobody can reproduce your layout. Janek has engaged half his choir in entering some scores. Having a standard setup really has advantages. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Decrescendo on accented whole note
Thanks! That worked great!
dis2\pp a2 | dis2 f2 \< | cis2. cis4 | dis1->\f\> <>\p | R1*2 | R1*2 \bar "|."
>
> From: Janek Warchoł
>To: Richard Rohrich
>Cc: "lilypond-user@gnu.org"
>Sent: Saturday, October 27, 2012 11:11 PM
>Subject: Re: Decrescendo on accented whole note
>
>On Sun, Oct 28, 2012 at 4:32 AM, Richard Rohrich wrote:
>> The following results in a crescendo to forte on dis1:
>>
>> cis2. cis4 | dis1->\f | R1*2 | R1*2 \bar "|."
>
>I don't quite see the decrescendo, but anyway, try this:
>{
> cis2.\< cis4 | dis1->\f\> <>\p | R1*2 | R1*2 \bar "|."
>}
>or this:
>{
> cis2.\< cis4 | dis1->\f\> s1*0\p | R1*2 | R1*2 \bar "|."
>}
>If you're wondering what <> is, here's the answer: it's just an empty
>chord. I think there should be some information about it somewhere in
>the manuals and on the maling list (this one or developers' one).
>
>hth,
>Janek
>
>
>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Modified laissez vibrer ties
David Kastrup wrote Sunday, October 28, 2012 10:07 AM
> Daniel Rosen writes:
>
>> I did consider that; the problem is those ties go _over_ the barline
>> instead of stopping just short, so they'd still need to be adjusted
>> manually.
>
> I tried using normal ties to invisible notes after the barline and
> tweaking to-barline in order to have them stop short. I have not been
> able to make to-barline have any effect, though.
Not very elegant, but this might be a possibility:
\relative c'' {
\override Slur #'to-barline = ##t
a1*3/4( \once \hideNotes a4) a1
}
or, if you prefer,
\relative c'' {
a1*3/4 -\tweak #'to-barline ##t ( \once \hideNotes a4) a1
}
Unlike hairpins, 'to-barline for Slurs seems to extend the slur to the
_next_ bar line rather than stopping it short at the previous one.
And the hidden note seems to require a non-zero duration too.
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
enlarge vertical distance in time signature
Dear community, I would like to know how to enlarge the vertical distance between enumerator and denominator of a time signature. I hope, this will be possible. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Word wrapping section headers (book-titling.ily)
Hi all, I'm using the book-titling.ily macros by Nicolas Sceaux to create an etude book. I can't however get long section titles to word wrap. I suppose the code I have to edit is this but I am no Scheme expert: section = #(define-music-function (parser location title) (string?) (add-toc-item parser 'tocSectionMarkup title) (add-toplevel-markup parser (markup #:section-title (string-upper-case title))) (add-no-page-break parser) (make-music 'Music 'void #t)) Can some helpful mind shed some light on how to do so? Best regards, Olivier ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Word wrapping section headers (book-titling.ily)
2012/10/28 Olivier Biot :
> Hi all,
>
> I'm using the book-titling.ily macros by Nicolas Sceaux to create an etude
> book.
>
> I can't however get long section titles to word wrap.
>
> I suppose the code I have to edit is this but I am no Scheme expert:
>
> section =
> #(define-music-function (parser location title) (string?)
> (add-toc-item parser 'tocSectionMarkup title)
> (add-toplevel-markup parser (markup #:section-title
> (string-upper-case title)))
> (add-no-page-break parser)
> (make-music 'Music 'void #t))
>
> Can some helpful mind shed some light on how to do so?
>
> Best regards,
>
> Olivier
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Oliver,
Nicolas' template is a very special one. He deals a lot with strings,
formating them in different ways.
And it works with 2.14.2 only (if you use the LSR-version)
You could try:
section =
#(define-music-function (parser location title) (markup?)
(add-toc-item parser 'tocSectionMarkup title)
;(add-toplevel-markup parser (markup #:section-title
(string-upper-case title)))
(add-toplevel-markup parser (markup #:section-title title))
(add-no-page-break parser)
(make-music 'Music 'void #t))
with
\section \markup {
\override #'(line-width . 40)
\justify-string #"Lorem ipsum dolor sit amet, consectetur
adipisicing elit, sed do eiusmod tempor incididunt ut labore
et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco
laboris nisi ut aliquip ex ea commodo consequat.
Excepteur sint occaecat cupidatat non proident, sunt in culpa
qui officia deserunt mollit anim id est laborum"
}
But I'm not sure you realy want this output. :)
Please note that the string-upper-case-feature of \section doesn't
work any more.
-Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Word wrapping section headers (book-titling.ily)
On Sun, Oct 28, 2012 at 8:29 PM, Thomas Morley
wrote:
> 2012/10/28 Olivier Biot :
>> Hi all,
>>
>> I'm using the book-titling.ily macros by Nicolas Sceaux to create an etude
>> book.
>>
>> I can't however get long section titles to word wrap.
>>
>> I suppose the code I have to edit is this but I am no Scheme expert:
>>
>> section =
>> #(define-music-function (parser location title) (string?)
>> (add-toc-item parser 'tocSectionMarkup title)
>> (add-toplevel-markup parser (markup #:section-title
>> (string-upper-case title)))
>> (add-no-page-break parser)
>> (make-music 'Music 'void #t))
>>
>> Can some helpful mind shed some light on how to do so?
>
> Hi Oliver,
>
> Nicolas' template is a very special one. He deals a lot with strings,
> formating them in different ways.
> And it works with 2.14.2 only (if you use the LSR-version)
>
> You could try:
>
> section =
> #(define-music-function (parser location title) (markup?)
> (add-toc-item parser 'tocSectionMarkup title)
> ;(add-toplevel-markup parser (markup #:section-title
> (string-upper-case title)))
> (add-toplevel-markup parser (markup #:section-title title))
> (add-no-page-break parser)
> (make-music 'Music 'void #t))
>
> with
>
> \section \markup {
> \override #'(line-width . 40)
> \justify-string #"Lorem ipsum dolor sit amet, consectetur
> adipisicing elit, sed do eiusmod tempor incididunt ut labore
> et dolore magna aliqua.
>
>
> Ut enim ad minim veniam, quis nostrud exercitation ullamco
> laboris nisi ut aliquip ex ea commodo consequat.
>
>
> Excepteur sint occaecat cupidatat non proident, sunt in culpa
> qui officia deserunt mollit anim id est laborum"
> }
>
>
> But I'm not sure you realy want this output. :)
>
> Please note that the string-upper-case-feature of \section doesn't
> work any more.
Hi Thomas,
Thank you for your input! This is maybe a silly question, but isn't
there a simple way to hide the following markup code into the Scheme
procedure?
\override #'(line-width . 40) \justify-string
I'd love to keep my 60 etude input files as simple as possible, so if
possible I'd rather write 60 times the shorthand:
\section "The section title comes here. It can be lengthy but it
should gently word wrap if its length exceeds one line."
Best regards,
Olivier
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: enlarge vertical distance in time signature
2012/10/28 Stefan Thomas :
> Dear community,
> I would like to know how to enlarge the vertical distance between enumerator
> and denominator of a time signature.
> I hope, this will be possible.
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
Hi Stefan,
try:
\version "2.16.0"
spreadTimeSignature =
#(define-music-function (parser location baselineSkip strg
music)(number? string? ly:music?)
(let* ((num (car (string-split strg #\/)))
(denom (cadr (string-split strg #\/
#{
\override Staff.TimeSignature #'stencil =
#(lambda (grob)
(grob-interpret-markup grob
#{
\markup %\fontsize #5
\vcenter
\override #`(baseline-skip . ,baselineSkip)
\column {
\number $num
\number $denom
}
#}))
$(make-music
'TimeSignatureMusic
'beat-structure '()
'denominator (string->number denom)
'numerator (string->number num))
$music
#}))
% test
\relative c' {
\spreadTimeSignature #8 "2/4"
c8 c c c
\spreadTimeSignature #8 "3/4"
c16 c c c c c c c c4
}
Usage: \spreadTimeSignature # ""
Setting \time is integrated in the function.
There might arise a problem because of
'beat-structure '()
If so, delete
$(make-music
'TimeSignatureMusic
'beat-structure '()
'denominator (string->number denom)
'numerator (string->number num))
$music
and use default \time x/y after the function-call.
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Word wrapping section headers (book-titling.ily)
2012/10/28 Olivier Biot :
> On Sun, Oct 28, 2012 at 8:29 PM, Thomas Morley
> wrote:
>> 2012/10/28 Olivier Biot :
>>> Hi all,
>>>
>>> I'm using the book-titling.ily macros by Nicolas Sceaux to create an etude
>>> book.
>>>
>>> I can't however get long section titles to word wrap.
>>>
>>> I suppose the code I have to edit is this but I am no Scheme expert:
>>>
>>> section =
>>> #(define-music-function (parser location title) (string?)
>>> (add-toc-item parser 'tocSectionMarkup title)
>>> (add-toplevel-markup parser (markup #:section-title
>>> (string-upper-case title)))
>>> (add-no-page-break parser)
>>> (make-music 'Music 'void #t))
>>>
>>> Can some helpful mind shed some light on how to do so?
>>
>> Hi Oliver,
>>
>> Nicolas' template is a very special one. He deals a lot with strings,
>> formating them in different ways.
>> And it works with 2.14.2 only (if you use the LSR-version)
>>
>> You could try:
>>
>> section =
>> #(define-music-function (parser location title) (markup?)
>> (add-toc-item parser 'tocSectionMarkup title)
>> ;(add-toplevel-markup parser (markup #:section-title
>> (string-upper-case title)))
>> (add-toplevel-markup parser (markup #:section-title title))
>> (add-no-page-break parser)
>> (make-music 'Music 'void #t))
>>
>> with
>>
>> \section \markup {
>> \override #'(line-width . 40)
>> \justify-string #"Lorem ipsum dolor sit amet, consectetur
>> adipisicing elit, sed do eiusmod tempor incididunt ut labore
>> et dolore magna aliqua.
>>
>>
>> Ut enim ad minim veniam, quis nostrud exercitation ullamco
>> laboris nisi ut aliquip ex ea commodo consequat.
>>
>>
>> Excepteur sint occaecat cupidatat non proident, sunt in culpa
>> qui officia deserunt mollit anim id est laborum"
>> }
>>
>>
>> But I'm not sure you realy want this output. :)
>>
>> Please note that the string-upper-case-feature of \section doesn't
>> work any more.
>
> Hi Thomas,
>
> Thank you for your input! This is maybe a silly question, but isn't
> there a simple way to hide the following markup code into the Scheme
> procedure?
>
> \override #'(line-width . 40) \justify-string
>
> I'd love to keep my 60 etude input files as simple as possible, so if
> possible I'd rather write 60 times the shorthand:
>
> \section "The section title comes here. It can be lengthy but it
> should gently word wrap if its length exceeds one line."
>
> Best regards,
>
> Olivier
How about
\version "2.14.2"
section =
#(define-music-function (parser location arg) (string?)
(let* ((title (markup #:override '(line-width . 40)
#:justify-string arg)))
(add-toc-item parser 'tocSectionMarkup title)
;(add-toplevel-markup parser (markup #:section-title
(string-upper-case title)))
(add-toplevel-markup parser (markup #:section-title title))
(add-no-page-break parser)
(make-music 'Music 'void #t)))
\section "The section title comes here. It can be lengthy but it
should gently word wrap if its length exceeds one line."
-Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Stanzas beginning in the middle of the piece
Perfect, thank you so much. I have yet to fully understand the whole repeat/unfold concept. It's great to have an example close at hand. > > Yes. You have created one long string of lyrics, which runs off the end > of the music. > > ~Chris ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Word wrapping section headers (book-titling.ily)
2012/10/28 Thomas Morley :
> 2012/10/28 Olivier Biot :
>> On Sun, Oct 28, 2012 at 8:29 PM, Thomas Morley
>> wrote:
>>> 2012/10/28 Olivier Biot :
Hi all,
I'm using the book-titling.ily macros by Nicolas Sceaux to create an etude
book.
I can't however get long section titles to word wrap.
I suppose the code I have to edit is this but I am no Scheme expert:
section =
#(define-music-function (parser location title) (string?)
(add-toc-item parser 'tocSectionMarkup title)
(add-toplevel-markup parser (markup #:section-title
(string-upper-case title)))
(add-no-page-break parser)
(make-music 'Music 'void #t))
Can some helpful mind shed some light on how to do so?
>>>
>>> Hi Oliver,
>>>
>>> Nicolas' template is a very special one. He deals a lot with strings,
>>> formating them in different ways.
>>> And it works with 2.14.2 only (if you use the LSR-version)
>>>
>>> You could try:
>>>
>>> section =
>>> #(define-music-function (parser location title) (markup?)
>>> (add-toc-item parser 'tocSectionMarkup title)
>>> ;(add-toplevel-markup parser (markup #:section-title
>>> (string-upper-case title)))
>>> (add-toplevel-markup parser (markup #:section-title title))
>>> (add-no-page-break parser)
>>> (make-music 'Music 'void #t))
>>>
>>> with
>>>
>>> \section \markup {
>>> \override #'(line-width . 40)
>>> \justify-string #"Lorem ipsum dolor sit amet, consectetur
>>> adipisicing elit, sed do eiusmod tempor incididunt ut labore
>>> et dolore magna aliqua.
>>>
>>>
>>> Ut enim ad minim veniam, quis nostrud exercitation ullamco
>>> laboris nisi ut aliquip ex ea commodo consequat.
>>>
>>>
>>> Excepteur sint occaecat cupidatat non proident, sunt in culpa
>>> qui officia deserunt mollit anim id est laborum"
>>> }
>>>
>>>
>>> But I'm not sure you realy want this output. :)
>>>
>>> Please note that the string-upper-case-feature of \section doesn't
>>> work any more.
>>
>> Hi Thomas,
>>
>> Thank you for your input! This is maybe a silly question, but isn't
>> there a simple way to hide the following markup code into the Scheme
>> procedure?
>>
>> \override #'(line-width . 40) \justify-string
>>
>> I'd love to keep my 60 etude input files as simple as possible, so if
>> possible I'd rather write 60 times the shorthand:
>>
>> \section "The section title comes here. It can be lengthy but it
>> should gently word wrap if its length exceeds one line."
>>
>> Best regards,
>>
>> Olivier
>
> How about
>
> \version "2.14.2"
>
> section =
> #(define-music-function (parser location arg) (string?)
> (let* ((title (markup #:override '(line-width . 40)
> #:justify-string arg)))
> (add-toc-item parser 'tocSectionMarkup title)
> ;(add-toplevel-markup parser (markup #:section-title
> (string-upper-case title)))
> (add-toplevel-markup parser (markup #:section-title title))
> (add-no-page-break parser)
> (make-music 'Music 'void #t)))
>
> \section "The section title comes here. It can be lengthy but it
> should gently word wrap if its length exceeds one line."
>
>
>
> -Harm
Hi again,
the mail-program inserted a line-break in a commented line, which
could be misunderstood.
Here I've deleted that:
section =
#(define-music-function (parser location arg) (string?)
(let* ((title (markup #:override '(line-width . 40)
#:justify-string arg)))
(add-toc-item parser 'tocSectionMarkup title)
(add-toplevel-markup parser (markup #:section-title title))
(add-no-page-break parser)
(make-music 'Music 'void #t)))
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: enlarge vertical distance in time signature
Dear Thomas,
thanks for Your code!
I think the code is not the best for my special aim.
I just want to have a different time-signature style for a custom
percussion staff with 6 instead of five lines.
So, I just would like to change this special thing only in this staff. I
would like to do this in the "with" block, if possible.
The timesignatures itself are defined in a global variable.
2012/10/28 Thomas Morley
> 2012/10/28 Stefan Thomas :
> > Dear community,
> > I would like to know how to enlarge the vertical distance between
> enumerator
> > and denominator of a time signature.
> > I hope, this will be possible.
> >
> > ___
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
> >
>
> Hi Stefan,
>
> try:
>
> \version "2.16.0"
>
> spreadTimeSignature =
> #(define-music-function (parser location baselineSkip strg
> music)(number? string? ly:music?)
> (let* ((num (car (string-split strg #\/)))
>(denom (cadr (string-split strg #\/
> #{
>\override Staff.TimeSignature #'stencil =
> #(lambda (grob)
> (grob-interpret-markup grob
>#{
> \markup %\fontsize #5
> \vcenter
> \override #`(baseline-skip . ,baselineSkip)
> \column {
> \number $num
> \number $denom
> }
>#}))
>$(make-music
>'TimeSignatureMusic
>'beat-structure '()
>'denominator (string->number denom)
>'numerator (string->number num))
>
>$music
> #}))
>
> % test
>
> \relative c' {
> \spreadTimeSignature #8 "2/4"
> c8 c c c
>
> \spreadTimeSignature #8 "3/4"
> c16 c c c c c c c c4
> }
>
>
> Usage: \spreadTimeSignature # ""
>
> Setting \time is integrated in the function.
> There might arise a problem because of
> 'beat-structure '()
> If so, delete
>$(make-music
>'TimeSignatureMusic
>'beat-structure '()
>'denominator (string->number denom)
>'numerator (string->number num))
>
>$music
> and use default \time x/y after the function-call.
>
>
> HTH,
> Harm
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: pitch name transpose into numeric per key signature
(let* ... (scalestep (modulo (- (ly:pitch-notename pitch) (...base of key signature...)) 7)) (name (format #f "~a~a" (string-ref "1234567" (scalestep))... assuming someone can point out what to substitute for my unknown quantity. The following is only work for C Major. It is not working for other keys. I am no programer. I don't know how to code for blue text above. the original code: namer = #(make-engraver (acknowledgers ((note-head-interface engraver grob source) (let* ((event (ly:grob-property grob 'cause)) (pitch (ly:event-property event 'pitch)) (newgrob (ly:engraver-make-grob engraver 'TextScript event)) (name (format #f "~a~a" (string-ref "1234567" (ly:pitch-notename pitch)) (assoc-ref '((-1/2 . "") (0 . "") (1/2 . "")) (ly:pitch-alteration pitch) (if (string= name "Hb") (set! name "B")) (set! (ly:grob-property newgrob 'text) name) Blessing in+,___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: enlarge vertical distance in time signature
2012/10/28 Stefan Thomas :
> Dear Thomas,
> thanks for Your code!
> I think the code is not the best for my special aim.
> I just want to have a different time-signature style for a custom percussion
> staff with 6 instead of five lines.
> So, I just would like to change this special thing only in this staff. I
> would like to do this in the "with" block, if possible.
> The timesignatures itself are defined in a global variable.
>
> 2012/10/28 Thomas Morley
>>
>> 2012/10/28 Stefan Thomas :
>> > Dear community,
>> > I would like to know how to enlarge the vertical distance between
>> > enumerator
>> > and denominator of a time signature.
>> > I hope, this will be possible.
>> >
>> > ___
>> > lilypond-user mailing list
>> > lilypond-user@gnu.org
>> > https://lists.gnu.org/mailman/listinfo/lilypond-user
>> >
>>
>> Hi Stefan,
>>
>> try:
>>
>> \version "2.16.0"
>>
>> spreadTimeSignature =
>> #(define-music-function (parser location baselineSkip strg
>> music)(number? string? ly:music?)
>> (let* ((num (car (string-split strg #\/)))
>>(denom (cadr (string-split strg #\/
>> #{
>>\override Staff.TimeSignature #'stencil =
>> #(lambda (grob)
>> (grob-interpret-markup grob
>>#{
>> \markup %\fontsize #5
>> \vcenter
>> \override #`(baseline-skip . ,baselineSkip)
>> \column {
>> \number $num
>> \number $denom
>> }
>>#}))
>>$(make-music
>>'TimeSignatureMusic
>>'beat-structure '()
>>'denominator (string->number denom)
>>'numerator (string->number num))
>>
>>$music
>> #}))
>>
>> % test
>>
>> \relative c' {
>> \spreadTimeSignature #8 "2/4"
>> c8 c c c
>>
>> \spreadTimeSignature #8 "3/4"
>> c16 c c c c c c c c4
>> }
>>
>>
>> Usage: \spreadTimeSignature # ""
>>
>> Setting \time is integrated in the function.
>> There might arise a problem because of
>> 'beat-structure '()
>> If so, delete
>>$(make-music
>>'TimeSignatureMusic
>>'beat-structure '()
>>'denominator (string->number denom)
>>'numerator (string->number num))
>>
>>$music
>> and use default \time x/y after the function-call.
>>
>>
>> HTH,
>> Harm
>
>
How about:
\version "2.16.0"
widerTimeSignature =
#(define-music-function (parser location baseline-skip music)(number? ly:music?)
(let* ((num (number->string (ly:music-property music 'numerator)))
(denom (number->string (ly:music-property music 'denominator
#{
\override Staff.TimeSignature #'stencil =
#(lambda (grob)
(grob-interpret-markup grob
#{
\markup
\vcenter
\override #`(baseline-skip . ,baseline-skip)
\column {
\number $num
\number $denom
}
#}))
$music
#}))
% test
global = {
\widerTimeSignature #3
\time 15/16
}
\new DrumStaff \with {
\override StaffSymbol #'line-count = #6
% \widerTimeSignature #3
% \time 15/16
}
{ \global \drummode { bd4 sn bd toml8 toml bd } }
With the possibility to place \widerTimeSignature in \global or in \with.
Using the latter there's need to write the TimeSignature after
\widerTimeSignature.
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: enlarge vertical distance in time signature
2012/10/28 Thomas Morley :
> 2012/10/28 Stefan Thomas :
>> Dear Thomas,
>> thanks for Your code!
>> I think the code is not the best for my special aim.
>> I just want to have a different time-signature style for a custom percussion
>> staff with 6 instead of five lines.
>> So, I just would like to change this special thing only in this staff. I
>> would like to do this in the "with" block, if possible.
>> The timesignatures itself are defined in a global variable.
>>
>> 2012/10/28 Thomas Morley
>>>
>>> 2012/10/28 Stefan Thomas :
>>> > Dear community,
>>> > I would like to know how to enlarge the vertical distance between
>>> > enumerator
>>> > and denominator of a time signature.
>>> > I hope, this will be possible.
>>> >
>>> > ___
>>> > lilypond-user mailing list
>>> > lilypond-user@gnu.org
>>> > https://lists.gnu.org/mailman/listinfo/lilypond-user
>>> >
>>>
>>> Hi Stefan,
>>>
>>> try:
>>>
>>> \version "2.16.0"
>>>
>>> spreadTimeSignature =
>>> #(define-music-function (parser location baselineSkip strg
>>> music)(number? string? ly:music?)
>>> (let* ((num (car (string-split strg #\/)))
>>>(denom (cadr (string-split strg #\/
>>> #{
>>>\override Staff.TimeSignature #'stencil =
>>> #(lambda (grob)
>>> (grob-interpret-markup grob
>>>#{
>>> \markup %\fontsize #5
>>> \vcenter
>>> \override #`(baseline-skip . ,baselineSkip)
>>> \column {
>>> \number $num
>>> \number $denom
>>> }
>>>#}))
>>>$(make-music
>>>'TimeSignatureMusic
>>>'beat-structure '()
>>>'denominator (string->number denom)
>>>'numerator (string->number num))
>>>
>>>$music
>>> #}))
>>>
>>> % test
>>>
>>> \relative c' {
>>> \spreadTimeSignature #8 "2/4"
>>> c8 c c c
>>>
>>> \spreadTimeSignature #8 "3/4"
>>> c16 c c c c c c c c4
>>> }
>>>
>>>
>>> Usage: \spreadTimeSignature # ""
>>>
>>> Setting \time is integrated in the function.
>>> There might arise a problem because of
>>> 'beat-structure '()
>>> If so, delete
>>>$(make-music
>>>'TimeSignatureMusic
>>>'beat-structure '()
>>>'denominator (string->number denom)
>>>'numerator (string->number num))
>>>
>>>$music
>>> and use default \time x/y after the function-call.
>>>
>>>
>>> HTH,
>>> Harm
>>
>>
>
> How about:
>
> \version "2.16.0"
>
> widerTimeSignature =
> #(define-music-function (parser location baseline-skip music)(number?
> ly:music?)
> (let* ((num (number->string (ly:music-property music 'numerator)))
> (denom (number->string (ly:music-property music 'denominator
> #{
> \override Staff.TimeSignature #'stencil =
>#(lambda (grob)
> (grob-interpret-markup grob
> #{
> \markup
> \vcenter
> \override #`(baseline-skip . ,baseline-skip)
> \column {
> \number $num
> \number $denom
> }
> #}))
> $music
> #}))
>
> % test
>
> global = {
> \widerTimeSignature #3
> \time 15/16
> }
>
> \new DrumStaff \with {
> \override StaffSymbol #'line-count = #6
> % \widerTimeSignature #3
> % \time 15/16
> }
>
> { \global \drummode { bd4 sn bd toml8 toml bd } }
>
> With the possibility to place \widerTimeSignature in \global or in \with.
> Using the latter there's need to write the TimeSignature after
> \widerTimeSignature.
>
>
> Cheers,
> Harm
Hi again,
I forgot one thing: please change
\override Staff.TimeSignature #'stencil = ...
into
\override DrumStaff.TimeSignature #'stencil = ...
This will limit the override to the DrumStaff.
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: enlarge vertical distance in time signature
Dear Thomas,
thanks very much for Your code, again!
The problem is:
I would like to have a score with drumstaff and a "normal" staff. And only
in the normal Staff shall be a wider time signature.
I give you an short example:
global = {
\time #'(4 3) 7/8
s2..
\time #'(2 2 2 3) 9/8
s8*9
}
drumnotes = \drummode {
wbl4 wbl wbh4.
\repeat "unfold" 3 {wbl4 } wbh4.
}
somenotes = \relative c' {
c4 b c4 d8
e4 e f e8 d c
}
\score {
<<
\new Devnull \global
\new Staff \somenotes
\new DrumStaff \with {
\override StaffSymbol #'line-count = #6
% \widerTimeSignature #3 % this doesn't work!
} { \drumnotes }
>>
}
2012/10/28 Thomas Morley
> 2012/10/28 Stefan Thomas :
> > Dear Thomas,
> > thanks for Your code!
> > I think the code is not the best for my special aim.
> > I just want to have a different time-signature style for a custom
> percussion
> > staff with 6 instead of five lines.
> > So, I just would like to change this special thing only in this staff. I
> > would like to do this in the "with" block, if possible.
> > The timesignatures itself are defined in a global variable.
> >
> > 2012/10/28 Thomas Morley
> >>
> >> 2012/10/28 Stefan Thomas :
> >> > Dear community,
> >> > I would like to know how to enlarge the vertical distance between
> >> > enumerator
> >> > and denominator of a time signature.
> >> > I hope, this will be possible.
> >> >
> >> > ___
> >> > lilypond-user mailing list
> >> > lilypond-user@gnu.org
> >> > https://lists.gnu.org/mailman/listinfo/lilypond-user
> >> >
> >>
> >> Hi Stefan,
> >>
> >> try:
> >>
> >> \version "2.16.0"
> >>
> >> spreadTimeSignature =
> >> #(define-music-function (parser location baselineSkip strg
> >> music)(number? string? ly:music?)
> >> (let* ((num (car (string-split strg #\/)))
> >>(denom (cadr (string-split strg #\/
> >> #{
> >>\override Staff.TimeSignature #'stencil =
> >> #(lambda (grob)
> >> (grob-interpret-markup grob
> >>#{
> >> \markup %\fontsize #5
> >> \vcenter
> >> \override #`(baseline-skip . ,baselineSkip)
> >> \column {
> >> \number $num
> >> \number $denom
> >> }
> >>#}))
> >>$(make-music
> >>'TimeSignatureMusic
> >>'beat-structure '()
> >>'denominator (string->number denom)
> >>'numerator (string->number num))
> >>
> >>$music
> >> #}))
> >>
> >> % test
> >>
> >> \relative c' {
> >> \spreadTimeSignature #8 "2/4"
> >> c8 c c c
> >>
> >> \spreadTimeSignature #8 "3/4"
> >> c16 c c c c c c c c4
> >> }
> >>
> >>
> >> Usage: \spreadTimeSignature # ""
> >>
> >> Setting \time is integrated in the function.
> >> There might arise a problem because of
> >> 'beat-structure '()
> >> If so, delete
> >>$(make-music
> >>'TimeSignatureMusic
> >>'beat-structure '()
> >>'denominator (string->number denom)
> >>'numerator (string->number num))
> >>
> >>$music
> >> and use default \time x/y after the function-call.
> >>
> >>
> >> HTH,
> >> Harm
> >
> >
>
> How about:
>
> \version "2.16.0"
>
> widerTimeSignature =
> #(define-music-function (parser location baseline-skip music)(number?
> ly:music?)
> (let* ((num (number->string (ly:music-property music 'numerator)))
> (denom (number->string (ly:music-property music 'denominator
> #{
> \override Staff.TimeSignature #'stencil =
>#(lambda (grob)
> (grob-interpret-markup grob
> #{
> \markup
> \vcenter
> \override #`(baseline-skip .
> ,baseline-skip)
> \column {
> \number $num
> \number $denom
> }
> #}))
> $music
> #}))
>
> % test
>
> global = {
> \widerTimeSignature #3
> \time 15/16
> }
>
> \new DrumStaff \with {
> \override StaffSymbol #'line-count = #6
> % \widerTimeSignature #3
> % \time 15/16
> }
>
> { \global \drummode { bd4 sn bd toml8 toml bd } }
>
> With the possibility to place \widerTimeSignature in \global or in \with.
> Using the latter there's need to write the TimeSignature after
> \widerTimeSignature.
>
>
> Cheers,
> Harm
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Lyrics placement
Hello everyone -- my first question to this list.
I am new to Lilypond and have been working with it over the past week or
so. I think I have notation well in hand and lyrics. I'm using
Frescobaldi for entering data and running Lilypond against the .ly file.
I have all the music coded for a new SSATBB choral piece. I want the
lyrics for the SopranoOne part to be above the staff with the lyrics for
SopranoTwo below. Naturally, Lilypond puts the lyrics below the staff
per the default.
I have looked over the Learning Guide and the Notation Reference for
help in telling Lilypond to put S1 lyrics above the staff. Yet I'm
stymied by differences in terminology. The Learning Guide uses
"/addlyrics" in its examples (as does my file) while the Notation
Reference uses "/new lyrics /lyricsto". When the Notatation Reference
shows examples on how to modify lyric placement, it shows two different
examples that I cannot map to my use of /addlyrics. I know it's a
context thing, but I cannot grok what's supposed to happen. I'm building
the score with variables thus:
sopranoVoicePart = \new Staff \with {
instrumentName = "Soprano"
midiInstrument = "choir aahs"
} <<
{ \sopranoVoiceOne }
\addlyrics { \verseSopranoVoiceOne }
{ \sopranoVoiceTwo }
\addlyrics { \verseSopranoVoiceTwo }
>>
altoVoicePart = \new Staff \with {
instrumentName = "Alto"
midiInstrument = "choir aahs"
} { \altoVoice }
\addlyrics { \verseAltoVoice }
tenorVoicePart = \new Staff \with {
instrumentName = "Tenor"
midiInstrument = "choir aahs"
} { \clef "treble_8" \tenorVoice }
\addlyrics { \verseTenorVoice }
bassVoicePart = \new Staff \with {
instrumentName = "Bass"
midiInstrument = "choir aahs"
} { \clef bass \bassVoice }
\addlyrics { \verseBassVoice }
\score {
<<
\sopranoVoicePart
\altoVoicePart
\tenorVoicePart
\bassVoicePart
>>
\layout { }
\midi { }
This works perfectly with lyrics for sopranoVoiceOne and places them
below the staff aligned with the notes. How to I get the lyrics above
the staf if I use /addlyrics? I've tried futzing with modifying
/addlyrics to /new lyrics, etc. but that creates errors on compiling.
Any help is appreciated.
Guy
--
"There is only love, and then oblivion. Love is all we have
to set against hatred." (paraphrased) Ian McEwan
Guy Stalnaker, I^2@DOIT, 1210 West Dayton Street, Room 3209 CSS, Madison
WI 53719-1220, jstal...@wisc.edu, work 608.263.8035, cell 608.235.4718,
fax 608.265.6681, page page-...@watchdog.doit.wisc.edu
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: enlarge vertical distance in time signature
Thomas Morley writes: [...] I know that the discussion has moved beyond the first version, but I still want to point out something: > \version "2.16.0" > > spreadTimeSignature = > #(define-music-function (parser location baselineSkip strg > music)(number? string? ly:music?) > (let* ((num (car (string-split strg #\/))) >(denom (cadr (string-split strg #\/ I consider it much nicer to make "strg" of type fraction?, and then num can be (car strg) and denom can be (cdr strg). and > \spreadTimeSignature #8 "2/4" can just be \spreadTimeSignature #8 2/4 ... which is nicer on the eyes. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
