Re: Note names are causing text marks to be duplicated

2024-04-25 Thread Eric Benson
Is this intentional or desired? If so, is there a way to prevent this from
happening?

On Thu, Apr 25, 2024 at 10:09 PM Aaron Hill 
wrote:

> On 2024-04-25 9:43 pm, Eric Benson wrote:
> > I took one of the NoteName examples from the documentation and dropped
> > a
> > \textMark in the middle of it, and there is an extra copy of that text
> > mark
> > for each NoteName staff.
>
>
> This makes sense, since the \textMark command is within the \melody
> music variable, which gets used three times.  The same behavior occurs
> without NoteNames:
>
> 
> \version "2.24.3"
>
> melody = { b'4 4 \textMark Hey 2 }
>
> << \melody \\ \melody >>
> 
>
>
> -- Aaron Hill
>


Re: Note names are causing text marks to be duplicated

2024-04-25 Thread Aaron Hill

On 2024-04-25 9:43 pm, Eric Benson wrote:
I took one of the NoteName examples from the documentation and dropped 
a
\textMark in the middle of it, and there is an extra copy of that text 
mark

for each NoteName staff.



This makes sense, since the \textMark command is within the \melody 
music variable, which gets used three times.  The same behavior occurs 
without NoteNames:



\version "2.24.3"

melody = { b'4 4 \textMark Hey 2 }

<< \melody \\ \melody >>



-- Aaron Hill



Note names are causing text marks to be duplicated

2024-04-25 Thread Eric Benson
I took one of the NoteName examples from the documentation and dropped a
\textMark in the middle of it, and there is an extra copy of that text mark
for each NoteName staff.


nntest.ly
Description: Binary data


nntest.pdf
Description: Adobe PDF document


Re: Mixed ChoirGroup: Solo/Choir

2024-04-25 Thread David Wright
On Thu 25 Apr 2024 at 13:36:49 (+), Schlipf, John (schlipf) wrote:
> On question:
> On Wed 24 Apr 2024 at 19:13:47 (+0200), Johannes Roeßler wrote:
> > Hey David,
> >
> > it works - but I am running into an issue with short passages.
> > I would like to stretch the choir part to the right side,
> > but when I bring in "ragged-right = ##f" then it breaks:
> >
> > I assume you have a solution for that issue?
> 
> This is simple, but perhaps it would work for you.  I've stretched (what I 
> thought were) over-compressed lines by just putting in a manual line break 
> before and after the line I want to stretch.  Lilypond then spreads the 
> demarcated line out to fill the space.

Just to clarify what I wrote Wed, 24 Apr 2024 23:46:22 -0500

  "I don't like to stretch the responses music much at all, …"

The sole control I exercise on the layout of each V is
to set the individual   indent = NN   that's added to
the global   ragged-right = ##f ragged-last = ##f.

I choose the values by trial and error, to give the first
(or sole) line of a response a balanced appearance compared
with the full-width lines in the rest of the setting.
Overcompression beyond a certain point will lead to LP's
addition of a linebreak anyway.

In the thumbnail score that I previously attached, the values
of NN were: 70, 40, 110, 20, 0, 80, 50, 70, 80, 40, 60, 0, the
Lord's Prayer having no intonation, and the Amens being labelled,
with no cue or indent required.

Cheers,
David.



Re: Lyrics and Barchecks

2024-04-25 Thread David Wright
On Thu 25 Apr 2024 at 13:06:01 (-0700), Steve Carlock wrote:
> Thanks.  I agree that the barcheck warning message is cryptic.  It appears
> that this issue happens when the lyric is attached to notes that are tied
> across a measure boundary.  Unfortunately I can't change the third measure
> - that motif from my simple example is used frequently in the pieces I am
> working on at the moment.  It's a catch-22.  I start ignoring the barcheck
> warnings because of the lyrics that cross measure boundaries and then miss
> the legit warnings from where I've messed up the lyrics.  The good news is
> that even with the warnings, the output is exactly what I need it to be.

It's possible to set your extract, make all the checks, and get no
warning messages, but it's tedious, and means using lyric durations.
(check1.ly, attached.) Using addlyrics instead of lyric durations
is a trade-off, and I assume the documenter had already made that
choice when they wrote:

  "Note that bar check marks in lyrics are evaluated at the musical
   moment when the syllable following the check mark is processed. If
   the lyrics are associated with the notes of a voice which has a rest
   at the beginning of a bar, then no syllable can be located at the
   start of that bar and a warning will be issued if a bar check mark
   is placed in the lyrics at that position."

One compromise you can make is to leave out any bar checks that occur
within lyrics that happen to cross barlines. You can still add a
barNumberCheck as long as you bear in mind that its number applies
to the measure of the /next/ lyric. (check2.ly, attached.)

Alternatively, you can leave the bar and bar number checks in place,
as you suggest above, but use the tersely documented¹ expect-warning
feature to silence just these warnings. (check3.ly, attached.) That
will prevent their spam from obscuring other, significant warnings
amd errors.

Each expect-warning line at the top of the file (which is where they
must all be placed) will silence one warning with the corresponding
text. They must be placed in the corresponding order as well.²

Run check3.ly with its expect-warning line commented out, and again
with it duplicated: you will see how it works, and that extra
expect-warning lines are treated as errors, not ignored.

AIUI the expect-warning string has to match the warning message from
the start of the text, but can be truncated, ie expect-warning
"bar check failed" would still match the warning in check3.ly.

¹ Internals References §4 Scheme functions (alphabetical)
  page 872 in version 2.25.10

² But particularly for bar checks, bear this in mind:
  "If successive bar checks are off by the same musical interval,
  only the first warning message is displayed. This allows the
  warning to focus on the source of the timing error."
  (Notation Reference.)

Cheers,
David.
\version "2.24.3"
\language "english"

<<
  \new Staff {
\new Voice = vvv {
  \relative c' {
\override Score.BarNumber.break-visibility = #all-visible
\set Score.barNumberVisibility = #(every-nth-bar-number-visible 1)
f8 4 f8 f4 8 f8~ \barNumberCheck #2 |
4 r4 r2 \barNumberCheck #3 |
r2 r8 f8 4 \barNumberCheck #4 |
  }
}
  }
  \new Lyrics {
\lyricmode {
  \set associatedVoice = vvv
  This8 Lit4 -- tle8 star4 -- O8 -- mine8 __ \barNumberCheck #2 |
  _4 \skip4 \skip2 \barNumberCheck #3 |
  \skip2 \skip8 I8 said4 \barNumberCheck #4 |
}
  }
