Re: Compilation time (was: Generate \scaleDurations procedurally)

Dear Jean (and Valentin!), thank you so much! The page breaker was the problem, and after applying your fix the compilation time on my machine is around 3 minutes. I'll soon be able to finish the score, just need to fix the duration ratio and the layout. Again, thank you! Lib P.S. I just fou

Re: Compilation time (was: Generate \scaleDurations procedurally)

Le mardi 13 juin 2023 à 11:13 +0200, Valentin Petzel a écrit : > ``` > bargrid = > #(define-music-function (d type mus) (pair? string? ly:music?) >    (let* ((mus-len (ly:music-length mus)) >   (mus-len (/ (ly:moment-main-numerator mus-len) > (ly:moment-main-denominator mus-len))) >  

Re: Compilation time (was: Generate \scaleDurations procedurally)

, Valentin Am Dienstag, 13. Juni 2023, 09:16:15 CEST schrieb Lib Lists: > Hello, > When trying to compile the complete score of the piece below (88 > staves and 120 quarter notes), I noticed it was taking many hours (I > didn't finish the compilation). Trying with shorter versions, I

Re: Compilation time (was: Generate \scaleDurations procedurally)

Le mardi 13 juin 2023 à 09:16 +0200, Lib Lists a écrit : > Hello, > > When trying to compile the complete score of the piece below (88 > staves and 120 quarter notes), I noticed it was taking many hours (I > didn't finish the compilation). Trying with shorter versions, I

Compilation time (was: Generate \scaleDurations procedurally)

Hello, When trying to compile the complete score of the piece below (88 staves and 120 quarter notes), I noticed it was taking many hours (I didn't finish the compilation). Trying with shorter versions, I got the following compilation times: - 2x quarter notes -> 16.7", - 4x quarter

Re: Compilation errors 2.24.1 Fedora 38

>> Alas, LilyPond doesn't support it for technical reasons. > > They work just fine in the Cairo backend though. Andrew, try > compiling with the `-dbackend=cairo` option. This currently fails with variation fonts based on CFF2 technology, like 'Noto CJK VF'. Apparently, LilyPond tries to emb

Re: Compilation errors 2.24.1 Fedora 38

You nailed it. Thank you so much. Andrew On 30/04/2023 11:02 pm, Werner LEMBERG wrote: Apparently, somewhere in your score there is a glyph that isn't covered by LilyPond's default fonts or the fonts that you specify with `font-name`. For such glyphs, LilyPond relies on Fontconfig to find a f

Re: Compilation errors 2.24.1 Fedora 38

Le dimanche 30 avril 2023 à 13:02 +, Werner LEMBERG a écrit : > Alas, LilyPond doesn't support it > for technical reasons. They work just fine in the Cairo backend though. Andrew, try compiling with the `-dbackend=cairo` option. signature.asc Description: This is a digitally signed message

Re: Compilation errors 2.24.1 Fedora 38

> > > warning: font index 262144 too large for font > > > `/usr/share/fonts/google-noto-vf/NotoSans[wght].ttf', using index 0 > > > > This is a variation font, which LilyPond doesn't support. I > > suggest that you explicitly specify the font in your `.ly` file > > that you are going to use. htt

Re: Compilation errors 2.24.1 Fedora 38

Thanks. That works. Brilliant Andrew On 30/04/2023 10:47 pm, Jean Abou Samra wrote: I've pushed https://github.com/openlilylib/snippets/commit/63858cdaf121935a6a2d835058bf24e2cea81a5a to fix this in OLL.

Re: Compilation errors 2.24.1 Fedora 38

