Re: Tuning description at beginning of TabStaff

On 31/01/2023 15:07, Valentin Petzel wrote: > Hello Jean, > > this does not work on 2.24. Do you happen to know what changed to make this > work on 2.25? commit 86cdf5a56d123f3b1145e3eaba09805d6e43453e Author: Jean Abou Samra Date: Tue Oct 4 21:57:10 2022 +0200 Make Staf

Re: Translating “Extending LilyPond” — any takers?

On 22/01/2023 21:06, Jean Abou Samra wrote: > If you are interested in translating this into another language, > please let me know. The translation is done in .po files, like > most translation workflows (but not the one for the official > documentation). There is now a com

Re: Tuning description at beginning of TabStaff

On 30/01/2023 22:45, Stefan E. Mueller wrote: > This works for me, but I wonder if the vertical position of the individual > tablature lines could be accessed and used for the positioning of the > letters instead of doing things by hand. Yes, it's possible. Try \version "2.25.1" % doesn't

Re: Changes to png file while using \omit Accidental

On 31/01/2023 05:52, Rajesh Baskar wrote: > Hello Experts, > > I'm facing a unique issue or it would be because of my limited knowledge of > Lilypond. I have 2 identical Lilypond files, the only difference being that > one has \omit Accidental in it. You can see in the mage attached that >

Re: Tweak Slur direction "neutral"

On 30/01/2023 23:08, Ahanu Banerjee wrote: > Perhaps the documentation could be amended to clarify how neutral direction > is handled for slurs? There are two documentation pages here that mention > slur orientation but don't describe the calculation that occurs in > \slurNeutral: >

Re: Strange behaviour of multiple \include’d documents

On 30/01/2023 22:26, Immanuel Asmus wrote: > Hello Jean, > > actually, I /did/ subscribe. I wonder why my subscription was unsuccessful. I > just tried again. It didn't work this time either. I approved your message again. Did you receive the confirmation email after filling the subscription

Re: Strange behaviour of multiple \include’d documents

Hello Immanuel, Welcome to this list. For your information, I had to approve your message manually as a list administrator because you are not subscribed to the list yet. Please fix this by subscribing on https://lists.gnu.org/mailman/listinfo/lilypond-user (note that once subscribed, you can

Re: breaking vertical alignment of dynamic items