>>
\version "2.24.3"
\language "english"

<<
  \new Staff {
\new Voice {
  \relative c' {
\override Score.BarNumber.break-visibility = #all-visible
\set Score.barNumberVisibility = #(every-nth-bar-number-visible 1)
f8 4 f8 f4 8 f8~ \barNumberCheck #2 |
4 r4 r2 \barNumberCheck #3 |
r2 r8 f8 4 \barNumberCheck #4 |
  }
}
  }
  \addlyrics {
\lyricmode {
  This Lit -- tle star -- O -- mine __ \barNumberCheck #3
  I said \barNumberCheck #4 |
}
  }
>>
#(ly:expect-warning "bar check failed at: 5/8")
\version "2.24.3"
\language "english"

<<
  \new Staff {
\new Voice {
  \relative c' {
\override Score.BarNumber.break-visibility = #all-visible
\set Score.barNumberVisibility = #(every-nth-bar-number-visible 1)
f8 4 f8 f4 8 f8~ \barNumberCheck #2 |
4 r4 r2 \barNumberCheck #3 |
r2 r8 f8 4 \barNumberCheck #4 |
  }
}
  }
  \addlyrics {
\lyricmode {
  This Lit -- tle star -- O -- mine __ \barNumberCheck #3 |
  I said \barNumberCheck #4 |
}
  }
>>


Re: Lyrics and Barchecks

2024-04-25 Thread Aaron Hill
It is known (and documented) that bar checks need to be used with care 
within Lyrics contexts.  I was thinking about this problem and wondered 
if a custom engraver would be able to assist.  (The actual bar checks 
are implemented in an iterator, presumably because it results in faster 
processing when skipping typesetting.)  At this time, I am not sure if 
custom iterators can be created within Scheme, so consider this just a 
proof-of-concept using a Scheme engraver.


