Re: subscript in lyrics
On Fri 26 Apr 2024 at 20:33:26 (-0400), David Olson wrote:
> As it turns out, the "bc" text needs to be in lower case for \smallCaps to
> work.
>
> title = \markup { 539. Threshing Floor of Aruna. 1100 \smallCaps bc }
>
> it doesn't operate on text that's already capitalized.
There's a bumper collection of markups and fonts in the
Notation Reference, about two pages into §1.8.1. There,
the example:
\markup \smallCaps "LyricText"
shows why only lowercase letters are set in small capitals.
Cheers,
David.
Re: subscript in lyrics
As it turns out, the "bc" text needs to be in lower case for \smallCaps to work.
title = \markup { 539. Threshing Floor of Aruna. 1100 \smallCaps bc }
it doesn't operate on text that's already capitalized.
Thanks for the help!
I never would have solved this by myself.
David Olson
Los Angeles
- Original Message -
From: "William Rehwinkel"
To: "dadadharma @dslextreme.com" , "lilypond-user"
Sent: Friday, April 26, 2024 3:51:32 PM
Subject: Re: subscript in lyrics
Dear David,
You have to make the whole title a markup, in other words
title = \markup { 539. Threshing Floor of Aruna. 1100 \smallCaps BC }
-William
On 4/26/24 18:49, David Olson wrote:
> Thanks for drawing my attention to \markup
>
> Does \markup also work in the header?
>
> If I'm giving a historical date in the title and wish "BCE" to be smallCaps
>
> \header {
> title = "539. Threshing Floor of Aruna. 1100 \markup { \smallCaps { BCE }
> }."
> }
>
> Its seems that the \markup command is not being compiled.
> The PDF only prints the literal text of the command itself, including the
> curly brackets.
>
> Thanks again for your earlier help; it works beautifully.
>
> David Olson
> Los Angeles
>
>
>
> - Original Message -
> From: "mskala"
> To: "dadadharma @dslextreme.com"
> Cc: "lilypond-user"
> Sent: Saturday, April 20, 2024 5:59:03 PM
> Subject: Re: subscript in lyrics
>
> On Sat, 20 Apr 2024, David Olson wrote:
>
>> I'm a lyric poet writing songs about science.
>>
>> "CO2" is three syllables and often works better than "carbon dioxide".
>>
>> It's acceptable even if "2" doesn't appear as a subscript (one sees this
>> usage frequently), but subscript would be cool.
>>
>> A superscript option would be cool too.
>
> Easy enough to do using \markup and \sub, as in:
>
> <<
>\new Voice = melody { c'2 c'2 | c'4 bes4 f'2 | }
>\new Lyrics \lyricsto melody { \lyricmode {
> "ooh!" "ooh!" C O \markup { \sub { "2" } "!" }
>} }
>>>
>
> There are a number of variations possible: \super for superscript,
> \normal-size-sub for subscript without making the font smaller (which
> might be easier to read even if it's not standard chemistry usage), and so
> on. In general, you can just break into \markup and use any of the usual
> markup commands. See "Formatting text" in the Notation manual:
> https://lilypond.org/doc/v2.24/Documentation/notation/formatting-text
>
--
William Rehwinkel - Oberlin College and Conservatory '24
will...@williamrehwinkel.net
PGP key: https://ftp.williamrehwinkel.net/pubkey.txt
Re: slur cross staves
On Fri, Apr 26, 2024 at 2:57 PM Robert Garrigos wrote:
> This is the original music to copy:
>
>
>
> I have this:
>
> <<
> {
> \change Staff = "upper" \set tieWaitForNote = ##t
> \grace {cs'4_~ fs_~ cs'~ s4} 1^\fermata
> }
> \\
> {
> \set tieWaitForNote = ##t
> \grace { fs,,4~^\pp\sustainOn cs'~ as'^~ s4*4} as'>1_\fermata
> }
> >>
>
Thanks for including some example code, however, what you posted doesn't
produce the output you show. So I went back to my original code. I put a
slur in the upper grace notes, then used the \shape command to manipulate
the slur. I wasn't able to get the end of the slur to go into the lower
staff, but it's close. Maybe someone else can improve on it.
\version "2.24.3"
rightHand = \relative {
\set tieWaitForNote = ##t
\shape #'((-5 . -7.5) (-4 . 0) (0 . 0) (0 . 0)) Slur
\grace { c'4~^( g'~ c~) } 1
}
leftHand = \relative {
\clef bass
\set tieWaitForNote = ##t
\grace { f,4~ c'~ a'~ s4 * 3 } 1
}
\score {
\new PianoStaff <<
\new Staff = "upper" \rightHand
\new Staff = "lower" \leftHand
>>
}
--
Knute Snortum
Re: subscript in lyrics
Dear David,
You have to make the whole title a markup, in other words
title = \markup { 539. Threshing Floor of Aruna. 1100 \smallCaps BC }
-William
On 4/26/24 18:49, David Olson wrote:
Thanks for drawing my attention to \markup
Does \markup also work in the header?
If I'm giving a historical date in the title and wish "BCE" to be smallCaps
\header {
title = "539. Threshing Floor of Aruna. 1100 \markup { \smallCaps { BCE } }."
}
Its seems that the \markup command is not being compiled.
The PDF only prints the literal text of the command itself, including the curly
brackets.
Thanks again for your earlier help; it works beautifully.
David Olson
Los Angeles
- Original Message -
From: "mskala"
To: "dadadharma @dslextreme.com"
Cc: "lilypond-user"
Sent: Saturday, April 20, 2024 5:59:03 PM
Subject: Re: subscript in lyrics
On Sat, 20 Apr 2024, David Olson wrote:
I'm a lyric poet writing songs about science.
"CO2" is three syllables and often works better than "carbon dioxide".
It's acceptable even if "2" doesn't appear as a subscript (one sees this
usage frequently), but subscript would be cool.
A superscript option would be cool too.
Easy enough to do using \markup and \sub, as in:
<<
\new Voice = melody { c'2 c'2 | c'4 bes4 f'2 | }
\new Lyrics \lyricsto melody { \lyricmode {
"ooh!" "ooh!" C O \markup { \sub { "2" } "!" }
} }
There are a number of variations possible: \super for superscript,
\normal-size-sub for subscript without making the font smaller (which
might be easier to read even if it's not standard chemistry usage), and so
on. In general, you can just break into \markup and use any of the usual
markup commands. See "Formatting text" in the Notation manual:
https://lilypond.org/doc/v2.24/Documentation/notation/formatting-text
--
William Rehwinkel - Oberlin College and Conservatory '24
will...@williamrehwinkel.net
PGP key: https://ftp.williamrehwinkel.net/pubkey.txt
OpenPGP_signature.asc
Description: OpenPGP digital signature
Re: subscript in lyrics
Thanks for drawing my attention to \markup
Does \markup also work in the header?
If I'm giving a historical date in the title and wish "BCE" to be smallCaps
\header {
title = "539. Threshing Floor of Aruna. 1100 \markup { \smallCaps { BCE } }."
}
Its seems that the \markup command is not being compiled.
The PDF only prints the literal text of the command itself, including the curly
brackets.
Thanks again for your earlier help; it works beautifully.
David Olson
Los Angeles
- Original Message -
From: "mskala"
To: "dadadharma @dslextreme.com"
Cc: "lilypond-user"
Sent: Saturday, April 20, 2024 5:59:03 PM
Subject: Re: subscript in lyrics
On Sat, 20 Apr 2024, David Olson wrote:
> I'm a lyric poet writing songs about science.
>
> "CO2" is three syllables and often works better than "carbon dioxide".
>
> It's acceptable even if "2" doesn't appear as a subscript (one sees this
> usage frequently), but subscript would be cool.
>
> A superscript option would be cool too.
Easy enough to do using \markup and \sub, as in:
<<
\new Voice = melody { c'2 c'2 | c'4 bes4 f'2 | }
\new Lyrics \lyricsto melody { \lyricmode {
"ooh!" "ooh!" C O \markup { \sub { "2" } "!" }
} }
>>
There are a number of variations possible: \super for superscript,
\normal-size-sub for subscript without making the font smaller (which
might be easier to read even if it's not standard chemistry usage), and so
on. In general, you can just break into \markup and use any of the usual
markup commands. See "Formatting text" in the Notation manual:
https://lilypond.org/doc/v2.24/Documentation/notation/formatting-text
--
Matthew Skala
msk...@ansuz.sooke.bc.ca People before tribes.
https://ansuz.sooke.bc.ca/
Transparent box around notes
Hello LilyPonders,
How can I draw a box around a group of notes so that (see the attached
image)
1) it is filled with a transparent color
2) it occupies the minimum area that includes the notes + four (optional)
offsets (left, top, right, bottom) that can be set by the user?
3) ... it would be great if I can add a label to the top or bottom of the
box
Something like:
\coloredBox color offsLeft offsTop offsRight offsBottom "labelstring"
labeldirection { c' e' f' }
Many thanks for your help!
Paolo
slur cross staves
This is the original music to copy:
I have this:
<<
{
\change Staff = "upper" \set tieWaitForNote = ##t
\grace {cs'4_~ fs_~ cs'~ s4} 1^\fermata
}
\\
{
\set tieWaitForNote = ##t
\grace { fs,,4~^\pp\sustainOn cs'~ as'^~ s4*4} 1_\fermata
}
>>
Which makes me this:
But I'm still missing the slur from cue low f to high c. Any ideas how to do it?
Thanks.
Robert
Re: explicit arpeggio
Thanks, Nute. You are right, I should have said what I did. I actually tried
the link that Robin send:
https://lilypond.org/doc/v2.25/Documentation/snippets/rhythms_003a-using-ties-with-arpeggios
\set tieWaitForNote = ##t
\grace {fs,,4~^\pp\sustainOn cs'~ as'^~ s4*3} 1
> El 26 abr. 2024, a les 20:05, Knute Snortum va escriure:
>
> On Fri, Apr 26, 2024 at 7:07 AM Robert Garrigos > wrote:
>> How about moving the grace notes of the lower staff to the left? I’m trying
>> with GraceSpacing but cannot make it work just for the lower staff. It is
>> applied to the Score, not the Staff.
>
> It's nice to show what you have tried, so people have a starting point on
> which to proceed. Here's what I did; there may be other ways to do it:
>
> \version "2.24.3"
>
> staffUp = \change Staff = "upper"
> staffDown = \change Staff = "lower"
>
> rightHand = \relative {
> \set tieWaitForNote = ##t
> \grace { c'4~ g'~ c~ } 1
> }
>
> leftHand = \relative {
> \clef bass
> \set tieWaitForNote = ##t
> \grace { f,4~ c'~ a'~ \staffUp \hideNotes \shiftOff c g' c }
> \unHideNotes \staffDown 1
> }
>
> \score {
> \new PianoStaff <<
> \new Staff = "upper" \rightHand
> \new Staff = "lower" \leftHand
> >>
> }
>
>
> --
> Knute Snortum
>
>
Re: GraceSpacing on Staff
Thanks, Leo, this is indeed the easiest solution. > El 26 abr. 2024, a les 20:08, Knute Snortum va escriure: > > On Fri, Apr 26, 2024 at 10:02 AM Leo Correia de Verdier > mailto:leo.correia.de.verd...@gmail.com>> > wrote: >> s4*3 after the grace notes (within the grace group) in the lower staff. > > This is probably better than what I posted. > > > -- > Knute Snortum > >
Re: Note names are causing text marks to be duplicated
On Fri, 26 Apr 2024 at 16:46, Eric Benson wrote:
>
> I see. How hard would it be to write a Scheme function that would copy a
melody variable and remove the text marks, or in fact everything other than
the note values, which are all I want in the NoteNames variable? That would
be preferable to entering a separate sequence containing only the text
marks in my application.
Hello,
Do you want your text marks to be above the staff or above the upper
NoteNames context?
The following just keep the text marks above the staff.
\layout {
\context {
\Score
\remove Text_mark_engraver
}
\context {
\Staff
\consists Text_mark_engraver
}
}
Kind regards,
Xavier
Re: GraceSpacing on Staff
On Fri, Apr 26, 2024 at 10:02 AM Leo Correia de Verdier < leo.correia.de.verd...@gmail.com> wrote: > s4*3 after the grace notes (within the grace group) in the lower staff. > This is probably better than what I posted. -- Knute Snortum
Re: explicit arpeggio
On Fri, Apr 26, 2024 at 7:07 AM Robert Garrigos wrote:
> How about moving the grace notes of the lower staff to the left? I’m
> trying with GraceSpacing but cannot make it work just for the lower staff.
> It is applied to the Score, not the Staff.
>
It's nice to show what you have tried, so people have a starting point on
which to proceed. Here's what I did; there may be other ways to do it:
\version "2.24.3"
staffUp = \change Staff = "upper"
staffDown = \change Staff = "lower"
rightHand = \relative {
\set tieWaitForNote = ##t
\grace { c'4~ g'~ c~ } 1
}
leftHand = \relative {
\clef bass
\set tieWaitForNote = ##t
\grace { f,4~ c'~ a'~ \staffUp \hideNotes \shiftOff c g' c }
\unHideNotes \staffDown 1
}
\score {
\new PianoStaff <<
\new Staff = "upper" \rightHand
\new Staff = "lower" \leftHand
>>
}
--
Knute Snortum
Re: GraceSpacing on Staff
s4*3 after the grace notes (within the grace group) in the lower staff. > 26 apr. 2024 kl. 17:11 skrev Robert Garrigos : > > I have this music to replicate: > > > > I managed to get this: > > > > Still, I need to move the lower grace notes to the left. I can only apply > GraceSpacing on the whole Score, which doesn’t help. Can I apply it on just > one Staff? > Also, I need the slur across the Staves but cannot find how to do so. > > Thanks. > > Robert
Re: Note names are causing text marks to be duplicated
True, I was using \mark instead of \textMark. I just switched to \textMark,
which is definitely more correct, and I am also using \textEndMark, so I
can have one at the end of one system and the other at the beginning of the
next system in the same spot in the score. It does seem to me that if you
are using NoteNames in addition to regular notation you would not want to
include anything other than those note labels. Perhaps this could be added
as an option. I don't suppose NoteNames gets very much use, but I do have
some users who need the help!
I was unaware of tags in LilyPond until now. I might have some other uses
for them.
On Fri, Apr 26, 2024 at 8:15 AM David Wright
wrote:
> On Fri 26 Apr 2024 at 07:59:09 (-0700), Aaron Hill wrote:
> > On 2024-04-26 7:44 am, Eric Benson wrote:
> > > I see. How hard would it be to write a Scheme function that would
> > > copy a
> > > melody variable and remove the text marks, or in fact everything
> > > other than
> > > the note values, which are all I want in the NoteNames variable?
> > > That would
> > > be preferable to entering a separate sequence containing only the text
> > > marks in my application.
> >
> >
> > \tagging your \textMarks would let you apply them only where you intend:
> >
> >
> > \version "2.24.3"
> >
> > textMark = \tag textMark \textMark \etc
> > withTextMarks = \keepWithTag textMark \etc
> > withoutTextMarks = \removeWithTag textMark \etc
> >
> > melody = { b'4 4 \textMark "Hey!" 2 }
> >
> > << \withTextMarks \melody \\ \withoutTextMarks \melody >>
> >
>
> Ironically, replacing \textMark with \mark would achieve much the
> same thing in the MWE provided. But I suppose it all depends on
> the purpose of including the text mark in melody itself.
>
> Cheers,
> David.
>
Re: Note names are causing text marks to be duplicated
On Fri 26 Apr 2024 at 07:59:09 (-0700), Aaron Hill wrote:
> On 2024-04-26 7:44 am, Eric Benson wrote:
> > I see. How hard would it be to write a Scheme function that would
> > copy a
> > melody variable and remove the text marks, or in fact everything
> > other than
> > the note values, which are all I want in the NoteNames variable?
> > That would
> > be preferable to entering a separate sequence containing only the text
> > marks in my application.
>
>
> \tagging your \textMarks would let you apply them only where you intend:
>
>
> \version "2.24.3"
>
> textMark = \tag textMark \textMark \etc
> withTextMarks = \keepWithTag textMark \etc
> withoutTextMarks = \removeWithTag textMark \etc
>
> melody = { b'4 4 \textMark "Hey!" 2 }
>
> << \withTextMarks \melody \\ \withoutTextMarks \melody >>
>
Ironically, replacing \textMark with \mark would achieve much the
same thing in the MWE provided. But I suppose it all depends on
the purpose of including the text mark in melody itself.
Cheers,
David.
GraceSpacing on Staff
I have this music to replicate: I managed to get this: Still, I need to move the lower grace notes to the left. I can only apply GraceSpacing on the whole Score, which doesn’t help. Can I apply it on just one Staff? Also, I need the slur across the Staves but cannot find how to do so. Thanks. Robert
Re: Note names are causing text marks to be duplicated
On 2024-04-26 7:44 am, Eric Benson wrote:
I see. How hard would it be to write a Scheme function that would copy
a
melody variable and remove the text marks, or in fact everything other
than
the note values, which are all I want in the NoteNames variable? That
would
be preferable to entering a separate sequence containing only the text
marks in my application.
\tagging your \textMarks would let you apply them only where you intend:
\version "2.24.3"
textMark = \tag textMark \textMark \etc
withTextMarks = \keepWithTag textMark \etc
withoutTextMarks = \removeWithTag textMark \etc
melody = { b'4 4 \textMark "Hey!" 2 }
<< \withTextMarks \melody \\ \withoutTextMarks \melody >>
-- Aaron Hill
Re: Note names are causing text marks to be duplicated
I see. How hard would it be to write a Scheme function that would copy a melody variable and remove the text marks, or in fact everything other than the note values, which are all I want in the NoteNames variable? That would be preferable to entering a separate sequence containing only the text marks in my application. On Fri, Apr 26, 2024 at 6:48 AM David Wright wrote: > On Thu 25 Apr 2024 at 22:16:21 (-0700), Eric Benson wrote: > > Is this intentional or desired? > > AIUI this is one of the reasons \textMark was invented, so that > multiple text marks could be placed at the same point: > > "Note: Older LilyPond versions used the \mark command for text marks, > even though it is primarily intended for rehearsal marks (see > [Rehearsal marks], page 127). The \textMark and \textEndMark > commands are better suited for text marks with regard to their de- > fault settings as well as the ability to have several text marks at > the same moment. It is therefore recommended to use \textMark and > \textEndMark instead of \mark "Text" or \mark \markup Note that > if converting code that uses \mark for text marks, overrides using > RehearsalMark should be changed to TextMark." > > > If so, is there a way to prevent this from happening? > > Treat the text mark as you would lyrics or dynamics, defined in a > separate variable, which you interpret inside your << >> only once. > > Cheers, > David. >
Re: explicit arpeggio
How about moving the grace notes of the lower staff to the left? I’m trying with GraceSpacing but cannot make it work just for the lower staff. It is applied to the Score, not the Staff. > El 26 abr. 2024, a les 13:33, Robin Bannister va escriure: > > Robert Garrigos wrote: > >> I don’t find a way to do this kind of explicit arpeggio (piano): > > This is covered at > https://lilypond.org/doc/v2.25/Documentation/snippets/rhythms_003a-using-ties-with-arpeggios > > > > Cheers, > Robin
Re: Note names are causing text marks to be duplicated
On Thu 25 Apr 2024 at 22:16:21 (-0700), Eric Benson wrote: > Is this intentional or desired? AIUI this is one of the reasons \textMark was invented, so that multiple text marks could be placed at the same point: "Note: Older LilyPond versions used the \mark command for text marks, even though it is primarily intended for rehearsal marks (see [Rehearsal marks], page 127). The \textMark and \textEndMark commands are better suited for text marks with regard to their de- fault settings as well as the ability to have several text marks at the same moment. It is therefore recommended to use \textMark and \textEndMark instead of \mark "Text" or \mark \markup Note that if converting code that uses \mark for text marks, overrides using RehearsalMark should be changed to TextMark." > If so, is there a way to prevent this from happening? Treat the text mark as you would lyrics or dynamics, defined in a separate variable, which you interpret inside your << >> only once. Cheers, David.
Re: Lyrics and Barchecks
On Thu, Apr 25, 2024 at 8:06 PM David Wright wrote: > [...] > 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. > If you go this route, it can become tiresome to write the same warning several times. Someone on this list wrote me a little Scheme function that is like expect-warnings but takes a "number of times" argument: #(define ly:expect-warning-times (lambda args (for-each (lambda _ (apply ly:expect-warning (cdr args))) (iota (car args) You might use it like this: #(ly:expect-warning-times 4 "bar check failed") -- Knute Snortum
Re: explicit arpeggio
Oh thanks. I knew it was somewhere, but couldn't find it. Robert On 26 d’abr. de 2024, 13:33, at 13:33, Robin Bannister wrote: > Robert Garrigos wrote: > >> >> I don’t find a way to do this kind of explicit arpeggio (piano): >> >> > >This is covered at >https://lilypond.org/doc/v2.25/Documentation/snippets/rhythms_003a-using-ties-with-arpeggios > > > >Cheers, >Robin
Re: explicit arpeggio
Robert Garrigos wrote: I don’t find a way to do this kind of explicit arpeggio (piano): This is covered at https://lilypond.org/doc/v2.25/Documentation/snippets/rhythms_003a-using-ties-with-arpeggios Cheers, Robin
explicit arpeggio
Dear list, I don’t find a way to do this kind of explicit arpeggio (piano): Any clues would be much appreciated. Robert
Re: Mixed ChoirGroup: Solo/Choir
Thx David, will try with those ideas! Am 26. April 2024 05:06:52 schrieb 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.