On 30/01/2023 12:38, Werner LEMBERG wrote: > > What is the 'official' way to break the alignment between, say, a > crescendo wedge and a subsequent forte sign? What I want is automatic > placement of the 'f' by LilyPond as if there were no crescendo wedge. > > ``` > { > e1\< | g''1\ff | > } >

Re: Tweak Slur direction "neutral", Re: Tweak Slur direction "neutral"

On 30/01/2023 08:19, Werner LEMBERG wrote: > >>> When I attempt to change the "direction" property of a slur, >>> whether that is with \tweak or \override, I cannot set the >>> direction to neutral (0). UP (1) and DOWN (-1) work fine, but when >>> setting to 0, I get the following error:  >>> >>>

Re: Frescobaldi crashes on startup

> Le 30 janv. 2023 à 09:26, Valentin Petzel a écrit : > >  > Hello Jean, > > This seems to come from PyQt5, so maybe downgrading that one will solve this. > Also you might want to report the problem directly to Frescobaldi: > > https://github.com/frescobaldi/frescobaldi/issues > > so it

Re: Tweak Slur direction "neutral"

On 30/01/2023 02:20, Ahanu Banerjee wrote: > When I attempt to change the "direction" property of a slur, whether that is > with \tweak or \override, I cannot set the direction to neutral (0). UP (1) > and DOWN (-1) work fine, but when setting to 0, I get the following error:  > > "Assertion

Re: Define "tweak" function

On 29/01/2023 23:45, Ahanu Banerjee wrote: > How can I define a function that applies one or more tweaks to the object > that comes after it?  > > example: I want the following expression to be a function called "\makeRed": > -\tweak color "red" > > so that I can type \makeRed \downbow instead

Re: substitution function variable name

On 22/01/2023 18:31, Jean Abou Samra wrote: > Le 22/01/2023 à 18:22, Darren Ng a écrit : >> Thanks. The following works: >> >>    accOne = >>    #(define-music-function >>    (x    ) >>    (ly:pitch?) >> #{ >>    $x 8 $x 8 >

Re: Clef change after end-repeat before break -- how?

>> Under 2.22 I do not get extra space. > > That’s still more curious. On 2.22.2 I get a warning > that the break is overwritten by another event, so we > don’t get the line break that I had specified and wanted. It's expected. 2.22 doesn't accept mid-measure breaks without a bar line. You need

Re: Clef change after end-repeat before break -- how?

On 28/01/2023 06:52, Ole V. Villumsen wrote: > Thanks, everyone, for your contributions. > > First of all Jean. Your code gives me exactly what I wanted. I haven’t > learned to use the internals, but see here that it’s useful. > >> Not sure, but my guess is that LilyPond might be trying to make

Re: Clef change after end-repeat before break -- how?

On 28/01/2023 16:51, David Kastrup wrote: > Jean Abou Samra writes: > >>> Le 28 janv. 2023 à 08:01, Darren Ng a écrit : >>> >>> [subject] How to define a macro that expands to a percussion "pitch"? >> >> >> It may be worth

Re: How to define a macro that expands to a percussion "pitch"?

> Le 28 janv. 2023 à 08:01, Darren Ng a écrit : > > [subject] How to define a macro that expands to a percussion "pitch"? It may be worth noting that LilyPond does not have macros, only variables and regular functions. Call me pedantic, but I think it is helpful not to conflate the two.

Re: Clef change after end-repeat before break -- how?

On 27/01/2023 22:35, Ole V. Villumsen wrote: > Hi, I am typesetting a movement with a repeat and a clef change right after > the repeat. I have a suitable line break where the repeat ends and the clef > change happens. Default Lilypond sets the new clef within the repeat, before > the

Re: Choir-Parts - working with \tag#' - Mulitmeasure Rests not printed

On 27/01/2023 11:06, Christian Hummer wrote: > Dear specialits, > > I'm workin on Choir-Parts with Solists. I store the music in single files > (e.g. soprano, alto,...). Each of the voices has Solo-Parts while the choir > is muted. I want to have > > 1. the choir partes (print only the choir

Re: jeté

On 26/01/2023 14:16, Werner LEMBERG wrote: > > >> jetéMarkup = >> \markup \undertie \pad-x #0.3 >> \pattern #4 #X #0.1 \musicglyph "dots.dot" > > Note that this kind of markup is not only used for jeté but also for > staccati under a slur if the note has a stem tremolo, as shown in the >

Re: jeté

On 26/01/2023 10:24, Martín Rincón Botero wrote: > Dear Jean, > > thank you very much for this! I only changed the horizontal distances > of the dots to 0.1 as in \pattern #4 #X #0.1. If it's not too hard, is > there any way to make this behave like an articulation (say, like a > staccato)

Re: jeté

On 25/01/2023 22:57, Martín Rincón Botero wrote: > Dear list, > > is there any way to make this markup mockup of a jeté symbol into a > proper articulation (so that Lilypond knows how to give it an > appropriate direction, f. ex.)? I suspect a Scheme workaround might be > possible :-). > >

Re: Translating “Extending LilyPond” — any takers?

On 22/01/2023 21:06, Jean Abou Samra wrote: > The same goes for https://scheme-tutorial.readthedocs.io/, > which is currently available in English and French. Actually, > this one might be both shorter and less technical for a translator, > and more important to translate. However,

Re: scheme-sandbox

On 24/01/2023 15:26, Mark Mathias wrote: > I've taken up Jean Abou Samra's invitation to develop my understanding of > Scheme through the scheme-sandbox. I'm on Windows 10 with Guile 2.2.7 in a > command prompt window. The command prompt looks correct:  > > scheme@(#{ g100}#)>. > > > I

Re: Repeat Segno with MIDI

> Le 23 janv. 2023 à 15:52, Mats Bengtsson a écrit : > >  > > > On 2023-01-22 21:17, Jean Abou Samra wrote: >> Le 22/01/2023 à 21:05, Mark Mathias a écrit : >>> I'm not seeing a post from anyone else exactly on this issue, so... >>> >&

Re: Repeat Segno with MIDI

On 22/01/2023 22:03, Jean Abou Samra wrote: > Le 22/01/2023 à 21:58, Jean Abou Samra a écrit : >>   \volta   1        {   a4 a4 a4 a4   } >>         >> ~~ >>   \volta      

Re: Repeat Segno with MIDI

Le 22/01/2023 à 21:58, Jean Abou Samra a écrit :   \volta   1        {   a4 a4 a4 a4   }         ~~   \volta       Stupid mail client mangling indentation... I hope it'll work this time

Re: Repeat Segno with MIDI

Le 22/01/2023 à 21:25, Mark Mathias a écrit : Jean, Ahh... of course. I had forgotten that LilyPond doesn't require the braces for a single note, but does for anything more. Well... that is true in a sense, but from the way you phrase it, I have the impression that the underlying logic that

Re: Repeat Segno with MIDI

Le 22/01/2023 à 21:05, Mark Mathias a écrit : I'm not seeing a post from anyone else exactly on this issue, so... I like the new repeat structure: https://lilypond.org/doc/v2.24/Documentation/notation/long-repeats#segno-repeat-structure The example works with the whole note after volta 1, but

Translating “Extending LilyPond” — any takers?

Hi, [Sent to lilypond-user, BBCed to lilypond-devel] After almost two years of promising myself I would integrate https://extending-lilypond.readthedocs.io/ into the official LilyPond documentation someday while never doing it, I decided to officialize the status quo that it would be maintained

Re: substitution function variable name

Le 22/01/2023 à 18:22, Darren Ng a écrit : Thanks. The following works: accOne = #(define-music-function (x) (ly:pitch?) #{ $x 8 $x 8 #}) My ultimate goal is a function which does the following accTwo = #(define-music-function (x

Re: Override note properties in markup,note or rhythm

Le 22/01/2023 à 14:11, | || | | a écrit : Thank you for the really comprehensive answer! You solved a few other problems I was struggling with in the process. I don't get why this kind of diversity with overriding properties would have any purpose for a user. I mean, I see there are different

Re: substitution function variable name

Le 22/01/2023 à 17:33, Jean Abou Samra a écrit : Le 22/01/2023 à 17:20, Darren Ng a écrit : Define substitution function accOne() as: accOne = #(define-music-function (x    ) (ly:music?)    #{ $x8 $x8 $x8 $x8 $x8    #}) Call accOne

Re: substitution function variable name

Le 22/01/2023 à 17:20, Darren Ng a écrit : Define substitution function accOne() as: accOne = #(define-music-function (x) (ly:music?) #{ $x8 $x8 $x8 $x8 $x8 #}) Call accOne() with: \accOne f Expected output is: f8 f8 f8

Re: Override note properties in markup,note or rhythm

Le 21/01/2023 à 17:26, | || | | a écrit : Hiya! I'm trying to find a gentle solution for the problem I encountered. I overrided flag stencil in general Score, but it turns out that this doesn't influence notes in \tempo, \note and \rhythm functions. I there a possibility to influence those

Re: LilyPond 2.25.1

 > Le 21 janv. 2023 à 20:43, Knute Snortum a écrit : > Am I missing something? The download page seems to still be pointing at > 2.24.0. The main download page https://lilypond.org/download.html always points at the current stable release because that is what most people want. The current

Re: autobeaming over rests

Le 19/01/2023 à 21:35, Werner LEMBERG a écrit : The NR says that autobeaming doesn't work over rests. In some situations this means a lot of additional work. As an example, consider a piece that uses almost exclusively a saltarello-like rhythm: ``` \time 6/8 d8[ r d] d[ r d] ``` I now wonder

Re: N in markup command exported as I with an underlying dot

Le 07/01/2023 à 20:48, Jean Abou Samra a écrit : In short: use the official binaries provided on lilypond.org for now. This has been fixed now. You should be able to install LilyPond from Homebrew and use it without this bug. Best, Jean OpenPGP_signature Description: OpenPGP digital

Re: Title font changed?

Le 14/01/2023 à 10:30, Bart Kummel a écrit : Hi Jean, Thanks for your reply. Very insightful! I wonder why Google didn’t come up with a link to this issue… Anyway, it looks like the solution will be merged into Homebrew’s main soon. I might be able to just wait for it. I’ll keep an eye on

Re: irrational meters

Le 18/01/2023 à 01:29, David Zelinsky a écrit : No, it's really not quirky. A "rational" number is a ratio of two integers. An irrational number is one that cannot be so expressed. The word "ratio" comes from Latin for calculation. The common english usage of "rational" meaning sensible

Re: irrational meters

Le 18/01/2023 à 01:08, David Zelinsky a écrit : As another professional number theorist and musician (though not a composer), I also find this use of "irrational" to mean "non-dyadic" very grating. But I once said as much on the Music Engraving Tips facebook group, and got summarily shot down

Re: Help understanding event listeners

Le 17/01/2023 à 10:10, Saul Tobin a écrit : What I can't figure out is why when my autoKeysigEngraver broadcasts a KeyChangeEvent, it gets picked up by the Key_engraver but not by the autoTransposeEngraver. What do you mean? If I insert ly:message calls, I see the event from

Re: Completion_heads_engraver for line-ends only?

Le 17/01/2023 à 20:33, Graham King a écrit : I'm not really sure what best practice is here; it might be that these collisions are just to be expected? (I can certainly live with them). I don't have experience with this type of music, but my first question would be: what is the

Re: Completion_heads_engraver for line-ends only?

Le 17/01/2023 à 18:31, Graham King a écrit : I'm preparing an edition of de Wert's motet "Ascendente Jesu in naviculam" which has an extended stretto section with dotted rhythms across barlines. For this, Harm's Mensurstriche example in the Learning Manual produces a mostly beautiful result.

Re: Making two functions into one

Le 16/01/2023 à 22:58, David Kastrup a écrit : From the Lilypond-Extending manual: 1.2.1 LilyPond Scheme syntax The Guile interpreter is part of LilyPond, which means that Scheme can be included in LilyPond input files. There are several methods for including

Re: Making two functions into one

Le 16/01/2023 à 15:12, | || | | a écrit : So I thought about delete one nested (list) and try it: nd =  #(define-music-function (number) (integer?)   (make-music   'TimeSignatureMusic   'numerator   8   'denominator   8   'beat-structure   

Re: Unicode accidentals vs. Markup accidentals,Re: Unicode accidentals vs. Markup accidentals

Le 16/01/2023 à 16:57, Kieren MacMillan a écrit : Hi all, In any case, please submit this to the LSR! I was *just* going to look at this to see if it could be improved viz-a-viz Jean’s suggestion that callbacks using after-line-breaking are often better done with grob-transformer. [Yes, I

Re: Unicode accidentals vs. Markup accidentals, Re: Unicode accidentals vs. Markup accidentals

> Le 16 janv. 2023 à 15:07, Mark Knoop a écrit : > >  > At 12:51 on 16 Jan 2023, Werner LEMBERG wrote: >>> \new Staff { >>> \override TextScript.before-line-breaking = >>> #(lambda (grob) >>> (ly:grob-set-property! grob 'text >>>(markup #:replace >>>

Re: Old scheme code not working in lilypond 2.25.0

Le 16/01/2023 à 00:21, Graham King a écrit : My first steps into recent versions of lilypond are ruthlessly exposing my ignorant copy-&-paste approach to scheme... I'm pretty sure that the following code worked fine under lilypond 2.18, but throws errors under 2.25.0: \version "2.25.0" %

Re: Obscure error message from 2.25.0

I forgot the second part of the question: Le 15/01/2023 à 20:20, Graham King a écrit : Before I start laboriously bisecting the file, is there a way to get an error message that points to one or more lines of code in the file? Try #(ly:set-option 'compile-scheme-code) (Caveat: not

Re: Obscure error message from 2.25.0

Le 15/01/2023 à 20:20, Graham King a écrit : I've just run convert-ly on a 600+ line file and its \include files, from 2.19.40 to 2.25.0. Nothing seemed to change apart from the \version statement, but on trying to compile the file, I get: Processing `/tmp/ly' Parsing...ERROR: In