It would seem that for the case of lyrics, the behavior of a so-called 
"lyric bar check" would be less precise than that of the normal bar 
check.  Instead of requiring the bar check to occur only at the first 
moment of a measure, the logic instead simply checks that no lyrics have 
been created from the beginning of the measure to the time of the lyric 
bar check.  That is to say, the lyric bar check should be the first 
"thing" that occurs in a measure when it appears.


Attached is the proof-of-concept code.

NOTE: The final lyric bar check intentionally is an example of a failing 
case.  Here is the expected compiled output:



lyric-bar-check.ly:64:54: warning: lyric bar check failed
\addlyrics { | lo -- rem | ips -- um | do -- lor sit
 | a -- met }


Also NOTE: The code includes a toplevel-music-function that converts 
normal bar checks that occur within Lyrics contexts into lyric bar 
checks that the custom engraver handles.  This was done so that the user 
could input lyric bar checks using the same symbol as for normal music 
but get the unique behavior.  Not sure if this transparent approach is 
best, as it could be seen as surprising to some users.



-- Aaron Hill\version "2.25.13"

#(define-event-class 'lyric-bar-check 'music-event)
#(define custom-music-descriptions
  `((LyricBarCheck
  . ((description . "Check whether lyrics correlate with
 the start of the measure.")
 (types . (lyric-bar-check event))

#(set!
  custom-music-descriptions
  (map (lambda (x)
(set-object-property! (car x)
  'music-description
  (cdr (assq 'description (cdr x
(let ((lst (cdr x)))
  (set! lst (assoc-set! lst 'name (car x)))
  (set! lst (assq-remove! lst 'description))
  (hashq-set! music-name-to-property-table (car x) lst)
  (cons (car x) lst)))
  custom-music-descriptions))
#(set! music-descriptions
  (sort
(append music-descriptions custom-music-descriptions)
alist

Re: Lyrics and Barchecks

2024-04-25 Thread Steve Carlock
William,

Thanks.  I agree that the barcheck warning message is cryptic.  It appears
that this issue happens when the lyric is attached to notes that are tied
across a measure boundary.  Unfortunately I can't change the third measure
- that motif from my simple example is used frequently in the pieces I am
working on at the moment.  It's a catch-22.  I start ignoring the barcheck
warnings because of the lyrics that cross measure boundaries and then miss
the legit warnings from where I've messed up the lyrics.  The good news is
that even with the warnings, the output is exactly what I need it to be.

Thanks
 -steve

On Tue, Apr 23, 2024 at 7:02 PM William Rehwinkel <
will...@williamrehwinkel.net> wrote:

> Dear Steve,
>
> I think the reason for this is hinted at by the cryptic "5/8" in the
> barcheck failure message. The "mine" at the end of the first measure
> extends all the way until the next note ("I"), which is not at the
> beginning of a bar, causing the barcheck to fail. If you try the
> following example which is identical except for removing "\skip |" which
> doesn't do anything and changing the notes of the third measure, the
> barcheck warning goes away.
>
> I think the only way to deal with this is to put barline checks in
> lyrics only when the lyric is on the first beat of the measure.
>
> Thanks,
> -William
>
> %
> \version "2.25.6"
> \language "english"
>
> <<
> \new Staff { \relative c' {
>f8 4 f8 f4 8 f8~ |
>4 r4 r2 |
>4 4
>%r2 r8 f8 4 |
>}
> }
>\addlyrics { \lyricmode {
>  This Lit -- tle star -- O -- mine __ |
>  I said |
>  }
>}
>  >>
>
>
> On 4/23/24 20:52, Steve Carlock wrote:
> > I'm confused.  Given the following:
> >
> > %
> > \version "2.24.3"
> > \language "english"
> >
> > <<
> > \new Staff { \relative c' {
> >f8 4 f8 f4 8 f8~ |
> >4 r4 r2 |
> >r2 r8 f8 4 |
> >}
> > }
> >\addlyrics { \lyricmode {
> >  This Lit -- tle star -- O -- mine __ |
> >  \skip |
> >  I said |
> >  }
> >}
> >  >>
> > %
> >
> > I get a barcheck warning on the first measure of lyrics.  I can resolve
> > it by adding a \skip to the end of the lyrics for the first measure, by
> > removing the bar at the end of the first measure of lyrics, or by
> > removing the third measure completely (both music and lyric).
> >
> > I have 6 notes in the first measure and 6 syllables in the lyrics so I
> > don't understand why I'm getting a barcheck warning, especially because
> > if you take out the third measure of music you don't get the warning.
> >
> > (In all cases the layout is exactly what I'm expecting/wanting).
> >
> > Please help me see the error of my ways.
> > Thanks!
> >   -steve
> >
> > Version Info:
> > Lilypond: 2.24.3
> > Frescobaldi: 3.2
> > Extension API: 0.9.0
> > Python: 3.10.12
> > python-ly: 0.9.6
> > Qt: 5.15.3
> > PyQt: 5.15.6
> > sip: 6.5.1
> > qpageview: 0.6.2
> > poppler: 22.2.0
> > python-poppler-qt: 0.75.0
> > OS: Linux-5.15.0-102-generic-x86_64-with-glibc2.35
>
> --
> William Rehwinkel - Oberlin College and Conservatory '24
>
> will...@williamrehwinkel.net
>
> PGP key: https://ftp.williamrehwinkel.net/pubkey.txt
>


Re: Highlighting lyric words

2024-04-25 Thread Walt North
Thanks, that does seem to work at least in a small test case.  I saved 
the function off to an include file and will try it on a larger set of 
lyrics later.  It does seem like a bit of work to do something that 
could a base lilypond feature since it would seem like background 
highlighting of some words in lyrics wouldn't be that uncommon.  That 
type of feature is currently available for staff notes.


Thanks for the help.

Walt

On 4/24/2024 8:21 PM, Aaron Hill wrote:

On 2024-04-24 4:05 pm, Walt North wrote:
Thanks, that's close enough to what I wanted.  I was originally for 
yellow background with back letters... but red (or other bright) font 
will suffice.



Here is an (over-engineered and probably bug-ridden) approach:


\version "2.25.13"

#(define-markup-command
  (highlight layout props arg) (markup?)
  #:category other
  #:properties ((blot 0.2)
    (color yellow)
    (padding 0.2))
  (let* ((stencil (interpret-markup layout props arg))
 (strut (interpret-markup layout props
  #{ \markup qxb #}))
 (x-extent (ly:stencil-extent stencil X))
 (y-extent (interval-union
 (ly:stencil-extent stencil Y)
 (ly:stencil-extent strut Y)))
 (x-extent-wide (interval-widen x-extent padding))
 (y-extent-wide (interval-widen y-extent padding)))
    (interpret-markup layout props #{
  \markup \combine
    \with-color #color
  \with-dimensions #x-extent #y-extent
  \filled-box #x-extent-wide #y-extent-wide #blot
    \stencil #stencil
    #})))

#(define (highlighter blot color padding)
  (grob-transformer 'stencil
    (lambda (grob orig)
  (grob-interpret-markup grob #{
    \markup
  \override #`(blot . ,blot)
  \override #`(color . ,color)
  \override #`(padding . ,padding)
  \highlight \stencil #orig
  #}

