Re: Tweaking the string number: no circle, and to the right?

Le 04/01/2023 à 01:43, Alasdair McAndrew a écrit : Many thanks indeed for that heads-up!  But I have another problem, in that I'm typesetting my chords as per the practice of the time, which was to have the stem of the upper note up, and the stem of the lower note(s) down.  I have done this

Re: Frescobaldi & edition engraver

Le 05/01/2023 à 09:08, Michael Dietz a écrit : Thank you Jean, 1. I will try Flatpack 2. Here I was not precise enough: I am already up to date in this repo. git pull says that I am "Already up to date." I apparently forked it back then. The upstream is

Re: Unexpected placement of accidental

Le 05/01/2023 à 07:26, Ahanu Banerjee a écrit : Hello, Please see the example below. I tried running it in 2.22 and 2.23 as well, and got the same result. Am I missing an obvious reason that the c-natural accidental is placed so far to the left? \version "2.24.0" \language "english"

Re: Frescobaldi & edition engraver

Hello, Le 05/01/2023 à 01:21, Michael Dietz a écrit : Hi, after a few years, I come back to LilyPond. I just installed the latest stable version 2.24. Thanks a lot for it. Working on Ubuntu 22.04, I now have two issues: - How to use Frescobaldi (I really enjoyed it but it crashes on

Re: weird fonts in volta endings

Le 04/01/2023 à 22:42, Flaming Hakama by Elaine a écrit : Hi, I was hoping someone could help me figure out how to fix this font issue. For quite some number of years, I've been using this function that prints custom text for volta ending labels. But now it is producing strange results.

Re: Allowing a collision

Le 04/01/2023 à 17:24, Paul Hodges a écrit : I have a score which has two staves, for unrelated instruments.  To reproduce the composer's notation, I occasionally need to join the stems of simultaneous notes on the two staves. In a piano staff this is catered for using the \crossStaff

Re: flat symbol in text?

> Le 03/01/2023 15:45 CET, Matthew Pierce a écrit : > > > How might I display the text "Bb Major," but with the flat symbol instead of > a lower case "b"? You will find \flat in the index. https://lilypond.org/doc/v2.24/Documentation/notation/lilypond-index.html Best, Jean

Re: Extending Lilypond

Le 31/12/2022 à 16:43, Rip mus a écrit : May I ask if you have any advice to better understand how all the "pieces" that make up Lilypond work?I don't know exactly where I intend to get with this study, but I think it will be really useful for me. Well, my first reaction was point to

Re: Strange font problem in 2.24.0

Le 02/01/2023 à 14:31, Jean Abou Samra a écrit : Le 31/12/2022 à 18:23, Sven Axelsson a écrit : I sent the font file to you privately. Thanks, I opened https://gitlab.com/lilypond/lilypond/-/issues/6508 It was diagnosed as a bug in the font (!), not in LilyPond. OpenPGP_signature

Re: Subdividing beams

Le 02/01/2023 à 14:44, Renato Biolcati Rinaldi a écrit : Hello and Happy New Years I am trying to engrave this piece as per attached, I am going crazy trying to figure out how to replicate the exact beaming of the image. When you don't manage to make LilyPond understand what beaming you

Re: Strange font problem in 2.24.0

Le 31/12/2022 à 18:23, Sven Axelsson a écrit : I sent the font file to you privately. Thanks, I opened https://gitlab.com/lilypond/lilypond/-/issues/6508 OpenPGP_signature Description: OpenPGP digital signature

Re: Footnotes in Lyrics

Le 02/01/2023 à 11:31, Pierre Perol-Schneider a écrit : Hi Johannes, Here's a little hack: \markup \footnote \null "(1) footnote text" \score { <<   { a' b' c'' d'' c'' b' a' }   \addlyrics {      One two      \markup \concat { three \raise #.7 \teeny (1) }      four five six se -- ven   }  

Re: Getting grob Y position (spacing error)

Le 31/12/2022 à 19:43, Gregory Evans a écrit : It appears to be the case that there is a limitation to how far to the right notes can be checked. Let’s call the starting note |A| and the stopping note |B|. It seems like the boundary is if the start-offset of |B| is further forward than the

Re: Strange font problem in 2.24.0

Le 31/12/2022 à 17:11, Sven Axelsson a écrit : On Sat, 31 Dec 2022 at 16:33, Jean Abou Samra wrote: Le 31/12/2022 à 14:56, Sven Axelsson a écrit : > Hi list, > > I have just updated my sheet music archive to LilyPond 2.24.0. It went > well, but I am seei

Re: Strange font problem in 2.24.0

Le 31/12/2022 à 14:56, Sven Axelsson a écrit : Hi list, I have just updated my sheet music archive to LilyPond 2.24.0. It went well, but I am seeing a strange font encoding problem. I have installed LilyPond on a Mac M1 running MacOS 13.1 with Homebrew which builds from source using Guile

Re: Extending Lilypond

Le 30/12/2022 à 13:27, Rip _Mus a écrit : Hello everyone, for three days I have been immersed in the documentation written by Mr. Samra, on how to define a new grob, a new event and a new engraver that takes care of engraving the new grob, following a specific command. Nice to hear :-)

