Re: Fwd: Compile crashing... help!

[Brent Annable]

FWIW, I just tried this out on my decrepit Windows 7 machine (64-bit, 8GB,
i7 core). After about 8 minutes of whizzing and whirring at 12% CPU
capacity and utilising just under 5 GB of RAM, it returned the same error.

Brent.


On Thu, 10 May 2018 at 1:14 pm, Brent Annable 
wrote:

> Being a layman, most of this is all going over my head. But I gather that
> compiling this particular project will not be possible for the time being
> on my current machine, so I’ll either try to get my decrepit laptop up and
> running, or ask a friend to help out :-)
>
> Thanks for the replies,
>
> Brent.
> On Thu, 10 May 2018 at 6:55 am, Michael Gerdau  wrote:
>
>> > I have no idea what it would entail to also provide 64bit Windows
>> > binaries.
>>
>> Last time I looked (about 1.5 years ago) the problem was a missing
>> mingw-w64 package that exists for mingw (the 32bit version) for which I
>> think it is not actually required for the lilypond build, only for GUB
>> in general.
>>
>> I'm not very knowledgeable w/r to GUB. So here is a question for those
>> with better knowledge:
>> Is it possible to reduce the required packages for GUB for particular
>> software (as in lilypond)?
>>
>> If that's the case I'd expect it to be fairly straight forward to
>> replace the mingw stuff by mingw-w64 since the later is (or was)
>> supposed to be a dropin replacement for the former.
>>
>> Kind regards,
>> Michael
>> --
>>  Michael Gerdau   email: m...@qata.de
>>  GPG-keys available on request or at public keyserver
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[Brent Annable]

Being a layman, most of this is all going over my head. But I gather that
compiling this particular project will not be possible for the time being
on my current machine, so I’ll either try to get my decrepit laptop up and
running, or ask a friend to help out :-)

Thanks for the replies,

Brent.
On Thu, 10 May 2018 at 6:55 am, Michael Gerdau  wrote:

> > I have no idea what it would entail to also provide 64bit Windows
> > binaries.
>
> Last time I looked (about 1.5 years ago) the problem was a missing
> mingw-w64 package that exists for mingw (the 32bit version) for which I
> think it is not actually required for the lilypond build, only for GUB
> in general.
>
> I'm not very knowledgeable w/r to GUB. So here is a question for those
> with better knowledge:
> Is it possible to reduce the required packages for GUB for particular
> software (as in lilypond)?
>
> If that's the case I'd expect it to be fairly straight forward to
> replace the mingw stuff by mingw-w64 since the later is (or was)
> supposed to be a dropin replacement for the former.
>
> Kind regards,
> Michael
> --
>  Michael Gerdau   email: m...@qata.de
>  GPG-keys available on request or at public keyserver
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[Michael Gerdau]

> I have no idea what it would entail to also provide 64bit Windows
> binaries.

Last time I looked (about 1.5 years ago) the problem was a missing
mingw-w64 package that exists for mingw (the 32bit version) for which I
think it is not actually required for the lilypond build, only for GUB
in general.

I'm not very knowledgeable w/r to GUB. So here is a question for those
with better knowledge:
Is it possible to reduce the required packages for GUB for particular
software (as in lilypond)?

If that's the case I'd expect it to be fairly straight forward to
replace the mingw stuff by mingw-w64 since the later is (or was)
supposed to be a dropin replacement for the former.

Kind regards,
Michael
-- 
 Michael Gerdau   email: m...@qata.de
 GPG-keys available on request or at public keyserver



signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[David Kastrup]

Samuel Speer  writes:

> On Wed, May 9, 2018 at 10:44 AM David Kastrup  wrote:
>
>> 1.82G is a bit of a strange number for a 64bit binary.  Are you using a
>> 64bit Windows and definitely a 64bit LilyPond (!) executable?
>>
>
> I checked my executable and it looks to be 32-bit. However, I couldn't find
> a 64-bit version on lilypond.org or at
> http://lilypond.org/downloads/binaries/
>
> Perhaps 64-bit releases for Windows aren't currently being built? Or more
> likely, I just don't know where to find them.

Oh.  The way it looks, we indeed only provide 32bit executables for
Windows (at least there is only one Mingw installer).  So it would
appear that you are indeed running out of memory.  Now make no mistake:
2GB for a 100-page document are pretty silly but LilyPond's grob storage
requirements are indeed excessive currently.  No work toning them down
has been done so far, so you'll not likely fare better with current
master.

I have no idea what it would entail to also provide 64bit Windows
binaries.

Would it be an option to try running a 64bit Linux executable under a
VM?  I'll readily agree that this an utter nuisance and not a viable
state at the current point of time but I cannot think of a better quick
fix right now.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[Werner LEMBERG]

>> What about setting up GUB (with LilyPond) on
>> https://hydra.nixos.org/?  Other GNU projects like Emacs are also
>> hosted there for daily builds, so it should be easy to get lilypond
>> registered there...
>>
>>   https://nixos.org/hydra/
> 
> Are you going to do it?

Basically, I'm interested.  It's time for me to learn how to set up a
CI system.  However, I have zero experience with GUB since I always
compile directly from the git repository for my GNU/Linux box...

Alas, I can't make any promises when I will find time for such a job.
As you know, May and June are the busiest months for lecturers in a
university...