Re: how would one cross-reference two [or more] books?

Le 14/01/2023 à 21:51, Jeff Olson a écrit : On 1/13/2023 1:27 PM, Jean Abou Samra wrote: LilyPond 2.24.1 is planned for the end of January or early February. Whether it includes this mostly depends on whether Ivan Maidanski has released BDWGC 8.2.3 by then. Thanks for the update, Jean

Re: defineBarLine confusion

Le 14/01/2023 à 07:14, David Zelinsky a écrit : I have submitted a bug report, and I'm working on submitting a patch. Did you see that Harm has already submitted a patch for this? https://gitlab.com/lilypond/lilypond/-/merge_requests/1813 Best, Jean OpenPGP_signature Description: OpenPGP

Re: Font change in 2.24.0 Figured bass "4"

Le 14/01/2023 à 18:27, Richard Shann a écrit : I didn't get a response to this email, ?? You got a reponse from Werner last Monday. While there can be distribution delays on this list, you were in the direct recipients of the email so it is a mystery if it didn't reach you. You can always

Re: Image width issue

Le 14/01/2023 à 00:22, Rajesh Baskar a écrit : Hi Jean, I don't think I saw your response.Here is the question again - The solution that you gave makes the 1st image match the width of the 2nd image by reducing it. Can the 2nd images width match the 1st images width by increasing it.

