Re: Output PDF to stdout

Hello Vlad, You will not avoid intermediate files in any case, as Lilypond with gs output will generate ps code, which is then turned into a pdf. If you want to pipe PDFs for convenience you might create a wrapper say plilypond in the search path doing something like this: #!/bin/bash t=$(mkt

Re: Output PDF to stdout

On 13 Jan 2024, at 02:05, Curt McDowell wrote:Have you actually tried this? LilyPond appends ".pdf" to the output filename (and ".midi"). If you try to make the fifo ending in ".pdf", you find lilypond removes the fifo before writing a new file. For the same reasons, the output file cannot be /de

Re: Output PDF to stdout

Have you actually tried this? LilyPond appends ".pdf" to the output filename (and ".midi"). If you try to make the fifo ending in ".pdf", you find lilypond removes the fifo before writing a new file. For the same reasons, the output file cannot be /dev/stdout. Maybe you could write something ex

Re: Output PDF to stdout

On 05/01/2024 03:46, David Wright wrote: On Thu 04 Jan 2024 at 23:34:28 (+0100), Volodymyr Prokopyuk wrote: I know that lilypond can receive a source.ly file from the stdin by using lilypond -. Is it possible for lilypond to output PDF to the stdout? My motivation behind using lilypond in a

Re: Output PDF to stdout

Thank you very much for your thoughts! I expected that the PDF output to stdout would be difficult to implement due to multiple Lilypond backends, and, probably, is not a real bottleneck in PDF generation. It is nice to know that intermediary files are already handled by a FS cache, and can be ext

Re: Output PDF to stdout

On Thu 04 Jan 2024 at 23:34:28 (+0100), Volodymyr Prokopyuk wrote: > > I know that lilypond can receive a source.ly file from the stdin by > using lilypond > -. Is it possible for lilypond to output PDF to the stdout? > > My motivation behind using lilypond in a pipeline is to speed up PDF > gene

Re: Output PDF to stdout

On Fri, 5 Jan 2024, Dr. Arne Babenhauserheide wrote: > > intermediate "files" will be written to and read from the buffer cache at > > RAM speed and only later go to the disk in the background. > > That depends on the file system and its synchronization model. I once > sped up a script to control

Re: Output PDF to stdout

msk...@ansuz.sooke.bc.ca writes: > On Thu, 4 Jan 2024, Volodymyr Prokopyuk wrote: > >> My motivation behind using lilypond in a pipeline is to speed up PDF >> generation by avoiding storing intermediary files on disk. The pipeline I'd > > Is that issue real? In Linux and most other operating sys

Re: Output PDF to stdout

This doesn't exist, sorry. It wouldn't be *that* straightforward to implement, because there are multiple code paths for output (GhostScript via API, GhostScript via subprocess, SVG backend and Cairo). I'm not even sure that direct PDF output in GhostScript's PS → PDF conversion is not going throu

Re: Output PDF to stdout

On Thu, 4 Jan 2024, Volodymyr Prokopyuk wrote: > My motivation behind using lilypond in a pipeline is to speed up PDF > generation by avoiding storing intermediary files on disk. The pipeline I'd Is that issue real? In Linux and most other operating systems, intermediate "files" will be written

Re: output PDF

Welcome to LilyPond! Peter Jongh Visscher wrote > I started using Lilypond and the in the PDF output the first line(staff) > jumps a little bit forward(see Example) > > I can not find a command to set all the staff starting at the same point. For this, use "indent = #0" in the \layout block as

Re: output PDF

Hi Peter, > I started using Lilypond Welcome to the ‘Pond!! =) > I can not find a command to set all the staff starting at the same point. \paper { indent = 0\in } See for more information on how

RE: output PDF

Peter: Use: \layout { indent = #0 } Mark From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Peter Jongh Visscher Sent: Monday, January 12, 2015 7:55 AM To: lilypond-user@gnu.org Subject: output PDF I sta

Re: output PDF

At 16:54 12/01/2015 +0100, Peter Jongh Visscher wrote: I started using Lilypond and the in the PDF output the first line (staff) jumps a little bit forward (see Example) I can not find a command to set all the staff starting at the same point. Try: \layout { indent = #0 } I trust this helps.

Re: Output PDF has different chord font than expected

r Scheuer To: mayornancy Cc: "lilypond-user@gnu.org" Sent: Wednesday, February 27, 2013 6:43 PM Subject: Re: Output PDF has different chord font than expected On 27 February 2013 20:29, mayornancy wrote: > Hello, > > I am using lilypond (2.16.2) on Windows7 SP1 in "portable

Re: Output PDF has different chord font than expected

On 27 February 2013 20:29, mayornancy wrote: > Hello, > > I am using lilypond (2.16.2) on Windows7 SP1 in "portable" mode (I simply > extracted the installer to a folder). > > After compiling the following Chord example found at: > > http://lilypond.org/doc/v2.12/input/lsr/lilypond-snippets/Chords

Re: Output PDF has different chord font than expected

From: Federico Bruni To: lilypond-user@gnu.org Sent: Wednesday, February 27, 2013 4:27 PM Subject: Re: Output PDF has different chord font than expected Il 27/02/2013 20:29, mayornancy ha scritto: > After compiling the following Chord example found at: > > http://lilypon

Re: Output PDF has different chord font than expected

Il 27/02/2013 20:29, mayornancy ha scritto: After compiling the following Chord example found at: http://lilypond.org/doc/v2.12/input/lsr/lilypond-snippets/Chords#Single-staff-template-with-notes-and-chords my result PDF chord symbols are using a very different font than the example output show