Recently I updated my lilypond from 2.18 to 2.19.44. I am
using Frescobaldi for the GUI.
It used to take only a few seconds to compile a score, but
now it takes at least 28 seconds every time.
This is the case even if I don't create a midi.
Am I missing something, or is this the case for every
On Thu, Jul 7, 2016 at 2:25 PM, BGM [via Lilypond] <
ml-node+s1069038n192343...@n5.nabble.com> wrote:
> Recently I updated my lilypond from 2.18 to 2.19.44. I am using
> Frescobaldi for the GUI.
> It used to take only a few seconds to compile a score, but now it takes at
> least 28 seconds every
Okay, when I try exactly that, I still get 28.8 seconds for compile time.
Moving the \new statements does not change anything for me.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Long-Compile-time-with-version-2-19-44-tp192343p192346.html
Sent from the User mailing li
"Br. Gabriel-Marie | SSPX" writes:
> Recently I updated my lilypond from 2.18 to 2.19.44. I am using
> Frescobaldi for the GUI.
> It used to take only a few seconds to compile a score, but now it
> takes at least 28 seconds every time.
> This is the case even if I don't create a midi.
>
> Am I m
Well, it seems like it hangs on just starting lilypond. (and, as I've
mentioned, I didn't have this problem with version 2.18)
As soon as it gets past this line...
So, this line takes 99% of the time in the progressbar:
Starting lilypond-windows.exe 2.19.44 [whatever.ly]...
then all the rest pro
On Thu 07 Jul 2016 at 15:15:42 (-0700), BGM wrote:
> Well, it seems like it hangs on just starting lilypond. (and, as I've
> mentioned, I didn't have this problem with version 2.18)
>
> As soon as it gets past this line...
> So, this line takes 99% of the time in the progressbar:
> Starting lilyp
Hi Gabriel-Marie,
What platform are you using? Linux, Windows, Mac? Can you tell us
that, and the OS version? Which Frescobaldi are you running - platform
distribution, or a build from source?
Can you obtain timings from the command line to compare with Frescobaldi?
I have observed the Frescobal
Thanks for you interest, fellas.
I downgraded lilypond to version 2.19.36-1 and everything works as expected
- that is, it compiles any of my scores normally in just a second or two.
My problems were all with the latest lilypond 2.19.44-1 version.
I am using Frescibaldo 2.19 on Windows 7 Pro x64
On Thu 07 Jul 2016 at 19:37:54 (-0700), BGM wrote:
> Thanks for you interest, fellas.
>
> I downgraded lilypond to version 2.19.36-1 and everything works as expected
> - that is, it compiles any of my scores normally in just a second or two.
>
> My problems were all with the latest lilypond 2.19.
Hi David,
A long time UNIX user myself (pre 1970’s…), I follow what you are saying,
but you may want to explain to ordinary folks what clearing the caches does
and the command 'echo 3 > /proc/sys/vm/drop_caches ‘, especially since the
OP is on Windows and does not have such nice things available.
On Thu 07 Jul 2016 at 23:17:26 (-0700), Andrew Bernard wrote:
>
> A long time UNIX user myself (pre 1970’s…), I follow what you are saying,
> but you may want to explain to ordinary folks what clearing the caches does
> and the command 'echo 3 > /proc/sys/vm/drop_caches ‘, especially since the
> O
I tried this. I took a Windows 7 computer that never before had Lilypond and
I installed Lilypond 2.19.44 and Frescobaldi 2.19 and I had the same compile
problem taking a really long time to compile - and that using the "choir
hymn" template that comes with Frescobaldi's "New" menu.
So, to cont
Alright, so that was on a fresh system.
So, I completely removed Lilypond and Frescobaldi from my workstation -
preferences and all - and reinstalled Lilypond 2.19.44 and Frescobaldi 2.18
from scratch. But I have the same old problem.
So there is something in my computer that is messing up Lily
So, on my workstation, I've tried different versions of Lilypond until I
found the most recent version that works correctly.
That version is 2.19.42-1.
Therefore, I deduce that the problem I am having comes from the changes
between version 2.19.42 and 2.19.43.
I'm fetching the Windows binaries
Have you tried running different versions of lilypond on different systems, without using frescobaldi? I mean running lilypond directly from the commandline? MT Oorspronkelijk bericht Onderwerp: Re: Long Compile time with version 2.19.44Van: BGM Aan: lilypond-user@gnu.orgCc: I tried
On Fri, 8 Jul 2016 08:40:56 -0700 (MST)
BGM wrote:
> So there is something in my computer that is messing up Lilypond 2.19.44.
Looks like a job for strace to pinpoint the exact place where the process
stalls.
My intuition is that someone is making a network call that times out.
The delay is muc
Hi Johan,
Th OP is on Windows where there is no strace, I don’t think. However, I
suspect you are on the right track. I attempted to build Frescobaldi
2.19.latest-whatever a while ago on several Linux distros and gave up after
a few weeks of frustration due to the complex Qt code timing out in, su
Hi all,
I'm just writing to confirm that under macOS Sierra (10.12) Lilypond 2.19.48
is extremely slow.
I've downgraded to 2.19.47 and finally to 2.19.46.
2.19.47 was also terribly slow but 2.19.46 worked as usual.
As a sample, a simple file took 1.2 seconds to compile under 2.19.46 and
51.4 se
18 matches
Mail list logo