Hi Kim,
Am 02.07.25 um 06:38 schrieb Kim Cascone:
Hello,
need some pointers for a score I wrote out by hand in 2017 for a small
ensemble performance
the score is a collection of fragments on a single 17 x 11 inch page
it is divided into three sections -- each section lasted around 6
minutes & was conducted
my score contains no key signature, no time signature, mostly stemless
note heads
each section contains a different number of measures
for example, in section one the euphonium part takes up one whole
measure containing three whole notes (to be improvised on)
under that bar in section one a guitar has five bars with various
fragments -- the end of which line up with the euphonium bar line above it
the organ under that has two bars again with varying amount of notes
comprising fragments to be improvised upon
Is cadenza mode the right way tocreate staves of varying measures that
all line up with a section end bar?
here's an ascii score fragment of what I'm trying to achieve - hope it
comes through
euph | . . . |
gtr |....|...|..|..|..|
organ | . . | . . |
^ end section #1
Do you have a working LilyPond file as a starting point? This would
simplify matters.
But in any case your description is quite clear. It is possible to do
something like this in LilyPond; some thoughts:
* The independent bar lines need polymetric notation
(https://lilypond.org/doc/v2.25/Documentation/notation/polymetric-notation)
* cadenza mode is suited for this kind of music since it makes it easy
to subdivide the music at arbitrary positions with bar lines.
* The limiting factor is LilyPond's habit (which cannot be
sidestepped) of having a strict notion of whether notes (across all
staves) happen simulteneously resp. which note is earlier than the
other. So we cannot get truly independent horizontal spacing.
* The lining up of the "end section" bar line can be accomplished by
"compressing" all the individual parts so that they take up the same
amount of musical time. (That precise amount is basically arbitrary.)
I hope I'll have time to cook up a proof of concept later.
Lukas