Re: A question about a scheme function with two input notes

Le 30/12/2022 à 15:07, David Kastrup a écrit : Jean Abou Samra writes: Le 30/12/2022 à 13:51, David Kastrup a écrit : However, it doesn't work right now for local variables, like function parameters, in #{ ... #}. I think you may underestimate the cost of magic involved with making

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

Le 30/12/2022 à 16:24, Mario Bolognani a écrit : Many thanks Jean, useful suggestions, but , possibly for my ignorance of technicalities, convert.ly is still not working. Hm. This is like going to a doctor and complaining 'I am feeling bad' without further information. If you don't tell

Re: A question about a scheme function with two input notes

Le 30/12/2022 à 13:51, David Kastrup a écrit : However, it doesn't work right now for local variables, like function parameters, in #{ ... #}. I think you may underestimate the cost of magic involved with making #/$ integrate into local Scheme scoping. If you want Scheme semantics, $ offers

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

Le 30/12/2022 à 14:24, Mario Bolognani a écrit : Using LilyPond 2.24.0 with Frescobaldi 3.1.3 on iMac M1 Ventura 13.0.1, I discovered some incompatibilities: 1) convert.ly  not operating I think you're running into a Frescobaldi problem, not a LilyPond problem. See

Re: A question about a scheme function with two input notes

Le 30/12/2022 à 00:19, Alasdair McAndrew a écrit : Thank you SO very much! Such a simple thing ... (as is so often the case, certainly with my queries).  It now works perfectly. Well, as a matter of fact, you're not the first one tripped up by this. Makes me wonder if we should make it

Re: A question about a scheme function with two input notes

Le 30/12/2022 à 00:12, Alasdair McAndrew a écrit : Hello, I am typesetting some late Renaissance, early Baroque music for which a double stop (= chord with two notes) on a stringed instrument would be notated with the stem of the top note up and the stem of the lower note down.  So instead

Re: Custom gradual spanners

Le 26/12/2022 à 17:39, Rip _Mus a écrit : Hello, is there a way to modify a spanner to get a slow-fast trill (like the one in the picture)? Obviously with user-provided glyphs. Try \version "2.24.0" slowFastTrill = \tweak TrillSpanner.stencil #(lambda (grob)    (let* ((left

Re: Getting grob Y position (spacing error)

Le 26/12/2022 à 19:18, Gregory Evans a écrit : Hi Jean, I apologize for my delayed reply. I do not think I can use the VoiceFollower grob because I am not using staff changes. You can. A VoiceFollower won't be created automatically without a staff change, but you can create it yourself in

Re: How to color dynamics

> Le 23 déc. 2022 à 20:56, Paul McKay a écrit : > >  > Hi > I'm making a setting of some music with repeated melodies. The dynamics on > the second repeat are slightly different in that some appear to have been > omitted from the first time. I'd like to use the same code, but to show the >

Re: A matter of optional arguments

