Re: Tweaking completion ties

> It didn’t work in the \alterBroken command (perhaps because it’s accessed > before line breaking?) \alterBroken does not support subproperties yet. Best, Jean signature.asc Description: This is a digitally signed message part

Re: embed lilypond into godot application

Le mercredi 26 juillet 2023 à 01:54 +1000, Andrew Bernard a écrit : > > What is godot, if I may ask? Presumably this thing? https://godotengine.org/ https://en.wikipedia.org/wiki/Godot_(game_engine) signature.asc Description: This is a digitally signed message part

Re: System delimiters for middle of stave

Le lundi 24 juillet 2023 à 22:23 +0100, Alex Voice a écrit : > > > I tried replacing the replicate-stil code with your version, but the whole > code does not now seem to compile, giving the message  > > “Guile signaled an error for the expression beginning here > > #(let ((book-handler (if

Re: Tweaking completion ties

Hi, If you just want to tweak both parts of the broken tie that extends over the line break, you should simply put the override before the note where it starts, like this: \version "2.24.1" \relative c' { 1~ 1~ 1~ 1~ \override Tie.direction = #UP 1~ \break 1 R1*3 } If you want to

Re: Suggestion: Hooks for formatting titling fields

Le dimanche 23 juillet 2023 à 23:23 +0200, Valentin Petzel a écrit : > But I feel that this is a bigger issue. Generally the issue here is that > systems-per-page only cares about systems of music and not about anything > else > that may be placed on the page, as one can see here: > > \paper

Re: embed lilypond into godot application

Le lundi 24 juillet 2023 à 10:09 +0200, Stjepan Horvat a écrit : > Hi guys, > I'm trying to embed lilypond score into simple godot application which would > follow music. > One idea that comes to mind would be to have a single svg/png image and have > positions (pixels) of each bar. > Another idea

Re: Suggestion: Hooks for formatting titling fields

Le dimanche 23 juillet 2023 à 14:36 -0400, Kieren MacMillan a écrit : > While we‘re talking about this… :) How difficult would it be to separate > titling from systems in the spacing engine? I would love it — and I know > others would, too! — if Lily could easily/automagically put [e.g.] score

Re: Suggestion: Hooks for formatting titling fields

Le dimanche 23 juillet 2023 à 16:55 +0200, Valentin Petzel a écrit : > Hello Pondmates, > > I’ve just stumbled upon a music SE question regarding the formatting of page > numbers. Currectly we do not have any hooks to change formatting of such > things, rather the general approach to this is

Re: Are hyphens no longer required to prefix postevent tweaks?

Le vendredi 21 juillet 2023 à 23:38 +0200, David Kastrup a écrit : > > As of 2.25.6, the difference between the two forms of \tweak no longer > > appears necessary: globally replacing thousands of "- \tweak ..." with > > just "\tweak ..." now seems to work perfectly. > > Don't. If the syntax

Re: Cropped output

