Re: getting paid for an include (I offer)

>> ??? Are you really trying to reactivate Neue Deutsche >> Orgeltabulatur, three hundred years after it was abandonded? > > There can be multiple reasons why one would do that: [...] All of these are valid points. However, it seems to me that he wants to actually *add* features to this tablatu

Re: Crop only top and bottom

> I have looked for ways to crop the EPS to only two borders of the > bounding box but didn't find anything useful so far. While I can't help with the lilypond issue, I suggest to have a look at the `pdfcrop' program that comes with TeXLive: It supports a `--margins' option. Werner ___

Re: Issues about optical spacing

> I [...] submit this article which discusses the topic in detail. > > https://quod.lib.umich.edu/cache//b/b/p/bbp2372.2002.097/bbp2372.2002.097.pdf#page=2;zoom=75 > > I would love to see Lilypond incorporate this improved algorithm > [...] This sounds like an interesting GSoC project! Han-Wen

Re: Font names convention

> When in the .tex file I write > >   \setmainfont{Adobe Garamond Pro} > > the font is correctly used, but the "fullname" I get out of the Lua > object is "AGaramondPro-Regular". This looks like the PostScript name. > This is also what is shown in the properties of the PDF, but with > differen

Re: Tweaking Hairpin shape

> I wanted to make it so that the two lines that form the hairpin > would end in the same vertical line, Please show a real-world example for that. I can't remember having ever seen this... Werner ___ lilypond-user mailing list lilypond-user@gnu

Re: Tweaking Hairpin shape

> Sure, I attached a few from here > Thanks, but in this score there is not a single heavily rotated hairpin; I would say that the differences are not of any importance. > . Oh, and an orche

Re: Tromba "mo"

> What MS, what context? I don't know of 'mo' in any tonic sol fa. `mo' is a term from (German?) `relative solmisation', cf. https://de.wikipedia.org/wiki/Solmisation#Relative_Solmisation However, I have never seen this in any score... >> I've got a manuscript with two "Trombas" - in "mo" an

Re: Tromba "mo"

> a 18th century cantata - I found (very few) links with google where > you can see "Tromba I mo" "Oboe I mo" and "Cornu I mo"  - so its not a > typo... Uh, oh, this means `Tromba primo', `first Tromba', so please forget what I talked about solmisation :-) Werner ___

Re: Tromba "mo"

>>> I've got a manuscript with two "Trombas" - in "mo" and "do". Obviously, the other one is `II do' – Tromba secondo :-) Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Tromba "mo"

> Just out of curiosity - shouldn't it be "tromba prim*a*/second*a*" > in Italian (1ma/2da)? Indeed. > Or is it a case of "modo russico" ;) Hehe, I think you are right :-) Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://list

Re: Build error. MergeFonts: Can't find font: feta11.pfb

> Invoking "t1asm parmesan-noteheads14.pt1 parmesan-noteheads14.pfb"... > mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find > another way to convert parmesan-noteheads14.pt1 to > parmesan-noteheads14.pfb > […] > > t1utils (including t1asm) are installed in the correct version

Re: Thriple flat/sharp glyphs...

Nice work! > 2. Abraham's equally compressed flats > > Both flats are equally compressed as a compromise, thus keeping the > original glyph width: > > > This is my favourite. Werner

Re: Thriple flat/sharp glyphs...

> Version 2: Abrahams equalized flats: > test-issue3356-condensed.pdf > > Thanks. And this is still my preferred version. Werner ___ lilypond-user mailing list lil

Re: Thriple flat/sharp glyphs...

> Please find attached the proofsheet I'm planning to attach to the > issue tracker (if nothing dreadful happens). There's also a concise > test of \chordmode and note entry. MIDI output isn't contained, but > it's working as it should. > > issue3356-proofsheet.pdf >

Re: Thriple flat/sharp glyphs...

