Re: Help with some lyrics gymnastics

[Thomas Richter]

Hello again,

a few more ideas:

My solution uses the TextSpanner which works for two or more notes. But 
for a single note (syllable), a function like your lyricsWithOption is 
more suitable. The following draws the separating line in the proper length.


%%-

#(define-markup-command (stacked-lyric-single layout props one two)
  (string? string?)
  (let* ((lyric (interpret-markup layout props 
(make-stacked-lyric-markup one two)))

 (width (interval-length (ly:stencil-extent lyric X
    (ly:stencil-add
  lyric
  (make-line-stencil 0.1 0 0.8 width 0.8

%%-

It can be used in the Lyrics context, e.g.

\markup \stacked-lyric-single "you" "God the Father"


For another line thickness, change the first argument of 
make-line-stencil (0.1) and include the following for the TextSpanner in 
the startStackedLyric function with a 10 times larger value:


\once \override TextSpanner.thickness = #1.0


For a proper layout in case of a TextSpanner line break, it could be 
necessary to set the properties of left-broken and right-broken in 
bound-details.



All the best,

Thomas

--

Thomas Richter
Vienna / Austria
thomas-rich...@aon.at

Grandstaff multi-bar rest count shared between staves

[Martin Brown]

Where two-stave scores (eg. piano) have multiple bars rest in common
between the treble and bass parts, the number of bars rest should be placed
once, in between the two staves, not separately on each stave. How can I
achieve this in Lilypond? By default, it seems to treat each stave's rest
count separately, placing the number above the multi-bar rest symbol on
each stave.

Thanks,
Martin

Re: Help with some lyrics gymnastics

[Matthew Fong]

Hello Thomas,

That works splendidly. Thank you. The NullVoice is a new concept to me, and
seems necessary here.

I also found the same LSR example and was working through trying to
understand it.


Many thanks,
mattfong

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

[Hans Aikema]

On 15 Jan 2024, at 19:40, Knute Snortum  wrote:On Mon, Jan 15, 2024 at 7:47 AM David Kastrup  wrote:

Calling

git grep "override[^=]*#'[a-z]"

in the current Frescobaldi source tree delivers _way_ too many hits.  I
don't consider it sane that the current Frescobaldi will pump out
pre-2.18 syntax in droves in its templates.

And I suspect that it also splits overrides into multiple lines, making
it harder to recognize them.I've created an issue for Frescobaldi and I should be able to start work on it today.https://github.com/frescobaldi/frescobaldi/issues/172Knute, you've missed a digit while copying the link and without doubt intended to refer tohttps://github.com/frescobaldi/frescobaldi/issues/1728--Knute Snortum 

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

[Knute Snortum]

On Mon, Jan 15, 2024 at 7:47 AM David Kastrup  wrote:

>
> Calling
>
> git grep "override[^=]*#'[a-z]"
>
> in the current Frescobaldi source tree delivers _way_ too many hits.  I
> don't consider it sane that the current Frescobaldi will pump out
> pre-2.18 syntax in droves in its templates.
>
> And I suspect that it also splits overrides into multiple lines, making
> it harder to recognize them.
>

I've created an issue for Frescobaldi and I should be able to start work on
it today.

https://github.com/frescobaldi/frescobaldi/issues/172


--
Knute Snortum

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

[David Kastrup]

Knute Snortum  writes:

> On Mon, Jan 15, 2024 at 5:28 AM David Kastrup  wrote:
>
>> Bernhard Kleine  writes:
>>
>> > Dear David,
>> >
>> > the file was created this morning from frescobaldi with the
>> > Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
>> > Nothing was done be myself apart from wrinting notes and lyrics.
>>
>> If the "Partitur-Assistent" creates those overrides, it needs to get fixed.
>>
>
> It has been:
>
> https://github.com/frescobaldi/frescobaldi/commit/fb79df399056ddd8ce2fa2b48ac36fc37bdc0588

Well, it's a start.  See my note about

git grep "override[^=]*#'[a-z]"

I get

TODO:  * drag an object to e.g. create an \override #'extra-offset command
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:\override 
DynamicLineSpanner #'staff-padding = #2.0
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:  \override 
BreathingSign #'text = \markup { \musicglyph #"scripts.rvarcomma" }
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:  \override 
TrillSpanner #'direction = #DOWN
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:  \override 
BreathingSign #'text = \markup { \musicglyph #"scripts.caesura.curved" }
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:  \override 
BreathingSign #'text = \markup { \musicglyph #"scripts.caesura.straight" }
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:  \override 
BreathingSign #'text = \markup { \musicglyph #"scripts.tickmark" }
frescobaldi_app/fonts/templates/musicfont-realbook.ly:\override Score.Clef 
#'break-visibility = #'#(#f #f #f)
frescobaldi_app/fonts/templates/musicfont-realbook.ly:\override 
Score.KeySignature #'break-visibility = #'#(#f #f #f)
frescobaldi_app/fonts/templates/musicfont-realbook.ly:\override 
Score.SystemStartBar #'collapse-height = #1
frescobaldi_app/scorewiz/scoreproperties.py:
ly.dom.Line(r"\override Staff.TimeSignature #'style = #'()", node)
frescobaldi_app/symbols/arpeggio_defaults.ily:\override StaffSymbol 
#'transparent = ##t
frescobaldi_app/symbols/arpeggio_defaults.ily:\override StaffSymbol #'width 
= #4
frescobaldi_app/symbols/arpeggio_defaults.ily:\override NoteHead 
#'no-ledgers = ##t
frescobaldi_app/symbols/arpeggio_defaults.ily:\override NoteHead #'stencil 
= #empty-stencil
frescobaldi_app/symbols/arpeggio_defaults.ily:\override Stem #'stencil 
=#empty-stencil
frescobaldi_app/symbols/bar_defaults.ily:\override StaffSymbol #'width = #'4
frescobaldi_app/symbols/bar_defaults.ily:\override StaffSymbol #'thickness 
= #1.2
frescobaldi_app/symbols/bar_kievan.ly:\override StaffSymbol #'width = #1.44
frescobaldi_app/symbols/bar_repeat_angled_double.ly:\override StaffSymbol 
#'width = #5.5
frescobaldi_app/symbols/bar_repeat_angled_end.ly:\override StaffSymbol 
#'width = #5.5
frescobaldi_app/symbols/bar_repeat_angled_start.ly:\override StaffSymbol 
#'width = #5.5
frescobaldi_app/symbols/bar_segno.ly:\override StaffSymbol #'width = #7
frescobaldi_app/symbols/bar_tick.ly:\override StaffSymbol #'staff-space = 
#(/ 7 8)
frescobaldi_app/symbols/clef_defaults.ily:\override StaffSymbol #'width = #4
frescobaldi_app/symbols/clef_tab.ly:\override StaffSymbol #'width = #4
frescobaldi_app/symbols/clef_tab.ly:\override StaffSymbol #'staff-space = #1
frescobaldi_app/symbols/clef_tab.ly:\override Clef #'font-size = #-3.5
frescobaldi_app/symbols/glissando_defaults.ily:\override StaffSymbol 
#'transparent = ##t
frescobaldi_app/symbols/glissando_defaults.ily:\override StaffSymbol 
#'width = #4
frescobaldi_app/symbols/glissando_defaults.ily:\override NoteHead #'stencil 
= #empty-stencil
frescobaldi_app/symbols/glissando_defaults.ily:\override Stem #'stencil = 
#empty-stencil
frescobaldi_app/symbols/glissando_defaults.ily:\override Stem #'length = #0
frescobaldi_app/symbols/glissando_defaults.ily:\override Glissando 
#'bound-details = #
frescobaldi_app/symbols/glissando_defaults.ily:  \override Glissando 
#'style = $style
frescobaldi_app/symbols/glissando_dotted.ly:\override Glissando #'thickness 
= #1.5
frescobaldi_app/symbols/spanner_beam16.ly:  \override NoteHead 
#'extra-spacing-width = #'(0 . 1.3)
frescobaldi_app/symbols/spanner_defaults.ily:\override StaffSymbol #'width 
= #4.4
frescobaldi_app/symbols/spanner_defaults.ily:\override StaffSymbol 
#'transparent = ##t
frescobaldi_app/symbols/spanner_melisma.ly:  \override Stem #'length = #3
frescobaldi_app/symbols/spanner_melisma.ly:  \override VerticalAxisGroup 
#'nonstaff-relatedstaff-spacing =
frescobaldi_app/symbols/spanner_phrasingslur.ly:\override Stem #'length = #0
frescobaldi_app/symbols/spanner_phrasingslur.ly:\override Stem #'direction 
= #DOWN
frescobaldi_app/symbols/spanner_phrasingslur.ly:\override Stem 
#'transparent = ##t
frescobaldi_app/symbols/spanner_phrasingslur.ly:\override Tie 
#'minimum-length = #4.4

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

[David Kastrup]

Bernhard Kleine  writes:

> Am 15.01.2024 um 14:28 schrieb David Kastrup:
>> Bernhard Kleine  writes:
>>
>>> Dear David,
>>>
>>> the file was created this morning from frescobaldi with the
>>> Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
>>> Nothing was done be myself apart from wrinting notes and lyrics.
>> If the "Partitur-Assistent" creates those overrides, it needs to get fixed.
>
> It does create them. Any idea how to get is fixed in this particular case?

Calling

git grep "override[^=]*#'[a-z]"

in the current Frescobaldi source tree delivers _way_ too many hits.  I
don't consider it sane that the current Frescobaldi will pump out
pre-2.18 syntax in droves in its templates.

And I suspect that it also splits overrides into multiple lines, making
it harder to recognize them.

-- 
David Kastrup

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

[Knute Snortum]

On Mon, Jan 15, 2024 at 5:28 AM David Kastrup  wrote:

> Bernhard Kleine  writes:
>
> > Dear David,
> >
> > the file was created this morning from frescobaldi with the
> > Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
> > Nothing was done be myself apart from wrinting notes and lyrics.
>
> If the "Partitur-Assistent" creates those overrides, it needs to get fixed.
>

It has been:

https://github.com/frescobaldi/frescobaldi/commit/fb79df399056ddd8ce2fa2b48ac36fc37bdc0588


--
Knute Snortum

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

[Bernhard Kleine]

Am 15.01.2024 um 14:28 schrieb David Kastrup:

Bernhard Kleine  writes:


Dear David,

the file was created this morning from frescobaldi with the
Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
Nothing was done be myself apart from wrinting notes and lyrics.

If the "Partitur-Assistent" creates those overrides, it needs to get fixed.


It does create them. Any idea how to get is fixed in this particular case?

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

[David Kastrup]

Bernhard Kleine  writes:

> Dear David,
>
> the file was created this morning from frescobaldi with the
> Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
> Nothing was done be myself apart from wrinting notes and lyrics.

If the "Partitur-Assistent" creates those overrides, it needs to get fixed.

-- 
David Kastrup

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

[Bernhard Kleine]

Dear David,

the file was created this morning from frescobaldi with the
Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
Nothing was done be myself apart from wrinting notes and lyrics.

Am 15.01.2024 um 13:06 schrieb David Kastrup:

Bernhard Kleine  writes:


The following MWE gave a warning

C:/Users/bk/AppData/Local/Temp/frescobaldi-n7fp9iem/tmp_isr57mt/document.ly:52:25:
Warnung: deprecated: missing `.' in property path StaffSymbol.staff-space

I think maybe the frescobaldi is not aware of changes to this lilypond
version. What do I have change to make the score compile without this
warning?

Kind regards

Bernhard

\version "2.25.7"

Do _NOT_ update the version header by hand.  That is the job of
convert-ly when it also updates the syntax of your file to a newer
version.

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

[David Kastrup]

Bernhard Kleine  writes:

> The following MWE gave a warning
>
> C:/Users/bk/AppData/Local/Temp/frescobaldi-n7fp9iem/tmp_isr57mt/document.ly:52:25:
> Warnung: deprecated: missing `.' in property path StaffSymbol.staff-space
>
> I think maybe the frescobaldi is not aware of changes to this lilypond
> version. What do I have change to make the score compile without this
> warning?
>
> Kind regards
>
> Bernhard
>
> \version "2.25.7"

Do _NOT_ update the version header by hand.  That is the job of
convert-ly when it also updates the syntax of your file to a newer
version.

-- 
David Kastrup

Re: zero-duration s to hold marks

[David Kastrup]

Raphael Mankin  writes:

> As a more general response to this thread, I feel that the reference
> manual needs to have more cross references. I frequently get a bit
> lost trying to find a suitable construct, or discovering what a
> construct means.
>
> This thread has already shown that 1.2.2, 1.3.* and 1.5.* need to
> cross-reference each other.

Fortunately, this is Free Software.  If you feel there is a deficiency
in code or manual, you can contribute a patch to address it, and it is
likely to get accepted since volunteers contributing changes is actually
the only way in which LilyPond is getting improved.

-- 
David Kastrup

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

[Kevin Cole]

On Mon, Jan 15, 2024 at 6:26 AM Bernhard Kleine  wrote:

> The following MWE gave a warning
>
> C:/Users/bk/AppData/Local/Temp/frescobaldi-n7fp9iem/tmp_isr57mt/document.ly:52:25:
>  Warnung: deprecated: missing `.' in property path StaffSymbol.staff-space
>
> I think maybe the frescobaldi is not aware of changes to this lilypond 
> version. What do I have change to make the score compile without this warning?

I'm FAR from an expert, but the few times I've encountered errors like
that, the error message basically seems to tell me what I should do,
albeit not in the clearest way.

Does changing StaffSymbol #'staff-space to StaffSymbol.staff-space fix
the problem?

(Or am I misunderstanding your question?)

I note, as I often do, too many older versions of documentation --
apparently, from 2.13 to 2.24, with the documentation for 2.25 not
there yet. But this page for 2.24 suggests to me, the change that the
error message suggested...

https://lilypond.org/doc/v2.24/Documentation/snippets/spacing

Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

[Bernhard Kleine]

The following MWE gave a warning

C:/Users/bk/AppData/Local/Temp/frescobaldi-n7fp9iem/tmp_isr57mt/document.ly:52:25:
Warnung: deprecated: missing `.' in property path StaffSymbol.staff-space

I think maybe the frescobaldi is not aware of changes to this lilypond
version. What do I have change to make the score compile without this
warning?

Kind regards

Bernhard


\override StaffSymbol

#'staff-space = #(magstep -1)


\version "2.25.7"
\language  "deutsch"

global = {
  \key b \major
  \time 2/2
}

soprano = \relative c' {
  \global
    f1
}

alto = \relative c' {
  \global
    b1|
}

tenor = \relative c' {
  \global
    b1
}

bass = \relative c' {
  \global
  % Die Noten folgen hier.
  b1
}

sopranoVerse = \lyricmode {
  % Liedtext folgt hier.
  O mag -- num
}

altoVerse = \lyricmode {
  % Liedtext folgt hier.
  O mag -- num
}

tenorVerse = \lyricmode {
  % Liedtext folgt hier.
  O mag -- num
}

bassVerse = \lyricmode {
  % Liedtext folgt hier.
  O mag -- num
}

pianoReduction = \new PianoStaff \with {
  fontSize = #-1
\override StaffSymbol #'staff-space = #(magstep -1)
} <<
  \new Staff \with {
    \consists "Mark_engraver"
    \consists "Metronome_mark_engraver"
    \remove "Staff_performer"
  } {
    #(set-accidental-style 'piano)
    <<
  \soprano \\
  \alto
    >>
  }
  \new Staff \with {
    \remove "Staff_performer"
  } {
    \clef bass
    #(set-accidental-style 'piano)
    <<
  \tenor \\
  \bass
    >>
  }
>>

\score {
  <<
    \new ChoirStaff <<
  \new Staff \with {
    midiInstrument = "choir aahs"
  } { \soprano }
  \addlyrics { \sopranoVerse }
  \new Staff \with {
    midiInstrument = "choir aahs"
  } { \alto }
  \addlyrics { \altoVerse }
  \new Staff \with {
    midiInstrument = "choir aahs"
  } { \clef "treble_8" \tenor }
  \addlyrics { \tenorVerse }
  \new Staff \with {
    midiInstrument = "choir aahs"
  } { \clef bass \bass }
  \addlyrics { \bassVerse }
    >>
    \pianoReduction
  >>
  \layout { }
  \midi {
    \tempo 4=100
  }
}

Re: fony-size chord wiyh bass chord

[achar]

Hello Robin

Thank you so much Have a good day

JP

Le 14/01/2024 à 22:43, Robin Bannister a écrit :

achar wrote:


I would like to be able to change only the size of the bass in a bass
chord, for example G in the F/G chord.

And possibly be able to move it down and to the right of the 
agreement name.




Add the attached layout section and adjust the numbers.


Cheers,
Robin

Re: zero-duration s to hold marks

[Raphael Mankin]

As a more general response to this thread, I feel that the reference 
manual needs to have more cross references. I frequently get a bit lost 
trying to find a suitable construct, or discovering what a construct means.


This thread has already shown that 1.2.2, 1.3.* and 1.5.* need to 
cross-reference each other.


On 12/01/2024 17:48, Mats Bengtsson wrote:


On 2024-01-12 15:58, Knute Snortum wrote:


At least section 1.2.2 of the reference manual ought to be updated to
include <> in the discussion of invisible rests.


Can you share how you would want that section changed?  Or I could 
take a stab at it, but it may not be what you want.  Also, <> can be 
used for a lot of different things that aren't rests, so maybe that 
section of the Notation manual is not the best place for it.


Agreed! In fact it's not a rest but the empty chord construct should 
rather be seen as a placeholder without any duration, to which you can 
attach things that normally are attached to notes. The question is where 
to best describe it in the manuals. If you search the full manuals for 
<>, the construct is used in several examples without any explanation, 
but there are also a few places where "empty chord" is described in 
conjunction with special cases of how to use it (see the entries for 
"chord, empty" in the Lilypond Index). In A.15 there's even a reference 
to the learning manual, 
http://lilypond.org/doc/v2.25/Documentation/learning-big-page#structure-of-a-note-entry, which unfortunately doesn't seem to explain it either, even though the construct is used in several examples also in the learning manual.


Perhaps one suitable place could be Sect. 1.3.1 of the NR "1.3.1 
Expressive marks attached to notes", but it could also be worth 
mentioning in 1.7 "Editorial annotations", for example. Technically, 
Sect. 1.5.1 "Chorded Notes" is the natural place to describe it, but 
that's probably not the most obvious place to look when you don't know 
about the construct.


    /Mats




--
Why you get crap software: testing just raises problems and makes you 
look bad.