Re: unwanted randomness while generating LilyPond output

[Michael Käppler]

Hello Werner,
thanks for your reply!

Just to make sure we're on the same page: You don't assume that there is
variability across
different runs of the same LilyPond build on the same machine? (Aka some
kind of "non-deterministic behaviour")
That would be my understanding of "randomness", which I find a bit of a
misleading term here.

FWIW, I can confirm that 100 subsequent runs of `lilypond --eps
input.ly` on my machine
produce exactly bit-identical eps files.

Carl and Werner, could you please:

* patch scm/framework-ps.scm with the attached patch (go to the
directory where framework-ps.scm resides
and run `patch < epsdebug.patch`)

(Does not have to be in the source tree, you can also do a backup of
framework-ps.scm and patch your working installation)

This patch will print the page stencils as pretty-printed scheme code to
stdout, while
normal messages go to stderr.

* run `lilypond --eps input.ly > epsdebug.log`

* send me the resulting log files

Michael

Am 17.02.2024 um 08:05 schrieb Werner LEMBERG:
> Hello Michael,
>
>
> sorry for the late reply.
>
> > I would like to help debugging the problem. Which exact invocation
> > do I have to use to replicate the EPS files you sent?
> This is due to using `extractpdfmark`, which makes the build add the
> options
>
> ```
> -dfont-ps-resdir=$(top-build-dir)/out-fonts -O TeX-GS
> ```
>
> However,...
>
> > If I do `lilypond --eps input.ly` I get a much bigger EPS file, that
> > seemingly has the fonts attached as binary data.
> ... it doesn't matter for the problem at hand: you also get the
> differences with normal `lilypond --eps` calls.
>
>
>      Werner

epsdebug.patch
Description: Text document

input.ly
Description: Text Data