Thanks to you both for your replies and for taking the time to help me. Much appreciated!
The second method suggested by Hans worked for me. Out of curiosity, I also installed the latest unstable version (2.25.32) and tested both my old approach (including only the preamble) and Hans’s second method. In that version, however, both approaches resulted in full-page output with a single system per page.
So it seems I’ll need to look for an alternative solution once a new stable version is released. For now, though, the current method works well with the stable version 2.24.4, which is sufficient for my use case.
With kind regards,
LodewijkOp do 22 jan 2026 om 20:42 schreef Hans Aikema <[email protected]>:On 22 Jan 2026, at 19:59, [email protected] wrote:Lodewijk de Vries-van Hoeijen:
...I’ve been using LilyPond for many years, and until recently I always...
included
\include "lilypond-book-preamble.ly"
at the top of my files. When exporting to PNG via Frescobaldi, this
resulted in small images without extra white space around them, which was
exactly what I needed.
Same here, but I use eps instead.
Works fine with version 2.25.1, what version do you have ?Most likely Lodewijk is on latest Lilypond stable (2.24.4). IT administrators usually opt for a ’Stable release’ over ‘Unstable release’.I can replicate the symptoms on 2.24.4 (MacPorts build) and can resolve in in line with the comment history of issueadapt the commandline to include the required flag:-dseparate-page-formats=png(for page per system)or-dtall-page-formats=png(for a cropped image of all systems)On Frescobaldie these can be added in the Engrave (Custom)… dialogMethod 2 (an alternative way to set the options that doesn’t need command-line switches)after the include of the lilypond-book-preamble add#(ly:set-option 'separate-page-formats 'png)(for page per system)or#(ly:set-option ’tall-page-formats 'png)(for a cropped image of all systems)HTHkind regards,Hans Aikema
Thanks to you both for your replies and for taking the time to help me. Much appreciated!
The second method suggested by Hans worked for me. Out of curiosity, I also installed the latest unstable version (2.25.32) and tested both my old approach (including only the preamble) and Hans’s second method. In that version, however, both approaches resulted in full-page output with a single system per page.
So it seems I’ll need to look for an alternative solution once a new stable version is released. For now, though, the current method works well with the stable version 2.24.4, which is sufficient for my use case.
With kind regards,
LodewijkOp do 22 jan 2026 om 20:42 schreef Hans Aikema <[email protected]>:On 22 Jan 2026, at 19:59, [email protected] wrote:Lodewijk de Vries-van Hoeijen:
...I’ve been using LilyPond for many years, and until recently I always...
included
\include "lilypond-book-preamble.ly"
at the top of my files. When exporting to PNG via Frescobaldi, this
resulted in small images without extra white space around them, which was
exactly what I needed.
Same here, but I use eps instead.
Works fine with version 2.25.1, what version do you have ?Most likely Lodewijk is on latest Lilypond stable (2.24.4). IT administrators usually opt for a ’Stable release’ over ‘Unstable release’.I can replicate the symptoms on 2.24.4 (MacPorts build) and can resolve in in line with the comment history of issueadapt the commandline to include the required flag:-dseparate-page-formats=png(for page per system)or-dtall-page-formats=png(for a cropped image of all systems)On Frescobaldie these can be added in the Engrave (Custom)… dialogMethod 2 (an alternative way to set the options that doesn’t need command-line switches)after the include of the lilypond-book-preamble add#(ly:set-option 'separate-page-formats 'png)(for page per system)or#(ly:set-option ’tall-page-formats 'png)(for a cropped image of all systems)HTHkind regards,Hans Aikema
Thanks to you both for your replies and for taking the time to help me. Much appreciated!
The second method suggested by Hans worked for me. Out of curiosity, I also installed the latest unstable version (2.25.32) and tested both my old approach (including only the preamble) and Hans’s second method. In that version, however, both approaches resulted in full-page output with a single system per page.
So it seems I’ll need to look for an alternative solution once a new stable version is released. For now, though, the current method works well with the stable version 2.24.4, which is sufficient for my use case.
With kind regards,
LodewijkOp do 22 jan 2026 om 20:42 schreef Hans Aikema <[email protected]>:On 22 Jan 2026, at 19:59, [email protected] wrote:Lodewijk de Vries-van Hoeijen:
...I’ve been using LilyPond for many years, and until recently I always...
included
\include "lilypond-book-preamble.ly"
at the top of my files. When exporting to PNG via Frescobaldi, this
resulted in small images without extra white space around them, which was
exactly what I needed.
Same here, but I use eps instead.
Works fine with version 2.25.1, what version do you have ?Most likely Lodewijk is on latest Lilypond stable (2.24.4). IT administrators usually opt for a ’Stable release’ over ‘Unstable release’.I can replicate the symptoms on 2.24.4 (MacPorts build) and can resolve in in line with the comment history of issueadapt the commandline to include the required flag:-dseparate-page-formats=png(for page per system)or-dtall-page-formats=png(for a cropped image of all systems)On Frescobaldie these can be added in the Engrave (Custom)… dialogMethod 2 (an alternative way to set the options that doesn’t need command-line switches)after the include of the lilypond-book-preamble add#(ly:set-option 'separate-page-formats 'png)(for page per system)or#(ly:set-option ’tall-page-formats 'png)(for a cropped image of all systems)HTHkind regards,Hans Aikema