> Like with any project driven by volunteers, LilyPond does not really
> suffer from a shortage of suggestions about what somebody else
> should really be doing.

Hold your horses!  Hydra has not been suggested yet as a CI system for
LilyPond, so this is a *new* suggestion, and I dared to mention just
for the sake of mentioning.  As an alternative, gitlab's CI support
can be used (after setting up a lilypond mirror).


Werner

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[Samuel Speer]

On Wed, May 9, 2018 at 10:44 AM David Kastrup  wrote:

> 1.82G is a bit of a strange number for a 64bit binary.  Are you using a
> 64bit Windows and definitely a 64bit LilyPond (!) executable?
>

I checked my executable and it looks to be 32-bit. However, I couldn't find
a 64-bit version on lilypond.org or at
http://lilypond.org/downloads/binaries/

Perhaps 64-bit releases for Windows aren't currently being built? Or more
likely, I just don't know where to find them.

Sam
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Compile crashing... help!

[Stanton Sanderson]

Not much help, but the source seems o.k.

MacBook Air (2013), 4GB Ram, OS 10.13.4- for what it’s worth, compiled the file
successfully and output a pdf of 104 pages.

Stan


> On May 9, 2018, at 11:17 AM, tyronicus  wrote:
> 
> Phil Holmes wrote
>> My guess is that there's a memory allocation problem that only shows up on
>> large projects on Windows.
> 
> That's my suspicion, too. I tried it on a Win10 i7-8xxx with 8G ram and saw
> it cut out around 1.85G memory every time. When I remove two bookparts, it
> only uses 1.82G of memory or so and manages to complete. When I set the
> process to high or realtime priority, which should allow more memory to be
> allocated, it still fails.
> 
> 
> 
> --
> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[Timothy Lanfear]

On 09/05/18 15:42, Karlin High wrote:

On 5/9/2018 8:16 AM, Ben wrote:
I also ran into your issue by compiling "SG_complete_DE.ly" on my 
Windows 10 machine. 32GB RAM. Newest i7 build.


Curiouser and curiouser... It compiled successfully on my Windows 7 
Pro x64 SP1, Intel Core i5-3450, 24 GB RAM, LilyPond 2.19.80


I also successfully compiled this score with Windows 7 Enterprise, Intel 
Core i7-4600, 8 GB RAM, LilyPond 2.19.81.


This example, reported on the bugs list as crashing on Windows, also 
built successfully.


