Re: Unicode accidentals vs. Markup accidentals

>>> Is there a possibility to register this or a similar function globally >>> so that all markup strings can use it? > > It is the same mechanism, and add-text-replacements! answers > Werner’s question. Thanks. I only did a quick index search for 'replace' in the NR, and there was no hit.

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

> I quite like this, but incorporating this into my previous code I > found going down TWO steps to be optically more pleasing. OK :-) > \new Staff { > \override TextScript.before-line-breaking = > #(lambda (grob) > (ly:grob-set-property! grob 'text >

Re: Unicode accidentals vs. Markup accidentals

> Lilypond ships with a text font as well as a music font. I agree > that I suspect that currently Lilypond's text font does not actually > define these Unicode music characters, so it falls back on the OS to > find them. Why not just add copies of Emmentaler glyphs to the > Lilypond text fonts

Re: Unicode accidentals vs. Markup accidentals

> IMO Lilypond should render musical Unicode characters using the same > font as the music itself, No, it should not. If you select font 'foo' for text rendering, everything should come from that font. If a certain character is not in 'foo', it is the FontConfig library rather than LilyPond

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

>> 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 bug: No need to ever align key

Re: Font change in 2.24.0 Figured bass "4"

> The figure "4" in figured bass is coming out with a stunted upright in > the new release > > 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< > %\version "2.20.0" > \version "2.24.0" > \score { > \new Staff << > \context Staff \figuremode { <4> } >

Re: Strange font problem in 2.24.0

>> It was diagnosed as a bug in the font (!), not in LilyPond. > > Yes, I saw the issue. That's extraordinarily weird. It's not. > It is one of the fonts installed with Microsoft Office so maybe this > should be reported to Microsoft. Newer versions of this font have it fixed. For example,

Re: 2.24 weirdness with slurred chords

>> Here's an MWE showing this. > > Indeed, this looks like a bug. This is now https://gitlab.com/lilypond/lilypond/-/issues/6495 Werner

Re: 2.24 weirdness with slurred chords

> Hey all. Ran into a bit of weirdness when trying to do slurred > chords. I'm wanting a slur between each of the matching notes > within the chord. Why slurs and not ties? > Here's an MWE showing this. > > \version "2.24.0" > \language "english" > > \relative c'' { > b4 b b > < b\1\=1(

Re: Whiteout staff lines behind beams

> When a beam group (especially 1/16 or shorter) crosses a staff line, it can > create some annoying skinny triangles that can be visually > distracting. [...] > > 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

Re: Feta optical sizes

> For example, I'd like to have a staff size of 16 or 17, but use > feta14 or feta11. (Untested) Try to play around redefining `feta-design-size-mapping`; see file `scm/font.scm`. Werner

Re: lilypond-book -> latex

> I need package "lilypond-book->latex". How can I download it ? If you have downloaded or installed LilyPond, you should already have the `lilypond-book` script. On the command line, say ``` lilypond-book --help ``` for a first overview of the available options; you need to add

Re: Hiding lyrics extenders on empty measures

Hello Kieren, >> I agree that LilyPond should be able to handle this, for example >> with a predefined command like `\trailingHyphen`. > > An automagic solution would be great! Please check our issue tracker whether we really don't have such a request. If not, could you open an issue?

Re: Hiding lyrics extenders on empty measures

> As it turns out, it’s Score.LyricHyphen.stencil I have to play with, > since in my actual score, the end of the word 'Kum -- ba -- ya' > occurs at the beginning of the coda [...] This is an interesting case, which probably nobody has thought of previously (at least I can't remember this ever

Re: Hiding lyrics extenders on empty measures

> Overriding Score.LyricExtender.stencil to hide the extenders seems > to be ineffective, as show below. OverridingScore.LyricText.stencil > works fine, though. Well, you have ``` Lor -- d -- | ``` If you replace this with ``` Lor -- d __ | ``` it works as expected. What

Re: Checkpoints

>> > > Oh, goodness… This is like a Plato’s Cave moment for me in Lilypond. > I honestly can’t believe I haven’t had this in my quiver. Unless > somebody (Jean? David K?) says this is somehow a sub-optimal > implementation, I am using this in everything from now on. Indeed, this looks

Re: Flexible lyric alignment,Re: Flexible lyric alignment

>>> But how do you take into account the constraints from lyrics here? >>> That is the whole problem. >> >> They should be completely ignored. > > In that case, it should be completely doable even in Scheme now. > (I started writing some code yesterday in response to Abraham that > does

Re: aligning text in text spanner

> I volunteer for opening an issue ;-). I have barely any idea of how > those commands work, much less of how to explain them to someone > else. Then do so, please! Werner

Re: Flexible lyric alignment,Re: Flexible lyric alignment

>> * In the first pass, typeset everything without stuff marked for a >> follow-up pass. > > Namely, typeset all notes? Yes. > But how do you take into account the constraints from lyrics here? > That is the whole problem. They should be completely ignored. My idea was to make the first

Re: aligning text in text spanner

> By the way, shouldn't \with-dimension(-from) be documented here > https://lilypond.org/doc/v2.23/Documentation/notation/dimensions.html > ? I don't think so. However, it makes probably sense to mention related markup commands in the 'See also' section. Do you volunteer for a MR? :-)

Re: Flexible lyric alignment

>> I think that such a fine granularity of automatic lyric adjustment >> would only be possible with LilyPond doing (at least) two >> typesetting passes, if at all. > > Can you elaborate? What would it help with? I draw my idea from LaTeX, for example handling multi-page tables (see the

Re: Flexible lyric alignment

> The main problematic measures are 5, 7, and 9/10. My tweaks are > good bandaids, but not ideal, nor perfect, but they get the job > done. I think that such a fine granularity of automatic lyric adjustment would only be possible with LilyPond doing (at least) two typesetting passes, if at all.

Re: Curious behaviour of q and a tweak

> [...] As you can deduce from the existence of the \chordRepeats > function, the substitution of q is not immediate. In contrast, > \tweak takes effect immediately by modifying each of the notes in > the chord. Since there are no notes yet in the "q" chord at the > time \tweak is applied

Re: line-width in lilypond book

>> Actually, >> >> ``` >> \begin[line-width=394\pt]{lilypond} >> ``` >> >> is also correct. > > Nope. It is backward compatibility but should not be used anywhere. > > git grep '\\begin\[' > > unfortunately shows that this isn't consistently done yet. The > problem with the old form is that

Re: line-width in lilypond book

> The correct syntax is > > \begin{lilypond}[line-width=394\pt] Actually, ``` \begin[line-width=394\pt]{lilypond} ``` is also correct. Werner

Re: another 'wrong type argument' error

>> So you checked all of LilyPond's dependencies and can guarantee >> that it will stay like this forever? > > I am on Big Sur (11.6) and I can still choose 10.9 as a deployment > target. [...] >> I'm not going to work on anything. I have been alone trying to get >> a build for macOS even

Re: LilyPond-2.22.2 does not work on Windows XP

> I thought I had downloaded the Lilypond file from the list that you > mentioned, but to make sure, I repeated the download and made sure I > downloaded (lilypond-2.22.2-1.mingw.exe) from the list you suggested > for 32 bits systems. Unfortunately, I had the same result as the > first time: >

Re: LilyPond-2.22.2 does not work on Windows XP

> How do I know which of the versions listed and offered for download > are for 32 bits or 64 bits systems? *All* versions given in my link are 32bit versions. Recent 64bit versions are provided on gitlab. Note that we no longer provide 32bit versions. Werner

Re: LilyPond-2.22.2 does not work on Windows XP

> I have a Windows XP computer with Lilypond 2.10.25. It works fine > with simple program codes and advanced code developed with earlier > versions of Lilypond. It does not work so well when I try to use a > newer program developed with a later version of Lilypond, as I get > many error

Re: another 'wrong type argument' error

>> I read that SDK 10.14.1 supports 10.9 as the oldest version (I >> couldn't quickly find the lowest value for SDK 10.15).  AFAIK, we >> don't use any functionality that is available on newer macOS >> versions only, so this route seems safe. > > So you checked all of LilyPond's dependencies and

Re: another 'wrong type argument' error

>> That is certain to be the reason why it doesn’t run, but I suspect >> a local build might run fine. I’d suggest setting this lower for >> binary releases if there’s no pressing reason to require 10.15 on >> Mac. > > Sounds sensible. Jonas? And thanks for having done the release, Jonas!

Re: another 'wrong type argument' error

> Confirmed using otool that the minimum OS for the linked build is > 10.15: > > Load command 10 > cmd LC_BUILD_VERSION > cmdsize 32 > platform 1 > minos 10.15 > sdk 10.15.6 Thanks. > That is certain to be the reason why it doesn’t run, but I suspect a > local build might run

Re: Lyric extender in RhythmicStaff

> The engraver should probably be named after its purpose rather than > after an obscure abbreviation of a data structure it should be > using. > > Something like Grob_lifetime_tracking_engraver or similar. +1 Werner

Re: Is the default value for Beam.details.stem-length-demerit-factor too small?

> Increasing the Beam.details.stem-length-demerit-factor does prevent > this and produces an in my eyes slightly better looking Beam. +1 Have you run LilyPond's test suite to check whether everything else looks fine with this setting? Werner

Re: Alphabetised table of contents?

> I'm just wondering if it's possible in Lilypond to create a table of > contents that is alphabetical by item, rather than by page number > order? IMHO this is not a table of context but rather an index that is positioned near the beginning. > I'm trying to create an alphabetical index by

Re: How to engrave this (screenshot attached) 12/8 time (looks like an arpeggio with ties)

> How to engrave this (screenshot attached) 12/8 time (looks like an > arpeggio with ties) Exactly. Look up the Notation Reference Index under 'arpeggio and ties'... Werner

Re: LilyPond compared

>> Attached is an image from the Urtext edition of Schumann's >> 'Humoreske', typeset around 2009. > > This image would seem to show that Henle's accidentals have diverged > quite a lot from LP's. In this Schumann example the sharp's > vertical lines are considerably longer and the glyph is

Re: is this a slashed grace?

> A multi-note beamed acciaccatura is printed without a slash, > and looks exactly the same as a multi-note beamed appoggiatura. And if you want to overcome this, look at https://lsr.di.unimi.it/LSR/Item?id=721 Werner

Re: Create 16th-century microtonal accidental

> A modern half note, sorry for the unclear terminology. The original > notation puts the dot above the (centered) minim stem, but in a modern > transcription I would prefer to have the dot above the notehead. OK. ``` { \override Script.add-stem-support = ##f \override

Re: Create 16th-century microtonal accidental

> Thank you! Is there a way to keep the staccato dot just above the > notehead also when there is a stem (on a minima for example)? A minima? Really? How shall this look like? Contrary to modern notation, the stems of minimae and friends are horizontally centered... Werner

Re: Create 16th-century microtonal accidental

> To mimic the appearance of this sign I need to place a dot centered > above the notehead in the next available space (not above the staff > like articulations, not on staff lines). What about a normal staccato point? You can force its direction by using `^`, for example ``` g\breve^. ```

Re: Customizing tremolo

> Maybe it's worth to at least extend the doc tagged lsr snippet > "Engraving tremolos with floating beams" > https://lsr.di.unimi.it/LSR/Item?id=553 I think this is rather a bug that should be fixed, so please open an issue. Werner

Re: Pointing Aiken Fa up in partCombine

> In this case, since Werner and I already approved this as a valid > feature request, you could also add it directly to the GitLab issue > tracker Yes, please do that, and post the relevant images there, too! I suggest that Benjamin does that as the initiator of the issue. Werner

Re: Pointing Aiken Fa up in partCombine

>>> \partCombine #'(1 . 1) >>> { \aikenHeads f'2 } >>> { \aikenHeads f'2 } >> >> This is an interesting problem. LilyPond's Emmentaler font >> contains two shapes of this glyph, namely `noteheads.d1fa` and >> `noteheads.u1fa`, where the 'd' and 'u' stands for 'down' and 'up', >> respectively

Re: Why not have a Lilypond documentation set arranged as layman's Q: does LP do this?

> What even makes it more difficult is when I don't even know what > something is called at all (no terminology) and/or when I have no > clue how to succinctly describe what it is that I don't know. For > example, the tremolo; I recognized the graphic but I had no way to > search for it by

Re: Pointing Aiken Fa up in partCombine

> \partCombine #'(1 . 1) > { \aikenHeads f'2 } > { \aikenHeads f'2 } This is an interesting problem. LilyPond's Emmentaler font contains two shapes of this glyph, namely `noteheads.d1fa` and `noteheads.u1fa`, where the 'd' and 'u' stands for 'down' and 'up', respectively (you can see the

Re: Byzantine singing

> Based on a group of byzantine fonts, I made my own ByzLily.otf. > Font "ByzLily.otf": https://disk.yandex.ru/d/jW8aScwbZvgzgA Nice! Is there a documentation that maps character codes to glyph descriptions? > In LilyPond, there is no way to combine characters from different > fonts

Re: Amharic

>> Maybe your Mac OS Amharic font is using Apple-specific SFNT tables >> (not covered by the OpenType standard) that are not understood >> and/or supported by Pango... > > It is a TrueType Collection, containing two fonts. > https://en.wikipedia.org/wiki/TrueType#TrueType_Collection > > I get:

Re: Amharic

>> On my system (Ubuntu), your amharic characters are encoded in the >> Ethiopan pane (U+1200-U+137C) and they are displayed with the >> FreeSerif Font > > This works. Maybe your Mac OS Amharic font is using Apple-specific SFNT tables (not covered by the OpenType standard) that are not

Re: Amharic

> Amharic does not display when using: > \header{ > composer = "Mulatu Astatke (ሙላቱ አስታጥቄ)" > } > Instead, showing a series of PRIVATE USE AREA-10FC18 U+10FC18. > > On MacOS, there is a system font Kefa for Amharic. > > So what is missing here? No idea. On my GNU/Linux box using current

Re: Circles

>> Well, Metafont uses a third-order Bézier approximation to build up >> circles (from four quarter circles). However, the Metafont book >> says that the difference to a real circle is less than 0.06%, which >> is thus imperceptible. >> >> The same holds for PostScript-based fonts. > >

Re: Circles

>> There's a lot of oldish webpages with complex Bezier curve >> constructions for circles. > > Those must be approximate constructions. It is not mathematically > possible to construct a Bézier curve which is at the same time an > exact circle. Well, Metafont uses a third-order Bézier

Re: vertical shift of trill

> That said, there's a much simpler way. [...] Your solution is ingenious. However, how on earth are we mere mortals able to find that? Both `note-columns` and `side-support-elements` are tagged as internal properties, which essentially means "don't touch". Additionally, the documentation

Re: hspace in markup cancels other directives

> Hi Aaron, thanks for that. I thought I had tried all permutations > of the order of specifications but I missed that one. It's hard to > guess which one is correct. Is it? I don't think so. Just bear in mind whether you have used up all arguments of a markup command. In your case,

Re: Last note of a first alternative is a tie to the first note in the repeat; how to engrave this?

> I guess I was thinking it might be easier/clearer for documentation, > since people wouldn't have to search for "repeat tie" as opposed to > "laissez vibrer" to get the two different versions of what is > ultimately the same thing. The current git version of the NR has the index entries

Re: Is there a SIMPLE way to embed an href in a title?

>> Thanks all. (Searches for URL, href, hypertext, etc, were failing >> to turn up \with-url and kept pointing me at much more complicated >> stuff that didn't seem to do what I wanted.) > > I used the index entry "inserting URL link, into text" > > Admittedly, Emacs Info makes it rather easy

Re: Searching fonts?

> I don't think this is well enough explained for peopleoin the NR. Any suggestions how to improve are highly welcomed – ideally in the form of a patch... Werner

Re: Generating a spiccato

>> In MusixXML, this sign is (The element | >> MusicXML 4.0 (w3.org) >> ), >> the same sign is named \staccatissimo in Lilypond. >> In MusixXML, looks like this:  (The >> element | MusicXML 4.0 (w3.org) >>

Re: `ly:context-property` and empty alist

>> I have a use case where I want to say >> >> ``` >> \set SYM = #'() >> ``` >> >> i.e., I explicitly want to override the default DEF with an empty >> list. How can I do that? > > As a user, if the code is written that way, you have no proper > solution. Yes, that’s a bit sad. (If the

Re: `ly:context-property` and empty alist,Re: `ly:context-property` and empty alist

> the problem here is not really ly:context-property, but the > C-implementation Context::internal_get_property, which uses SCM_EOL > as default value. [...] Thanks for the explanation! > #(define (context-has-defined? context sym) >(eq? (ly:context-property-where-defined context sym)

`ly:context-property` and empty alist

The documentation of `ly:context-property` is as follows. -- Function: ly:context-property context sym def Return the value for property SYM in CONTEXT. If DEF is given, and property value is ‘'()’, return DEF. I have a use case where I want to say ``` \set SYM = #'() ``` i.e.,

Re: vertical half-brackets,Re: vertical half-brackets

> how about something simple but functional like this: > > chbracket = > #(define-music-function (offset height width) (number? number? number?) >(let* ((x0 -0.7) > (x1 (+ x0 width)) > (y0 offset) > (y1 (+ y0 height))) > #{ >\tweak

Re: stacking of figured bass elements

>> I see that the function also listens to `basic-distance` (probably >> from `VerticalAxisGroup`), but I wasn't able to trigger it – most >> probably, this code part is not specific to figured bass. > > I think this should do (I can elaborate when I have more time): > > \version "2.22.2" > >

Re: stacking of figured bass elements

> This sounds like it might be related to my [long-standing] concerns > about leading, etc., in markups: there either isn’t a convenient > mechanism to deal with texts/markups *from their baseline [and not > their reference point]*, or the convenient mechanism exists and > isn’t sufficiently well

Re: stacking of figured bass elements

> Then I don't understand the problem. What characteristic of > baseline-skip do you wish? Is it that it counts from the origin of > each markup and somehow this distance is more convenient for you to > provide? Is it that it ignores the extents of the markups? I want equal vertical spacing of

Re: stacking of figured bass elements

>> Consider the following example: >> >> ``` >> \figures { >> >> } >> ``` >> >> As can be seen in the attached image, the elements are separated by >> padding only; they are not vertically spaced using `baseline-skip` >> or something similar. >> >> How can I change that? > > Like this? > >

stacking of figured bass elements

Consider the following example: ``` \figures { } ``` As can be seen in the attached image, the elements are separated by padding only; they are not vertically spaced using `baseline-skip` or something similar. How can I change that? Werner

Re: Left-hand end of tuplet bracket sometimes wrong

>> I find that even using shorten-pair (with a negative first value) >> fails to do this as I expected. So now I don't know any way to >> print the bracket with the preferred layout... > > This looks like a bug. Please file an issue at > > https://gitlab.com/lilypond/lilypond/-/issues

Re: Left-hand end of tuplet bracket sometimes wrong

> I find that even using shorten-pair (with a negative first value) > fails to do this as I expected. So now I don't know any way to > print the bracket with the preferred layout... This looks like a bug. Please file an issue at https://gitlab.com/lilypond/lilypond/-/issues Werner

Re: make \breath (kind-of) ignore clef change

>> This code might serve as an example for `\propertyTweak`, which the >> NR is currently missing. >> >> Would you care to submit an MR, expanding the documentation >> accordingly? > > I'm not sure if the NR is the best place for explaining > \propertyTweak. Its usefulness is basically to be a

Re: make \breath (kind-of) ignore clef change

> I'm not sure why this takes into account the right endpoint of the > extent on the left but not the left endpoint of the extent on the > right. I think it might just be assuming that all break-aligned > grobs have an extent starting at 0. Or maybe it's simply a thinko... Werner

Re: make \breath (kind-of) ignore clef change

David, thanks for your code – I consider it quite an elegant solution. > squashed = > \once \propertyTweak stencil > #(grob-transformer 'stencil > (lambda (grob old) > (ly:stencil-aligned-to old X RIGHT))) > \etc > > { 1 \breathe | } > > { 1 \breathe \squashed

Re: rehearsal marks, top-staff lyrics, and moved engravers

> Rehearsal and tempo marks should be aligned > on the selected staff as if they were part of it, see attached > example. I forgot to also move `Metronome_mark_engraver` in my example, but it doesn't make a visual difference here. Werner

Re: rehearsal marks, top-staff lyrics, and moved engravers

>> the snippet below demonstrates that top-staff lyrics are >> incorrectly positioned above rehearsal marks if the engraver for >> the latter is moved to another context (I need that in a full score >> with rehearsal marks printed simultaneously at three different >> vertical positions). > >

Re: rehearsal marks, top-staff lyrics, and moved engravers

> I think you likely want to move the Mark_engraver to a kind of > MarkLine context instead. Well, the problem is that such a context needs the `Axis_group_engraver`, which tries to align stuff horizontally on a line. I don't want that. Rehearsal and tempo marks should be aligned on the

rehearsal marks, top-staff lyrics, and moved engravers

Dear LilyPonders, the snippet below demonstrates that top-staff lyrics are incorrectly positioned above rehearsal marks if the engraver for the latter is moved to another context (I need that in a full score with rehearsal marks printed simultaneously at three different vertical positions).

Re: vertical half-brackets

>> * Has someone coded this already? I couldn't find code in the LSR. > > I don't know if this is still the most ideal way, but it works. > [...] Thanks a lot for all the replies! I'll analyze them and cook something up for my needs. Werner

Re: vertical half-brackets

>> For piano music it is common to indicate the use of the right hand in >> the lower staff with a 'half-bracket' [...] > > In the NR I find > > Indicating cross-staff chords with arpeggio bracket [...] > > It's not a half-bracket but it's the closest in the manual I can > find at a glance.

Re: vertical half-brackets

> * What's the right term for this 'half-bracket'? BTW, in SMuFL this symbol is called 'keyboardPlayWithRH' :-) https://w3c.github.io/smufl/latest/tables/keyboard-techniques.html Werner

vertical half-brackets

For piano music it is common to indicate the use of the right hand in the lower staff with a 'half-bracket' (and vice versa for the upper staff), see image. Two questions. * What's the right term for this 'half-bracket'? * Has someone coded this already? I couldn't find code in the LSR.

Re: Piano pedalling in (conductor) scores

> Well, just look at a Mahler score. He was one of the great > conductors, and the strings are full of bowing marks. How many of > them are followed by conductors these days I don't know. Well, just look at a Richard Strauss score :-) His scores are full of legatos in the strings which are

Re: make \breath (kind-of) ignore clef change

>>> Please have a look at the attached image. What must I do to make >>> the breathe sign 'ignore' the change clef so that the breathe sign >>> is positioned as if the change clef wasn't there? [...] > > There's always this sort of trick: [...] Excellent, thank you! > Is this canonical

Re: make \breath (kind-of) ignore clef change

> [git f326290b65351] > > Please have a look at the attached image. What must I do to make > the breathe sign 'ignore' the change clef so that the breathe sign > is positioned as if the change clef wasn't there? Well, having some code certainly helps :-) ``` { 1 \breathe | } { 1 \breathe

make \breath (kind-of) ignore clef change

[git f326290b65351] Please have a look at the attached image. What must I do to make the breathe sign 'ignore' the change clef so that the breathe sign is positioned as if the change clef wasn't there? Werner

Re: printing "a 2" at the beginning of staves automatically

>> * Contrary to Valentin's solution, the first 'a 2' text is not >> left-aligned to the left edge of the note head. This is >> especially visible with whole notes (see attached image). [...] > > See the attached file, fixing that problem and making it per-voice. Thanks, will test soon in

Re: `StaffGroup` prevents articulation shifted under time signature

> dynamicLengthOff = { > \override DynamicText.extra-spacing-width = #'(+inf.0 . -inf.0) > \override DynamicText.extra-spacing-height = #'(0 . 0) > } Nice idea, thanks! Werner

Re: `StaffGroup` prevents articulation shifted under time signature

>> The following example >> >> ``` >> << >>\new Staff { f'1 } >>\new Staff { f'1 \tweak X-offset #-5 \pp } >> \new StaffGroup << >>\new Staff { f'1 } >>\new Staff { f'1 \tweak X-offset #-5 \pp } >> ``` >> >> shows that I can't move the 'pp' to sit under the time signature if >> I

`StaffGroup` prevents articulation shifted under time signature

[LilyPond version 2.23.9] The following example ``` << \new Staff { f'1 } \new Staff { f'1 \tweak X-offset #-5 \pp } >> \new StaffGroup << \new Staff { f'1 } \new Staff { f'1 \tweak X-offset #-5 \pp } >> ``` shows that I can't move the 'pp' to sit under the time signature if I use

Re: printing "a 2" at the beginning of staves automatically

>>> Meanwhile, how about using a spanner rather than an item? See >>> attached. > > Aaand some nits :-) I forget another one. * If you look at the attached image (from 'Carmina burana') it probably makes sense to have the staff annotation engraver actually live in the Voice context. We

Re: printing "a 2" at the beginning of staves automatically

>> Meanwhile, how about using a spanner rather than an item? See >> attached. Aaand some nits :-) * Contrary to Valentin's solution, the first 'a 2' text is not left-aligned to the left edge of the note head. This is especially visible with whole notes (see attached image). It is not

Re: printing "a 2" at the beginning of staves automatically,Re: printing "a 2" at the beginning of staves automatically

> I’ve changed it up so that the a2 is always aligned to the note when > it is set. This also solves the first one not being printed. Thanks! Werner

Re: printing "a 2" at the beginning of staves automatically

> Meanwhile, how about using a spanner rather than an item? See > attached. Very nice, thanks! Besides the (hopefully) harmless warning ``` programming error: Spanner `TextSpanner' is not fully contained in parent spanner. Ignoring orphaned part continuing, cross fingers

Re: printing "a 2" at the beginning of staves automatically

> Basically, it works great, but there are two problems (tested with > 2.23.9). > > * It doesn't print 'a 2' at the very beginning. > > * Contrary to `\mark`, the 'a 2' should always be horizontally > aligned to a note column and not to prefatory matter like time or > key signatures. And

Re: printing "a 2" at the beginning of staves automatically

> The optimal solution (IMO) would be to improve the whole instrument > definition, switching, and [staff-]labelling framework such that > \addInstrumentDefinition and \instrumentSwitch would change the > appropriate texts so that the engraver(s) could present the > information automagically

Re: printing "a 2" at the beginning of staves automatically

>> while it is probably not the best way to do it, here is a >> pragmatical solution to the problem. > > Thanks a lot! Will try it soon. Basically, it works great, but there are two problems (tested with 2.23.9). * It doesn't print 'a 2' at the very beginning. * Contrary to `\mark`, the 'a

Re: printing "a 2" at the beginning of staves automatically,Re: printing "a 2" at the beginning of staves automatically

> while it is probably not the best way to do it, here is a > pragmatical solution to the problem. Thanks a lot! Will try it soon. Werner

Re: LilyPond 2.23.9 released

>> Note that the MacPorts port of LilyPond 2.22.2 already uses Guile >> 2.2 bytecode and provides a binary for Apple Silicon, too. >> >>   https://ports.macports.org/port/lilypond/details/ > > No, the 2.22.2 version uses Guile 1.8 as can be easily seen from the > dependencies. Even if it used

Re: LilyPond 2.23.9 released

>> Currently homebrew provides Lilypond 2.22.2 for Apple Silicon, >> that is what I am using. > > Did you try running the x86_64 binaries via Apple's Rosetta tool? That > might be a bit slower than native executables, but given that Homebrew > builds 2.22.2 without Guile bytecode, it might

printing "a 2" at the beginning of staves automatically

Let's assume that I have 40 bars of flute 1 and 2 in a single staff of a full score. At the very beginning of these bars I write "a 2", and I want this remark repeated at the beginning of every staff where this is still true. [Obviously I'm not using `\partCombine` :-)] Has anyone already set

Re: within \markup, how to \translate by width of another markup?

>> AFAICS, we are back to square one, needing the possibility to >> `\translate` something by the width of another markup. I will cook >> something up and see how well it works. > > > Probably > > ``` > \version "2.22.2" > > #(define-markup-command (translate-by-extent-of layout props axis

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