Lyricmode and fonts

[Mark Probert]

Hi.

I’m setting a song and there are two voices, like a call and response. I want 
to show these two different voices by making one italic and the other regular 
font. 

I there are simple way, say using some \override, where I can change the 
default on the fly and not have to do an, IMO, ugly \markup block with every 
syllable in a {\italic baz} group?

Thanks!

 .. mark.

---
\version "2.24.0"

mel = \relative c' { c4 d e f | a g a g | bes a g2 }

lyr = \lyricmode {
  foo bar foo bar

  %% the followin all italics
  baz bop baz bop
  baz bop baz
}

<<
  \new Voice = melody \mel
  \new Lyrics \lyricsto melody \lyr
>>

Re: Booth on Chemnitzer Linuxtage 2024

[Henning Hraban Ramm]

Am 06.12.23 um 02:33 schrieb David Kastrup:


Hi,

if you think you'd like to help providing a booth on the Chemnitzer
Linuxtage 2024 (happening on the weekend March 16/17), please checkout
the CfP at
.

Note that companies but not community projects are charged for booths.
We'd need 2–4 persons manning the booth and prepare suitable
presentation material, and help people with questions and showcase
working on music and performance material.

If we have suitable people and can figure out a suitable goal, we could
think about offering a workshop.  I am not sure we'd get a talk slot
since I just held a LilyPond talk this year.  I'd probably try to land a
Shotcut video editor talk (I've not yet talked about key frames in
Shotcut which allow to the "smooth scrolling" stuff in videos like
).  Particularly if I get that talk in, it
would be good to have at least two more people for the booth.

There is a yearly bus organized from the Ruhr area if that helps.  The
conference is the largest in Germany with a similar theme (typically
about 2500 to 3000 visitors).

Interest?  The conference is a friendly meeting place, and presenters
get a nice social event on Saturday with catering.



Hi David,

I’ll probably help at the DANTE booth and give some ConTeXt related 
talk, but I’d like to finally meet you in person. Maybe it makes sense 
to ask for neighbouring booths, since TeX and LilyPond folks tend to 
overlap anyway.


I would appreciate a lift from the Rhein/Main area, otherwise will try 
to come by train (with Deutsche Bahn you can only try). I’ll stay in the 
area for Leipzig book fair afterwards.


Hraban

Re: clefs, time signatures, and key signatures

[Werner LEMBERG]

>> please have a look at Merge Request 2188 and comment there on how
>> to proceed with the new distances between clefs and time
>> signatures, [...]
> 
> FWIW, I think the Petrucci clef distances are a big improvement and
> make incipits closer to what they usually look like in sources.

Yes, this was the starting point of the original bug report.

  https://gitlab.com/lilypond/lilypond/-/issues/3598

However, the distances are actually still too large IMHO;
additionally, the clef should directly start at the left edge, without
any leading space.  I eventually plan to improve that in a follow-up
commit by adjusting the spacing values within the `PetrucciStaff`
(and/or `MensuralStaff`) context.


Werner

Re: Hide chords

[Flaming Hakama by Elaine]

> -- Forwarded message --
> From: Jan 
> To: lilypond-user Mailinglist 
> Cc:
> Bcc:
> Date: Tue, 5 Dec 2023 22:51:44 +0100
> Subject: Hide chords
> What is the recommended method to “hide” chord names for a couple of
> measures? For example, in the snipped below I’d like to hide the chords for
> measures 5 to 8.
>
>
>
> Any help would be greatly appreciated.
> Jan



You can just enter either rests or spacers for the measures where you don't
want chords to appear.


Instead of what you have, which would be something like

mychords = \chordmode {
df1 | bf:7 | ef2:7 af:7 | f1:m7 |
df1 | bf:7 | ef2:7 af:7 | f1:m7 |
}

You could use the following

mychords = \chordmode {
df1 | bf:7 | ef2:7 af:7 | f1:m7 |
s1*4
}



If you have different parts that need all the chords
then you would define different variables, such as in
the following example, allChords and someChords.

For material that would appear in both, like this 4 bar chord sequence,
you can define that as a variable, too, then reference
that in the other variables.

chordSequence = \chordmode {
df1 | bf:7 | ef2:7 af:7 | f1:m7 |
}

allChords = \chordmode {
 \chordSequence
 \chordSequence
}

someChords = \chordmode {
\chordSequence
s1*4
}


HTH,

Elaine Alt
415 . 341 .4954   "*Confusion is
highly underrated*"
ela...@flaminghakama.com
Producer ~ Composer ~ Instrumentalist ~ Educator
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: clefs, time signatures, and key signatures

[Vaughan McAlley]

On Tue, 5 Dec 2023, 07:42 Werner LEMBERG,  wrote:

>
> Folks,
>
>
> please have a look at Merge Request 2188 and comment there on how to
> proceed with the new distances between clefs and time signatures,
> together with the new distances between clefs and key signatures.
>
>   https://gitlab.com/lilypond/lilypond/-/merge_requests/2188
>
> The question is whether the new distances should be based on the
> widest standard clef glyph (which is the alto clef, and which is done
> currently in the MR), or whether they should be based on the most
> common one, the treble clef.
>
>
> Werner
>

FWIW, I think the Petrucci clef distances are a big improvement and make
incipits closer to what they usually look like in sources.