\version "2.19.80"
\repeat unfold 36 {
  << { e'8 f' } \\ { c'4 } >> d'4
  << { g'4. f'8 } \\ { e'16 d' e'4 d'8 } >>
}



--
Timothy Lanfear, Bristol, UK.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[David Kastrup]

tyronicus  writes:

> Phil Holmes wrote
>> My guess is that there's a memory allocation problem that only shows up on
>> large projects on Windows.
>
> That's my suspicion, too. I tried it on a Win10 i7-8xxx with 8G ram and saw
> it cut out around 1.85G memory every time. When I remove two bookparts, it
> only uses 1.82G of memory or so and manages to complete. When I set the
> process to high or realtime priority, which should allow more memory to be
> allocated, it still fails.

1.82G is a bit of a strange number for a 64bit binary.  Are you using a
64bit Windows and definitely a 64bit LilyPond (!) executable?

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[tyronicus]

Phil Holmes wrote
> My guess is that there's a memory allocation problem that only shows up on
> large projects on Windows.

That's my suspicion, too. I tried it on a Win10 i7-8xxx with 8G ram and saw
it cut out around 1.85G memory every time. When I remove two bookparts, it
only uses 1.82G of memory or so and manages to complete. When I set the
process to high or realtime priority, which should allow more memory to be
allocated, it still fails.



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[David Kastrup]

Werner LEMBERG  writes:

> What about setting up GUB (with LilyPond) on https://hydra.nixos.org/?
> Other GNU projects like Emacs are also hosted there for daily
> builds, so it should be easy to get lilypond registered there...
>
>   https://nixos.org/hydra/

Are you going to do it?

Like with any project driven by volunteers, LilyPond does not really
suffer from a shortage of suggestions about what somebody else should
really be doing.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[Werner LEMBERG]

> On my GUB build machine (4 core hyperthreaded i7, 8 Gigs, SSD) an
> incremental build (i.e. with a stable version of GUB with the
> toolset all up to date) takes around one to one and a half hours.
> If GUB needs updating, it can, as you say, take over 6 hours even on
> that machine.  The upload is then a few Gigs and on my old broadband
> this took around 6 hours to upload.  My shiny VDSL connection does
> it in about 5 minutes.  So a complete GUB rebuild is feasible.
> However, I'm not sure that was what was requested.  A simple Linux
> binary in a specific location of Lilypond.org would be fairly
> straightforward - about 2 minutes for the build and very quick
> upload.

What about setting up GUB (with LilyPond) on https://hydra.nixos.org/?
Other GNU projects like Emacs are also hosted there for daily
builds, so it should be easy to get lilypond registered there...

  https://nixos.org/hydra/


Werner

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[Lukas-Fabian Moser]

Am 09.05.2018 um 17:23 schrieb Phil Holmes:

Question: How difficult/costly/... would it be to prepare a "daily
build from current master" for download?


Very.  We are talking about 6 hours of build time on a pretty solidly
powered 8-processor machine.  Actually, we _were_ talking about that
before adding the Catalan translation to the docs and further
complicating the Documentation build process in order to get more
compact PDFs.


On my GUB build machine (4 core hyperthreaded i7, 8 Gigs, SSD) an 
incremental build (i.e. with a stable version of GUB with the toolset 
all up to date) takes around one to one and a half hours. If GUB needs 
updating, it can, as you say, take over 6 hours even on that machine.  
The upload is then a few Gigs and on my old broadband this took around 
6 hours to upload. My shiny VDSL connection does it in about 5 
minutes.  So a complete GUB rebuild is feasible.  However, I'm not 
sure that was what was requested. A simple Linux binary in a specific 
location of Lilypond.org would be fairly straightforward - about 2 
minutes for the build and very quick upload.


I admit that I thought more of a binary package than of the full 
documentation (which I gather is very involved to build). A possible 
rationale might be that a power-user who wants to have access to the 
latest features is likely to get to know these features by watching the 
-user or -devel lists, issue trackers etc., so it's maybe not terribly 
important to have the very latest documentation. (But I know that this 
argument could be disputed, for instance regarding the Internals manual).


As for the choice of the platform: One could argue that, e.g., binaries 
for Windows etc. might be even more useful than Linux binaries (which 
are comparatively easy to compile for oneself).


So: What I thought of when I asked about the costs of a "daily build" 
would be something like: Binaries for as many platforms as possible, but 
without the documentation. If something like that would be reasonable at 
all.


Best
Lukas

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[Phil Holmes]

- Original Message - 
From: "David Kastrup" 

To: "Lukas-Fabian Moser" 
Cc: "lilypond-user" ; 
Sent: Wednesday, May 09, 2018 4:11 PM
Subject: Re: Release schedule for 2.20



Lukas-Fabian Moser  writes:


(I, for example, just recently switched to self-compiled Lilypond
because of Malte's amazing work on the \haydnTurn which was prompted
by my question. To my surprise, compiling turned out to be quite easy,
but of course there /were /some slight dependency issues, /and /I'm
running on Linux which simplifies matters.)


"simplifies matters" -- not really.  It's the only possible way.  We do
all other versions via crosscompilation.


Question: How difficult/costly/... would it be to prepare a "daily
build from current master" for download?


Very.  We are talking about 6 hours of build time on a pretty solidly
powered 8-processor machine.  Actually, we _were_ talking about that
before adding the Catalan translation to the docs and further
complicating the Documentation build process in order to get more
compact PDFs.


On my GUB build machine (4 core hyperthreaded i7, 8 Gigs, SSD) an 
incremental build (i.e. with a stable version of GUB with the toolset all up 
to date) takes around one to one and a half hours.  If GUB needs updating, 
it can, as you say, take over 6 hours even on that machine.  The upload is 
then a few Gigs and on my old broadband this took around 6 hours to upload. 
My shiny VDSL connection does it in about 5 minutes.  So a complete GUB 
rebuild is feasible.  However, I'm not sure that was what was requested.  A 
simple Linux binary in a specific location of Lilypond.org would be fairly 
straightforward - about 2 minutes for the build and very quick upload.


--
Phil Holmes 



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[David Kastrup]

Lukas-Fabian Moser  writes:

> (I, for example, just recently switched to self-compiled Lilypond
> because of Malte's amazing work on the \haydnTurn which was prompted
> by my question. To my surprise, compiling turned out to be quite easy,
> but of course there /were /some slight dependency issues, /and /I'm
> running on Linux which simplifies matters.)

"simplifies matters" -- not really.  It's the only possible way.  We do
all other versions via crosscompilation.

> Question: How difficult/costly/... would it be to prepare a "daily
> build from current master" for download?

Very.  We are talking about 6 hours of build time on a pretty solidly
powered 8-processor machine.  Actually, we _were_ talking about that
before adding the Catalan translation to the docs and further
complicating the Documentation build process in order to get more
compact PDFs.

> While this certainly would be overkill during times when there's a new
> unstable release every few weeks or so, it would I think, by way of
> contrast, highlight the status of the unstable releases more clearly:
> "The stable releases are rock-solid; the unstable releases usually
> work flawlessly but are subject to change; the daily build is
> something for the reckless and impatient." (Whereas now, the latter is
> the way people tend to think about the /unstable /releases which
> underestimates their quality.)

There will be another prerelease coming up soonish as there were again a
few (just not all) critical fixes.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[Phil Holmes]

- Original Message - 
From: "Lukas-Fabian Moser" 

To: ; "lilypond-user" 
Sent: Wednesday, May 09, 2018 3:09 PM
Subject: Re: Release schedule for 2.20




But an increasing number of questions asked in forums or on the lists can 
be answered by “compile current master or wait for 2.21.0”. And a huge 
number of answers requires at least 2.19.xx but people understandably don’t 
want to install an “unstable” version.


IIUC, the situation used to be: i) Rare-to-very-rare stable releases for 
"normal" users, ii) frequent instable releases for those who wanted to use 
the latest features. This seems to have changed due to the preparations 
for the next stable release in that the instable releases stopped 
appearing as well for the time being. Since at the same time, development 
of new features goes on, people who want the latest features now have to 
compile for themselves.


(I, for example, just recently switched to self-compiled Lilypond because 
of Malte's amazing work on the \haydnTurn which was prompted by my 
question. To my surprise, compiling turned out to be quite easy, but of 
course there /were /some slight dependency issues, /and /I'm running on 
Linux which simplifies matters.)