\markup {
  \pad-around #1
  \override #'(blot . 1.5)
  \override #`(color . ,(x11-color 'orange))
  \override #'(padding . 0.5)
  \highlight \line { \bold lorem \italic ipsum }
}

myHighlight = \override LyricText.stencil =
  #(highlighter 0.6 (x11-color 'cornflowerblue) 0.1)

\paper { indent = 0 }
{ \repeat unfold 3 { b'4 4 2 } }
\addlyrics {
  no high -- light
  \myHighlight high --
  \tweak font-family #'sans
  \tweak font-series #'bold
  light -- er
  \undo \myHighlight none
  \once \myHighlight once
  done
}



-- Aaron Hill




Re: Spacing between staves

2024-04-25 Thread Mats Bengtsson


  
  


On 2024-04-25 15:44, Peter Mayes wrote:

I
  may be missing something in the documentation here.
  
  
  I have a two-movement score for a single melodic instrument. Each
  movement fits conveniently onto a single page.
  
  
  I realise this is not a MWE, but I just wanted to specify the
  overall layout of my input
  
  
  \version "2.24.1"
  
  
  \paper { ... }
  
  
  FirstMovement = { ... }
  
  
  \score {
  
    \new Staff { \FirstMovement }
  
    \layout {}
  
  }
  
  \pageBreak
  
  SecondMovement = { ... }
  
  
  \score {
  
    \new Staff { \SecondMovement }
  
    \layout {}
  
  }
  
  
  What I want is for the second movement, on the second page, to
  have slightly increased vertical spacing between staves. (It has
  32nd and even a few 64th notes, and just looks a little "bunched
  up" to my eyes.)
  
  
  I can only see ways to set the vertical spacing globally in the
  \paper block.
  
  
  What I am looking for is a way to say "Increase the vertical
  spacing between staves from this point onwards.
  
  
  Is that possible?
  

This is not an answer to your question, but possibly still part
  of a solution to your problem with "bunched up". If you have a
  movement with sections of mostly long notes and other sections
  with lots of short notes, you can improve the horizontal (I know
  you asked about vertical) spacing significantly, by inserting
  \newSpacingSection at suitable places. Compare the following two
  examples:
\version "2.24.0"
  
  \fixed c' {
  % First a long passage with only long notes
  \repeat unfold 10 { c2 d | }
  % Then a passage with only short notes
  \repeat unfold 20 {c32 d e f g f e d }
  % Finally, long notes again
  \repeat unfold 10 { c2 d | }
  
  }
  
  
  % Same with \newSpacingSection:
  \fixed c' {
  % First a long passage with only long notes
  \repeat unfold 10 { c2 d | }
  \newSpacingSection
  % Then a passage with only short notes
  \repeat unfold 20 {c32 d e f g f e d }
  \newSpacingSection
  % Finally, long notes again
  \repeat unfold 10 { c2 d | }
  }

   /Mats


  




Re: Spacing between staves

2024-04-25 Thread Michael Werner
Hi Peter,

On Thursday, 25 April 2024 09:44:56 EDT Peter Mayes wrote:
> What I want is for the second movement, on the second page, to have
> slightly increased vertical spacing between staves. (It has 32nd and
> even a few 64th notes, and just looks a little "bunched up" to my eyes.)
> 
> I can only see ways to set the vertical spacing globally in the \paper
> block.

You can indeed accomplish this, with a little bit of rearranging. \paper blocks 
can go a few 
different places, one of which is a \bookpart  And as \bookparts are by default 
separated 
by a page break, and you are (apparently) wanting a page break between the two 
movements, this is a bit of two birds, one stone thing here.

Basically, put each movement into it's own \bookpart. You can then give each 
movement 
it's own paper block, while still having a global paper block if you want one. 
The bookparts 
will also take care of the page break for you, so that can be removed. You'll 
end up with a 
structure something like:

\version "2.24.1"

\paper { global \paper settings }

FirstMovement = { ... }

\bookpart {
  \paper { \paper setting specific to the 1st movement }
  \score {
\new Staff { \FirstMovement }
\layout {}
  }
}

SecondMovement = { ... }

\bookpart {
  \paper { \paper setting specific to the 2nd movement }
  \score {
\new Staff { \SecondMovement }
\layout {}
  }
}

\bookpart sections can have their own \paper block, even their own \header 
blocks. For a 
bit more see:
https://lilypond.org/doc/v2.24/Documentation/notation/multiple-scores-in-a-book[1]
-- 
Michael


[1] 
https://lilypond.org/doc/v2.24/Documentation/notation/multiple-scores-in-a-book


signature.asc
Description: This is a digitally signed message part.


Re: Spacing between staves

2024-04-25 Thread Pierre Perol-Schneider
Hi Peter,
Using \bookpart? E.g.:

%%
\version "2.24"

\paper {
  % ...
}

\header {
  title = "Two-movement Score"
  subtitle = " For A Single Melodic Instrument"
}

FirstMovement = { s1*32 }

\bookpart {
  \paper {
system-system-spacing.basic-distance = 10
  }
  \score {
 \new Staff { \FirstMovement }
 \layout { system-count = 10 }
  }
  \header {
piece = "First Movement"
  }
}
%\pageBreak

SecondMovement = { s1*32 }

\bookpart {
  \paper {
system-system-spacing.basic-distance = 15
  }
  \score {
 \new Staff { \SecondMovement }
 \layout {
   system-count = 10
 }
  }
  \header {
title = ""
subtitle = ""
piece = "Second Movement"
  }
}
%%

Cheers,
Pierre

Le jeu. 25 avr. 2024 à 15:45, Peter Mayes  a écrit :

> I may be missing something in the documentation here.
>
> I have a two-movement score for a single melodic instrument. Each
> movement fits conveniently onto a single page.
>
> I realise this is not a MWE, but I just wanted to specify the overall
> layout of my input
>
> \version "2.24.1"
>
> \paper { ... }
>
> FirstMovement = { ... }
>
> \score {
>\new Staff { \FirstMovement }
>\layout {}
> }
> \pageBreak
> SecondMovement = { ... }
>
> \score {
>\new Staff { \SecondMovement }
>\layout {}
> }
>
> What I want is for the second movement, on the second page, to have
> slightly increased vertical spacing between staves. (It has 32nd and
> even a few 64th notes, and just looks a little "bunched up" to my eyes.)
>
> I can only see ways to set the vertical spacing globally in the \paper
> block.
>
> What I am looking for is a way to say "Increase the vertical spacing
> between staves from this point onwards.
>
> Is that possible?
>
> Thanks in advance
>
> --
> Best wishes -- Peter
> --
> Peter Mayes
>
>
>


Re: lilypond-user Digest, Vol 257, Issue 85

2024-04-25 Thread Schlipf, John (schlipf)
On question:
On Wed 24 Apr 2024 at 19:13:47 (+0200), Johannes Roeßler wrote:
> Hey David,
>
> it works - but I am running into an issue with short passages.
> I would like to stretch the choir part to the right side,
> but when I bring in "ragged-right = ##f" then it breaks:
>
> I assume you have a solution for that issue?

This is simple, but perhaps it would work for you.  I've stretched (what I 
thought were) over-compressed lines by just putting in a manual line break 
before and after the line I want to stretch.  Lilypond then spreads the 
demarcated line out to fill the space.