> I just used \score inside a custom markup-command and set the size > by \layout { #(layout-set-staff-size design_size) } > > It looks as if #(layout-set-staff-size) doesn't scale down all the > distances. I think this behaviour is correct – the idea is to have staves with different sizes aligne

Re: Is lilypond really suitable for composing?

>> I think it's likely rather hard to compose dissonant pieces without >> access to the actual timbre (and thus overtone composition) used >> for playing it. > > Apparently you haven’t been to any new classical music concerts in > the last half-century. It’s *quite* clear that many composers — >

Re: Thriple flat/sharp glyphs...

> I've set up two PDFs for comparing the original and my current > working draft design (the triple flat missing in the original > design, though). All existing accidentals containing flats both on > and between stave-lines in all design sizes. In my printout, the > opening-up of counters does n

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: 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 outside-staff-prio

`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., I

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

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 property

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

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 tie

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, \sm

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 is

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 approximat

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. > > PostScrip

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 git,

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 understo

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

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 gly

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 appea

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

> 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 Script.toward-stem-shi

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

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

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

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

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

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

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 (they

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: 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 'longtab

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

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 pa

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

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

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 extremely

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 a

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 be

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: 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 `--format=lat

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

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: 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: 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, 'Ti

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

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 tha

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,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 > (markup

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. Thi

autobeaming over rests

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 whether it makes sense to control this behaviour

Re: autobeaming over rests,Re: autobeaming over rests

>> 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 whether it makes sense

Re: Re: jeté,Re: jeté

> 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 attached image. Ideally, it would be very nice if we could a

Re: autobeaming over rests,Re: autobeaming over rests,Re: autobeaming over rests,Re: autobeaming over rests

> > IMHO, there are definitely valid situations where > > automatic beaming over rests does make sense. > > this would not be hard to get done. Here’s an experimental commit: > [...] Veeery nice, thanks! I only wonder what situation you envision to add a special property for skips... Werner

Re: autobeaming over rests,Re: autobeaming over rests,Re: autobeaming over rests,Re: autobeaming over rests

>> Veeery nice, thanks! I only wonder what situation you envision to >> add a special property for skips... > > \version "2.24.0" > > \new Staff \relative > << >   { c'8[ s s c] } >   \\ >   { s c c s } >>> > > doesn't seem unreasonable to me (for example in piano music). OK, thanks. Wer

Re: The "R.H." instruction with 45 degree slope down and up from treble to bass clef: How?

> The "R.H." instruction with 45 degree slope down and up from treble > to bass clef: How? Look up 'staff-change lines' in the Notation Reference index to get details on the `\showStaffSwitch` command. Werner

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

>> 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 failed: d, file >> /home/lily/lilypond-

breaking vertical alignment of dynamic items

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 | } ``` Werner

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

>> But the user shouldn't see an assertion error even in case of a wrong >> argument, right? > > Yeah, > https://gitlab.com/lilypond/lilypond/-/merge_requests/1828 Thanks! Werner

Re: breaking vertical alignment of dynamic items,Re: breaking vertical alignment of dynamic items

>> 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. > > \version "2.24.0" > > { > e1\< | g''1\breakDynamicSpan\ff | > } Aah,

Re: German notation

>> Strange transposition rules also exist for horns, where in the >> violin clef you transpose down, and in the bass clef you transpose >> up. > > Violin clef? Sorry, bad translation from German: I meant horn parts notated with a treble clef. Werner

Re: breaking vertical alignment of dynamic items

> I've always terminated my cresc/decres with \! > I found that in the docs a while ago, but is that still the case? > > e1\< | a2\!\ff b2 > > Is the way I'd have done it. AFAIK, this has never worked. If `\!` and `\ff` are at the same moment, `\!` gets ignored. Note that `\breakDynamicSpan

Re: breaking vertical alignment of dynamic items

>> { >> e1\< | g''1\breakDynamicSpan\ff | >> } > > I'll eventually submit a patch to fix that. This is now https://gitlab.com/lilypond/lilypond/-/merge_requests/1829 Werner

Re: The "R.H." instruction with 45 degree slope down and up from treble to bass clef: How?

> REDACTED/source/The_Way_We_Were.ly:259:1: warning: cannot find > context to change to: Staff = lower This is because you are already in the "lower" staff. As the name `\change Staff` implies, it is intended to display material temporarily in another staff. In other words, the eighth notes in

Re: Clef with Ottava in parenthese

> I actually looked, but found this page - > https://lilypond.org/doc/v2.22/Documentation/notation/clef-styles > there it's not mentioned :( https://gitlab.com/lilypond/lilypond/-/merge_requests/1838 Werner

`\offsetPosition` fails

I'm using the `\offsetPosition` command (https://lsr.di.unimi.it/LSR/Item?id=748). Unfortunately, it fails in a multi-staff, real-world piece: it has zero effect, and I don't know why. What could be the cause for that? If I had a hint, creating an MWE would perhaps be more straightforward...

Re: `\offsetPosition` fails

> This is because it assumes that Slur.control-points is still set to > its original callback at the time `after-line-breaking` is run, > which isn't true if something like > `ly:side-position-interface::move-to-extremal-staff`, in > `BarNumber.after-line-breaking`, reads `control-points` earlier

`\afterGrace` and clef problem

Please look at this example. ``` \relative c' { << { \afterGrace f1 { e16[ f] } | g1 } { c1 \clef "bass" | c,1 } >> } \relative c' { << { f2.. e16[ f] | g1 } { c1 \clef "bass" | c,1 } >> } ``` What can I do to make the clef move 'under' the grace, similar to the non-grac

Re: `\afterGrace` and clef problem

Hello Valentin, > My suggestion to getting around this would be the tell Lilypond that > the clef stencil is in fact narrower than it actually is, which will > allow the Clef stencil to protrude arbitrarily much: [...] Thanks! Interestingly, the clef still gets some extra horizontal space, whi

Re: `\afterGrace` and clef problem

> [...] I'm rather inclined to count the behaviour of `space-alist` > for clefs as a buglet: It doesn't make sense allowing the clef to > move 'under' other notes in different staves while its `space-alist` > values are applied globally to all staves. This is now issue #6529. https://gitlab.com

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