[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: faster lilypond rendering

From: Cameron Horsburgh
Subject: Re: faster lilypond rendering
Date: Tue, 14 Feb 2006 09:09:34 +1100
User-agent: Debian Thunderbird 1.0.7 (X11/20051017)

Ramana Kumar wrote:
> what about caching the lilypond output in such a way that small
> changes to the ly code don't result in redoing all the parsing
> again... i mean say if someone only adds a bar to the end maybe some
> of the work wouldn't need to be redone?
> i understand lilypond does some work on the whole score which needs to
> be redone no matter how similar the new input file is... but there may
> be ways around this, or ways to speed it up.
> On 2/14/06, Erik Sandberg <address@hidden> wrote:
>>Citerar Ben Fisher <address@hidden>:
>>>Running lilypond seems to take a while on my machine. For a project I'm
>>>working on it'd be nice to have much faster time to output. Maybe some of
>>>this time is spent for lilypond to load all of its fonts and set up.
>>>Instead of running lilypond.exe several times, is there a way to start
>>>lilypond so that it stays active? For example, it would sit and capture from
>>>stdin, creating a pdf/or png of the output whenever an eof is fed in, but
>>>only quitting upon recieving a certain code? I'm willing to do c++ coding if
>>>Or, ideally, a standard windows dll of lilypond that would only need to get
>>>set up once.
>>>And if it were possible to do this, would the time saving be significant?
>>I think the only time that would be saved, is some of the setup which is done
>>before lily displays "Parsing...". There was a discussion on lilypond-devel
>>recently, and IIRC Han-Wen thought that it would be rather easy to implement a
>>lilypond daemon, but that the time savings would be rather small.
>>lilypond-user mailing list
> _______________________________________________
> lilypond-user mailing list
> address@hidden
Have you tried the technique in the docs at

I haven't tried it, but it seems to do something similar to what you're


reply via email to

[Prev in Thread] Current Thread [Next in Thread]