Re: Help with some lyrics gymnastics

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.

Grandstaff multi-bar rest count shared between staves

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

Re: Help with some lyrics gymnastics

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

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

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

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. >

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Re: zero-duration s to hold marks

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,

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

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

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

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

Re: fony-size chord wiyh bass chord

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

Re: zero-duration s to hold marks

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