From: lilypond-user-bounces+john.schlipf=uc@gnu.org 
 on behalf of 
lilypond-user-requ...@gnu.org 
Sent: Thursday, April 25, 2024 12:46 AM
To: lilypond-user@gnu.org 
Subject: lilypond-user Digest, Vol 257, Issue 85

External Email: Use Caution


Send lilypond-user mailing list submissions to
lilypond-user@gnu.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.gnu.org/mailman/listinfo/lilypond-user
or, via email, send a message with subject or body 'help' to
lilypond-user-requ...@gnu.org

You can reach the person managing the list at
lilypond-user-ow...@gnu.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of lilypond-user digest..."


Today's Topics:

   1. Re: Mixed ChoirGroup: Solo/Choir (David Wright)


--

Message: 1
Date: Wed, 24 Apr 2024 23:46:19 -0500
From: David Wright 
To: Johannes Roeßler 
Cc: lilypond-user@gnu.org
Subject: Re: Mixed ChoirGroup: Solo/Choir
Message-ID: 
Content-Type: text/plain; charset="utf-8"

On Wed 24 Apr 2024 at 19:13:47 (+0200), Johannes Roeßler wrote:
> Hey David,
>
> it works - but I am running into an issue with short passages.
> I would like to stretch the choir part to the right side,
> but when I bring in "ragged-right = ##f" then it breaks:
>
> I assume you have a solution for that issue?

