---- On Sun, 13 Apr 2025 03:13:41 +0800 Carl Sorensen
<[email protected]> wrote ---
> I'd suggest that you make a minimal example that uses variables, and see if
> the use of variables is the issue. I'd be surprised if that is the case.
> But IMO you should test your hypotheses.
OK.
\version "2.24.3"
\language "english"
minimalExampleVariableOne = \relative c' {
\time 3/4
c4 d e
\time 4/4
f g a b
}
minimalExampleVariableTwo = \relative c' {
\time 4/4
c4 d e
\time 3/4
f g a b
}
\score { <<
\new Staff \minimalExampleVariableOne
\new Staff \minimalExampleVariableTwo
>>
\layout {
\enablePolymeter
}
}
Transcript:
Starting lilypond 2.24.3 [test-poly-vars-main.ly]...
Processing `......snip....../test-poly-vars-main.ly'
Parsing...
Interpreting music...
......./test-poly-vars.ly:16:3: warning: mid-measure time signature without
\partial
\time 3/4
Also, the printed output does not reflect polymeter (attached) -- 3/4 in the
lower staff should occur one beat later.
(Really, this is for a section of ad-lib ordering of some chunks of notation,
where Gould recommends big [ brackets ] with barlines to denote the units to be
reordered. Since the units in different instruments are of different lengths, I
can probably just hide the barlines in different places... will have to see how
that lines up. Maybe set 1/4 time lol)
In any case, \enablePolymeter is a documented feature, and it appears to be
incompatible (at least in 2.24) with a common way of structuring ensemble
score/parts projects. I assume that's a bug, then.
hjh
