Re: Dash one sibling of a slur/PhrasingSlur/Tie
2013/7/16 Urs Liska : > in an edition I prepare I often have the situation that I want to dash one > sibling of a Slur (because the original edition forgot to start a slur > before the line break. > > Is there a convenient way to do so without having to define two curves and > tweak them independently? Use \alterBroken by David Nalesnik: \alterBroken Slur #'dash-definition #'(() ((0 1.0 0.4 0.75))) I think it was published somewhere on the mailing list, and i think we have it in our library. best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dash one sibling of a slur/PhrasingSlur/Tie
Ok I' look into it. Then I can do it myself and spare you all those \todo entries ;-) Urs "Janek Warchoł" schrieb: >2013/7/16 Urs Liska : >> in an edition I prepare I often have the situation that I want to >dash one >> sibling of a Slur (because the original edition forgot to start a >slur >> before the line break. >> >> Is there a convenient way to do so without having to define two >curves and >> tweak them independently? > >Use \alterBroken by David Nalesnik: > >\alterBroken Slur #'dash-definition #'(() ((0 1.0 0.4 0.75))) > >I think it was published somewhere on the mailing list, and i think we >have it in our library. > >best, >Janek -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR preview broken?
- Original Message - From: "Werner LEMBERG" To: Sent: Tuesday, July 16, 2013 7:34 AM Subject: LSR preview broken? I've just added a snippet to the LSR (`Percent repeat counters for piano music'), but I'm not able to preview it. Since I don't have a 1.14 lilypond binary, I can't check whether the problem is in the file (it compiles fine with 1.16 and the current development version). However, even adding a very simple lilypond snippet which certainly displays fine doesn't succeed. I thus wonder whether the LSR preview for non-approved snippets currently work at all... Werner I believe it's somewhat erratic. Thomas has tried to contact Sebastiano about a number of problems with the LSR, but without success, I believe. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR preview broken?
2013/7/16 Phil Holmes : > - Original Message - From: "Werner LEMBERG" > To: > Sent: Tuesday, July 16, 2013 7:34 AM > Subject: LSR preview broken? > > > >> >> I've just added a snippet to the LSR (`Percent repeat counters for >> piano music'), but I'm not able to preview it. Since I don't have a >> 1.14 lilypond binary, I can't check whether the problem is in the file >> (it compiles fine with 1.16 and the current development version). >> However, even adding a very simple lilypond snippet which certainly >> displays fine doesn't succeed. I thus wonder whether the LSR preview >> for non-approved snippets currently work at all... >> >> >>Werner Hi Werner, to state same obvious: The LSR runs 2.14.2. Your snippet compiles fine with 2.14.2 (tested). There are some problems in the LSR concerning cropped images. > > I believe it's somewhat erratic. Thomas has tried to contact Sebastiano > about a number of problems with the LSR, but without success, I believe. And I _had_ contacted Sebastiano about the cropped images. Though, nothing happened. > -- > Phil Holmes > In the past I sometimes observed the fact that the LSR didn't return an image. Though this changed the next day. If the problem still persists tomorrow, I'll try to contact Sebatiano again. Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR preview broken?
> Your snippet compiles fine with 2.14.2 (tested). Thanks. > There are some problems in the LSR concerning cropped images. Hmm, I don't think this affects my snippet. Maybe simply approving it solves the issue :-) Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR preview broken?
2013/7/16 Werner LEMBERG : > >> Your snippet compiles fine with 2.14.2 (tested). > > Thanks. > >> There are some problems in the LSR concerning cropped images. > > Hmm, I don't think this affects my snippet. > > Maybe simply approving it solves the issue :-) No. Already tested. > > > Werner -Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
pedal markings in dynamic context
hi,
i have a question regarding the spacing of dynamic contexts. given the
following (contrived for simplicity) snippet:
\version "2.17.22"
music = \relative c {
\clef bass
c4 c c c
c c c c
c,, c'' c c
}
pedals = {
\repeat unfold 5 {s2\sustainOn}
s4\sustainOn s4\sustainOff
}
\score {
<<
\new Staff \music
\new Dynamics \pedals
>>
}
this is a very simplified example, but it highlights the problem. is there any
way to make the pedal markings in bar 1-2 and on beat 3 of bar 3 closer to the
staff? i have attached a screen shot of a real world example -- bar 3 is
particularly bad in this case, and i'd prefer to have the pedal markings closer
to the staff.
i know i could twiddle the Y-offset for the given bar, but i have a gut feeling
that it might be possible to move the whole dynamic line closer to the staff
and let the pedal markings on the lowest notes drop below the "normal" line.
any ideas?
thanks, regards,
sb
--
Simon Bailey
Oompa Loompa of Science
+43/699/190 631 25
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dash one sibling of a slur/PhrasingSlur/Tie
Hi Urs and Janek, On Tue, Jul 16, 2013 at 2:07 AM, Urs Liska wrote: > Ok I' look into it. > > Then I can do it myself and spare you all those \todo entries ;-) > > Urs > > > > "Janek Warchoł" schrieb: > >> 2013/7/16 Urs Liska : >> >>> >>> in an edition I prepare I often have the situation that I want to dash one >>> sibling of a Slur (because the original edition forgot to start a slur >>> before the line break. >>> >>> Is there a convenient way to do so without having to define two curves and >>> >>> tweak them independently? >> >> >> Use \alterBroken by David Nalesnik: >> >> \alterBroken Slur #'dash-definition #'(() ((0 1.0 0.4 0.75))) >> >> I think it was published somewhere on the mailing list, and i think we >> >> have it in our library. >> >> This function is available in the current stable release. I've created issue 3458 for its documentation. [I'm unsure of the proper place to put this in the NR, as there is a section (2.9 -- "Difficult Tweaks") which describes how to modify broken spanners.] Urs, would you mind if I used an editorial slur as an example of its usage? Do you have a nice one you'd be willing to share? --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: pedal markings in dynamic context
- Original Message -
From: "Simon Bailey"
To:
Sent: Tuesday, July 16, 2013 12:10 PM
Subject: pedal markings in dynamic context
hi,
i have a question regarding the spacing of dynamic contexts. given the
following (contrived for simplicity) snippet:
[snip snippet]
this is a very simplified example, but it highlights the problem. is there
any way to make the pedal markings in bar 1-2 and on beat 3 of bar 3
closer to the staff? i have attached a screen shot of a real world
example -- bar 3 is particularly bad in this case, and i'd prefer to have
the pedal markings closer to the staff.
i know i could twiddle the Y-offset for the given bar, but i have a gut
feeling that it might be possible to move the whole dynamic line closer to
the staff and let the pedal markings on the lowest notes drop below the
"normal" line.
That's the point of a dynamics context. From the NR: "Pedal indications may
be placed in a Dynamics context, which aligns them on a horizontal line."
Why not use a separate voice?
\score {
<<
\new Staff {
<<
\new Voice \music
\new Voice \pedals
>>
}
>>
}
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: pedal markings in dynamic context
Simon Bailey-5 wrote
> hi,
>
> i have a question regarding the spacing of dynamic contexts. given the
> following (contrived for simplicity) snippet:
>
> this is a very simplified example, but it highlights the problem. is there
> any way to make the pedal markings in bar 1-2 and on beat 3 of bar 3
> closer to the staff? i have attached a screen shot of a real world example
> -- bar 3 is particularly bad in this case, and i'd prefer to have the
> pedal markings closer to the staff.
>
> i know i could twiddle the Y-offset for the given bar, but i have a gut
> feeling that it might be possible to move the whole dynamic line closer to
> the staff and let the pedal markings on the lowest notes drop below the
> "normal" line.
>
> any ideas?
the intention of using a dynamics context is exactly to keep the marks on
one horizontal line but.
but you can try to bring the Dynamics nearer to the staff and \tweak or
\override the problematic SustainPedal - I'm not sure this could cause
problems in scores with more than one line, though.
\new Dynamics \with {\override
VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding = #-5 }
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/pedal-markings-in-dynamic-context-tp148075p148079.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: pedal markings in dynamic context
hi eluze, phil,
i realize the point of the dynamics context. and it does what i want it to do.
the case i cited is a borderline case where it does exactly what it says on the
box; however, the result is not satisfactory – one note forces the whole line a
long way from the staff.
here's what happens if i change the example and put the pedals in a separate
voice:
\version "2.17.22"
music = \relative c {
\clef bass
c4 c c, c'
c,, c c' c'
c8 b a g f e d c
}
pedals = {
\repeat unfold 5 {s2\sustainOn}
s4\sustainOn s4\sustainOff
}
\score {
\new Staff <<
\new Voice \music
\new Voice \pedals
>>
}
see attached pdf. bar 3 especially is not really very pretty…
(try changing the repeat in pedals to \repeat unfold 5 {s4\sustainOn
s4\sustainOff} – in my opinion that's even worse – see attached
weird-pedals.png)
eluze's solution _may_ work, but i reckon that it may also shift pedal markings
which are related to notes in the staff into the staff…
if all fails, then i suppose i can look into shifting the dynamics line by
hand… :)
regards,
sb
--
Simon Bailey
Oompa Loompa of Science
+43/699/190 631 25
On Tuesday, 16 July 2013 at 13:52, Eluze wrote:
> Simon Bailey-5 wrote
> > hi,
> >
> > i have a question regarding the spacing of dynamic contexts. given the
> > following (contrived for simplicity) snippet:
> >
> > this is a very simplified example, but it highlights the problem. is there
> > any way to make the pedal markings in bar 1-2 and on beat 3 of bar 3
> > closer to the staff? i have attached a screen shot of a real world example
> > -- bar 3 is particularly bad in this case, and i'd prefer to have the
> > pedal markings closer to the staff.
> >
> > i know i could twiddle the Y-offset for the given bar, but i have a gut
> > feeling that it might be possible to move the whole dynamic line closer to
> > the staff and let the pedal markings on the lowest notes drop below the
> > "normal" line.
> >
> > any ideas?
>
> the intention of using a dynamics context is exactly to keep the marks on
> one horizontal line but.
>
> but you can try to bring the Dynamics nearer to the staff and \tweak or
> \override the problematic SustainPedal - I'm not sure this could cause
> problems in scores with more than one line, though.
>
> \new Dynamics \with {\override
> VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding = #-5 }
>
> Eluze
>
>
>
> --
> View this message in context:
> http://lilypond.1069038.n5.nabble.com/pedal-markings-in-dynamic-context-tp148075p148079.html
> Sent from the User mailing list archive at Nabble.com (http://Nabble.com).
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org (mailto:lilypond-user@gnu.org)
> https://lists.gnu.org/mailman/listinfo/lilypond-user
blah.pdf
Description: Adobe PDF document
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: pedal markings in dynamic context
- Original Message - From: "Simon Bailey" To: "lilypond-user Mailinglist" Sent: Tuesday, July 16, 2013 2:09 PM Subject: Re: pedal markings in dynamic context see attached pdf. bar 3 especially is not really very pretty… Not sure what's not pretty? The thing I would adjust is the alignment of pedal on and off marks, but otherwise it looks OK to me? -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: feature request: abs-fontsize available for all text grobs
Hi Marc (et al.),
> I had thought of such a feature some months ago; my syntax proposal
> would be something like
>
> \set fontScaling = #absolute
> or
> \set fontScaling = #relative
As long as this is per-grob, and not global, I'm fine with it.
> a feature like this would come in handy for eps inclusions, too
Interesting!
> My estimations in such situations go horribly wrong each time, so
> I just state "I don't know" for safety reasons ;-)
=)
Hopefully someone else will respond. A while ago I paid Mike Solomon to make a
"Band-Aid™ Solution":
\version "2.17"
#(define ((set-abs-fontsize n) grob)
(grob-interpret-markup grob
(markup #:abs-fontsize n (ly:grob-property grob 'text
\layout {
\context {
\Lyrics
\override LyricText #'stencil = #(set-abs-fontsize 30)
}
}
\relative c' {
e4 e e e
}
\addlyrics {
foo bar foo bar
}
Now I'm hoping we can make Lilypond "Do The Right Thing™" out of the box.
This might be a job for GLISS… whenever the heck that happens.
Cheers,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: pedal markings in dynamic context
On Tuesday, 16 July 2013 at 15:25, Phil Holmes wrote: > - Original Message - > From: "Simon Bailey" mailto:si...@bailey.at)> > To: "lilypond-user Mailinglist" (mailto:lilypond-user@gnu.org)> > Sent: Tuesday, July 16, 2013 2:09 PM > Subject: Re: pedal markings in dynamic context > > > > see attached pdf. bar 3 especially is not really very pretty… > > Not sure what's not pretty? The thing I would adjust is the alignment of > pedal on and off marks, but otherwise it looks OK to me? the sustainOn on beat 1 in bar 3 is far too far away from the music. the sustainOn on beat 3 and sustainOff on beat 4 should be on the same line (read: i would like). adjusting the alignment of the marks for each and every mark is extremely tedious and involves a lot of trial and error – especially in an 18-page piece with about 470 pedalling instructions, which is what i'm currently working on… for whatever reason, the vertical alignment in bar 1 looks good, albeit too far away from the staff. bar 2 is agreeable as well, but four different levels of pedal markings in bar 3 is not pretty. in my highly subjective opinion. :) which is the reason i wanted to use a Dynamics context for the pedalling and simply raise the context line to a suitable level and have some pedalling instructions drop out of the line… looks like it's the hard way for now though… :) regards, sb ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: feature request: abs-fontsize available for all text grobs
Kieren MacMillan writes: > Now I'm hoping we can make Lilypond "Do The Right Thing™" out of the > box. I have no idea what you would consider more right than what Mike provided. > This might be a job for GLISS… Not at all. It's not input syntax related. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: feature request: abs-fontsize available for all text grobs
Hi David, > I have no idea what you would consider more right than what Mike provided. Here are a couple of things, any of which, if implemented, would make it "more right" than what Mike provided: 1. The user doesn't have to add a function to a file, because Lilypond has it built in. 2. The user doesn't have to change the #'stencil of something, rather they use a far more intuitive function/method like the one already in place for markup (e.g., \abs-fontsize). 3. The syntax*** for setting a grob to an absolute fontsize is identical (or essentially so) regardless of the grob. >> This might be a job for GLISS… > > Not at all. It's not input syntax related. Oh, but it is, as I've clearly just shown (***). Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: feature request: abs-fontsize available for all text grobs
Kieren MacMillan writes: > Hi David, > >> I have no idea what you would consider more right than what Mike provided. > > Here are a couple of things, any of which, if implemented, would make > it "more right" than what Mike provided: > > 1. The user doesn't have to add a function to a file, because Lilypond > has it built in. That's not a question of wrong or right. > 2. The user doesn't have to change the #'stencil of something, rather > they use a far more intuitive function/method like the one already in > place for markup (e.g., \abs-fontsize). It's not at all clear what it should apply to. > 3. The syntax*** for setting a grob to an absolute fontsize is > identical (or essentially so) regardless of the grob. Before one even has a notion what "regardless of the grob" is supposed to mean, one needs to have an idea what it should apply to. Grobs don't generally are made from markup. >>> This might be a job for GLISS… >> >> Not at all. It's not input syntax related. > > Oh, but it is, as I've clearly just shown (***). One person's clearly is another's hand-waving. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: feature request: abs-fontsize available for all text grobs
David, > That's not a question of wrong or right. You didn't ask what was wrong or right — you said you had no idea what I would CONSIDER to be more right, so I told you. > It's not at all clear what it should apply to. Ah, another of your completely unhelpful answers. Thanks. > Before one even has a notion what "regardless of the grob" is supposed > to mean, one needs to have an idea what it should apply to. Grobs don't > generally are made from markup. Please rephrase in proper English. > One person's clearly is another's hand-waving. Wow. Just wow. Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: feature request: abs-fontsize available for all text grobs
Kieren MacMillan writes: > David, > >> That's not a question of wrong or right. > > You didn't ask what was wrong or right — you said you had no idea what > I would CONSIDER to be more right, so I told you. > >> It's not at all clear what it should apply to. > > Ah, another of your completely unhelpful answers. Thanks. > >> Before one even has a notion what "regardless of the grob" is supposed >> to mean, one needs to have an idea what it should apply to. Grobs don't >> generally are made from markup. > > Please rephrase in proper English. > >> One person's clearly is another's hand-waving. > > Wow. Just wow. I don't have time for this. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: feature request: abs-fontsize available for all text grobs
On 2013-Jul-16, at 10:54, David Kastrup wrote: > I don't have time for this. If anyone has time to discuss this with me in a reasonable, non-patronizing, and non-pedantic way, feel free to contact me on- or off-list. As always, I'm open to sponsoring work that will help move Lilypond forward. Best regards, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pattern-generating Scheme function challenge
Hi there,
I am not at home ... so here is not a solution, but here is a little
snippet, that includes two functions, that may be helpful:
\version "2.16.1"
musA = \relative c'' {
bes4 a c b
}
musB = #(music-map
(lambda (m)
(let* ((mus m)
(dur (ly:music-property mus 'duration)))
(if (ly:duration? dur)
(ly:music-set-property! mus 'duration
(ly:make-duration
(+ 1 (ly:duration-log dur))
(ly:duration-dot-count dur)
2 1)))
mus)) (ly:music-deep-copy musA))
<<
\new Staff \musA
\new Staff \musB
>>
HTH
Cheers, Jan-Peter
On 13.07.2013 16:03, Urs Liska wrote:
Hi all, the Schemers in particular,
you surely know by now that I am writing a series of posts that
demonstrate how elegantly and efficiently we can recreate a portion of
a book that obviously has been produced with many pains in Finale.
I'm confident that it will be an impressive display of LilyPond's
power :-) but I would love to go even one step further.
In the post published yesterday I showed how easy it is to typeset
that polymetric example from Aldridge's book.
In the second post (finished but scheduled for monday or tuesday) I
show a Python function that generates the LilyPond code for a complete
set of patterns.
The third post will set up the files to finally print the whole set.
I would be happy to include an alternative approach if I can get the
necessary input from the list (of course I will credit it correctly):
Instead of generating the patterns' code with Python I would like to
see a Scheme function that achieves the same directly from within the
LilyPond files. Probably such an approach could even simplify a few
other things.
The Python code I used is here:
https://github.com/openlilylib/aldridge-patterns/blob/master/pattern-generator.py
and the resulting LilyPond file here:
https://github.com/openlilylib/aldridge-patterns/blob/master/pattern-definitions.ily
and you can of course inspect the whole repository if you want.
The task is to print these examples in five parallel metric contexts
(see
http://lilypondblog.org/wp-content/uploads/2013/07/aldridge-ex-19-score.pdf),
therefore I had to do some things about those virtual time signatures.
If the patterns are generated by a Scheme function we can do better
and handle this specification 'at source level'.
I have added a dummy file that should hold that function:
https://github.com/openlilylib/aldridge-patterns/blob/master/pattern-definitions-scheme.ily
So:
The function should take three arguments (as already in the dummy):
- start and
- end of the range (which in my Python function is hardcoded)
- denominator of the time signatures
For each number in the range it should:
- produce a LilyPond pattern corresponding to the binary
representation of the given number
- chose note/rest duration to be 1/denominator (which is an
improvement over my Python approach because we can omit the \shift-
and \scaleDurations process
- beam from the first to the last note if there is more than one note
and if denominator > 4
Additionally the function should:
- Insert a manual break after four patterns or if the length of the
pattern increases (which happens when the number is a power of two)
(don't forget to reset the counter in that case)
- after that break re-print the time signature (calculated from the
length of the pattern and the given denominator) and insert a \mark
\default
Modifications in the main file I would expect:
- The \newExercise function is obsolete (it was necessary because the
patterns themselves weren't aware of the denominator)
- Instead of the \shiftDurations - \scaleDurations steps (which can be
dropped) I'd move the Timing to the individual staves, that is I don't
use the timeSignatureFractions anymore but real time signatures.
- the \noBeamForLongerNotes function would become obsolete (as we
don't generate those beams in the first place)
(Sorry Harm, but it's not in vain because I'd of course also present
my first approach)
- the patterns are called with \patterns start end denominator.
- As the \shiftDurations are obsolete I don't need that I-II-III-IV-V
stuff anymore but can place the call of \patterns directly in the \score
I'm sure this would deliver even one more deep hit in our "notation
battle", therefore I'm really looking forward to your suggestions.
They can be discussed here, or I'd happily accept them as pull requests.
Urs
___
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
Henle piano template
Hello all, I'm getting close with my Henle piano stylesheet(s) — see attached. Once this is ready, I'm going to document it and put it up on the Lilyblog. I think the last thing I need is an "oval BarNumber enclosure" (see photo). Can anyone help with that? Thanks, Kieren. <> piano_concert_Henle.ly Description: Binary data Beethoven_Op10No3.ly Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Henle piano template
Kieren MacMillan writes: > Hello all, > > I'm getting close with my Henle piano stylesheet(s) — see attached. > Once this is ready, I'm going to document it and put it up on the Lilyblog. > > I think the last thing I need is an "oval BarNumber enclosure" (see photo). > Can anyone help with that? Try starting from #(define-markup-command (ellipse layout props text) (markup?) #:properties ((thickness 0.2) (box-padding 0)) (ellipse-stencil (interpret-markup layout props text) thickness box-padding box-padding)) \markup \ellipse "12" -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Henle piano template
Hi David, > Try starting from Thanks — that's very helpful! Here's what I have from there: \version "2.17" #(define-markup-command (ellipse layout props text) (markup?) #:properties ((thickness 0.2) (x-padding 0.1) (y-padding 0.75)) (ellipse-stencil (interpret-markup layout props text) thickness x-padding y-padding)) \markup \ellipse "2" \markup \ellipse "20" \markup \ellipse "200" \markup \ellipse "2000" \markup \ellipse "2" The 200 looks sufficiently like the three-digit bar numbers in my Henle score that I'm totally satisfied. The four- and five-digit ones are fine (though the five-digit one is probably a little "pointy": I don't have any 1+ bar Henle scores to compare it to). However, I'd love to fix the one- and two-digit versions: they're currently too "vertical" and "circular", respectively. What's the easy way of saying "center the number in a box at least 'this big', but use the number's real extent if it's bigger than that"? Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Henle piano template
2013/7/16 Kieren MacMillan :
> Hi David,
>
>> Try starting from
>
> Thanks — that's very helpful!
>
> Here's what I have from there:
>
> \version "2.17"
>
> #(define-markup-command (ellipse layout props text) (markup?)
> #:properties ((thickness 0.2) (x-padding 0.1) (y-padding 0.75))
> (ellipse-stencil (interpret-markup layout props text)
>thickness x-padding y-padding))
>
> \markup \ellipse "2"
> \markup \ellipse "20"
> \markup \ellipse "200"
> \markup \ellipse "2000"
> \markup \ellipse "2"
>
> The 200 looks sufficiently like the three-digit bar numbers in my Henle score
> that I'm totally satisfied.
> The four- and five-digit ones are fine (though the five-digit one is probably
> a little "pointy": I don't have any 1+ bar Henle scores to compare it to).
>
> However, I'd love to fix the one- and two-digit versions: they're currently
> too "vertical" and "circular", respectively.
> What's the easy way of saying "center the number in a box at least 'this
> big', but use the number's real extent if it's bigger than that"?
>
> Thanks,
> Kieren.
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Kieren,
below my own approach.
I defined two formatters for BarNumber,
1) using my version of \ellipse (though, it's nearly the same as David's).
2) using \oval
I'd prefer \oval, because it's better appearence with one- and
two-digit numbers.
\version "2.17.22"
%%
% markup-commands
%%
#(define-markup-command (ellipse layout props arg)
(markup?)
#:properties ((thickness 1)
(font-size 0)
(ellipse-padding 0.2))
"
Draw an ellipse around @var{arg}. Use @code{thickness},
@code{ellipse-padding} and @code{font-size} properties to determine line
thickness and padding around the markup.
@lilypond[verbatim,quote]
\\markup {
\\ellipse {
Hi
}
}
@end lilypond
"
(let ((th (* (ly:output-def-lookup layout 'line-thickness)
thickness))
(pad (* (magstep font-size) ellipse-padding))
(m (interpret-markup layout props arg)))
(ellipse-stencil m th pad pad)))
#(define-markup-command (oval layout props arg)
(markup?)
#:properties ((thickness 1)
(font-size 0)
(oval-padding 0.65))
"
Draw a oval around @var{arg}. Use @code{thickness},
@code{oval-padding} and @code{font-size} properties to determine line
thickness and padding around the markup.
@lilypond[verbatim,quote]
\\markup {
\\oval {
Hi
}
}
@end lilypond
"
(let ((th (* (ly:output-def-lookup layout 'line-thickness)
thickness))
(pad (* (magstep font-size) oval-padding))
(m (interpret-markup layout props arg)))
(oval-stencil m th pad pad)))
%%
% barnumbers-formatter
%%
#(define (format-oval-barnumbers barnum measure-pos alt-number context)
(make-oval-markup
(robust-bar-number-function barnum measure-pos alt-number context)))
#(define (format-ellipse-barnumbers barnum measure-pos alt-number context)
(make-ellipse-markup
(robust-bar-number-function barnum measure-pos alt-number context)))
%%
% Examples
%%
% toplevel-markup
\markup \fill-line {
\column { \bold "Toplevel-markups"
\line { "using \\ellipse: " \ellipse { "1" "11" "111" "" "1" } }
\line { "using \\oval:" \oval { "1" "11" "111" "" "1" } }
\vspace #2
}
}
% scores, including tests for 'alternativeNumberingStyle'
mus =
\relative c'{
\repeat volta 3 { c4 d e f | }
\alternative {
{ c4 d e f | c2 d \break }
{ f4 g a b | f4 g a b | f2 a | \break }
{ c4 d e f | c2 d }
}
c1 \break
\set Score.alternativeNumberingStyle = #'numbers
\repeat volta 3 { c4 d e f | }
\alternative {
{ c4 d e f | c2 d \break }
{ f4 g a b | f4 g a b | f2 a | \break }
{ c4 d e f | c2 d }
}
c1 \break
\set Score.alternativeNumberingStyle = #'numbers-with-letters
\repeat volta 3 { c,4 d e f | }
\alternative {
{ c4 d e f | c2 d \break }
{ f4 g a b | f4 g a b | f2 a | \break }
{ c4 d e f | c2 d }
}
c1
}
\score {
\new Staff \mus
\header {
piece =
\markup \bold \fill-line { \column { "Normal BarNumbers" \vspace #2 } }
}
}
\score {
\new Staff \mus
\layout {
\context {
\Score
barNumberFormatter = #format-oval-barnumbers
}
}
\header {
piece =
\markup \bold \fill-line { \column { "Oval BarNumbers" \vspace #2 } }
}
}
\score {
\new Staff \mus
\layout {
\context {
\Score
barNumberFormatter = #format-ellipse-barnumbers
}
}
\header {
piece =
\markup \bold \fill-line { \column { "Ellipse BarNumbers" \vspace #2 } }
}
}
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Henle piano template
Kieren MacMillan writes:
> What's the easy way of saying "center the number in a box at least
> 'this big', but use the number's real extent if it's bigger than
> that"?
\hcenter-in does that.
#(define-markup-command (ellipse layout props text) (markup?)
#:properties ((thickness 0.2) (box-padding 0))
(ellipse-stencil (interpret-markup layout props text)
thickness box-padding box-padding))
\markup \ellipse \hcenter-in #2.5 { "1" "12" "123" "1234" }
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Henle piano template
Hi everyone, Thanks to David K and Harm (whose functions and suggestions I mashed up to make the oval bar number formatter), we have a winner! Well, at least for now… further tweaks coming once I've typeset the rest of the movement. Then I'll do a side-by-side comparison of the printed version and start attacking line thicknesses, font properties, and other finer points. =) Cheers, Kieren. piano_concert_Henle.ly Description: Binary data Beethoven_Op10No3.ly Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pattern-generating Scheme function challenge
OK, sorry ... I missed the point, you want pattern generation ;)
--snip--
#(use-modules (srfi srfi-60))
#(define-public pattern
(define-music-function (parser location n pitch dur)
(integer? ly:pitch? ly:duration?)
(let ((l (list)))
(define (pat i)
(if (< i n)
(append (pat (* 2 i))
(list
(if (= (bitwise-and i n) 0)
(make-music 'RestEvent 'duration dur)
(make-music 'NoteEvent 'duration dur 'pitch pitch
(list)))
(make-music 'SequentialMusic
'elements (pat 1))
)))
\new Staff {
\time 7/2
\pattern #73 c'' 2
}
--snip--
This will create a series of note- and restevents based on the binary
pattern of the given integer.
I'll be back next week ;)
HTH
Best, Jan-Peter
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: can you globally set different padding values for different Script grobs?
Hi Harm, > sometime ago David Nalesnik and I were working on it. > Originally, it was 2.14.2-code but still works with 2.17.21. Sorry I never responded to this — it's amazing! This, IMHO, should be part of the default distro. Many thanks! Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
