Op 19-05-2026 om 05:22 schreef David Wright:
On Sun 17 May 2026 at 22:11:23 (+0200), Lilypond-User wrote:
Hmmm - I owe you all my deepest apologies... Removing all the "set
associatedVoice" phrases, it turned out that in the last of those
items I did not refer to "alto", but to "alto "; so with an extra
trailing space.
Removed that, and hooray! it works as expected...
So for the moment I'll stay with that construct, since in this piece a
lot of work has already been done. But I've certainly learned
something!
FTR, I would prefer to write the second voice separately. Here I've
skipped the sections where voices are unison, but unless the division
was only for a few measures, I'd write the second part in full with
\voiceTwo (and first one voiceOne throughout).
In this piece, the divisions are indeed only for a few bars, only in the
alto part of a S-A-T-B piece of 82 bars.
I commented the VerticalAxisGroup.staff-affinity = #CENTER because
I wasn't sure what it would do here (obviously with more staves).
The piece is set to four staves - I only gave the problematic few bars
in my op, not to clutter the posting with to much less relevant code.
Using the NullVoice = aligner to set the words is extensible. Here it
aligns to just two voices. I use it to set four-part hymns: it moves
the alignment complexity from being in a line of notes (like Kieren's
spacer variable) into the lyrics themselves.
On Sat 16 May 2026 at 15:24:05 (-0400), Kieren MacMillan wrote:
There are ways to automate the generation of the notes in that spacer variable
— I just didn’t want to get into that here, so I manually wrote out the rhythms.
I don't think I have seen that demonstrated. Does it involve scheme?
(Answering this might best involve a change in the Subject line.)
Cheers,
David.
As said before, I learned a lot again here, thanks!
cheers, Jogchum