Question: How difficult/costly/... would it be to prepare a "daily build 
from current master" for download? While this certainly would be overkill 
during times when there's a new unstable release every few weeks or so, it 
would I think, by way of contrast, highlight the status of the unstable 
releases more clearly: "The stable releases are rock-solid; the unstable 
releases usually work flawlessly but are subject to change; the daily 
build is something for the reckless and impatient." (Whereas now, the 
latter is the way people tend to think about the /unstable /releases which 
underestimates their quality.)


Best
Lukas



Are you referring to just a single (say Ubuntu) version of Lilypond, or the 
complete set of binary installations as produced in the release when you say 
a "daily build from current master"?


--
Phil Holmes 



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[Phil Holmes]

Might be simplest to create a Linux VM on the Windows box and use that for very 
big projects.  My guess is that there's a memory allocation problem that only 
shows up on large projects on Windows.

--
Phil Holmes


  - Original Message - 
  From: Brent Annable 
  To: David Kastrup 
  Cc: lilypond-user 
  Sent: Wednesday, May 09, 2018 2:59 PM
  Subject: Re: Fwd: Compile crashing... help!


  Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 Thinkpad 
machine with i7 and 16GB RAM. So looks like the errors are coming through on 
the same systems.


  Sigh. What to do? I have an old laptop with a rocket-engine fan that I could 
try


  Brent.


  On 9 May 2018 at 23:28, David Kastrup  wrote:

Ben  writes:

> On 5/9/2018 8:35 AM, Brent Annable wrote:
>> Hi everyone,
>>
>> I'm trying to compile a very large project, it keeps crashing and
>> I'm at a loss as to the cause. Some details:
>>
>> - The error first appears as a Windows notification saying: "
>> Runtime error! This application has requested the Runtime to
>> terminate it in an unusual way. Please contact the application's
>> support team for more information." The error code in Frescobaldi
>> varies, I've had 255, 3 and 1073741395.
>>
>> - I've monitored my laptop's CPU and memory usage during the
>> compiling process, and neither even comes close to reaching capacity
>> (CPU around 30%; Memory 5.6/16 gig).
>>   the file to compile is 'SG_complete_DE.ly".
>>
>> I would be very grateful for any ideas, suggestions or help.
>>
>>
>
> Hi Brent,
>
> I also ran into your issue by compiling "SG_complete_DE.ly" on my
> Windows 10 machine. 32GB RAM. Newest i7 build.
> So, there is some consistency...I see the same errors you do.
>
> However, I compiled your project successfully (and quite fast) on my
> Linux Mint laptop, 2GB RAM, old thinkpad. Took about 3 minutes total.

With an i5 2520M:

dak@lola:/tmp$ time lilypond SG_complete_DE.ly 
GNU LilyPond 2.21.0
Processing `SG_complete_DE.ly'
Parsing...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][192]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 10 or 11 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 11 or 12 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 13 or 14 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 13 or 14 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 14 or 15 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 13 or 14 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 17 or 18 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 14 or 15 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 14 or 15 p

Re: Fwd: Compile crashing... help!

[Karlin High]

On 5/9/2018 8:16 AM, Ben wrote:
I also ran into your issue by compiling "SG_complete_DE.ly" on my 
Windows 10 machine. 32GB RAM. Newest i7 build.


Curiouser and curiouser... It compiled successfully on my Windows 7 Pro 
x64 SP1, Intel Core i5-3450, 24 GB RAM, LilyPond 2.19.80

--
Karlin High
Missouri, USA

PS - Never saw this piece of music before, looks very interesting.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Re: Fwd: Compile crashing... help!

[Mats Bengtsson]

On 2018-05-09 15:59, Brent Annable wrote:
Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 
Thinkpad machine with i7 and 16GB RAM. So looks like the errors are 
coming through on the same systems.


Sigh. What to do? I have an old laptop with a rocket-engine fan that I 
could try


A first step could be to add
\pointAndClickOff
at the top of your file. At least, it will reduce the size of the 
resulting PDF file by almost a factor of 10, and hopefully it might 
reduce some of the memory consumption during the processing as well.


Can 
http://blogs.microsoft.co.il/sasha/2016/01/05/windows-process-memory-usage-demystified/ 
provide some hints on how to debug what is the limiting factor?


   /Mats



Brent.

On 9 May 2018 at 23:28, David Kastrup > wrote:


Ben mailto:soundsfromso...@gmail.com>>
writes:

> On 5/9/2018 8:35 AM, Brent Annable wrote:
>> Hi everyone,
>>
>> I'm trying to compile a very large project, it keeps crashing and
>> I'm at a loss as to the cause. Some details:
>>
>> - The error first appears as a Windows notification saying: "
>> Runtime error! This application has requested the Runtime to
>> terminate it in an unusual way. Please contact the application's
>> support team for more information." The error code in Frescobaldi
>> varies, I've had 255, 3 and 1073741395.
>>
>> - I've monitored my laptop's CPU and memory usage during the
>> compiling process, and neither even comes close to reaching
capacity
>> (CPU around 30%; Memory 5.6/16 gig).
>>   the file to compile is 'SG_complete_DE.ly".
>>
>> I would be very grateful for any ideas, suggestions or help.
>>
>>
>
> Hi Brent,
>
> I also ran into your issue by compiling "SG_complete_DE.ly" on my
> Windows 10 machine. 32GB RAM. Newest i7 build.
> So, there is some consistency...I see the same errors you do.
>
> However, I compiled your project successfully (and quite fast) on my
> Linux Mint laptop, 2GB RAM, old thinkpad. Took about 3 minutes
total.




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[Lukas-Fabian Moser]

But an increasing number of questions asked in forums or on the lists 
can be answered by “compile current master or wait for 2.21.0”. And a 
huge number of answers requires at least 2.19.xx but people 
understandably don’t want to install an “unstable” version.


IIUC, the situation used to be: i) Rare-to-very-rare stable releases for 
"normal" users, ii) frequent instable releases for those who wanted to 
use the latest features. This seems to have changed due to the 
preparations for the next stable release in that the instable releases 
stopped appearing as well for the time being. Since at the same time, 
development of new features goes on, people who want the latest features 
now have to compile for themselves.


(I, for example, just recently switched to self-compiled Lilypond 
because of Malte's amazing work on the \haydnTurn which was prompted by 
my question. To my surprise, compiling turned out to be quite easy, but 
of course there /were /some slight dependency issues, /and /I'm running 
on Linux which simplifies matters.)


Question: How difficult/costly/... would it be to prepare a "daily build 
from current master" for download? While this certainly would be 
overkill during times when there's a new unstable release every few 
weeks or so, it would I think, by way of contrast, highlight the status 
of the unstable releases more clearly: "The stable releases are 
rock-solid; the unstable releases usually work flawlessly but are 
subject to change; the daily build is something for the reckless and 
impatient." (Whereas now, the latter is the way people tend to think 
about the /unstable /releases which underestimates their quality.)


Best
Lukas
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[David Kastrup]

Brent Annable  writes:

> Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 Thinkpad
> machine with i7 and 16GB RAM. So looks like the errors are coming through
> on the same systems.
>
> Sigh. What to do? I have an old laptop with a rocket-engine fan that I
> could try

I consider it more likely that it's the version of gcc this has been
compiled with.  That would point to either using different LilyPond
versions or a different architecture as a short-term evasion attempt.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[Ben]

On 5/9/2018 9:59 AM, Brent Annable wrote:
Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 
Thinkpad machine with i7 and 16GB RAM. So looks like the errors are 
coming through on the same systems.


Sigh. What to do? I have an old laptop with a rocket-engine fan that I 
could try


Brent.


Hard to decide what to do with our Windows compilations here.  We
don't
want to release when stuff keeps crashing for Windows users.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org 
https://lists.gnu.org/mailman/listinfo/lilypond-user





Brent, if you are able to use that laptop for a Linux machine you could 
have two weapons in your arsenal for LilyPond projects... Windows and 
Linux. :)


But the rocket-engine fan sounds pretty promising too... ;)


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[Brent Annable]

Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 Thinkpad
machine with i7 and 16GB RAM. So looks like the errors are coming through
on the same systems.

Sigh. What to do? I have an old laptop with a rocket-engine fan that I
could try

Brent.

On 9 May 2018 at 23:28, David Kastrup  wrote:

> Ben  writes:
>
> > On 5/9/2018 8:35 AM, Brent Annable wrote:
> >> Hi everyone,
> >>
> >> I'm trying to compile a very large project, it keeps crashing and
> >> I'm at a loss as to the cause. Some details:
> >>
> >> - The error first appears as a Windows notification saying: "
> >> Runtime error! This application has requested the Runtime to
> >> terminate it in an unusual way. Please contact the application's
> >> support team for more information." The error code in Frescobaldi
> >> varies, I've had 255, 3 and 1073741395.
> >>
> >> - I've monitored my laptop's CPU and memory usage during the
> >> compiling process, and neither even comes close to reaching capacity
> >> (CPU around 30%; Memory 5.6/16 gig).
> >>   the file to compile is 'SG_complete_DE.ly".
> >>
> >> I would be very grateful for any ideas, suggestions or help.
> >>
> >>
> >
> > Hi Brent,
> >
> > I also ran into your issue by compiling "SG_complete_DE.ly" on my
> > Windows 10 machine. 32GB RAM. Newest i7 build.
> > So, there is some consistency...I see the same errors you do.
> >
> > However, I compiled your project successfully (and quite fast) on my
> > Linux Mint laptop, 2GB RAM, old thinkpad. Took about 3 minutes total.
>
> With an i5 2520M:
>
> dak@lola:/tmp$ time lilypond SG_complete_DE.ly
> GNU LilyPond 2.21.0
> Processing `SG_complete_DE.ly'
> Parsing...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144][152]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144][152][160][168][176][184][192][192]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144][152]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144][152][160]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144][152][160][168]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144][152][160][168][176][184][192][
> 200][208][216][224][232][240][248][256]
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 10 or 11 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 11 or 12 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 13 or 14 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 13 or 14 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 14 or 15 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 13 or 14 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 17 or 18 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 14 or 15 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 14 or 15 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 15 or 16 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 15 or 16 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 17 or 18 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 14 or 15 pages...
> Drawing systems...
> Layout output to `/tmp/lilypond-hUOD1g'...
> Converting to `SG_complete_DE.pdf'...
> Deleting `/tmp/lilypond-hUOD1g'...
> Success: compilati

Re: Fwd: Compile crashing... help!

[David Kastrup]

Ben  writes:

> On 5/9/2018 8:35 AM, Brent Annable wrote:
>> Hi everyone,
>>
>> I'm trying to compile a very large project, it keeps crashing and
>> I'm at a loss as to the cause. Some details:
>>
>> - The error first appears as a Windows notification saying: "
>> Runtime error! This application has requested the Runtime to
>> terminate it in an unusual way. Please contact the application's
>> support team for more information." The error code in Frescobaldi
>> varies, I've had 255, 3 and 1073741395.
>>
>> - I've monitored my laptop's CPU and memory usage during the
>> compiling process, and neither even comes close to reaching capacity
>> (CPU around 30%; Memory 5.6/16 gig).
>>   the file to compile is 'SG_complete_DE.ly".
>>
>> I would be very grateful for any ideas, suggestions or help.
>>
>>
>
> Hi Brent,
>
> I also ran into your issue by compiling "SG_complete_DE.ly" on my
> Windows 10 machine. 32GB RAM. Newest i7 build.
> So, there is some consistency...I see the same errors you do.
>
> However, I compiled your project successfully (and quite fast) on my
> Linux Mint laptop, 2GB RAM, old thinkpad. Took about 3 minutes total.

With an i5 2520M:

dak@lola:/tmp$ time lilypond SG_complete_DE.ly 
GNU LilyPond 2.21.0
Processing `SG_complete_DE.ly'
Parsing...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][192]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 10 or 11 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 11 or 12 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 13 or 14 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 13 or 14 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 14 or 15 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 13 or 14 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 17 or 18 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 14 or 15 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 14 or 15 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 15 or 16 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 15 or 16 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 17 or 18 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 14 or 15 pages...
Drawing systems...
Layout output to `/tmp/lilypond-hUOD1g'...
Converting to `SG_complete_DE.pdf'...
Deleting `/tmp/lilypond-hUOD1g'...
Success: compilation successfully completed

real2m29.251s
user2m26.092s
sys 0m2.629s
dak@lola:/tmp$ 

Hard to decide what to do with our Windows compilations here.  We don't
want to release when stuff keeps crashing for Windows users.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[Malte Meyn]

Am 09.05.2018 um 15:16 schrieb Ben:
I also ran into your issue by compiling "SG_complete_DE.ly" on my 
Windows 10 machine. 32GB RAM. Newest i7 build.

So, there is some consistency...I see the same errors you do.

However, I compiled your project successfully (and quite fast) on my 
Linux Mint laptop, 2GB RAM, old thinkpad. Took about 3 minutes total.


Old thinkpad with Linux (Manjaro) here too, 4GB RAM, no success because 
of too little memory.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

[Ben]

On 5/9/2018 8:35 AM, Brent Annable wrote:

Hi everyone,

I'm trying to compile a very large project, it keeps crashing and I'm 
at a loss as to the cause. Some details:


- The error first appears as a Windows notification saying: " Runtime 
error! This application has requested the Runtime to terminate it in 
an unusual way. Please contact the application's support team for more 
information." The error code in Frescobaldi varies, I've had 255, 3 
and 1073741395.


- I've monitored my laptop's CPU and memory usage during the compiling 
process, and neither even comes close to reaching capacity (CPU around 
30%; Memory 5.6/16 gig).

  the file to compile is 'SG_complete_DE.ly".

I would be very grateful for any ideas, suggestions or help.




Hi Brent,

I also ran into your issue by compiling "SG_complete_DE.ly" on my 
Windows 10 machine. 32GB RAM. Newest i7 build.

So, there is some consistency...I see the same errors you do.

However, I compiled your project successfully (and quite fast) on my 
Linux Mint laptop, 2GB RAM, old thinkpad. Took about 3 minutes total.


Hope this helps you.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[Urs Liska]

Am 9. Mai 2018 12:18:37 MESZ schrieb Aaron Hill :
>On 2018-05-09 02:49, Malte Meyn wrote:
>> But an increasing number of questions asked in forums or on the lists
>> can be answered by “compile current master or wait for 2.21.0”. And a
>> huge number of answers requires at least 2.19.xx but people
>> understandably don’t want to install an “unstable” version.
>> 
>> Since the first prerelease seven months have passed, people wonder
>> whether 2.20.0 will happen in a few weeks, a few months or even
>longer
>> in the future.
>
>I should have stated originally that I am not trying to force anything 
>here.  I totally understand that the developers on this project may be 
>most comfortable with the approach of "we'll release it when it's
>ready, 
>not a moment before".  Rather, I was curious if the team had a planned 
>roadmap they were currently targeting, and where one could easily track
>
>that information.  It sounds like nothing of that sort really exists.  
>This is not ideal but hardly something to stress about.
>
>What does have impact for me is whether the next release is still many 
>months out or longer.  Knowing a little bit about the schedule, I can 
>more easily justify the time expense of getting a build environment set
>
>up to be able to run from master or some other staging branch.  I have 
>no qualms of running "bleeding-edge" bits.  That said, it is always
>more 
>convenient to be able to work from pre-built binaries, although those 
>understandably take time to create and publish.
>

This very much looks to me that your best bet is to install the latest release 
from the 2.19 series.
The only reason to compile yourself would be to incorporate custom patches.

Urs

>So, I apologize if I have ruffled any feathers here.
>
>-- Aaron Hill
>
>___
>lilypond-devel mailing list
>lilypond-de...@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-devel

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: variable and tie

[David Kastrup]

Gianmaria Lari  writes:

> On 9 May 2018 at 10:45, David Kastrup  wrote:
>
>> Gianmaria Lari  writes:
>>
>> > On 13 April 2018 at 09:13, David Kastrup  wrote:
>> >
>> >> Gianmaria Lari  writes:
>> >> >
>> >> > At the moment I do this
>> >> >
>> >> > \version "2.19.81"
>> >> > var = {a b \tag #'lastnote a}
>> >> > {\removeWithTag #'lastnote \var a ~ a}
>> >> >
>> >> > but I would like to know if there are other solution (maybe better?).
>> >>
>> >> 2.21.0 (current master) ac"cepts it as-is.
>> >>
>> >> --
>> >> David Kastrup
>> >>
>> >
>> > What about this David:
>> >
>> > \version "2.19.81"
>> > var = {a b c d}
>> > {\var( \var )}
>> >
>> >
>> > Will it work in the future?

[image equivalent to { a b c d( a b c d) }

>> Probably not what you had in mind.  ( and ) are not treated differently:
>> they are attached to the last note of a preceding phrase, similarly any
>> other post-event.  But you could probably write
>>
>> {<>( \var \var )}
>>
>> instead to get what I presume to be the desired effect.

[which would be equivalent to { a( b c d a b c d) }]

> hihi :)
>
> This is exactly what I wanted. But I don't understand why your code works
> and mine doesn't.
> Isn't "var" a phrase and 'd' the last note of the that phrase?

This sounds like a misunderstanding.  At least it does not make sense to
me.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[Aaron Hill]

On 2018-05-09 02:49, Malte Meyn wrote:

But an increasing number of questions asked in forums or on the lists
can be answered by “compile current master or wait for 2.21.0”. And a
huge number of answers requires at least 2.19.xx but people
understandably don’t want to install an “unstable” version.

Since the first prerelease seven months have passed, people wonder
whether 2.20.0 will happen in a few weeks, a few months or even longer
in the future.


I should have stated originally that I am not trying to force anything 
here.  I totally understand that the developers on this project may be 
most comfortable with the approach of "we'll release it when it's ready, 
not a moment before".  Rather, I was curious if the team had a planned 
roadmap they were currently targeting, and where one could easily track 
that information.  It sounds like nothing of that sort really exists.  
This is not ideal but hardly something to stress about.


What does have impact for me is whether the next release is still many 
months out or longer.  Knowing a little bit about the schedule, I can 
more easily justify the time expense of getting a build environment set 
up to be able to run from master or some other staging branch.  I have 
no qualms of running "bleeding-edge" bits.  That said, it is always more 
convenient to be able to work from pre-built binaries, although those 
understandably take time to create and publish.


So, I apologize if I have ruffled any feathers here.

-- Aaron Hill

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: variable and tie

[Gianmaria Lari]

On 9 May 2018 at 10:45, David Kastrup  wrote:

> Gianmaria Lari  writes:
>
> > On 13 April 2018 at 09:13, David Kastrup  wrote:
> >
> >> Gianmaria Lari  writes:
> >> >
> >> > At the moment I do this
> >> >
> >> > \version "2.19.81"
> >> > var = {a b \tag #'lastnote a}
> >> > {\removeWithTag #'lastnote \var a ~ a}
> >> >
> >> > but I would like to know if there are other solution (maybe better?).
> >>
> >> 2.21.0 (current master) ac"cepts it as-is.
> >>
> >> --
> >> David Kastrup
> >>
> >
> > What about this David:
> >
> > \version "2.19.81"
> > var = {a b c d}
> > {\var( \var )}
> >
> >
> > Will it work in the future?
>
>
>
> Probably not what you had in mind.  ( and ) are not treated differently:
> they are attached to the last note of a preceding phrase, similarly any
> other post-event.  But you could probably write
>
> {<>( \var \var )}
>
> instead to get what I presume to be the desired effect.
>

hihi :)

This is exactly what I wanted. But I don't understand why your code works
and mine doesn't.
Isn't "var" a phrase and 'd' the last note of the that phrase?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[Malte Meyn]

Am 09.05.2018 um 11:16 schrieb David Kastrup:

Aaron Hill  writes:


Hi folks,

It would seem the release of version 2.20 must be nearing, but I have
not found anything published about the release schedule for the
project.


There isn't one.


[CC-ing to lilypond-devel]

I know that you don’t like that sort of questions because “Das Gras 
wächst nicht schneller, wenn man daran zieht.”*


But an increasing number of questions asked in forums or on the lists 
can be answered by “compile current master or wait for 2.21.0”. And a 
huge number of answers requires at least 2.19.xx but people 
understandably don’t want to install an “unstable” version.


Since the first prerelease seven months have passed, people wonder 
whether 2.20.0 will happen in a few weeks, a few months or even longer 
in the future.


Don’t get me wrong: We can be very happy to have such a committed 
project leader. But maybe also the other developers should join forces to


1. find out what blocks the release of 2.20.0
2. concentrate on that instead of new features.

Personally, I don’t know about 1. That’s why I added new features 
instead. At the moment I don’t have the time to that too but I would be 
happy if I could help to bring 2.20.0 out.


* “Grass doesn’t grow faster when you pull it.”

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[Phil Holmes]

- Original Message - 
From: "David Kastrup" 

To: "Aaron Hill" 
Cc: 
Sent: Wednesday, May 09, 2018 10:16 AM
Subject: Re: Release schedule for 2.20



Aaron Hill  writes:


Hi folks,

It would seem the release of version 2.20 must be nearing, but I have
not found anything published about the release schedule for the
project.


There isn't one.


The website mentions following the info-lilyp...@gnu.org mailing list,
but according to the archives that list hasn't seen a post in years.


Hm, I'd have thought that we announce developer releases there as well.
Last announcement is indeed 2.19.13 in 2014, so it seems like stuff
broke down some time after that.  12.19 has been around that long
already?


It would be my job to make these announcements, but at some point I lost the 
ability to post to that whitelisted list and could not work out how to 
rectify that.


So looking at the website news would be the best.

I suppose I could announce to lilypond-user?

--
Phil Holmes 



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Release schedule for 2.20

[David Kastrup]

Aaron Hill  writes:

> Hi folks,
>
> It would seem the release of version 2.20 must be nearing, but I have
> not found anything published about the release schedule for the
> project.

There isn't one.

> The website mentions following the info-lilyp...@gnu.org mailing list,
> but according to the archives that list hasn't seen a post in years.

Hm, I'd have thought that we announce developer releases there as well.
Last announcement is indeed 2.19.13 in 2014, so it seems like stuff
broke down some time after that.  12.19 has been around that long
already?

> Is there a better resource for staying up-to-date on the project?

Not really.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Release schedule for 2.20

[Aaron Hill]

Hi folks,

It would seem the release of version 2.20 must be nearing, but I have 
not found anything published about the release schedule for the project. 
 The website mentions following the info-lilyp...@gnu.org mailing list, 
but according to the archives that list hasn't seen a post in years.


Is there a better resource for staying up-to-date on the project?

-- Aaron Hill

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: disabling \break

[Caagr98]

If you want a more lightweight way to do it, this function should also work:
⋘
removeBreaks =
  #(define-music-function (mus) (ly:music?)
 (music-filter
   (lambda (v) (not (music-is-of-type? v 'break-event)))
   mus))
⋙


On 05/08/18 14:17, Jan-Peter Voigt wrote:
> Hi Herbie,
> 
> this is *the* use case for the edition-engraver:
> https://github.com/openlilylib/edition-engraver/
> or the page-layout package
> https://github.com/openlilylib/page-layout
> (which is using the edition-engraver for the conditional breaks)
> 
> If you install openLilyLib (https://github.com/openlilylib/oll-core), you can 
> make use of these packages quite easily. That way you can separate breaks and 
> page-layout from the music-content.
> 
> So the short answer is: Yes, it is possible to add a command that avoids 
> certain breaks for certain commands.
> 
> If you want to know more about these tools don't hesitate to ask!
> 
> HTH
> Jan-Peter
> 
> 
> 
> Am 08.05.2018 um 07:50 schrieb Herbert Liechti:
>> Hello
>>
>> I searched a long time in the forum an internet and could not find an answer 
>> for my issue.
>>
>> I write all my music with lilypond and at the end I have two output targets. 
>> One is the paper form and one
>> is a page layout for the tablet. The latter layout is optimized so that the 
>> screen of the table is used with small
>> margins. I use two book sections for this
>>
>> I often do a line break at the end of each part (i.E. part A, part B, part 
>> C). For the paper output this is useful for
>> the tablet it is wasting place.
>>
>> Is it possible to add a command that skips/disables/avoids the manual breaks 
>> when creating the tablet version?
>>
>> Thanks & best regards
>> Herbie
>>
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: variable and tie

[David Kastrup]

Gianmaria Lari  writes:

> On 13 April 2018 at 09:13, David Kastrup  wrote:
>
>> Gianmaria Lari  writes:
>> >
>> > At the moment I do this
>> >
>> > \version "2.19.81"
>> > var = {a b \tag #'lastnote a}
>> > {\removeWithTag #'lastnote \var a ~ a}
>> >
>> > but I would like to know if there are other solution (maybe better?).
>>
>> 2.21.0 (current master) accepts it as-is.
>>
>> --
>> David Kastrup
>>
>
> What about this David:
>
> \version "2.19.81"
> var = {a b c d}
> {\var( \var )}
>
>
> Will it work in the future?


Probably not what you had in mind.  ( and ) are not treated differently:
they are attached to the last note of a preceding phrase, similarly any
other post-event.  But you could probably write

{<>( \var \var )}

instead to get what I presume to be the desired effect.

-- 
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: variable and tie

[Gianmaria Lari]

On 13 April 2018 at 09:13, David Kastrup  wrote:

> Gianmaria Lari  writes:
>
> > I would like to tie the last note contained in a variable like this
> >
> > \version "2.19.81"
> > var = {a b a}
> > {\var ~ a}
> >
> > but this generates an error. This is just a simple example, the reason
> why
> > I would like to do this is because the variable in the real piece is used
> > many times without the tie except in one case where it has to be tied.
> >
> > At the moment I do this
> >
> > \version "2.19.81"
> > var = {a b \tag #'lastnote a}
> > {\removeWithTag #'lastnote \var a ~ a}
> >
> > but I would like to know if there are other solution (maybe better?).
>
> 2.21.0 (current master) accepts it as-is.
>
> --
> David Kastrup
>

What about this David:

\version "2.19.81"
var = {a b c d}
{\var( \var )}


Will it work in the future?
Thank you, g.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user