PATCHES - Countdown to February 14
Here is the current countdown report. The next countdown will begin on 2024-02-14 A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: No patches in Push at this time. Countdown: !2252 output-lib.scm: new measure divisions for median chord grid style. - Eric Würbel https://gitlab.com/lilypond/lilypond/-/merge_requests/2252 Review: !2254 Build fixes - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2254 New: No patches in New at this time. Waiting: No patches in Waiting at this time. Cheers, Colin
Re: RFC and help at MR 2256
Am Mo., 12. Feb. 2024 um 12:37 Uhr schrieb Jean Abou Samra : > > > It prints > > backtrace: > 0: AgogicLineSpanner.Y-offset (# ly:side-position-interface::y-aligned-side (_ #:optional _)>) > 1: AgogicLineSpanner.vertical-skylines (# ly:grob::vertical-skylines-from-element-stencils (_)>) > 2: VerticalAxisGroup.vertical-skylines (# ly:hara-kiri-group-spanner::calc-skylines (_)>) > > > Might be the same as https://gitlab.com/lilypond/lilypond/-/issues/3409 ? Actually, I feel not qualified to judge here. > Maybe I have an idea (about 'side-support-elements). > I'll try and report back. Filling 'side-support-elements with NoteHeads and Stems made things even worse. Currently I see only two alternatives: - Abandon it. Which would be a pity. I first worked on #3176 3 years ago and never got so far. But I'm completely stuck with no perspective left. - Polish the patch and add a warning in NR. Basically: only works in Score. Opinions? Thanks, Harm
Re: unwanted randomness while generating LilyPond output
Hi Werner, I would like to help debugging the problem. Which exact invocation do I have to use to replicate the EPS files you sent? If I do `lilypond --eps input.ly` I get a much bigger EPS file, that seemingly has the fonts attached as binary data. Michael Am 09.02.2024 um 09:11 schrieb Werner LEMBERG: Carl sent me his complete build (thanks!) for further investigation of differences, and this unveiled an unpleasant surprise: We have randomness in the construction of LilyPond EPS files. I'm attaching an EPS output of both Carl's and my own build, together with the corresponding source file; as can be seen, the EPS files differ (I've checked that they display exactly the same). Any idea how to fix this? The randomness itself isn't bad, but it makes it much harder to find problems, and it might prevent reproducible documentation builds. I suppose that somewhere in the SCM code we need to sort a list or something like that while generating output... Werner
Re: RFC and help at MR 2256
> It prints > > backtrace: > 0: AgogicLineSpanner.Y-offset (# ly:side-position-interface::y-aligned-side (_ #:optional _)>) > 1: AgogicLineSpanner.vertical-skylines (# ly:grob::vertical-skylines-from-element-stencils (_)>) > 2: VerticalAxisGroup.vertical-skylines (# ly:hara-kiri-group-spanner::calc-skylines (_)>) Might be the same as https://gitlab.com/lilypond/lilypond/-/issues/3409 ?
Re: RFC and help at MR 2256
Am So., 11. Feb. 2024 um 13:51 Uhr schrieb Jean Abou Samra : > > > Alas, as soon as the relevant engravers are moved to another context, > > which is a common use case, I get an error: > > > > programming error: cyclic dependency: calculation-in-progress > > encountered for AgogicLineSpanner.vertical-skylines > > > > and the graphical output is wrong. > > Again, this does not happen at score-level. > > Example-code to trigger it at #2256 > > > > I've no clue how to proceed. Every hint is very welcome. > > I don't really have the time to investigate, but have you tried > > #(ly:set-option 'debug-property-callbacks) > > ? It should print a stack of the callbacks showing the cyclic dependency. > It prints backtrace: 0: AgogicLineSpanner.Y-offset (#) 1: AgogicLineSpanner.vertical-skylines (#) 2: VerticalAxisGroup.vertical-skylines (#) Not sure what exactly that means and how to solve the problem. Maybe I have an idea (about 'side-support-elements). I'll try and report back. Thanks, Harm