Very simple, but not obvious from my cropped screenshot,
I right-justify the responses.

I don't stretch the versicles at all, and I set them with a breve
or semibreve (reciting note) and stemless crochets, avoiding any
indication of rhythm. (With the commonly used Ferial versicles,
only "O God make speed to save us" is entirely crochets, with no
reciting note.)

I don't like to stretch the responses music much at all, because
I find that makes it more difficult to read. So a short V pair
will have a wide margin to its left.

Right-justification is used by Shorter House in their Book of New
Responses, and by Church Music Society in their 1993 Watkins Shaw
edition of Preces and Responses. OTOH the older Atkins/Fellowes
edition of the latter had its V placed centrally.

I've attached a much-reduced illustration of one set (Smith/Stone).
On page 2, the choir sings everything after the 2nd versicle;
page 4 has the Lord's Prayer; and the final line of music is a
concatenation of the three Amens.

I've also attached my Plainlayout file, used here for the versicles.
I set the size externally because I use much larger sizes than here
with less familiar plainsong, like the Gospels of the Passion, and
the dreaded liturgical tracts.

  plainlayout = \layout {
\plainlayout
#(layout-set-staff-size 9)
  }

Cheers,
David.
-- next part --
A non-text attachment was scrubbed...
Name: smith-stone.png
Type: image/png
Size: 19722 bytes
Desc: not available
URL: 