Re: Key Signature Bug in 2.24.0,Re: Key Signature Bug in 2.24.0

Le 13/01/2023 à 10:16, Werner LEMBERG a écrit : Regardless of that, it is indeed a severe bug: No need to ever align key signatures vertically, AFAIK. Simply left-align them. I have opened an issue for this: https://gitlab.com/lilypond/lilypond/-/issues/6520 OpenPGP_signature Description:

Re: defineBarLine confusion

Le 13/01/2023 à 23:37, David Zelinsky a écrit : How should I best go about conveying this to the developers? See https://lilypond.org/bug-reports.html Thanks, Jean OpenPGP_signature Description: OpenPGP digital signature

Re: how would one cross-reference two [or more] books?

> Turns out, ironically, that I am now having to add lots more bookparts so > that garbage doesn't build up to where it triggers a third-party GC bug on > Windows. Still waiting for that fix RSN (2.24.1++?) LilyPond 2.24.1 is planned for the end of January or early February. Whether it

Re: Title font changed?

> Le 13 janv. 2023 à 20:19, b...@kummelweb.nl a écrit : > > Hi, > > Since I upgraded tot Lilypond 2.24, I noticed that the title font changed. It > looks much more like standard Times New Roman now, instead of the beautiful > Lilypond text font. (See the attached images: old.png is how it

Re: New list admin

Le 10/01/2023 à 22:17, Jean Abou Samra a écrit : In order to increase the bus factor, I would like to nominate one or two other regulars as admins. If you feel like it, please let me know. Thanks to Mark Knoop for accepting this task. He is now a co-admin. Best, Jean OpenPGP_signature

Re: Image width issue

Le 12/01/2023 à 05:44, Rajesh Baskar a écrit : Hi Jean, Thanks for your help this works. But I have a question, this solution makes the 1st image match the width of the 2nd image by reducing it. Can the 2nd images width match the  1st images width by increasing it. Try \version "2.24.0"

Re: Key Signature Bug in 2.24.0,Re: Key Signature Bug in 2.24.0

Le 13/01/2023 à 10:16, Werner LEMBERG a écrit : I just discovered this huge bug in the recent release of 2.24.0 which wasn't in the previous version. What previous version did you test this with? For me, the output is the same in 2.22 and in 2.18.2. Regardless of that, it is indeed a severe

Re: Key Signature Bug in 2.24.0

Le 13/01/2023 à 09:34, nitra...@posteo.net a écrit : Hi all, I just discovered this huge bug in the recent release of 2.24.0 which wasn't in the previous version. What previous version did you test this with? For me, the output is the same in 2.22 and in 2.18.2. Best, Jean

Re: Feedback request on image formats

Hello, Le 12/01/2023 à 20:01, NickS a écrit : Personally I certainly much prefer vector formats, as these scale much better in documents, are more editable if customisation is required, and they can easily be batch-converted into raster formats of the required resolution if needed. My main

Re: alteration-glyph-name-alist location?

Le 11/01/2023 à 00:10, leonardlthomp...@gmail.com a écrit : Hi. Does anyone know which file in the installation has the definition of the alteration-glyph-name-alist variable ? Or alterationGlyphs ?  I'm trying to access how triple sharps and triple flats get engraved. Thanks! Hello, For

Re: Image width issue

Le 11/01/2023 à 01:38, Rajesh Baskar a écrit : Hi Jean, I don't know if I'm doing this wrong as suggested by you, but I'm still not getting the results. The main point is not using \tweak transparent ##t, but using the same drawing for the note heads in both cases so that they have the

Re: Feedback request on image formats

Le 10/01/2023 à 23:35, Abraham Lee a écrit : If I had a vote, and if PDF really can be seamlessly converted Yes, it can. pdf2svg in.pdf out.svg (https://manpages.ubuntu.com/manpages/impish/man1/pdf2svg.1.html) In the opposite direction: rsvg-convert in.svg -f pdf -o out.pdf The only

Feedback request on image formats

Hi, This is a little call for feedback, especially from users of the \epsfile markup command. (To be clear, I'm not speaking "in the name of the development team", just in my name.) Over the past year and a half, LilyPond has gained a new output backend based on the Cairo graphics library.

Re: Image width issue

Le 10/01/2023 à 22:33, Rajesh Baskar a écrit : Hi, I have 2 staffs, one with the 3rd note hidden and another replacing the 3rd note with a red dot. But the 2 staffs are not having the same width. What do I need to do make the 2nd staff the same width as the 1st staff. Please see the image

New list admin

Hi, As per the discussion last October (https://lists.gnu.org/archive/html/lilypond-user/2022-10/msg00047.html) I have been made an admin for the lilypond-user, lilypond-devel and bug-lilypond mailing lists. (If you're wondering, there was some delay on the GNU side). I don't view this as

Re: Is there a simple way to test for command line options?

Le 10/01/2023 à 19:11, Timothy Lanfear a écrit : The function ly:command-line-options returns a string with all the -d options. The backend option is set to svg when when generating svg output and absent by default. \version "2.22.0" #(let* ((options (ly:command-line-options))     (svg   

Re: Question about custom articulation

Le 10/01/2023 à 08:12, Rip _Mus a écrit : Hello, I'm trying to define a new articulation, based on two stencils (above and below the staff), that I wrote. I succeeded in making two distinct articulations. However, the attempt to create a single articulation, which chooses the stencil based on

Re: Missing end-of-stave barline?

> Le 9 janv. 2023 à 07:56, Mark Probert a écrit : > > Hi. > > When I run this snippet the barline at the end of first stave, which I think > should be a “||”, goes “missing” (there is no barline at all). > > Is there a correct way of setting the end of stave barline in this kind of >

Re: Fit to one/n pages

Le 09/01/2023 à 01:08, Kieren MacMillan a écrit : Hi Mark, Okay. I did that and when I move the \paper (yes, my bad, I did write \page) into the \bookpart it generates a separate PDF for each \bookpart Hmmm… It should generate a page break between bookparts, but shouldn’t generate a new

Re: Fit to one/n pages

Le 09/01/2023 à 00:51, Mark Probert a écrit : [...] \song-one \song-two Make that \book {   \bookpart { \song-one }   \bookpart { \song-two } } Best, Jean OpenPGP_signature Description: OpenPGP digital signature

Re: Fit to one/n pages

Le 08/01/2023 à 23:45, Mark Probert a écrit : Jean, Following on. If my understanding is correct, each \book has a single \page. Did you mean \paper? So if my score consists of multiple \bookparts and I adjust the \page block, that impacts all the \bookparts? Yes, it means each

Re: Custom engraver to modify bent grace notes

Le 08/01/2023 à 14:58, Nate Whetsell a écrit : you can get the moment of the current time step in the engravers using (ly:context-current-moment context) Thanks, this is a huge help. Thank you also for putting together the Extending LilyPond  

Re: Resize \rhythm in mixed markup

Apparently, top-level markups are interpreted with \paper, although grob-interpret-markup interprets with a real \layout? \version "2.24.0" #(define-markup-command (whats-layout layout props) ()    (interpret-markup layout props (symbol->string (ly:output-def-lookup layout

Re: Resize \rhythm in mixed markup

Le 08/01/2023 à 13:36, Thomas Morley a écrit : I aimed at a smaller size and all Beams and (flagged) Stems should end at the same height. Can this be achieved more easily? For the time being I would just use a music variable, e.g., \version "2.24.0" setup = {   \set fontSize = -5  

Re: Resize \rhythm in mixed markup

Le 08/01/2023 à 11:13, Thomas Morley a écrit : Actually it works, if the \layout is placed toplevel. A bug? It's a limitation of \markup \score. \version "2.24.0" \layout {   \override Voice.NoteHead.color = "red" } \score {   \layout {     \override Voice.NoteHead.color = "blue"   }   {

Re: Fit to one/n pages

> Le 8 janv. 2023 à 06:02, Mark Probert a écrit : > > Hi. > > At the moment I’m doing quite a few lead sheets. The slightly unfortunate > thing is some of these tunes are a stave or two over a page in length. > > I thought I’d reach out and see if there is such a thing as a macro or music

Re: N in markup command exported as I with an underlying dot

Le 07/01/2023 à 20:45, Xin Guo a écrit : Hi, I’m new to lily pond. Somehow when I try to export “N” in markup command. It’s shown up as an I with an underlying dot in the PDF. When I copy it and pasted in the browser, it’s shown up as “N”. Not sure what’s the issue here. Can someone help me?

Re: \stopStaff \startStaff bug

Le 07/01/2023 à 19:16, Jean Abou Samra a écrit : "\dt + warning if not used" Come to think of it: For sure, we don't need a warning about \dt (or grace skips) not being used in the case where there are no zero-length events at that point. The grace note problem is extremely genera

Re: \stopStaff \startStaff bug

Le 07/01/2023 à 18:43, David Kastrup a écrit : Well, this was sort of saying that there may be no silver bullet, but we may have to pick between chrome and aluminum ones. Sometimes there is a solution that blends better into human expectations than strict logic. That's possible. In my

Re: Custom engraver to modify bent grace notes

Le 07/01/2023 à 18:41, Nate Whetsell a écrit : Hi, I have a question about using a custom engraver to modify how grace notes appear when LilyPond’s new string bending is applied to them. This is the first custom engraver I’ve attempted to write, so I think I’ve overlooked something rather

Re: \stopStaff \startStaff bug

Le 07/01/2023 à 18:32, Kieren MacMillan a écrit : David’s interpretation of my idea isn’t correct. I never suggested letting the second Staff start after the grace note, simply that decisions for that Staff should be made independently of the Staff that contains the grace music. Here’s a set

Re: \stopStaff \startStaff bug

Le 07/01/2023 à 17:58, David Kastrup a écrit : In that case, the NoteHead one has no effect, because \once applies to the next time step only, and the next time step is for a grace note another voice. The recovery action of \once should likely occur after the next _local_ timestep. OK, that

Re: \stopStaff \startStaff bug

Le 07/01/2023 à 17:50, Kieren MacMillan a écrit : Hi Jean, That sounds like you want to make all zero-length events happen before the grace by default, but that is not always desirable, as \once \set/\override shows. I would say the exact opposite: by default, all zero-length events should

Re: \stopStaff \startStaff bug

Le 07/01/2023 à 17:17, David Kastrup a écrit : I disagree. We have grace fixups in sequential music that do this (zero-length events before grace music are executed before the grace) and the same reasonably could be done with simultaneous music. That's more complex, but not terribly so. Some

Re: \stopStaff \startStaff bug

Le 07/01/2023 à 17:11, Kieren MacMillan a écrit : Could you explain this a bit more, please? This is a position I’ve never quite understood about Issue #34: I would love to see an input where I can’t determine the output with certainty just from the input. Just take the example I gave

Re: \stopStaff \startStaff bug

Le 07/01/2023 à 16:48, Kieren MacMillan a écrit : Hi all, [ It sometimes makes me wonder if we need a concept of "infinitesimal time", to allow disambiguating ] Yes, the concept of 0-cycles, that can be allowed to execute in order for decisions to be made at the end of the timestep once

Re: problems with release 2.24 on iMac M1 with Ventura 13.0.1

Le 07/01/2023 à 16:20, Mario Bolognani a écrit : Yes, you’re right Jean, using Scores in Desktop you can update all your files in batch mode. One more question: the updated files remain in Terminal and the files in Scores are not updated… Possibly another Terminal command is necessary?

Re: \stopStaff \startStaff bug

Le 06/01/2023 à 00:37, Lukas-Fabian Moser a écrit : The Staff_symbol_engraver is not really equipped to deal with multiple \startStaff / \stopStaff events at the same point of time. I would not call the current Staff_symbol_engraver behavior a bug, but a feature. You will see that your

Re: Conflict between articulate.ly and \accacciatura in 2.24.0

> Le 7 janv. 2023 à 10:42, Lukas-Fabian Moser a écrit : > > Hi Gordon, > >> Am 07.01.23 um 10:00 schrieb Gordon Bower: >> >> When I tried to recompile a piece I had written in 2.22.1 with 2.24.0, I got >> a mysterious error message: >> "Exited with return code -1073741784." >> >>

Re: problems with release 2.24 on iMac M1 with Ventura 13.0.1

Le 07/01/2023 à 00:46, Jean Abou Samra a écrit : Le 06/01/2023 à 22:22, Mario Bolognani a écrit : Thanks a lot Jean, apparently with Terminal convert.ly operates correctly, but of course this is not a practical procedure for frequent use. If you start using the command line more, you

Re: problems with release 2.24 on iMac M1 with Ventura 13.0.1

Le 06/01/2023 à 22:22, Mario Bolognani a écrit : Thanks a lot Jean, apparently with Terminal convert.ly operates correctly, but of course this is not a practical procedure for frequent use. If you start using the command line more, you will find that it is actually incredibly practical for

Re: problems with release 2.24 on iMac M1 with Ventura 13.0.1

Le 30/12/2022 à 17:00, Mario Bolognani a écrit : Ok, I’ll try to explain what I have done for convert.ly: First, following your suggestion, I forced the use of the tools’ #! lines: Then in Frescobaldi after having used the command convert.ly, this was the result: And, after this Fatal

Re: Frescobaldi & edition engraver

Le 06/01/2023 à 00:26, Michael Dietz a écrit : Thank you Laurie, I just upgraded to Ubuntu 22.04 and had Frescobaldi problems. Looking at your log it looks like qpageview is the culprit - it was with me too. You can install a working version by 1) pip install qpageview Unfortunately this

Re: Frescobaldi & edition engraver

Le 05/01/2023 à 17:20, Michael Dietz a écrit : I have three follow-up questions concerning Flatpak-Frescobaldi: The PDF next to the .ly files seems to be unchanged. Why doesn't it update? Most likely, you forgot to save the .ly file after changing it, so what you see is a temporary .pdf

Re: Unexpected placement of accidental

Le 05/01/2023 à 10:17, Ahanu Banerjee a écrit : If I wanted to override the position of this single accidental, how might I do so? Use extra-offset. \version "2.24.0" \language "english" \relative {   \clef bass   \key a \major   <     \tweak Accidental.extra-offset #'(-0.35 . 0) f,    

<    4   5   6   7   8   9   10   11   12   13   >