Le 23/12/2022 à 17:54, Rip _Mus a écrit : Hello everyone, I'm working on a function that prints a personal type of tremolo. This function has four arguments, the first and the last are optional. The first is actually optional, as you can see in the minimal exemple attached. The last, instead,

Re: Need help with usage of breve

Le 23/12/2022 à 16:50, Dave Seidel a écrit : fis1\breve This contains - fis : a pitch, - 1 : a duration, whole note, - \breve : another duration, breve. Therefore, the "fis" and "1" go together, as pitches and durations always do, and the "\breve" is alone without a pitch, which tells

Re: How to get log only

Le 23/12/2022 à 10:35, Thomas Morley a écrit : Hi, while debugging some files I'm interested in the log only, thus I'd like to avoid creating any other output. $ lilypond -dlog-file=AAALOG --formats=#f -ddelete-intermediate-files file-1.ly file-2.ly still returns .ps-files. What's the

Re: Depriciated ?

> Le 22 déc. 2022 à 17:52, Karim Haddad a écrit : > > Dear list, > > Using the latest Lilypond version 2.24.0, in my \layout section, i have two > issues: > > 1) > > \context { >\RemoveEmptyStaffContext > \override VerticalAxisGroup.remove-first = ##t > } > > The

Re: Whiteout staff lines behind beams

Le 21/12/2022 à 17:16, Kieren MacMillan a écrit : According to Wikipedia, David Maslanka is a composer who died in 2017... ? Oops! I meant Matthew, his son (who is still very much alive, and who was at the Salzburg conference with us). His father — whom I met several times — was a wonderful

Re: Mimicking `\chords` mode within `\markup`

Le 21/12/2022 à 17:56, Joel C. Salomon a écrit : \version "2.24.0" \markup { Compare \sans\concat{F\char ##x266F °/C} to \sans\concat{F\sharp °/C} to \score{\chords{\chordmode{ fis:dim/c }}} } Looks like `\chords` is aligning the sharp symbol differently (and probably using SMUFL U+E870

Re: Whiteout staff lines behind beams

Le 21/12/2022 à 16:16, Kieren MacMillan a écrit : Agreed. I recently hired David Maslanka to critique my engravings and help me finalize a housestyle — the first thing he noticed and criticized were the beams, especially all the intersections and wedges. According to Wikipedia, David

Re: Whiteout staff lines behind beams

Le 21/12/2022 à 01:26, Abraham Lee a écrit : Is there a way to turn the stencil into a composite of the original with a big block of whiteout that follows the entire group's outer skyline so it hides the staff lines? Would be a nice feature, IMO. I know the stems can be "frenched", but would

Re: spacing before acciaccatura

Le 21/12/2022 à 10:33, Owen Le Blanc a écrit : I found a number of improvements using 2.24.0, but one irritant is still there: before acciaccatura marks such as caesura and key changes are spaced differently, and so don't align with those in other staffs. Here are two simple examples. This is

Re: tremolo: 3/4 time, one dotted-half note chord, double-slash tremolo question

Le 20/12/2022 à 02:41, Kenneth Wolcott a écrit : I'm still do not understand the math (I'd like to generate a formula!) for tremolos. I also remained confused by this for a long time till I understood that the rules are pretty simple. The thing to keep in mind is that \repeat tremolo and :

Re: Difficulty running convert-ly under Linux/Ubuntu

Le 20/12/2022 à 03:52, Ralph Palmer a écrit : Greetings - Jean Abou Samra kindly pointed me in the right direction for the installation of 2.24.0 in Linux with Frescobaldi. I was successful. Then I tried running convert-ly for all my .ly files, using find . -name '*.ly' -exec convert-ly

Re: Modify flat flag appearance like beamed notes

Le 20/12/2022 à 10:53, Jean Abou Samra a écrit : Le 20/12/2022 à 06:23, William Rehwinkel a écrit : Dear list, In the following tiny example, I override some variables to do with how beamed notes are rendered, and also configure to use the flat-flag stencil. I was wondering

Re: Modify flat flag appearance like beamed notes

Le 20/12/2022 à 06:23, William Rehwinkel a écrit : Dear list, In the following tiny example, I override some variables to do with how beamed notes are rendered, and also configure to use the flat-flag stencil. I was wondering if it was possible to modify how the unbeamed flag stencil was

Re: Problems with musicxml2ly

Le 20/12/2022 à 09:36, Jacques Menu a écrit : Hello Mark, Unfortunately I do not know any way to produce a small xml  that will give this error. The file I wanted was "O holy night" by Adolphe Adam (translated into English) adapted by P. Le Bas. It came from this address:

Re: Installing 2.24.0 in Linux

Le 19/12/2022 à 23:17, Ralph Palmer a écrit : Greetings - I'm feeling stupid. I've installed new versions for years, and this time I'm totally floundering. I hope someone can give me some help. I've looked at the documentation online, Does that include this part?

Re: How to implement "f (second time p)" for midi?

Le 17/12/2022 à 04:10, Kenneth Wolcott a écrit : Thank you! I copied the right hand notes so that there would be a midi-specific version. That sounds like you want to learn about tags… See https://lilypond.org/doc/v2.24/Documentation/notation/different-editions-from-one-source#using-tags

Re: Including an EPS

Le 18/12/2022 à 01:36, Mike Kilmer a écrit : Link was incomplete. Should be https://lsr.di.unimi.it/form.php?type=snippet;id=1153;rld=m_snippet It was complete, but I should have used a space before the question mark ending my sentence. I suspect your mail client interpreted it as part of

Re: indicating rhythmic equivalence

Le 17/12/2022 à 21:07, David Kastrup a écrit : I'll make a pitch at it. My original rationale is open for discussion, but there was one; see https://gitlab.com/lilypond/lilypond/-/merge_requests/1761#note_1213670108 OpenPGP_signature Description: OpenPGP digital signature

Re: Including an EPS

Le 17/12/2022 à 21:30, Mike Kilmer a écrit : Thanks, Jean. With upgrade, compilation still failed, but it was in fact the eps file and/or its format that compiler was choking on. Here you can see the (truncated) diff btwn the (first) one that DID work (from my vector editor) and the one that

Re: indicating rhythmic equivalence

Le 17/12/2022 à 18:53, Paul Scott a écrit : A typical indication of rhythmic equivalence is to mark dotted quarter = quarter or it's many variations. The following is a simple modification of an example in 2.24.0 NR 1.3.3: Metronome marks.  I would think the part I added would give me the

Re: Including an EPS

Le 17/12/2022 à 17:41, Mike Kilmer a écrit : Hi. I'm using GNU LilyPond 2.22.2 (running Guile 2.2) The first thing I would check is whether this reproduces with LilyPond 2.24, which has been released this week. LilyPond 2.22 does not officially support Guile 2.2. Otherwise, reading the

Re: Problem let Frescobaldi recognize convert-ly in Lilypond 2.24.0 on macOS

> Le 17 déc. 2022 à 14:28, TamuraJun a écrit : > > I think it would be nice to document this somewhere since Frescobaldi is now > mentioned (and perhaps strongly recommended) in the Learning Manual. I actually think it should be fixed in Frescobaldi. Can you open an issue on its bug

Re: LilyPond 2.24.0 released!

Le 16/12/2022 à 20:39, H. S. Teoh via LilyPond user discussion a écrit : Hmm. I'm running a local Linux build of 2.24.0 (commit 916ae4111441a9426fbb9c11f7c42735eccf0cac). That is not 2.24.0, but current master. 2.24.0 is the tag v2.24.0, which the branch stable/2.24 also currently points to.

Re: Setting lytics to alternative endings

> Le 16 déc. 2022 à 15:25, Kieren MacMillan a > écrit : > > In a certain way, the unfolded example is inconsistent, right? Shouldn’t it > be something like […] > > Otherwise, you have an example with music that has a \repeat command and > lyrics that don’t… This doc example is not a

Re: Setting lytics to alternative endings

Le 16/12/2022 à 10:47, Jogchum Reitsma a écrit : Hi Jean, While this work in placing the words correctly, it is, in my case, not quite flawless. If I render the attached snippet, there is no "2"-bracket above the second alternative. But if you comment out the lyrics part, the "problem"

Re: Fwd: Setting lytics to alternative endings

Le 16/12/2022 à 10:40, Jogchum Reitsma a écrit : Hi, without a doubt it is my bad, but while I've spend quite some time looking for this in the documentation, I didn't come across it. Looked, among a lot of other places, in

Re: Installing 2.24

Le 16/12/2022 à 02:25, JxStarks a écrit : Greetings, I'm feeling rather foolish. I'm running under Windows 10 and use Frescobaldi (3.1.2) as my main interface with LilyPond. I have downloaded LilyPond 2.24 and un-zipped the files. Where is the Go button? How do I install 2.24? I haven't

Re: LilyPond 2.24.0 released!

Le 16/12/2022 à 00:34, Hendursaga a écrit : Completely rewritten, you say? Hopefully that will make it easier to update the GNU Guix package for LilyPond! I don't think so. It was a rewrite of the infrastructure for making official releases, which mostly means compiling LilyPond's

Re: LilyPond 2.24.0 released!

Le 15/12/2022 à 23:15, Paul Scott a écrit : Any idea when there will be a Debian package?  (Not that I can't install it the way I have done the all the other 2.23.x versions). [Removing informational lists from the recipients. Please don't reply to info-lilypond and info-gnu, as these are

Re: Setting lytics to alternative endings

Le 15/12/2022 à 14:57, Kieren MacMillan a écrit : Hi Jogchum, I suppose it is very simple, but I can't find it in documentation, or here on the list. How can one set different lyrics to alternative ending? It is simple — so simple, you probably didn’t think it would work: \version "2.23.14"

Re: Table of Contents, 2-column

Le 12/12/2022 à 16:59, Mark Mathias a écrit : LilyPond Friends, I wish to format a table of contents in two columns. The attached tiny file (at least as tiny as I could figure) shows a standard layout, then a clumsy visual of what I want (which has no automatic page numbering), then sample

Re: need help with 2.22 on mac

> Le 12 déc. 2022 à 08:34, Flaming Hakama by Elaine > a écrit : > Thinking about this more, it is likely that I did install the previous 2.22 > version from homebrew. > > Because it certainly was a lot slower than any previous version. > > I guess I'll try that again. > > Besides

Re: need help with 2.22 on mac

Le 12 déc. 2022 à 08:22, Flaming Hakama by Elaine a écrit :On Sun, Dec 11, 2022 at 3:53 PM Jean Abou Samra <j...@abou-samra.fr> wrote:Le 12/12/2022 à 00:45, Flaming Hakama by Elaine a écrit : > tl;dr: > > Does anyone have a download link of lilypond 2.22 that will work for > ma

Re: need help with 2.22 on mac

Le 12/12/2022 à 03:51, Mark Probert a écrit : The brew collection has lily pond at 2.22.2 (with Guile 2.2). If you already have brew installed then it is simply a matter of, from the command line, running  $ brew install lilypond Hope this helps. I would recommend against this, because

Re: need help with 2.22 on mac

Le 12/12/2022 à 00:45, Flaming Hakama by Elaine a écrit : tl;dr: Does anyone have a download link of lilypond 2.22 that will work for mac OS 12.6.1? I recently had to reinstall my mac OS.  It is now 12.6.1. Previously I had an earlier version of 12, most likley 12.1, based on the fact that

Re: Changing Header Mid-Score

Le 11/12/2022 à 18:44, Lukas-Fabian Moser a écrit : Am 11.12.22 um 10:32 schrieb Jacques Menu: Thumbs up, Jean, this is worth being in the LPNR! If I'm not mistaken, this marvelous code could easily be generalized to provide a command (during music) which sets arbitrary variables that may

Re: Tab staff - forcing a note onto a lower string

Le 10/12/2022 à 17:37, Richard Shann a écrit : Is it possible to specify the string to be used for a note when using a TAB staff? So that a lower string gets marked with a number higher than it usually goes up to (because the next higher string is ordinarily used). There is an example here

Re: Changing Header Mid-Score

Le 09/12/2022 à 23:04, Kieren MacMillan a écrit : As far as I know: 1. a separate bookpart is required to change the properties that the titling mechanism can read; and 2. a bookpart will always force a page break. Cue Jean providing code to contradict my claim in 3… 2… 1… ;) [Although

Re: after-line-breaking help

Le 09/12/2022 à 22:04, Rip _Mus a écrit : could you tell me the place, within the documentation, where I can learn more about the "after-line-breaking" property? As far as I know, there isn't more documentation about after-line-breaking than its description in the internals reference: “Dummy

Re: Breath marks

Le 08/12/2022 à 04:22, Andrew Bernard a écrit : So again, why not just use \breathe? Is there something else you need? Yes, exactly. In 2.23, use \breathe and you're done. In 2.22, use \breathe and override its text to whatever you want, as you showed, if you want a more comma-like shape.

Re: Breath marks

Le 08/12/2022 à 03:01, Molly Preston a écrit : Hello! I was wondering if there is a way to make a breath mark that is like a comma and in bold. I'm attaching a PNG file to show a small example, but I would like it much bigger. I didn't see it under breath marks and caesuras or glyphs.

Re: \tocItem within \score block, using header properties

Le 06/12/2022 à 19:05, Jean Abou Samra a écrit : Le 06/12/2022 à 18:10, Joel C. Salomon a écrit : The requirement that `\tocItem` is either outside the `\score` block or within a music variable is making it awkward for me to keep it near where the score `\header` block defines the piece title

Re: \tocItem within \score block, using header properties

Le 06/12/2022 à 18:10, Joel C. Salomon a écrit : The requirement that `\tocItem` is either outside the `\score` block or within a music variable is making it awkward for me to keep it near where the score `\header` block defines the piece title. And I have entirely failed to figure out a way to

Re: search term

Le 04/12/2022 à 18:21, Mark Stephen Mrotek a écrit : Jean, Thank you. Didn't think of slurs as "expressive marks". Shall make a note of it in my "cheat sheet", What about using the index? https://lilypond.org/doc/v2.22/Documentation/notation/lilypond-index.html In my opinion, this is the

Re: search term

Le 04/12/2022 à 14:57, Mark Stephen Mrotek a écrit : Hello, What term should I use to search for multiple slurs in chords? Thank you Mark Stephen Mrote Just read the section about slurs in the notation manual.

Re: "loco" after ottava

Le 03/12/2022 à 15:41, Thomas Morley a écrit : Granted, if I use -dcheck-internal-types I mostly wear my developer hat. But sometimes I use it even for huge custom codings as part of debugging processes. Why? What does it catch? In my view, warnings about a property being set on a grob that

Re: Different default arpeggio positions

Le 03/12/2022 à 15:58, Thomas Morley a écrit : Ofcourse. Though, it's another thing a (probably new) user has to learn, maybe scaring him/her away. For someone coming from a language like Haskell, Rust, OCaml or now even Python, pattern matching will feel already familiar. Someone new to

Re: "loco" after ottava

Le 03/12/2022 à 14:46, Thomas Morley a écrit : I didn't know about -S Thanks. Alas, this command extended as $ git log -S "check-internal-types" --oneline --author="Han-Wen" prints for me: $ git log -S "check-internal-types" --oneline --author="Han-Wen" 264570e68e Documentation: remove

Re: "loco" after ottava

[Valentin] The OttavaBracket looks like a line-spanner, but it isn’t! It doesn’t even follow the spanner interface (between notes) It does ...? OttavaBracket is not an item, therefore it is a spanner. Anything with bounds is a spanner (and consequently has spanner-interface). If for

Re: Different default arpeggio positions

Le 02/12/2022 à 23:47, Thomas Morley a écrit : I know you like pattern matching, though imho it makes things not always easier for users. Yes, I like pattern matching. No, I'm not going to stop using it :-) Sure, you have to learn it, like every construct, but it improves code clarity IMHO

Re: Vertically shift tempo prescription

Hello, Le 02/12/2022 à 21:11, Arno Waschk a écrit :   %\override MetronomeMark.extra-offset = #'(-20.0 . 20.0) Here, you are missing the context: \override Score.MetronomeMark.extra-offset = ...   ^ Without a context specified, overrides are applied in the innermost context,

Re: "loco" after ottava

Le 02/12/2022 à 02:27, Joel C. Salomon a écrit : Piece of music I have in front of me puts the text "loco." above the first note after an ottava. See also the attached example, from . The code below does not work, which makes me suspect I do not in

Re: Frescobaldi on Hi-res monitors

Le 02/12/2022 à 18:02, Abraham Lee a écrit : Touche lol. To be fair, I was in my bed when I responded to Andrew, but now that I'm back at my computer, I've checked what I've got installed: Frescobaldi: 3.2 Extension API: 0.9.0 Python: 3.6.8 python-ly: 0.9.5 Qt: 5.13.2 PyQt: 5.13.2 sip:

Re: Frescobaldi on Hi-res monitors

Le 02/12/2022 à 15:28, Abraham Lee a écrit : What version of Frescobaldi are you running? I have the same question for you. Best, Jean OpenPGP_signature Description: OpenPGP digital signature

Re: Spacing between stanzas

Le 01/12/2022 à 16:36, rev...@unitelc.com a écrit : Hi all: I used \addlyrics { \override VerticalAxisGroup.nonstaff-nonstaff-spacing.basic-distance = #4 and achieved the effect I wanted. But only for the last line of music. The other lines were unaffected. Is there a way I can get the

Re: Different default arpeggio positions

Le 02/12/2022 à 05:16, Abraham Lee a écrit : Code works perfectly, Jean, though what it's doing is a bit of a mystery. You've been very kind to provide a solution and I don't want to take more of your time on the subject, but is there some documentation somewhere that explains that commands

Re: Adding text to chord names or note names (solution)

Le 01/12/2022 à 19:04, Koen van Walstijn a écrit : Code can be found here: https://gitlab.com/kbvw/lilypond-tweaks/-/blob/master/harmonic-background.ly By the way: if you want to made a piece of code available that you think someone might want to reuse for LilyPond, you need to put it under

Re: Adding text to chord names or note names (solution)

Le 01/12/2022 à 19:04, Koen van Walstijn a écrit : Hello, (Separately reply follows to some of the specific things that were written.) In case there is interest, what I did now was tweaking the Current_chord_text_engraver from scheme_engravers.scm. It simply takes the first pitch specified

Re: Different default arpeggio positions

Le 01/12/2022 à 10:09, Thomas Morley a écrit : Ofcourse you're right advertising not to use after-line-breaking for all and everything. Though, I do understand why it's still in use. Yes, sure. My point was to advise against it, not to rebuke people who have used / are using it. Indeed,

Re: Different default arpeggio positions

Le 01/12/2022 à 07:08, Abraham Lee a écrit : Happy Holidays! A number of versions ago, I created the following function to extend the top and bottom ends of the Arpeggio grob, which I find more aesthetically pleasing (generally), though I know it's not perfect: \override

Re: LilyPond 2.23.82

Le 30/11/2022 à 23:13, Jean Abou Samra a écrit : The latter has length 0, the former has length 1/16. However, you didn't have this hack in the dynamics variables, so now your dynamics are all desynchronized. You need to remove an "s16" in both parts. One more thing: you may find t

Re: LilyPond 2.23.82

Le 30/11/2022 à 22:33, Jean Abou Samra a écrit : Le 30/11/2022 à 21:50, Galen Hazelwood a écrit : A minimized example will take some time. In the meantime, I'm attaching output from both 2.22 and 2.23.82, showing the difference. If this isn't useful, hold on, and I'll produce a minimized

Re: LilyPond 2.23.82

Le 30/11/2022 à 21:50, Galen Hazelwood a écrit : A minimized example will take some time. In the meantime, I'm attaching output from both 2.22 and 2.23.82, showing the difference. If this isn't useful, hold on, and I'll produce a minimized example when I'm free.

Re: LilyPond 2.23.82

Le 30/11/2022 à 19:33, Galen Hazelwood a écrit : Moved from 2.22.2 straight to this release. Everything seems to be fine, except that the final lines of both the 2-piano and full score of my project don't extend to the right edge of the page like they used to. It looks like "ragged-last" was

Re: Note head as a custom image chosen according to note duration

Le 30/11/2022 à 16:50, Jean Faure a écrit : Ah ok, thanks. Is there a way of keeping the original note heads, just superimpose them with a custom image? Yes, try this: \version "2.22.2" customHead = {   \once \override NoteHead.stencil =     #(grob-transformer   'stencil   (lambda

Re: Note head as a custom image chosen according to note duration

Le 30/11/2022 à 16:34, Jean Faure a écrit : Just for a test, I changed all image filenames to note4.eps. However, it turned out that the custom image is scaled differently depending on duration-log. Why? I attach the lily, eps and output pdf files. The code reads:   #(case

Re: Adding text to chord names or note names

Le 30/11/2022 à 05:26, Flaming Hakama by Elaine a écrit : I think here is where we dip into the reality that there are many different uses of chord changes. Chord symbols used for analysis are different than when used as an abbreviation for specific notes/voicings, which is different when

Re: Vertically shift tempo prescription

Le 30/11/2022 à 14:58, David Kastrup a écrit : Arno Waschk writes: Dear list, in a complex situation i need to vertically shift the result of a '\tempo \markup{\column{ ... }}' thing. Probably that could be done by a \override XXX.extra-offset = #'(0.0 . 8.0) . But what is XXX in that

Re: Adding text to chord names or note names

Hello, Le 29/11/2022 à 23:22, Flaming Hakama by Elaine a écrit : Lilypond provides ways both to choose among a few of the common approaches, and a way to define your own. It does not provide a way to use different symbols for the same chord in the same sequence.  There are workarounds for

Re: 2.23.81 coda in new staff or after blank space

Le 28/11/2022 à 06:17, Paul Scott a écrit : My current code involves a separate \score for the coda as I learned here a long time ago. As with the blank space question I haven't yet figured out how accomplish this with the new Segno structure. It's still possible to use several scores:

Re: Adding text to chord names or note names

Le 28/11/2022 à 20:27, Jean Abou Samra a écrit : The other piece of brainstorming I know about, although I didn’t chase all the discussions in the devel mailing list, is the GSoC patch. This has the same goal of making it easier to coerce LilyPond into formatting chord names the way you want

Re: Adding text to chord names or note names

Le 28/11/2022 à 15:37, Kieren MacMillan a écrit : Hi Koen, I still think it could be nice to try to write a longer-term solution. There has been a lot of work done on chord naming over the last decade, mainly as part of a Google Summer of Code project a few years ago, but essentially none

Re: comparing crashes in 2.23.81 with 2.23.14 and 2.22.1

Le 28/11/2022 à 00:24, Jean Abou Samra a écrit : FYI, this is going to remain unfixed for 2.24.0, but probably going to be fixed in the followup bugfix release 2.24.1 (probably around February). See https://lists.gnu.org/archive/html/lilypond-devel/2022-11/msg00102.html if you are interested

Re: Adding text to chord names or note names

> Le 28 nov. 2022 à 02:21, kbvw a écrit : > >  > Hi Jean, > > I just finished my reply when I saw your next message. :) > > Sorry, I was starting to forget about the "transposing" bit. > > Well, how about > > \version "2.22.2" > > t = > #(define-music-function (text) (markup?) >#{ >

Re: 2.23.81 blank bar of new line between D.S. and coda

Le 25/11/2022 à 04:08, Paul Scott a écrit : How do I add a totally blank bar (something like \stopStaff s1 \startStaff) between the D.S. and the Coda in the following example? Or a new line? \version "2.23.81" music = {   \repeat segno 2 {     c'1 1 1     \alternative{   \volta 2

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