Re: question to generating random pitches snippet

Dear Jean, thanks for Your answer. I understand now! Am Di., 13. Juni 2023 um 16:43 Uhr schrieb Jean Abou Samra < j...@abou-samra.fr>: > Le mardi 13 juin 2023 à 16:34 +0200, Stefan Thomas a écrit : > > Exactly. Sorry I've forgotten to send the link. > > > The snippet contains the expression > >

Re: shifting accidentals horizontally

Gould p91 "Altered Unisons" gives the requested layout, not the LilyPond one. Paul From: Werner LEMBERG To: Cc: Sent: 12/06/2023 18:46 Subject: Re: shifting accidentals horizontally > Not the answer to the Lilypond question, but as a reference of > comparison, here

Re: question to generating random pitches snippet

Le mardi 13 juin 2023 à 16:43 +0200, Jean Abou Samra a écrit : > Le mardi 13 juin 2023 à 16:34 +0200, Stefan Thomas a écrit : > > Exactly. Sorry I've forgotten to send the link. > > The snippet contains the expression > > (random 12 random-state) > > meaning that a random pitch between c' and

Re: question to generating random pitches snippet

Le mardi 13 juin 2023 à 16:34 +0200, Stefan Thomas a écrit : > Exactly. Sorry I've forgotten to send the link. The snippet contains the expression (random 12 random-state) meaning that a random pitch between c' and 11 steps higher (i.e., g'') is chosen. You can change that to, e.g., (random

Re: question to generating random pitches snippet

Exactly. Sorry I've forgotten to send the link. Am Di., 13. Juni 2023 um 16:15 Uhr schrieb Kenneth Flak < kennethf...@protonmail.com>: > > On 13 Jun 2023 16:12, Jean Abou Samra wrote: > >Le mardi 13 juin 2023 à 15:56 +0200, Stefan Thomas a écrit : > >> Dear community, > >> I discovered the

Re: question to generating random pitches snippet

On 13 Jun 2023 16:12, Jean Abou Samra wrote: >Le mardi 13 juin 2023 à 15:56 +0200, Stefan Thomas a écrit : >> Dear community, >> I discovered the snippet that lets you generate random pitches in Lilypond. >> How does Lilypond "know" what are the lowest, what are the highest pitches? >> How

Re: question to generating random pitches snippet

Le mardi 13 juin 2023 à 15:56 +0200, Stefan Thomas a écrit : > Dear community, > I discovered the snippet that lets you generate random pitches in Lilypond. > How does Lilypond "know" what are the lowest, what are the highest pitches? > How could I change that? Which snippet are you talking

Re: How to make a blank page

Hi Many thanks to you all for your help. I thought you might like to know that I found Simon's solution the best one. Perhaps my minimal example was a little too pared down. In reality, I use headers and footers on my music as well. So my minimal example begins: Jean Abou's suggestion \version

question to generating random pitches snippet

Dear community, I discovered the snippet that lets you generate random pitches in Lilypond. How does Lilypond "know" what are the lowest, what are the highest pitches? How could I change that? Thanks for Your help Stefan

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 found an

Re: shifting accidentals horizontally

Or rather there is the NoteColumn.ignore-collision property. If set to #t the Note column will not be added to any NoteCollision grob. The problem here is that in this case there need to be no positional correction. So we require some additional check in the engraver to apply this correction

Re: shifting accidentals horizontally

> A possible solution for this could be to do a similar thing to add > certain note columns to separate NoteCollision grobs, so they can be > spaced independently. However, it your case it should suffice to > prevent any Collisions to be detected by doing > > \once\override

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: shifting accidentals horizontally

Hello Werner, this Problem is not caused by my solution, but generally by your approach of taking the Notes with collision applied (the 8th note bb on the left, the b,e on the right) and shifting the bb until it is right of the others. This still means that the will be offcentered. So this

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

Hello Lib, this slowdown appears to be induced by forbidBreakBetweenBarLines = ##f This might be understandable: Your code will division at 30/1, 30/2, ..., 30/88, which might induce a relatively large number of potential break points. This appears to be too much for the line breaking

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 got > the following

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 notes ->