Le jeudi 20 juillet 2023 à 17:52 +0200, Henrik Frisk a écrit : > None at all, but maybe I'm misunderstanding the command. Here's what I do: > > $ lilypond --pdf -dcrop='#t' test6.ly > GNU LilyPond 2.24.1 (running Guile 3.0) > Processing `test6.ly' > Parsing... > Interpreting music... >

Re: Cropped output

Le jeudi 20 juillet 2023 à 15:55 +0200, Henrik Frisk a écrit : > Hi, > > I know that this is an old question but I'm seeing some strange behavior. On > Mac OS none of the suggested alternatives appear to work though it did on > Linux. The only way I can seem to get a cropped output is to output

Re: How to return markup conditionally?

Le jeudi 20 juillet 2023 à 00:06 +0200, Jean Abou Samra a écrit : > There is definitely a point in having this rule that constants > are read-only. What I don't find fine is Guile segfaulting on > a simple set-car! call. I mean, either doing it silently or > checking and raising an exc

Re: How to return markup conditionally?

> I debugged for half an eternity on a failed assertion because the failed > assertion pinpointed a call site that was not actually being used other > than some unrelated code jumping to its abort () call in order to save a > byte of instruction. Wow, thank you for sharing that anecdote. It is

Re: How to return markup conditionally?

Le mercredi 19 juillet 2023 à 21:57 +0200, Jean Abou Samra a écrit : > (In recent Guile versions, it can even lead to true "nasal demons" undefined > behavior ­— when you enable byte-compilation and optimizations, (set-car! '(1 > . 2) 3) outright segfaults. The time I l

Re: How to return markup conditionally?

Le mercredi 19 juillet 2023 à 22:11 +0200, Valentin Petzel a écrit : > Good point, I didn’t think of that! Also I know that using a callback on > bound-details would work as well, but I’m not sure if this is the best way to > replace a single value in an alist (what if you want to change other

Re: How to return markup conditionally?

> ``` >        (let* ((bound-details (ly:grob-property grob 'bound-details)) >   (left (assoc-get 'left bound-details)) >   (left (assoc-set! > left > ``` If you add another red text spanner, you will see that it gets the text "foo" in spite of \once.

Re: Tweak grobs with callback output?

>     \tweak color #(if (equal? DOWN (ly:grob-property grob 'direction)) red > blue) You just forgot to wrap the expression in `(lambda (grob) ...)` . Best, Jean signature.asc Description: This is a digitally signed message part

Re: How to supply missing end-of-system bar line?

Le mardi 18 juillet 2023 à 18:07 -0400, Trevor Bača a écrit : > Is this intentional? And, if it is, is there a way to re-supply the missing > bar line? Yes, and yes. This is a frequent question, so I've wondered a couple times if we should come up with a new command to recommend instead of \bar,

Re: How to test grob color?

Hi Trevor, In Scheme, the `=` function is for comparing numbers, and nothing else. For colors, you want `equal?` . ``` ~ $ guile2.2 GNU Guile 2.2.7 Copyright (C) 1995-2019 Free Software Foundation, Inc. Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'. This program is free

Re: Distance from barline to first note of bar

Le dimanche 16 juillet 2023 à 08:51 -0400, Kieren MacMillan a écrit : > I know > describes the different spacing-style options, but can you comment on > why/whether one would/should set both this spacing-style *and* another (e.g., >

Re: Getting grob Y position (spacing error)

Hi, > (ly:grob-set-property! follower 'details '((used-proportion > . 0.5))) ;;; HERE I would like to have user-input instead of 0.5 > ;; would prefer the above line to read something like: > ;; (ly:grob-set-property! follower 'details >

Re: Placement of tuplet numbers

This sounds similar to https://gitlab.com/lilypond/lilypond/-/issues/6346 . signature.asc Description: This is a digitally signed message part

Re: Distance from barline to first note of bar

I won't comment on the default value, but: > Can the gap be extended by some ratio of global staff size? (I'm assuming a > fixed increase would make problems with scores with a larger basic staff > size, like my own.) Sure: ``` \layout { \context { \Score \override

Re: detecting parallel fifths and octaves in figured bass

Le vendredi 14 juillet 2023 à 21:08 +, Eef Weenink a écrit : > Maybe somebody already made a script for this: > > In figured bass there are two fundamental rules: Avoid parallell octaves and > or fifhts. > So it would be nice to have some scipts what checks for this. So if two voices > have

Re: [BUG] WORG example for ob-lilypond is no longer working as described

Le jeudi 13 juillet 2023 à 08:33 +0200, Dr. Arne Babenhauserheide a écrit : > This is the lilypond-file in questoin: > https://hg.sr.ht/~arnebab/draketos-songbook/browse/delfini-tune.ly?rev=tip > > Converted to PNG in a two step process: > lilypond -dbackend=eps -dno-gs-load-fonts

Re: \partCombine when notes are far apart

>  When I use \partCombine and the notes are more than a ninth apart the stems > do not connect.  Can I force a longer stem on beats 3 and 4 in this example? This is intended. To customize the behavior, you should use the optional argument to `\partCombine`, which goes before the two music

Re: Using functions "parenthesize" in lilypond 2.24.1

Le mardi 11 juillet 2023 à 12:19 +0300, Виноградов Юрий a écrit : > Hello. I'm typing an accordion part. And in my left hand I need to put a note > in the \parenthesize function. But since this note takes up space in the > measure. Example: beat 2/4 and note 1/8 - it turns out to be 5/8 in a

Re: Using functions "parenthesize" in lilypond 2.24.1

Le mardi 11 juillet 2023 à 12:54 +0300, Виноградов Юрий a écrit : > How will be correct. Tell. To create a new topic on this list, you should send a new email to lilypond-user@gnu.org . You should use the same method as to create a new email to anybody. You should not take a digest you received

Re: Staff switch over page break spoils vertical spacing

Le samedi 08 juillet 2023 à 17:44 +1000, Vaughan McAlley a écrit : > When a staff-switch line goes over a page break, the first system in the next > page is stretched and may cover the next system. In the example here, it > nearly touches, but in a full score the top system is stretched beyond the

Re: Broken Slur + Key Signature Collision

Le mercredi 05 juillet 2023 à 18:45 -0600, Abraham Lee a écrit : > All, > > What property is used to control the spacing between the second part of a > broken slur's left control point and the preceding key signature? I'd like to > increase this spacing a bit as the current collision is quite

Re: Tuplet brackets do not respect edge skips

Hi, There are three different ways to have some invisible pause: 1) `s` 2) `\once \hide Rest  r` 3) `\once \omit Rest  r` None of these are equivalent. A hidden rest is basically just like a normal rest, with all the typesetting done with this normal rest in mind, except that the rest is

Re: Adjust midi volume mix between chord progression and melody

Hi, This question seems to have found an answer here: https://music.stackexchange.com/questions/130684/lilypond-midi-volume-mix-between-chord-progression-and-melody (On any forum, it's usually considered polite to link cross-posts so that people can notice your question has already been

Re: Tuplet brackets do not respect edge skips

> Le 4 juil. 2023 à 18:28, Gregory Evans a > écrit : > >  > Hi everyone, > I'm wondering if anyone can explain a lilypond behavior I did not expect. I > noticed today that tuplet brackets appear over skips in the middle of the > tuplet but not over skips which appear at the edges of the

Re: for-each?

Le lundi 03 juillet 2023 à 22:08 +0200, David Kastrup a écrit : > Ugh, that's a can of worms.  #xxx will only accept a context-dependent > set of values and reject values not fitting the context.  But the > context includes whether or not, for example, we are in lyrics mode. > For that reason \new

Re: How to submit a feature request (issue)

Le dimanche 02 juillet 2023 à 23:25 -0700, Curt McDowell a écrit : > > I don't think it's tenable to expect anyone to keep a separate version of > LilyPond for each unique \version called for by all the scores in their > library. In the current system, that would be the only way to guarantee >

Re: Music function to manage a moment and beat for the Staff and the Voice

Le dimanche 02 juillet 2023 à 18:47 +0200, Volodymyr Prokopyuk a écrit : > Thank you very much for multiple options! I've decided to try the first one. I > still have two difficulties > * How to create alist from the components ax, ay, ... (see comment in the code > below)? The control-points

Re: QUIBBLE: Interesting use (mis-matched) of left and right quotes of quoted strings in Lilypond output

Le dimanche 02 juillet 2023 à 12:24 -0700, Kenneth Wolcott a écrit : >   Is this deliberate? It's an oldish convention. As I understand it, in the old times of computing, “ ' ” quotes, which are straight today, were more like “ ´ ” . You can find the same in TeX (where the pure ASCII markup for

Re: for-each?

Le dimanche 02 juillet 2023 à 15:05 -0400, Pierre-Luc Gauthier a écrit : > How can I go about using for-each in this example for the group function to > accept an arbitrary number of parts ? You can't — for-each is not the right tool for this. for-each is a purely imperative tool: it runs the

Re: Music function to manage a moment and beat for the Staff and the Voice

Le dimanche 02 juillet 2023 à 14:28 +0200, Volodymyr Prokopyuk a écrit : > I wonder if there is a **way to define a music function with default > parameters** and be able to selectively specify some parameters using the > **parameters names** leaving all other parameters with their default

Re: How to submit a feature request (issue)

Le samedi 01 juillet 2023 à 11:30 -0700, Curt McDowell a écrit : > I tend not to use convert-ly because I feel upgrading a file version > would unfairly force anyone who wants to compile my music to upgrade > their LilyPond installation. Upgrading might not be straightforward when > using a

Re: Music function to manage a moment and beat for the Staff and the Voice

Le samedi 01 juillet 2023 à 16:42 +0200, Volodymyr Prokopyuk a écrit : > I'm trying to define a music function as below, however I've faced > difficulties with parameter predicates, visibility of the Staff object, and > flexibility of the solution ideally without code duplication > > **Desired

Re: How to submit a feature request (issue)

Le samedi 01 juillet 2023 à 12:46 +0200, Valentin Petzel a écrit : > Maybe Lilypond should also give a warning if it on a lower language version. > The assumption here is that lower language versions are generally compatible > with higher program versions, but this is not true. So basically we

Re: Lilypond 2.25.4 prints kanji, but not kana

Le vendredi 30 juin 2023 à 23:52 +0100, Joseph Mudrak a écrit : > I am typesetting a score with a Japanese title, but can't get any kana to > print. When I try to engrave a document, I get a series of errors like this: > > ``` warning: cannot get postscript name > programming error:

Re: How to submit a feature request (issue)

Le vendredi 30 juin 2023 à 15:36 -0700, Stu McKenzie a écrit : > > I'm not sure how to submit a feature request issue. > > I'd like to request the following change to the LilyPond parser: > > One feature that would be useful is for the LilyPond parser to output > the following version numbers:

Re: PDF file gets "-1" appended

Le mardi 27 juin 2023 à 21:17 +0200, Valentin Petzel a écrit : > Hello Knute, > > so you are using books to allow specification of the midi filename. This is > probably a fine usecase, but it still seems like a bit of an abuse of the book > mechanic to me. Rather I’d adapt the midi output name

Re: overriding digit-names

Le jeudi 29 juin 2023 à 18:21 +0200, David Kastrup a écrit : > Are there any Scheme interpreters/versions that didn't at any point of > time?  Just curious. To be honest, I have no idea. I just know a bit about the Scheme standards because of school projects, but I don't have practical

Re: overriding digit-names

Le jeudi 29 juin 2023 à 17:56 +0200, David Kastrup a écrit : > No, none of the "standards" say anything like that.  #(...) is a > self-quoting form, like #t and #f and numbers and strings and some other > things.  Quoting them doesn't change a thing. > > And to be honest, I don't know of any

Re: overriding digit-names

Le mercredi 28 juin 2023 à 21:35 -0400, William Rehwinkel via LilyPond user discussion a écrit : > Dear John, > > You need to add another pound sign before the list. StrokeFinger.digit-names > is a vector, with is a guile-specific construct not a standard list. Just FYI in passing, vectors are

Re: PDF file gets "-1" appended

Le lundi 26 juin 2023 à 16:39 -0700, Knute Snortum a écrit : > I've run into some odd behavior in LilyPond.  If your PDF-only is a score but > your MIDI-only is a separate  book, the PDF file gets "-1" appended to the > file name.  So for instance, with this code: > > File name: test.ly > > %%%

Re: Metronome marking with non-integer value

Le lundi 26 juin 2023 à 18:54 +0200, Simon Albrecht a écrit : > Would the relatively new > > \layout { >    \enablePolymeter > } > > be appropriate here? (plus of course \cadenzaOn and \remove > Time_signature_engraver) It won't really help — \enablePolymeter serves to enable different time

Re: O Canada with Ukrainian lyrics

Le dimanche 25 juin 2023 à 23:30 -0600, ericmcint...@mac.com a écrit : > I am totally new to Lillypond and want to compile lyrics and music to O Canada > for a Canada Day BBQ this Saturday with 50 newcomers from Ukraine. I > downloaded a version of the song sheet from this wiki site and added

Re: Displaying StaffGroupBar after tweak

Le vendredi 16 juin 2023 à 15:24 +0200, Jean Abou Samra a écrit : > > > I don't have the time to find a solution right now, but for a start, here is > already a more "M" MWE: [...] This appears to work better: ``` \version "2.24.1" #(define (Workaround_

Re: Da capo

Le dimanche 25 juin 2023 à 19:58 +0200, Stephan Schöll a écrit : > Hey Ponders > > It feels like I struggle with almost each and every repeat variant. > While I already have a couple of variants in my score colletion to look > up, it seems that I'm missing a "da capo al fine" variant (state of

Re: Metronome marking with non-integer value

Le dimanche 25 juin 2023 à 15:59 +0300, Lib Lists a écrit : > Hi Valentin, > > thank you so much for your time, it works perfectly and the detailed > explanation is really helpful and welcome (now I need to experiment > more on my own to fully understand everything). > > Interestingly, and this

Re: Using \after 8 \turn with beamed notes when stem is up produces a turn under the beam

Le samedi 24 juin 2023 à 16:54 -0700, Knute Snortum a écrit : > Hi, community. > > I was using \after 8 \turn to produce a delayed turn with beamed eighth-notes > in voice one and the turn renders under the beam.  Here is an MWE: > > \version "2.25.6" > > \relative e'' { \voiceOne e4 \after 8

Re: consistent height for \rightHandFinger marks

Le samedi 24 juin 2023 à 15:26 -0400, John Asmuth a écrit : > Thanks for the reply. Here's a stand-alone file that demonstrates what I see. > > I'd like each arrow to be at the same vertical position. Why do you have this line? \set strokeFingerOrientations = #'(up) signature.asc

Re: clef bass_16

Le vendredi 23 juin 2023 à 01:11 +0200, Jakob Pedersen a écrit : > You need to use \clef "bass_15" to get it down another octave, not 16. > That's a step too far. Coincidentally, someone was having this exact same problem on the French-speaking list last week. Perhaps LilyPond should emit

Re: LyricExtender snippet: still the best way?

> Le 22 juin 2023 à 19:03, Kieren MacMillan a > écrit : > > Now… Is there any benefit to this — or something similar — being rolled into > the main codebase? If so, maybe it’s the perfect size for my first MR > [finally!]? It should be rather easy, but the lyric extender code is in C++

Re: LyricExtender snippet: still the best way?

Le jeudi 22 juin 2023 à 09:14 -0400, Kieren MacMillan a écrit : > Hi all, > > The callback shown in this snippet is something that is automatically > included in all my engravings that include lyrics; it is designed to remove > LyricExtenders that fall below a minimum-length threshold. > > Is

Re: Start repeat after Ending bar line

Le mercredi 21 juin 2023 à 12:55 -0400, dfro a écrit : > Hello fellow music engravers, > > I would like to have a staff system end with an 'ending bar line', then > \break the staff, and then have the next staff system begin with a > 'start repeat'. > > The following code causes the first

Re: LSR 1169 issue: missing point-and-click

Le mardi 20 juin 2023 à 11:43 +0200, Simon Albrecht a écrit : > Hello everyone, > > it’s great to have LSR 1169 and it seems to be working as it should—many > thanks to Jean Abou Samra and Werner Lemberg! > > However I’m sorry to write this mail because there is one issue

Re: stem position

Le mardi 20 juin 2023 à 17:05 +0200, achar a écrit : > > Hello everyone. > > Following the installation of lilypond 2.24, I find myself on all stemDown > stem files placed on the right of the notehead. > > As I am using jazz fonts and the lilyjazz.ily file, I think the error comes > from

Re: Periodic extra blank in between-systems spacing

Le mardi 20 juin 2023 à 11:50 -0400, PMA via LilyPond user discussion a écrit : > > Dear LP List, > > I've drafted a score for solo piano.  Its systems are of two types: either a > PianoStaff (with the usual 2 internal staves) or a single independent Staff.  > The systems are grouped into

Re: Vertical Spacing with Tuplets and Lyrics

Le mardi 20 juin 2023 à 23:44 +0300, Lib Lists a écrit : > I think the problem is caused by Lilypond putting too many systems on the > page (have no idea why). The precise positioning of grobs such as tuplet brackets depends on the horizontal spacing, which is not known yet during page

Re: broken slurs shorter than ties

Le vendredi 16 juin 2023 à 20:21 +, Werner LEMBERG a écrit : > Suprisingly, no – at least I couldn't find an entry.  I've now created > > https://gitlab.com/lilypond/lilypond/-/issues/6631 And there is now https://gitlab.com/lilypond/lilypond/-/merge_requests/2043 See, if you report

Re: Lilypond 2.24.1 can't compile any score

Le vendredi 16 juin 2023 à 10:35 -0700, Joshua Armenta a écrit : > After upgrading from 2.20 to 2.24 to get graphical notation, any score I try > to run in Lilypond has this error: > > warning: `(gs -q -dNODISPLAY -dNOSAFER -dNOPAUSE -dBATCH > -dAutoRotatePages=/None -dPrinted=false >

Re: \uppercase function

Le vendredi 16 juin 2023 à 15:13 +0100, Mark Knoop a écrit : > Wait, I see there is already a \fontCaps command - does that not work? That's small caps, not normal caps. signature.asc Description: This is a digitally signed message part

Re: \uppercase function

Le vendredi 16 juin 2023 à 09:41 -0400, Kieren MacMillan a écrit : > Hi all! > > Anyone have a good \uppercase function they could share? > > I tried to make one, and it doesn’t throw an error, but also doesn’t work: > > ``` > \version "2.25.2" > > #(define-markup-command (uppercase layout

Re: Displaying StaffGroupBar after tweak

Le vendredi 16 juin 2023 à 14:59 +0200, Karim Haddad a écrit : > I customize staffs using the following tweak: > [...] > > Whenever there is a pagebreak (explicit or automatic), the StaffGroupBar > disappears. > I know i am missing something here. > Here is a somehow not so moderate MWE

Re: TrillSpan help

Le vendredi 16 juin 2023 à 19:36 +1000, Mark Probert a écrit : > > Many thanks, Jean. > > I kinda knew there would be a simple solution, but I had trouble finding > “TrillSpanner.” Is there a way of finding out about the various objects and > their names? Sure. Method 1: you look at the

Re: broken slurs shorter than ties

Le vendredi 16 juin 2023 à 05:37 +, Werner LEMBERG a écrit : > In my opinion, the worst flaw of LilyPond's otherwise excellent > formatting, a flaw that essentially everyone encounters rather > quickly, is that broken slurs are almost always shorter than broken > ties (it should be exactly

Re: Moving tempo-markup

Le vendredi 16 juin 2023 à 08:53 +0200, Johannes Roeßler a écrit : > > Hi, > > how can I raise the tempo markup to get some space in case I have other > markups in place: > > ``` > \version "2.24.0" > {\tempo "Andante" c'4^\markup \italic "mezza voce" c' c' c' } > ``` Try adding some

Re: TrillSpan help

Le vendredi 16 juin 2023 à 17:54 +1000, Mark Probert a écrit : > Hi. > > According to the manual "A hairpin ending on a downbeat will stop at > the preceding barline." By default, I've found this to be true of > \startTrillSpan \stopTrillSpan as well. > > With hairpins there is an override

Re: Passing pitch to function

Le jeudi 15 juin 2023 à 12:25 -0400, Pierre-Luc Gauthier a écrit : > ``` >    '( >   (piccolo . ((fullName "Piccolo") (transposition #{bf'#}))) >   )) > ``` Like many Scheme beginners, you got tripped up by quoting. Change that to ``` #(define instrumentsInfo `( ; ^^^

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 th

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

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: 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)

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

Re: shifting accidentals horizontally

Le lundi 12 juin 2023 à 17:02 +, Werner LEMBERG a écrit : > Please consider the example code below.  The first line shows > LilyPond's default, the second line shows what I need.  As can be > seen, the solution in the second line is imperfect – I just did the > most basic changes to

Re: How to generate \scaleDurations values procedurally

Le lundi 12 juin 2023 à 13:49 +0200, Lib Lists a écrit : > > Dear Jean, fantastic, thank you so much! And all clear. > > Concerning the staff size and page layout, I think I've found > something that is not clear to me from the documentation. When > reducing the staff size to accommodate all the

Re: How to generate \scaleDurations values procedurally

[Adding back the list] Le lundi 12 juin 2023 à 12:23 +0200, Lib Lists a écrit : > On Mon, 12 Jun 2023 at 10:58, Jean Abou Samra > <[j...@abou-samra.fr](mailto:j...@abou-samra.fr)> wrote: > Dear Jean, all clear, thank you so much! I was exactly trying to > figure out th

Re: How to generate \scaleDurations values procedurally

Le lundi 12 juin 2023 à 10:23 +0200, Lib Lists a écrit : > In your example, I changed the line: #{ \new Staff { \scaleDurations #(cons > 60 i) \mus } #}) > to this: #{ \new Staff { \scaleDurations #(cons 60 i)  #(ly:music-transpose > {\mus} i)  } #}) > but clearly there's something wrong,

Re: How to generate \scaleDurations values procedurally

Le dimanche 11 juin 2023 à 23:55 +0200, Lib Lists a écrit : > Hello, > I'm (re)working on a series of pieces for player piano. I'd like to > find a way to generate all the \scaleDurations values so that I don't > have to type them by hand. In the example below they follow a simple > pattern

Re: making arpeggios with straight lines

Le dimanche 11 juin 2023 à 12:18 -0400, John Asmuth a écrit : > Hi everyone, > I'm trying to draw an up or down arrow next to a chord. This is common > notation in classical guitar for strum direction. > > It seems that the most likely way to make this happen is to use \arpeggio and > set the

Re: How to make a blank page

Le dimanche 11 juin 2023 à 14:41 +0100, Paul McKay a écrit : > Hi > I'm engraving a piece in two sections. The first section fits on one page and > the second one is rather longer and requires 2 pages. I would like the pdf to > have a blank page at the start because I > often view pdf's with 2

Re: help me to install app

> Le 9 juin 2023 à 17:52, a...@daomauht.com a écrit : > >  > Hello everyone, I have downloaded for my windows. I really don't know where > to find the file to install please help me. > Welcome. Have you seen the tutorial? https://lilypond.org/doc/v2.24/Documentation/learning/installing

Re: Trying and failing to engrave a segno repeat with coda: More alternatives than repeats.

Le jeudi 08 juin 2023 à 22:56 -0700, Kenneth Wolcott a écrit : > Hi; > > Trying and failing to engrave a segno repeat with coda: > > warning: More alternatives than repeats.  Junking excess alternatives > > Attachments: > > I have screenshots for the following from the original pdf I am >

Re: In-staff fermata with 2.25.

> Le 7 juin 2023 à 23:52, Thomas Morley a écrit : > > thanks! > Though, below commit-message does not explain why a tweak works, but > an override not. > Personally I think this is very strange and apart from that, totally > undocumented. > Do we have other, but similar, situations where a

Re: In-staff fermata with 2.25.

Le mercredi 07 juin 2023 à 23:07 +0200, Thomas Morley a écrit : > Hi, > > this came up in the german forum: > https://lilypondforum.de/index.php/topic,1247.msg6512.html > > How to print fermata _in_ staff with 2.25.? Amusingly, the same question was asked on the French-speaking list today.

Re: Error in scheme-sandbox, LilyPond 2.24.1

> Le 6 juin 2023 à 20:29, Knute Snortum a écrit : > >  > While going through Jean's Extending LilyPond tutorial... > > https://extending-lilypond.gitlab.io/en/scheme/expressions.html > > ...I came upon instructions to type this expression into the scheme-sandbox: > > (skip-of-length #{ {

Re: Magnetic snap and whiteout on LyricText: warnings

Le mardi 06 juin 2023 à 15:56 +0200, Simon Albrecht a écrit : > Hi Jean, hi Werner, > > On 05.06.23 22:28, Jean Abou Samra wrote: > > Well, for my defense, I did also post a revised version of the > > “magnetic lyrics” snippet: > > > > https://www.mail-

Re: Magnetic snap and whiteout on LyricText: warnings

Le lundi 05 juin 2023 à 22:24 +0200, Jean Abou Samra a écrit : > Le lundi 05 juin 2023 à 22:22 +0200, Jean Abou Samra a écrit : > > Le lundi 05 juin 2023 à 21:23 +0200, Simon Albrecht a écrit : > > > Hello everyone, > > > > > > I don’t know where the “L

Re: Magnetic snap and whiteout on LyricText: warnings

Le lundi 05 juin 2023 à 21:23 +0200, Simon Albrecht a écrit : > Hello everyone, > > I don’t know where the “Lyric syllable magnetic snap” snippet is mainly stored https://lsr.di.unimi.it/LSR/Item?id=1154 signature.asc Description: This is a digitally signed message part

Re: Magnetic snap and whiteout on LyricText: warnings

Le lundi 05 juin 2023 à 22:22 +0200, Jean Abou Samra a écrit : > Le lundi 05 juin 2023 à 21:23 +0200, Simon Albrecht a écrit : > > Hello everyone, > > > > I don’t know where the “Lyric syllable magnetic snap” snippet is mainly > > stored > > > > https://

Re: Get the margin values

Le lundi 05 juin 2023 à 15:34 +0200, Simon Albrecht a écrit : > However, I can’t say why the right margin isn’t yet known by the time it  > is queried. Well, don't use “$defaultpaper”, that's the toplevel \paper block, which is almost always not what you want. If your markup command is used on

Re: chord.ly to extract notes from chords breaks with new Guile

Better make that: > ``` > \version "2.24.1" > > #(define ((Keep_only_engraver i) context) > ``` > ``` #(define ((Keep_only_performer i) context) ``` > > ``` > (let ((j 0)) > (make-performer > (listeners >((note-event performer event) > (unless (eqv? i j)

Re: Embed files other than source code in PDF file?

Le mercredi 31 mai 2023 à 17:23 -0400, William Rehwinkel via LilyPond user discussion a écrit : > Dear list, > > I have been using the line > > #(ly:set-option 'embed-source-code #t) > > to embed the lilypond files I used in the PDF, but was wondering if there > was a

Re: Library to embed LilyPond in other programs

Le mercredi 31 mai 2023 à 13:31 +1000, Andrew Bernard a écrit : > > I'd still be interested to know in rough outline how Denemo lets you add > single notes in a GUI and have the feedback from lilypond so quickly. As far as I know, it does not use LilyPond for the GUI preview that you edit on

Re: Library to embed LilyPond in other programs

Le mercredi 31 mai 2023 à 11:00 +1000, Andrew Bernard a écrit : > How does Denemo do it? Mr Shann? > It generates LilyPond code (which you can also export if I'm not mistaken). signature.asc Description: This is a digitally signed message part

<    1   2   3   4   5   6   7   8   9   10   >