Le dimanche 30 avril 2023 à 14:28 +0200, Jean Abou Samra a écrit : > I've already replied to you off-list about this one (you need to amend the > OLL slash-stem module). I've pushed [https://github.com/openlilylib/snippets/commit/63858cdaf121935a6a2d835058bf24e2cea81a5a](https://github.com/open

Re: Compilation errors 2.24.1 Fedora 38

What is a 'variation font'? I have lines like this: \override TupletNumber.font-name = "Noto Sans" What does it mean to 'explicitly specify the font'? Andrew On 30/04/2023 10:28 pm, Werner LEMBERG wrote: With 2.24.1 on Fedora 28 I am getting two issues with one file. 1. = warning: fo

Re: Compilation errors 2.24.1 Fedora 38

> With 2.24.1 on Fedora 28 I am getting two issues with one file. > > > 1. = > > warning: font index 262144 too large for font > `/usr/share/fonts/google-noto-vf/NotoSans[wght].ttf', using index 0 This is a variation font, which LilyPond doesn't support. I suggest that you explicitly spe

Re: Compilation errors 2.24.1 Fedora 38

Le dimanche 30 avril 2023 à 22:05 +1000, Andrew Bernard a écrit : > 2.= > > Unsupported SCM value for format: ((unquote-splicing (quote (moveto > -1.4142135623730951 -0.6191706933865051 lineto 3.5355339059327378 > -5.568918161692338 > Unsupported SCM value for format: ((unquote-splicing

Re: Compilation errors 2.24.1 Fedora 38

Le dimanche 30 avril 2023 à 22:05 +1000, Andrew Bernard a écrit : > 2.= > > Unsupported SCM value for format: ((unquote-splicing (quote (moveto > -1.4142135623730951 -0.6191706933865051 lineto 3.5355339059327378 > -5.568918161692338 > Unsupported SCM value for format: ((unquote-splicing

Compilation errors 2.24.1 Fedora 38

Further to previous queries, I am still attempting to build a large project from 6 years ago. With 2.24.1 on Fedora 28 I am getting two issues with one file. 1. = warning: font index 262144 too large for font `/usr/share/fonts/google-noto-vf/NotoSans[wght].ttf', using index 0 warning: fo

Re: Very weird output on any compilation

On 2019-11-12 11:49 am, David Menéndez Hurtado wrote: You are correct. Now let's hope it doesn't mess anything else, it does say DO NOT EDIT at the top... The "DO NOT EDIT" comment likely means one of two things: (1) the file in question is generated by some other process and may be overwritt

Re: Very weird output on any compilation

On Tue, 12 Nov 2019 at 20:24, Carl Sorensen wrote: > > > > > *From: *David Menéndez Hurtado > *Date: *Tuesday, November 12, 2019 at 12:18 PM > *To: *Carl Sorensen > *Cc: *"lilypond-user@gnu.org" > *Subject: *Re: Very weird output on any compilation

Re: Very weird output on any compilation

From: David Menéndez Hurtado Date: Tuesday, November 12, 2019 at 12:18 PM To: Carl Sorensen Cc: "lilypond-user@gnu.org" Subject: Re: Very weird output on any compilation Carl, you are correct. Changing it to 1200 fixes the problem. I will investigate more and see if there

Re: Very weird output on any compilation

On Tue, 12 Nov 2019 at 16:00, Carl Sorensen wrote: > > > > > *From: *David Menéndez Hurtado > *Date: *Tuesday, November 12, 2019 at 6:40 AM > *To: *Carl Sorensen > *Cc: *"lilypond-user@gnu.org" > *Subject: *Re: Very weird output on any compilation > &

Re: Very weird output on any compilation

From: David Menéndez Hurtado Date: Tuesday, November 12, 2019 at 6:40 AM To: Carl Sorensen Cc: "lilypond-user@gnu.org" Subject: Re: Very weird output on any compilation Thanks for all the tips. On Mon, 11 Nov 2019 at 22:13, Carl Sorensen mailto:c_soren...@byu.edu>> wrote: H

Re: Very weird output on any compilation

Thanks for all the tips. On Mon, 11 Nov 2019 at 22:13, Carl Sorensen wrote: > Here’s a solution that worked in the past -- it describes how DPI settings > get set in fonconfig to 96 dpi, instead of 1200 (the lilypond default): > > https://lists.gnu.org/archive/html/bug-lilypond/2017-01/msg00022.

Re: Very weird output on any compilation

On 11/11/19, 12:59 PM, "David Wright" wrote: On Mon 11 Nov 2019 at 17:17:00 (+0100), David Menéndez Hurtado wrote: > I am having trouble compiling even the simplest of scores. For example, > this is the template from Frescobaldi, compiled with lilypond from the > command line:

RE: Very weird output on any compilation

David, It compiled perfect from Frescobaldi for me. Mark From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of David Menéndez Hurtado Sent: Monday, November 11, 2019 8:17 AM To: lilypond-user@gnu.org Subject: Very weird output on any compilation

Re: Very weird output on any compilation

Hi David, Le lun. 11 nov. 2019 à 18:46, David Menéndez Hurtado a écrit : [...] > The output is the same for PNG and PDF. The same problem happens with any > other score from Mutopia. Does anyone know what is going on? > [...] Are you sure that the scores are in v.2.19 (many scores frome Mutopia

Re: Very weird output on any compilation

gt; I have not messed with dynamic linking: > $ echo $LD_LIBRARY_PATH > > (that is an empty string) > > > I am attaching the compilation log when using loglevel DEBUG. For > completeness, the template I used is also attached. > > Can anyone spot what is wrong here? Is t

Very weird output on any compilation

what is going on? I have installed lilypond 2.19.83 from the Fedora repositories, and I am sure that is what is being used: $ which lilypond /bin/lilypond I have not messed with dynamic linking: $ echo $LD_LIBRARY_PATH (that is an empty string) I am attaching the compilation log when using

Re: Arrowed quartertones notes snippet compilation problem

Thanks Harm! Here is the result of convert-ly, which compiles fine: menu@macbookprojm: ~/Documents/LaTeX/PartitionsLilypond > convert-ly ArrowedQuarterNotesExample.ly > ArrowedQuarterNotesExample_CONVERTED.ly convert-ly (GNU LilyPond) 2.19.83 convert-ly: Processing `ArrowedQuarterNotesExample.l

Re: Arrowed quartertones notes snippet compilation problem

Am Do., 18. Juli 2019 um 21:15 Uhr schrieb Jacques Menu : > > Hello folks, > > The snippet at http://lsr.di.unimi.it/LSR/Snippet?id=784 leads to the error > messages below with LP 2.19.83. > > Didn’t find eiseh nor feh in Lily's source code. > I don’t know which version it was written for. Does an

Arrowed quartertones notes snippet compilation problem

Hello folks, The snippet at http://lsr.di.unimi.it/LSR/Snippet?id=784 leads to the error messages below with LP 2.19.83. Didn’t find eiseh nor feh in Lily's source code. I don’t know which version it was written for. Does anyone know? Thanks! JM — Starting lilypond 2.19.83 [ArrowedQuarterNo

Re: Tie shape inside chords: Inconsistent compilation

version "2.19.82" > > music = > > \fixed c' { > > \time 3/8 > > \voiceOne > > 4. q > > } > > { \music } { \music } { \music } > > %% > > > > After trying several compilation, sometimes the shape command is > applied, sometim

Re: Tie shape inside chords: Inconsistent compilation

Am Fr., 26. Okt. 2018 um 15:41 Uhr schrieb Pierre Perol-Schneider : > > Hi, > Please consider the following example: > > %% > \version "2.19.82" > music = > \fixed c' { > \time 3/8 > \voiceOne > 4. q > } > { \music } { \music } { \music

Tie shape inside chords: Inconsistent compilation

Hi, Please consider the following example: %% \version "2.19.82" music = \fixed c' { \time 3/8 \voiceOne 4. q } { \music } { \music } { \music } %% After trying several compilation, sometimes the shape command is applied, sometimes not. I've found multiple workarounds

Re: Slow compilation

On 2/1/2018 6:56 AM, Andrew Bernard wrote: Hi Peter, Windows 7 reached official end of life January 2015. That means you no longer receive Microsoft patches for *security updates and protection* for your PC from malicious attacks. How can you say for sure your system has not been compromised,

Re: Slow compilation

I get security upgrades still. At least I did last month. Security support ends 2020. (April I think). Why not the latest Lilypond? Because I'm doing a quick job and that was the latest version when I had time to upgrade. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___

Re: Slow compilation

Thanks Ben, that did the trick! -- 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: Slow compilation

Hi Peter, Windows 7 reached official end of life January 2015. That means you no longer receive Microsoft patches for security updates and protection for your PC from malicious attacks. How can you say for sure your system has not been compromised, and that an attack of some kind is not affecting

Re: Slow compilation

On 2/1/2018 6:43 AM, Peter Toye wrote: Re: Slow compilation David, Sorry, I thought this was a well-known issue which had already been solved. There's some Nabble chat about Windows 10. I thought I had an email trail for it, but that also seems to have disappeared. Or never existed. I

Re: Slow compilation

x27;m sure that it didn't take 38 seconds to compile a 31-bar piece of polyphony. The OS is Windows 7 - that hasn't changed either. Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.com - Thursday, February 1, 2018, 11:21:00 AM, you wrote: > Peter T

Re: Slow compilation

On 2/1/2018 6:14 AM, Peter Toye wrote: Slow compilation Compilation has become very slow, and I suspect it's a return to the font caching problem. I thought I'd asked this question before a year or two ago, but I can't find it in Nabble so I must be dreaming. Can someone p

Re: Slow compilation

Peter Toye writes: > Compilation has become very slow, and I suspect it's a return to the > font caching problem. I thought I'd asked this question before a year > or two ago, but I can't find it in Nabble so I must be dreaming. > > Can someone please remind me wh

Slow compilation

Compilation has become very slow, and I suspect it's a return to the font caching problem. I thought I'd asked this question before a year or two ago, but I can't find it in Nabble so I must be dreaming. Can someone please remind me what to do? Regards, Peter mailto:lil

Re: Snippet for conditional score compilation

Hi Saul, > Here's a short little snippet to turn on or off whether a score is compiled. > I'm using this to control which movements are compiled across all my > instrumental parts from a flag in a single file. Nice! I do the same kind of thing in my big multi-movement works (operas, musicals, e

Snippet for conditional score compilation

Hi all, Here's a short little snippet to turn on or off whether a score is compiled. \version "2.18.2" % Swap the commented lines to demonstrate that you can turn the score on and off flag = ##t % flag = ##f compileIf = #(define-void-function (parser location flag score) (boolean? ly:score?)

Re: Compilation Problem with lilypondbook

Hi Emil, On Fri, Apr 21, 2017 at 3:57 PM, Emil Salim wrote: > Hello again, > > I removed the geometry package and was able to produce a PDF, but somewhat > erratic. I'll try out several things first. Sorry to bother. I don't think anyone can really comment on this since you didn't indicate you w

Re: Compilation Problem with lilypondbook

Hello again, I removed the geometry package and was able to produce a PDF, but somewhat erratic. I'll try out several things first. Sorry to bother. Emil On Fri, Apr 21, 2017 at 2:22 PM, Emil Salim wrote: > Hi Everyone, > > I have this snippet below that is compilable with lilypond, but when

Compilation Problem with lilypondbook

Hi Everyone, I have this snippet below that is compilable with lilypond, but when I put it in a .lytex file and tried compiling the .lytex file with lilypond-book --latex=lualatex --output=out ___.lytex I got an error message on compressing over-full page by a bunch of numbers and programming err

Re: Question: Cross compilation

On 27 Sep 2016 18:31, "Jan Nieuwenhuizen" wrote:. > > > A Lilypond build tool for all platforms to which someone's added half > > a dozen extra unrelated targets (possibly very large ones such as > > OpenOffice) = a terrible idea. > > Thanks! GUB was the first to be so generic that it could be us

Re: Question: Cross compilation

Chris Yate writes: > At a brief look over GUB, the really big question in my mind is why on > earth it seems to want to build *everything*.  That's mostly fault. > A Lilypond build tool for all platforms = a great idea. Thanks. I developed GUB together with Han-Wen and it was our 4th iteration

Re: Question: Cross compilation

- Original Message - From: "Richard Shann" To: "Phil Holmes" Cc: "David Kastrup" ; "Lilypond-User Mailing List" Sent: Tuesday, September 27, 2016 8:54 AM Subject: Re: Question: Cross compilation On Tue, 2016-09-27 at 08:53 +0100, P

Re: Question: Cross compilation

- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: "Richard Shann" ; "Lilypond-User Mailing List" Sent: Tuesday, September 27, 2016 9:04 AM Subject: Re: Question: Cross compilation "Phil Holmes" writes: -

Re: Question: Cross compilation

"Phil Holmes" writes: > - Original Message - > From: "Richard Shann" > To: "David Kastrup" > Cc: "Lilypond-User Mailing List" > Sent: Tuesday, September 27, 2016 8:38 AM > Subject: Re: Question: Cross compilation >> >

Re: Question: Cross compilation

On Tue, 2016-09-27 at 08:53 +0100, Phil Holmes wrote: > - Original Message - > From: "Richard Shann" > To: "David Kastrup" > Cc: "Lilypond-User Mailing List" > Sent: Tuesday, September 27, 2016 8:38 AM > Subject: Re: Question: Cross com

Re: Question: Cross compilation

On 27 Sep 2016 03:59, "David Kastrup" wrote: > > > At a brief look over GUB, the really big question in my mind is why on > > earth it seems to want to build *everything*. > > It wants to be _able_ to build everything, like autoconf. Fine. But Autoconf doesn't ship with makefiles for everything.

Re: Question: Cross compilation

- Original Message - From: "Richard Shann" To: "David Kastrup" Cc: "Lilypond-User Mailing List" Sent: Tuesday, September 27, 2016 8:38 AM Subject: Re: Question: Cross compilation and, more specifically, I would guess they are spent in creating the d

Re: Question: Cross compilation

On Tue, 2016-09-27 at 04:23 +0200, David Kastrup wrote: > Chris Yate writes: > > > On Mon, 26 Sep 2016 at 19:34 David Kastrup wrote: > > > >> > >> That's pretty good, actually. Not being able to do native/online > >> compilations by anybody wanting to is bad. Yes. Fixes to GUB (possibly > >>

Re: Question: Cross compilation

Chris Yate writes: > On Mon, 26 Sep 2016 at 19:34 David Kastrup wrote: > >> >> That's pretty good, actually. Not being able to do native/online >> compilations by anybody wanting to is bad. Yes. Fixes to GUB (possibly >> even just to its information/documentation, maybe it _can_ do it >> alre

Re: Question: Cross compilation

On Mon, 26 Sep 2016 at 23:05 Chris Yate wrote: > On Mon, 26 Sep 2016 at 19:34 David Kastrup wrote: > >> >> That's pretty good, actually. Not being able to do native/online >> compilations by anybody wanting to is bad. Yes. Fixes to GUB (possibly >> even just to its information/documentation,

Re: Question: Cross compilation

On Mon, 26 Sep 2016 at 19:34 David Kastrup wrote: > > That's pretty good, actually. Not being able to do native/online > compilations by anybody wanting to is bad. Yes. Fixes to GUB (possibly > even just to its information/documentation, maybe it _can_ do it > already) are of course welcome:

Re: Question: Cross compilation

On 26 Sep 2016 20:16, "Phil Holmes" wrote: > > TBH, you'd probably find it far easier to install a Linux VM on your Windows host, and compile the problematic score on that. I've done both, and what I suggest here is what I would do. That's exactly what I've done - I do a lot of my day job with V

Re: Question: Cross compilation

hil Holmes - Original Message - From: Chris Yate To: David Kastrup Cc: Phil Holmes ; Lilypond-User Mailing List Sent: Monday, September 26, 2016 7:48 PM Subject: Re: Question: Cross compilation On Mon, 26 Sep 2016 at 19:34 David Kastrup wrote: Chris Yate writes:

Re: Question: Cross compilation

Chris Yate writes: > On Mon, 26 Sep 2016 at 19:34 David Kastrup wrote: > >> Chris Yate writes: >> >> > Hi Phil, >> > >> > Sigh... Yes, that's basically the conclusion I'd already come to, but >> that >> > it seemed such a ludicrous state of affairs that _somebody_ must have a >> > better soluti

Re: Question: Cross compilation

On Mon, 26 Sep 2016 at 19:34 David Kastrup wrote: > Chris Yate writes: > > > Hi Phil, > > > > Sigh... Yes, that's basically the conclusion I'd already come to, but > that > > it seemed such a ludicrous state of affairs that _somebody_ must have a > > better solution. > > If you can find _any_ fr

Re: Question: Cross compilation

Chris Yate writes: > Hi Phil, > > Sigh... Yes, that's basically the conclusion I'd already come to, but that > it seemed such a ludicrous state of affairs that _somebody_ must have a > better solution. If you can find _any_ free software project requiring a number of free software compile- and r

Re: Question: Cross compilation

hours on a Core i7 quad core system. > > HTH > > -- > Phil Holmes > > > > - Original Message - > *From:* Chris Yate > *To:* Lilypond-User Mailing List > *Sent:* Monday, September 26, 2016 6:54 PM > *Subject:* Question: Cross compilation > > Hi all, > >

Re: Question: Cross compilation

ve compile time of the order of 24 hours on a Core i7 quad core system. HTH -- Phil Holmes - Original Message - From: Chris Yate To: Lilypond-User Mailing List Sent: Monday, September 26, 2016 6:54 PM Subject: Question: Cross compilation Hi all, Apologies for the p

Question: Cross compilation

Hi all, Apologies for the potentially "blindingly obvious" question, bu't having read the devel webpages about compiling Lilypond for mingw/Windows, I'm none the wiser. I can compile for native linux using the gnu make (via the smart-autoconf.sh script). However, I'm trying to track down a crash

Re: implicitly running a lilypond script through a python script before compilation

s! I have "Hello world" in the log, which is already great. > > However, I can't find yet whether I have some chance of recursively modifying > the Lilypond input through python before compilation goes any further... the > German forum conversation does not mention tha

Re: implicitly running a lilypond script through a python script before compilation

yet whether I have some chance of recursively modifying the Lilypond input through python before compilation goes any further... the German forum conversation does not mention that and I suspect it will not be very easy... However, I should be able to read from it and (over)write an external lily

Re: implicitly running a lilypond script through a python script before compilation

2016-05-01 22:48 GMT+02:00 Joseph Chrestien <_...@live.com>: > Hi all, > > I know this is going to sound strange: is it possible (or even imaginable) to > run a Python code snippet from "within" Lilypond code at compile time? Yes, see this thread in the german forum http://www.lilypondforum.de/i

implicitly running a lilypond script through a python script before compilation

Hi all, I know this is going to sound strange: is it possible (or even imaginable) to run a Python code snippet from "within" Lilypond code at compile time? This is my situation: I am currently using a custom extension of the "Column markup" Frescobaldi snippet, to print verses below a staff.

Re: Controlling compilation

David Sumbler writes: > From: David Kastrup >> > Date: Mon, 11 Apr 2016 09:29:40 +0200 >> > >> > #... at top level is executed and the result ignored to allow for >> > #(set! ...) and similar expressions with usually unspecified return >> > #codes. Just try >> > >> > $(if sectionA compileA) >

Re: Controlling compilation

Am 15.04.2016 um 19:46 schrieb David Sumbler: >>> You seem to be ready to *do* some manual changes to your master file >>> > > (e.g. defining a variable or not). So you could simply put your >>> > > different scores in individual include files and comment in/out these >>> > > includes. >>> > > If

Re: Controlling compilation

David Sumbler writes: > As an experiment, I produced this: > > File: experimentNotes.ly > > \version "2.19.24" > > compileA = > \score { > \new Staff { >a' a' a' a' > } > \layout { } > } [...] > #(if sectionA #{ \compileA #} ) From: David Kastrup > > Date: Mon, 11 Apr 2016 09:29:4

Re: Controlling compilation

David Sumbler writes: > As an experiment, I produced this: > > File: experimentNotes.ly > > \version "2.19.24" > > compileA = > \score { > \new Staff { >a' a' a' a' > } > \layout { } > } [...] > #(if sectionA #{ \compileA #} ) #... at top level is executed and the result ignored to

Re: Controlling compilation

of a single movement, and also a midi file of any of these items. I thought perhaps I could control this in my top-level file by having the compilation instructions for these possibilities defined in variables in an included file, and simply defining variables (or not, if there is a way of checking

Re: Controlling compilation

e movement, and also a midi file of any of > these items. > > I thought perhaps I could control this in my top-level file by having > the compilation instructions for these possibilities defined in > variables in an included file, and simply defining variables (or not, if > there

Controlling compilation

thought perhaps I could control this in my top-level file by having the compilation instructions for these possibilities defined in variables in an included file, and simply defining variables (or not, if there is a way of checking the existence of a variable) in the top level file. As an experiment, I

Re: faster compilation (was: Technical question)

On 08.04.2016 02:44, Flaming Hakama by Elaine wrote: So, the approach is to segment your piece using \tag and then work on it one segment at a time. (Of course, depending on what types of issues you are working on like page breaks or line breaks, you may need to compile the preceding or follo

Re: faster compilation (was: Technical question)

Hi, fot this particular goal, I would suggest to look here: http://lilypond.org/doc/v2.18/Documentation/notation/skipping-corrected-music It needs much less code changes than the tags. Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org

Re: faster compilation (was: Technical question)

> When my score becomes bigger i have to wait long to see my > result and this slows me down in my working proces. > > So i was wondering if lilypond could work faster > Here is an alternative approach to achieving faster compilation for large scores. Well, it is a workaro

Re: booleans and conditional compilation?

On 01.04.2016 22:43, Simon Albrecht wrote: you can use Guile Scheme. LilyPond uses Guile 1.8, whose Reference Manual is here: . ___ lilypond-user mailing list lilypond-user@gnu.org https:/

Re: booleans and conditional compilation?

On 01.04.2016 21:23, Johannes Waldmann wrote: Hi. Is there a standard way of conditional compilation, e.g., to turn parts (on any level) of a score on and off? The standard way is using tags, as Urs said. But of course you can do everything you like via scheme: \version "2.19.38" f

Re: booleans and conditional compilation?

Am 1. April 2016 21:23:17 MESZ, schrieb Johannes Waldmann : >Hi. > >Is there a standard way of conditional compilation, >e.g., to turn parts (on any level) of a score on and off? > Yes, look up \tag. HTH Urs >From a programmer's standpoint, >I'd want booleans

booleans and conditional compilation?

Hi. Is there a standard way of conditional compilation, e.g., to turn parts (on any level) of a score on and off? >From a programmer's standpoint, I'd want booleans, and branching, something like let foo = true % or false, somewhere at the top of the file, % o

Re: changepitch compilation error

Thank Richard and Thomas, it works! I report here what I did in case others have the same problem (and like me are beginner): - open the file changePitch.ly in frescobaldi - then menu "Tools/Update with convert-ly..." - in the dialog box, in the "From version", enter 2.18.0 and in the "To version"

Re: changepitch compilation error

2016-02-24 10:49 GMT+01:00 Gianmaria Lari : > I've used "changePitch.ly" in the past without problem but when I tried > today I get some compilation error. I'm using lilypond 2.19.35 with > Frescobaldi. Well, I don't know about changePitch.ly- If it is LSR, pl

Re: changepitch compilation error

use convert-ly ... On Wed, 2016-02-24 at 10:49 +0100, Gianmaria Lari wrote: > I've used "changePitch.ly" in the past without problem but when I > tried today I get some compilation error. I'm using lilypond 2.19.35 > with Frescobaldi. > > > This is the co

changepitch compilation error

I've used "changePitch.ly" in the past without problem but when I tried today I get some compilation error. I'm using lilypond 2.19.35 with Frescobaldi. This is the code I'm trying to compile (it should be an example from the changepitch.ly author): \include "cha

Re: compilation problem when using add-grace-property

king code (named grace_notes_and_ledger_lines.ly) was already uploaded to this thread (just above your post), so in the future someone may come across this. Thanks again and take care, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/compilation-problem-when-using-add-grace-property-tp15

Re: compilation problem when using add-grace-property

Gilberto Agostinho writes: > SOLVED, so I will post the solution here: > > David Kastrup wrote me "You are deleting all preexisting details without > replacement". So basically what needed to be done is that I should have > written... > > 'details 'beamed-lengths (3.26 3.26 3.26 3.26) > > ...inst

Re: compilation problem when using add-grace-property

ample: grace_notes_and_ledger_lines.ly <http://lilypond.1069038.n5.nabble.com/file/n158044/grace_notes_and_ledger_lines.ly> -- View this message in context: http://lilypond.1069038.n5.nabble.com/compilation-problem-when-using-add-grace-property-tp158000p158044.html Sent from the User mailing list

Re: compilation problem when using add-grace-property

On 01/16/2014 12:30 PM, Gilberto Agostinho wrote: Peter Bjuhr wrote >I get "Exited with exit status 1." (Ubuntu 13.10). >Could you point me to a reference how to use this? I don't think I understand what you meant. I meant only that if you where using any reference from the manual or somewh

Re: compilation problem when using add-grace-property

d-grace-property 'Voice 'Stem 'details 'beamed-lengths (3.26 3.26 3.26 3.26)) } } } } %%%%%%%% -- View this message in context: http://lilypond.1069038.n5.nabble.com/compilation-problem-when-using-add

Re: compilation problem when using add-grace-property

Gilberto Agostinho writes: > Hello all, > > I am trying to figure out why a code of mine is not compiling, and I found > that this is related to the add-grace-property. The error I receive is: > *Exited with return code -1073741819.* > > Here are two minimal examples. The top one compiles, the bo

Re: compilation problem when using add-grace-property

;details '((beamed-lengths 3.26 3.26 3.26 3.26))) } } } } -- View this message in context: http://lilypond.1069038.n5.nabble.com/compilation-problem-when-using-add-grace-property-tp158000p158029.html Sent from the User mailing list archive at Nabble.com. ___

Re: compilation problem when using add-grace-property

On 01/16/2014 10:29 AM, Gilberto Agostinho wrote: I am trying to figure out why a code of mine is not compiling, and I found that this is related to the add-grace-property. The error I receive is: *Exited with return code -1073741819.* \vers

compilation problem when using add-grace-property

7;((beamed-lengths 3.26 3.26 3.26 3.26))) } } } } Actually, every modification to 'Voice 'Stem in the add-grace-property works fine, except for 'details. Am I doing something wrong here? And in case this is relevant, I am running

Re: compilation error when using stemlet over rests

Done. Issue 3617: Compilation error when using stemlet over rests https://code.google.com/p/lilypond/issues/detail?id=3617 -- View this message in context: http://lilypond.1069038.n5.nabble.com/compilation-error-when-using-stemlet-over-rests-tp152356p152362.html Sent from the User mailing

Re: compilation error when using stemlet over rests

8->[ r8 c''8 a,8] >> } >> >> But this clearly isn't the case on my first minimal example above. So well, >> though I already found the solution to my problem (I would not want to use >> kneed beams anyway), I though I should s

  1   2   3   >