Vaughan

Booth on Chemnitzer Linuxtage 2024

[David Kastrup]

Hi,

if you think you'd like to help providing a booth on the Chemnitzer
Linuxtage 2024 (happening on the weekend March 16/17), please checkout
the CfP at
.

Note that companies but not community projects are charged for booths.
We'd need 2–4 persons manning the booth and prepare suitable
presentation material, and help people with questions and showcase
working on music and performance material.

If we have suitable people and can figure out a suitable goal, we could
think about offering a workshop.  I am not sure we'd get a talk slot
since I just held a LilyPond talk this year.  I'd probably try to land a
Shotcut video editor talk (I've not yet talked about key frames in
Shotcut which allow to the "smooth scrolling" stuff in videos like
).  Particularly if I get that talk in, it
would be good to have at least two more people for the booth.

There is a yearly bus organized from the Ruhr area if that helps.  The
conference is the largest in Germany with a similar theme (typically
about 2500 to 3000 visitors).

Interest?  The conference is a friendly meeting place, and presenters
get a nice social event on Saturday with catering.

-- 
David Kastrup

Re: Hide chords

[Kieren MacMillan]

Hi Jan,

[p.s. Always cc the list when responding!]

> Thanks ! I’ve looked at that section of the documentation but couldn’t find a 
> solution.

Does

   \temporary \omit Score.ChordName

not work?

Cheers,
Kieren.
__

My work day may look different than your work day. Please do not feel obligated 
to read or respond to this email outside of your normal working hours.

Re: Hide chords

[mskala]

On Tue, 5 Dec 2023, Jan wrote:

> What is the recommended method to “hide” chord names for a couple of 
> measures? For example, in the snipped below I’d like to hide the chords for 
> measures 5 to 8.

Depending on exactly how you're generating the chord names in the first
place, it may be easy to use spacer rests, as in:

\new ChordNames { \chordmode { c1 | a1:m | s1 | g1 | } }

-- 
Matthew Skala
msk...@ansuz.sooke.bc.ca People before tribes.
https://ansuz.sooke.bc.ca/

Re: Hide chords

[Kieren MacMillan]

Hi Jan,

> What is the recommended method to “hide” chord names for a couple of measures?

Depends on exactly what you mean by “hide”… :)
Read: 
 
for more information.

Hope that helps!
Kieren.
__

My work day may look different than your work day. Please do not feel obligated 
to read or respond to this email outside of your normal working hours.

Hide chords

[Jan]

What is the recommended method to “hide” chord names for a couple of measures? 
For example, in the snipped below I’d like to hide the chords for measures 5 to 
8.



Any help would be greatly appreciated.
Jan

Re: Video generation from multiple pages

[Jean Abou Samra]

Is this the sort of thing you're looking for?

```
#(define (dump-system-info sys)
   (let* ((right (ly:spanner-bound sys RIGHT))
  (time (ly:grob-property right 'when 0)))
 (format #t "\nline break at ~f" (ly:moment-main time

\layout {
  \context {
\Score
\override System.after-line-breaking = #dump-system-info
  }
}
```

It should work on LilyPond 2.23.7 or later (current stable is 2.24). This:

> ```
> \layout {
>   \context {
> \Staff
> \override System.after-line-breaking = #printPage
>   }
> }
> ```
>
> should work.  And it doesn't.  I tried \Score context,

probably means you're running an older version.

Listening to page-break-event in an engraver is not what you're looking for — 
these are only emitted for explicit `\break` commands.

Another way would be

```
#(define (dump-col-info col)
   (when (eqv? LEFT (ly:item-break-dir col))
 (let ((time (ly:grob-property col 'when 0)))
   (format #t "\nline break at ~f" (ly:moment-main time)

\layout {
  \context {
\Score
\override NonMusicalPaperColumn.after-line-breaking = #dump-col-info
  }
}
```

which prints the time of all NonMusicalPaperColumn grobs that are just before a 
line break. Note the difference between a PaperColumn, which is on a vertical 
alignment of notes, and a NonMusicalPaperColumn, which is between two 
PaperColumns (or at one extreme end of the system). There is a diagram 
[here](https://extending-lilypond.gitlab.io/en/extending/backend.html#how-line-breaking-clones-grobs)
 about `ly:item-break-dir`.

Both of these methods will print at each line break, but since you have just 
one system per page, that's equivalent to printing page breaks in your case.


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

Re: clefs, time signatures, and key signatures

[Leo Correia de Verdier]

At least for the clef+time signature I prefer the tighter spacing of the first 
suggestion. Improvement requires things to change. 


> 5 dec. 2023 kl. 07:39 skrev Werner LEMBERG :
> 
> 
>> please have a look at Merge Request 2188 and comment there on how to
>> proceed with the new distances between clefs and time signatures,
>> together with the new distances between clefs and key signatures.
>> 
>>  https://gitlab.com/lilypond/lilypond/-/merge_requests/2188
>> 
>> The question is whether the new distances should be based on the
>> widest standard clef glyph (which is the alto clef, and which is
>> done currently in the MR), or whether they should be based on the
>> most common one, the treble clef.
> 
> For better comparison, I've updated/added the screenshots in the MR so
> that you can do a blink-comparison of the images.
> 
> 
>Werner
>