How can I make a markup-text with a concatanation of italic text and the \sustainOn symbol?
Dear all,
I am presently re-engraving a number of almost forgotten piano pieces.
One of them has under the first bar of the LH staff the text: "sempre 2 Ped",
Ped being the usual standard notation as generated by \sustainOn.
Although the LilyPond documentation tells me somewhere that "Pedal indications
may be placed in a Dynamics context, which aligns them on a horizontal line."
this does obviously not imply that a markup-construction such as
"\markup {\line {\concat \italic { più } { \dynamics f } }}" can be used in my
case.
What should I do here to align "sempre 2" with \sustainOn?
Thanks in advance for any advice.
Best regards,
Robert Blackstone
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: export as image (png)
On 22.01.2017 01:10, David Wright wrote: I would use PDFs if you can, Or SVGs, if the respective software supports them. as they can be rescaled as much as you like without becoming blurred. Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How can I make a markup-text with a concatanation of italic text and the \sustainOn symbol?
On 22.01.2017 10:36, Robert Blackstone wrote:
I am presently re-engraving a number of almost forgotten piano pieces.
One of them has under the first bar of the LH staff the text: "/sempre
2 Ped/", Ped being the usual standard notation as generated by \sustainOn.
Although the LilyPond documentation tells me somewhere that "Pedal
indications may be placed in a Dynamics context, which aligns them on
a horizontal line." this does obviously not imply that a
markup-construction such as
"\markup {\line {\concat \italic { più } { \dynamics f } }}" can be
used in my case.
What should I do here to align "/sempre 2/" with \sustainOn?
You can of course use a markup construction. The ‘Ped’ symbol is
available through \markup { \musicglyph #"pedal.Ped" }, see
and
for \musicglyph.
So you /should/ be able to just do this:
%%%
\version "2.18.2"
sustainBothMrkp = \markup { sempre 2 \musicglyph #"pedal.Ped" }
sustainBothOn = -\tweak text \sustainBothMrkp \sustainOn
\new Staff {
c'1\sustainBothOn
c'1\sustainOff
}
%%%
which would then work equally fine in Staff and Dynamics contexts.
However, I get ‘warning: SustainPedal has empty extent and non-empty
stencil’ and \sustainBothOn isn’t printed, which I don’t know why. Anyone?
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
grace note suppresses instrument name!
Consider:
\version "2.19.43"
\new Staff
<<
\set Staff.instrumentName = \markup "Treble Recorder"
{
\grace f'8
g'4 g'
}
>>
with the grace note the instrument name is not printed, without it, it
is. Should the syntax used here work? I realize that by replacing << >>
with {} it works, but is there a good reason why this <<>> syntax
suddenly fails when a grace note starts the music?
Richard
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: grace note suppresses instrument name!
Le dimanche 22 janvier 2017 à 10:40 +, Richard Shann a écrit :
> Consider:
>
> \version "2.19.43"
> \new Staff
> <<
> \set Staff.instrumentName = \markup "Treble Recorder"
> {
> \grace f'8
> g'4 g'
> }
> >>
>
> with the grace note the instrument name is not printed, without it,
> it
> is. Should the syntax used here work? I realize that by replacing <<
> >>
> with {} it works, but is there a good reason why this <<>> syntax
> suddenly fails when a grace note starts the music?
>
> Richard
>
Try this:
\new Staff {
\set Staff.instrumentName = \markup "Treble Recorder"
<<
{
\grace f'8
g'4 g'
}
>>
}
Regards,
Jean
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: grace note suppresses instrument name!
On Sun, 2017-01-22 at 11:56 +0100, Jean Bréfort wrote:
> Le dimanche 22 janvier 2017 à 10:40 +, Richard Shann a écrit :
> > Consider:
> >
> > \version "2.19.43"
> > \new Staff
> > <<
> > \set Staff.instrumentName = \markup "Treble Recorder"
> > {
> >\grace f'8
> >g'4 g'
> > }
> > >>
> >
> > with the grace note the instrument name is not printed, without it,
> > it
> > is. Should the syntax used here work? I realize that by replacing <<
> > >>
> > with {} it works, but is there a good reason why this <<>> syntax
> > suddenly fails when a grace note starts the music?
> >
> > Richard
> >
>
> Try this:
> \new Staff {
> \set Staff.instrumentName = \markup "Treble Recorder"
> <<
> {
>\grace f'8
>g'4 g'
> }
> >>
> }
Thank you - I see that using { } makes it work via more than one route,
but is it a bug? (It is not a purely academic question, I would have
difficulty generating an extra { } from Denemo without some recoding, or
using a customised score layout.)
Richard
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Warning about beam slope configuration
On Sat, 2017-01-21 at 23:47 +0100, Simon Albrecht wrote:
> On 21.01.2017 21:46, David Sumbler wrote:
> >
> > could somebody explain to me what the warning
> > actually means, and what I would need to do to stop it appearing?
> It signifies problem in the calculation of beam slope. I get it all
> the
> time with kneed beams, even when the printed result is perfectly
> satisfactory.
> If it isn’t, something like
> { 8-\offset positions #'(10 . -10) [ 8] }
> might help.
> And in case the warning is the only problem: insert this at top level
> #(ly:expect-warning "no viable")
> The warning will be suppressed, and you’ll get a warning if there is
> no
> warning anymore to be suppressed.
>
> Best, Simon
Thank you for that. As I don't want a kneed beam I have now added
\once \override Beam.auto-knee-gap = #10
\once \override Beam.positions = #'(-4 . 0)
which solves the immediate problem. I need the auto-knee-gap override,
otherwise Lilypond tries to create a kneed beam and then complains
about negative stem lengths.
Your suggestion is clearly a tweak to Beam.positions, but I can't find
the documentation for the use of \offset. Assuming that there is such
documentation, could you point me to it, please?
David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: grace note suppresses instrument name!
2017-01-22 11:40 GMT+01:00 Richard Shann :
> Consider:
>
> \version "2.19.43"
> \new Staff
> <<
> \set Staff.instrumentName = \markup "Treble Recorder"
> {
>\grace f'8
>g'4 g'
> }
> >>
>
> with the grace note the instrument name is not printed, without it, it
> is. Should the syntax used here work? I realize that by replacing << >>
> with {} it works, but is there a good reason why this <<>> syntax
> suddenly fails when a grace note starts the music?
>
> Richard
Hi Richard,
the << ... >> initializes simultaneous music.
So the first expression is: \set Staff.instrumentName = ...
The second: { \grace f'8 ... }
Maybe you see it already: it's issue 34, grace-synchronization.
And indeed the following works:
\new Staff
<<
{ \set Staff.instrumentName = \markup "Treble Recorder" \grace s8 }
{ \grace f'8 g'4 g' }
>>
Ofcourse nobody wants this sort of code.
Best you can do is setting the instrumentName in \with {}:
\new Staff
\with { instrumentName = \markup "Treble Recorder" }
{ \grace f'8 g'4 g' }
Personally, I think we should change the docs to always show \with {
instrumentName = ... }.
A snippet showing a reasonable use-case for \set Staff.instrumentName
= ... could be added, although I can't think of such reasonable
use-case. Sometimes it makes sense to change th shortInstrumentName
with this command, though.
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: grace note suppresses instrument name!
Richard Shann writes:
> Consider:
>
> \version "2.19.43"
> \new Staff
> <<
> \set Staff.instrumentName = \markup "Treble Recorder"
> {
>\grace f'8
>g'4 g'
> }
> >>
>
> with the grace note the instrument name is not printed, without it, it
> is. Should the syntax used here work?
No.
> I realize that by replacing << >> with {} it works, but is there a
> good reason why this <<>> syntax suddenly fails when a grace note
> starts the music?
It doesn't fail. Due to choosing simultaneous music for setting the
instrument name, the instrument name gets set at time 0. The grace
note, however, gets typeset at time 0-1/8G (namely an eighth note's
grace time duration before that) and triggers creation of the staff.
This can be viewed as related to the _expectations_ of issue 34 in the
issue tracker.
But stuff like instrument names actually is a static property of the
staff. You really, really should set it like
\new Staff \with { instrumentName = "Treble Recorder" }
{
\grace f'8
g'4 g'
}
At some point of time, a fix to issue 34 might change the behavior in
situations like this. But I don't feel that such a fix would
unambiguously address your failed expectations here: in some respect the
behavior is actually correct and might be retained in this situation in
spite of an issue 34 fix.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How can I make a markup-text with a concatanation of italic text and the \sustainOn symbol?
Hello Simon,
Thanks for your advice. In its simple form, i.e. by adding: _\markup { \italic
{sempre 2} \musicglyph #"pedal.Ped" } , it works perfectly.
The other method, as in the ME you gave, it did not work.
But I got exactly what I needed. Thanks again.
Best regards,
Robert
On 22 Jan 2017, at 11:40 , Simon Albrecht wrote:
> On 22.01.2017 10:36, Robert Blackstone wrote:
>> I am presently re-engraving a number of almost forgotten piano pieces.
>> One of them has under the first bar of the LH staff the text: "/sempre 2
>> Ped/", Ped being the usual standard notation as generated by \sustainOn.
>>
>> Although the LilyPond documentation tells me somewhere that "Pedal
>> indications may be placed in a Dynamics context, which aligns them on a
>> horizontal line." this does obviously not imply that a markup-construction
>> such as
>> "\markup {\line {\concat \italic { più } { \dynamics f } }}" can be used in
>> my case.
>>
>> What should I do here to align "/sempre 2/" with \sustainOn?
>
> You can of course use a markup construction. The ‘Ped’ symbol is available
> through \markup { \musicglyph #"pedal.Ped" }, see
>
> and
>
> for \musicglyph.
> So you /should/ be able to just do this:
>
> %%%
> \version "2.18.2"
>
> sustainBothMrkp = \markup { sempre 2 \musicglyph #"pedal.Ped" }
> sustainBothOn = -\tweak text \sustainBothMrkp \sustainOn
>
> \new Staff {
> c'1\sustainBothOn
> c'1\sustainOff
> }
> %%%
>
> which would then work equally fine in Staff and Dynamics contexts.
>
> However, I get ‘warning: SustainPedal has empty extent and non-empty stencil’
> and \sustainBothOn isn’t printed, which I don’t know why. Anyone?
>
> Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Warning about beam slope configuration
On 22.01.2017 12:09, David Sumbler wrote: Your suggestion is clearly a tweak to Beam.positions, but I can't find the documentation for the use of \offset. Assuming that there is such documentation, could you point me to it, please? Alas, \offset is a 2.19 addition, but undocumented. Is there an entry in Changes? Anyway, that’s clearly something we need to fix for 2.20. Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: grace note suppresses instrument name!
On Sun, 2017-01-22 at 12:23 +0100, Thomas Morley wrote:
> 2017-01-22 11:40 GMT+01:00 Richard Shann :
> > Consider:
> >
> > \version "2.19.43"
> > \new Staff
> > <<
> > \set Staff.instrumentName = \markup "Treble Recorder"
> > {
> >\grace f'8
> >g'4 g'
> > }
> > >>
> >
> > with the grace note the instrument name is not printed, without it, it
> > is. Should the syntax used here work? I realize that by replacing << >>
> > with {} it works, but is there a good reason why this <<>> syntax
> > suddenly fails when a grace note starts the music?
> >
> > Richard
>
>
>
> Hi Richard,
>
> the << ... >> initializes simultaneous music.
>
> So the first expression is: \set Staff.instrumentName = ...
> The second: { \grace f'8 ... }
>
> Maybe you see it already: it's issue 34, grace-synchronization.
> And indeed the following works:
> \new Staff
> <<
> { \set Staff.instrumentName = \markup "Treble Recorder" \grace s8 }
> { \grace f'8 g'4 g' }
> >>
> Ofcourse nobody wants this sort of code.
>
> Best you can do is setting the instrumentName in \with {}:
> \new Staff
> \with { instrumentName = \markup "Treble Recorder" }
> { \grace f'8 g'4 g' }
>
Thank you very much for the explanation. Multiple \with{} clauses aren't
supported in 2.19.43 which makes automatic generation somewhat awkward,
but I guess I'll have to bite that bullet.
Thanks too, to David for his reply - I didn't realize how the grace note
typesetting moment is assigned.
Back to the drawing board...
Richard
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Warning about beam slope configuration
Now to everyone... On Jan 22, 2017 6:14 AM, "David Nalesnik" wrote: On Jan 22, 2017 5:54 AM, "Simon Albrecht" wrote: On 22.01.2017 12:09, David Sumbler wrote: > Your suggestion is clearly a tweak to Beam.positions, but I can't find > the documentation for the use of \offset. Assuming that there is such > documentation, could you point me to it, please? > Alas, \offset is a 2.19 addition, but undocumented. Is there an entry in Changes? Anyway, that’s clearly something we need to fix for 2.20. Best, Simon I'm actually midway through documentation now. Stay tuned! David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Space after barline before first chord notes
Hi Andrew,
2017-01-22 8:37 GMT+01:00 Andrew Bernard :
> In my large score, at one point there is a very large gap between a span
> bar/barline and the chords in the bar, which have lots of accidentals
> (dodecaphonic style). I would prefer to be able to move the chords left
> closer to the barline. I have made an MWE to illustrate. In the score with
> the line break where the bars are spread out, lilypond moves the chords away
> from the barline, and in my original context, far too much, much more than
> here. In the score with no break, the positioning is fine.
>
> I have experimented with space-alist values to no avail. Pointers to how to
> control this spacing issue would be most appreciated.
>
> Andrew
>
> == snip
>
> \version "2.19.54"
>
> treble = {
> \clef treble
> \time 1/4
> c'4
> \clef bass
> 1
> \break
> c'4 c'
> }
>
> bass = {
> \clef bass
> \time 1/4
> c4
> 1 |
> c4 c
> }
>
> \score {
> \new PianoStaff
> <<
> \new Staff \treble
> \new Staff \bass
> >>
> \layout {
> \Score
why do you copy the Score-settings, but do nothing else with it?
> \accidentalStyle Score.dodecaphonic
> }
> }
>
>
> trebleTwo = {
> \clef treble
> \time 1/4
> c'4
> \clef bass
> 1
> c'4
> %\break
> c'
> }
> \score {
> \new PianoStaff
> <<
> \new Staff \trebleTwo
> \new Staff \bass
> >>
> \layout {
> \Score
> \accidentalStyle Score.dodecaphonic
> }
> }
>
> == snip
You could try to use this:
\layout {
\context {
\Score
\accidentalStyle dodecaphonic
%% changing semi-fixed-space to fixed space
%% and 0.9 to 1.3 (same value as for first-note
\override BarLine.space-alist.next-note = #'(fixed-space . 1.3)
}
}
Not sure the results will be convincing, though.
Ofcourse you could apply it with
\once \override Score.BarLine.space-alist.next-note = ...
for one-time-use.
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Warning about beam slope configuration
Simon Albrecht wrote Sunday, January 22, 2017 11:54 AM > Alas, \offset is a 2.19 addition, but undocumented. Is there an entry in > Changes? > Anyway, that’s clearly something we need to fix for 2.20. See https://sourceforge.net/p/testlilyissues/issues/3830/ Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: autochange and multiple voices
Decimo tertio Kalendas Februarias MMXVII scripsit Malte Meyn : > > > Am 20.01.2017 um 18:39 schrieb Jérôme Plût: > > Problem 1: why, on the third beat, is the alto voice (playing a g') > > displayed on the "down" Staff? > > It doesn’t in LilyPond 2.19.53, which version are you using? I am using 2.18.2 (last stable version according to lilypond.org, also the version packaged by standard Linux distros). > Do you really want to have three separate voices? If so you should try > 2.19. The results look much better IMO. After installing 2.19 (thanks for providing an install script - I am still somwehat surprised that it worked out-of-the-box on my stable Debian!), it is indeed better. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: avoiding collisions between markup, tempo, and \mark
On 21/01/17 02:18, Andrew Bernard wrote:
> Hi Andrew,
>
> The manual is not well written concerning this matter. A \tempo is a
> metronome mark (I don't think that is entirely obvious).
>
> {
> \mark \default
>
> \once \override Score.MetronomeMark.extra-offset = #'(8 . 0)
> \tempo "A tempo" 8 = 104
> s2^\markup { \musicglyph #"scripts.segno" } | s2*15 \bar "||"
> }
>
>
> Andrew
>
The other trick to try (which I think is a bit iffy, iirc I find it
sometimes works well, and sometimes doesn't) is
\tempo " A tempo" 8 = 104
Note the leading spaces ...
Cheers,
Wol
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Putting a \layout block in a Scheme macro
I want to make a Scheme macro \BlankStaff that outputs a single white
staff. (Optionnally, \BlankStaff #3 would output three of them, etc.
In particular, using “\include "blank-staff.ly"” is a non-solution).
A snippet does the white staff:
http://lilypond.org/doc/v2.19/Documentation/snippets/staff-notation#staff-notation-creating-blank-staves
However, this snippet uses a \layout { } block, which I am unable to
include in the #{ ... #} block of a Scheme function definition:
#(collect-music-for-book #{
\score { \repeat unfold 12 { s1 } \break
\layout { \indent = 0 \in
\context { \Staff \remove "Bar_engraver" } } } #})
produces the following error:
scm/lily-library.scm:153:5:Wrong type argument in position 1 (expecting Prob):
#
So my question is this: how does the \layout{ } block translate to
Scheme?
Thanks,
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: avoiding collisions between markup, tempo, and \mark
Hi Andrew (et al.),
I would suggest X-offset is perhaps a good choice:
{
\mark \default
\once \override Score.MetronomeMark.X-offset = #11
\tempo "A tempo" 8 = 104
s2^\markup { \musicglyph #"scripts.segno" } | s2*15 \bar "||”
}
Or perhaps even extra-spacing-width/height, etc. In any case, I think it should
be something relatively surgical and specific: Wol's “ A tempo” idea is too
hacky/unpredictable, and extra-offset should only be used when there are no
better solutions.
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: Putting a \layout block in a Scheme macro
2017-01-22 19:30 GMT+01:00 Jérôme Plût :
>
> I want to make a Scheme macro \BlankStaff that outputs a single white
> staff. (Optionnally, \BlankStaff #3 would output three of them, etc.
> In particular, using “\include "blank-staff.ly"” is a non-solution).
>
> A snippet does the white staff:
> http://lilypond.org/doc/v2.19/Documentation/snippets/staff-notation#staff-notation-creating-blank-staves
>
> However, this snippet uses a \layout { } block, which I am unable to
> include in the #{ ... #} block of a Scheme function definition:
>
> #(collect-music-for-book #{
> \score { \repeat unfold 12 { s1 } \break
> \layout { \indent = 0 \in
> \context { \Staff \remove "Bar_engraver" } } } #})
>
> produces the following error:
>
> scm/lily-library.scm:153:5:Wrong type argument in position 1 (expecting Prob):
> #
>
> So my question is this: how does the \layout{ } block translate to
> Scheme?
Well, your example fails for several reasons.
(1)
In
\score { \repeat unfold 12 { s1 } \break
the \break has to be moved into { }, otherwise the score-command sees
two musical expressions.
You should have seen:
error: Spurious expression in \score
\score { \repeat unfold 12 { s1 }
\break
(2)
In
\indent
remove the slash.
You should have seen:
error: unknown escaped string: `\indent'
\layout {
\indent = 0 \in
(3)
collect-music-for-book is the wrong command. It expects _music_ not a
score. See:
#(display (ly:music? #{ c'1 #}))
#(newline)
#(display (ly:music? #{ \score { { c'1 } } #}))
You could do:
sc =
\score {
\repeat unfold 12 { s1 \break }
\layout {
indent = 0 \in
\context {
\Staff
\remove "Bar_engraver"
}
}
}
#(add-score sc)
%% probably:
#(collect-scores-for-book sc)
Cheers,
Harm
P.S.
The actual topic of this thread, \layout in scheme, is not answered.
Though, I doubt you still need it. If I'm wrong, please shout and I'll
have a second thought
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Putting a \layout block in a Scheme macro
On 22/01/17 20:12, Thomas Morley wrote:
P.S.
The actual topic of this thread, \layout in scheme, is not answered.
Though, I doubt you still need it. If I'm wrong, please shout and I'll
have a second thought
If you do feel the need to process layouts in Scheme, this may point you
in the right direction.
\version "2.19.54"
BlankStaff =
#(define-void-function (count) (integer?)
(let* ((blankstaff #{ \score { { s1 \break } } #} )
(layout #{ \layout { \context { \Staff \remove
"Bar_engraver" } } #} )
(bookpart (ly:make-book-part (make-list count blankstaff)))
(book (ly:make-book $defaultpaper $defaultheader)))
(ly:output-def-set-variable! layout 'indent (ly:mm 0))
(ly:output-def-set-variable! layout 'ragged-right #f)
(ly:book-add-bookpart! book bookpart)
(ly:book-process book $defaultpaper layout (ly:parser-output-name))
))
\BlankStaff 4
--
Timothy Lanfear, Bristol, UK.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Warning about beam slope configuration
On Sun, Jan 22, 2017 at 8:12 AM, Trevor Daniels wrote: > > Simon Albrecht wrote Sunday, January 22, 2017 11:54 AM > >> Alas, \offset is a 2.19 addition, but undocumented. Is there an entry in >> Changes? >> Anyway, that’s clearly something we need to fix for 2.20. > > See https://sourceforge.net/p/testlilyissues/issues/3830/ > Patch up for review. -David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Space after barline before first chord notes
Hello Harm, A good and excellent solution. Works fine in my context. It's hard to find one's way among all the spacing alist variables, as the documentation for each is fairly thin. This is really helpful. Andrew ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