-- next part --
\version "2.25.9" % 2016-05-04

%% Sets up \plainlayout, which is local, designed not to interfere
%% with the top-level layouts, which are cumulative.
%% Used for interspersing plainsong sections with normal music.

plainlayout = \layout {
  indent = 0
  ragged-right = ##t
  \context {
\Score
timing = ##f
\override SpacingSpanner.shortest-duration-space = #3.0
  }
  \context {
\Staff
\omit TimeSignature
\override BreathingSign.text = #(make-musicglyph-markup "scripts.tickmark")
  }
  \context {
\Voice
\omit Stem
\omit Flag
\override Slur.direction = #UP
  }
  \context {
\Lyrics
\override LyricHyphen.minimum-distance = #1.0
  }
}

--

Subject: Digest Footer

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


--

End of lilypond-user Digest, Vol 257, Issue 85
**


Spacing between staves

2024-04-25 Thread Peter Mayes

I may be missing something in the documentation here.

I have a two-movement score for a single melodic instrument. Each 
movement fits conveniently onto a single page.


I realise this is not a MWE, but I just wanted to specify the overall 
layout of my input


\version "2.24.1"

\paper { ... }

FirstMovement = { ... }

\score {
  \new Staff { \FirstMovement }
  \layout {}
}
\pageBreak
SecondMovement = { ... }

\score {
  \new Staff { \SecondMovement }
  \layout {}
}

What I want is for the second movement, on the second page, to have 
slightly increased vertical spacing between staves. (It has 32nd and 
even a few 64th notes, and just looks a little "bunched up" to my eyes.)


I can only see ways to set the vertical spacing globally in the \paper 
block.


What I am looking for is a way to say "Increase the vertical spacing 
between staves from this point onwards.


Is that possible?

Thanks in advance

--
Best wishes -- Peter
--
Peter Mayes




Re: Figured bass

2024-04-25 Thread Richard Shann
On Thu, 2024-04-25 at 01:15 +0300, Dimitri Sykias wrote:
> Hi Jacob
> Thanks for the reply.
> When I use for ex. (Version "2.24.1”)
> \figures {
>     \override FiguredBass.BassFigure.font-size = #2
>     <6- 4> <6> <6- 4-> <_-> <5-> <5+ _+> < 5- _-> <6 _+> <_+> <5- _-
> >}
> accidentals are placed at the left side of the number. 
> 
> > On 25 Apr 2024, at 1:10 AM, Jakob Pedersen 
> > wrote:
> > 
> >  
> >  Hi Dimitri
> >  
> >  Isn't that the standard as shown in the example?
> > http://lilypond.org/doc/v2.24/Documentation/notation/figured-bass

This example is the "standard" - not the default - if you click on it
you see it uses:

 \set figuredBassAlterationDirection = #RIGHT
  \set figuredBassPlusDirection = #RIGHT
  \override BassFigureAlignment.stacking-dir = #DOWN

and the first of these is what you need. 
HTH
Richard