Hi Kieren, Thanks again for your detailed response! I agree — your results look exactly like what I’m aiming for, and it makes sense that version differences might explain the discrepancy.
Before I go ahead and install v2.25.24, I just wanted to ask a quick question about compatibility. Since 2.25.x is still considered unstable, do you know if it’s fully backward-compatible with scores written for 2.24.4? Specifically: • If I install 2.25.24 but continue to specify \version "2.24.4" at the top of most of my files, will those files still compile in a stable and predictable way? • Or could running them in 2.25 introduce subtle differences or bugs, even if they’re marked as 2.24? If it’s generally safe, I’m happy to install 2.25.24 and just stick to declaring 2.24.4 in files where I need stability. Thanks again for your insight! Best regards, Peter On Tue, May 6, 2025 at 11:46 AM Kieren MacMillan < kie...@kierenmacmillan.info> wrote: > Hi Peter, > > > I gave it a try — it definitely helps organize things more cleanly — but > I’m still not quite getting the effect I’m hoping for. I’ve attached a > screenshot of the current output. > > <image.png> > > What I’m aiming for is this: > > > > On each system, every measure should have exactly the same width, so > that the total available line width (after excluding things like clefs and > key/time signatures) is evenly divided by the number of measures on that > line. > > > > So for example, if a system contains two bars, the spacing of the music > should be stretched (or compressed) so that those two bars are exactly > equal in width and together span the line evenly. > > > > Any idea how to enforce that more strictly? > > Here’s the output on my end (v2.25.24, which may be the difference?): > > > As you can see, the measures are exactly equal in width, as desired. > > Maybe upgrade to 2.25.24 and try it with that? Or perhaps those with more > knowledge of Lilypond’s magical inner workings can tell you how to obtain > this output with your earlier version of Lilypond. > > Best regards, > Kieren. > __________________________________________________ > > My work day may look different than your work day. Please do not feel > obligated to read or respond to this email outside of your normal working > hours. > >
