Re: Dump from https://lsr.di.unimi.it?

> > Well I just made such a script. Very nice! > https://github.com/eefweenink/LSRDump/tree/main/downloads IIRC, it is not necessary to download anything else but the MySQL dump since you can extract the contents of the other archive files from the dump. In other words, the `lsr-snippets-*.tar

Re: White Knight for https://lsr.di.unimi.it?

> * So the most simple approach I can think of, is making a dump of > the complete LSR and upload as html webpages. A daily dump of the database is available from the LSR in the form https://lsr.di.unimi.it/download/lsr--MM-DD.mysqldump.gz I wanted to simply add that to a git repository

Re: White Knight for https://lsr.di.unimi.it?

> FWIW I have used all of these technologies and would be willing to > help. This is great news! I'm very glad to hear that. Werner

Re: White Knight for https://lsr.di.unimi.it?

> Please tell a bit more about this “White Knight” for the LSR please. > > * Provide webspace to place it for a couple of years? > Place it on Github? > * Maintain/ editing > > What ’s the plan, Please read this thread: https://lists.gnu.org/archive/html/lilypond-devel/2025-06/msg00032.html

Re: https://lsr.di.unimi.it DOWN?

> Could it be that > > https://lsr.di.unimi.it > > Is down already for a couple of days. > > Where to address this, so it may be solved? I've CCed Sebastiano in this e-mail; hopefully, he can have a look. Unfortunately, he will no longer be able to maintain the LSR

Re: convert-ly: \version number updates

> Another question: there's a way to disable the creation of backup > files ending with ~? Nope. Werner

Re: convert-ly: \version number updates

> ''' > -c, --current-version > >By default, convert-ly updates the \version string to the lowest >necessary version. If this option is given, the current LilyPond >version (2.25.27) is used instead. > ''' > > So, IIUC, by default convert-ly should update the \version string only > if

Re: Tab notes before TabStaff

>> The only viable solution is to remove all Variation Fonts, in >> particular the `google-noto-vf` package. It should be replaced >> with non-VF Google Noto fonts. Of course, installing the >> 'liberation' fonts also helps :-) [...] > > I changed the snippet to avoid the overrides for 'font-n

Re: featherDurations when using manual syllable durations

>> it would be quite handy for me if I could use \featherDurations when >> specifying manual syllable durations: [...] > > featherDurations= [...] Looks like a useful addition to LilyPond – Harm, do you care to submit a MR? Werner

Re: Tab notes before TabStaff

> These are the logs: > > Drawing systems... > (process:73801): Pango-WARNING **: 21:21:21.999: Unable to open font > file /usr/share/fonts/liberation-sans-fonts/LiberationSans-Bold.ttf > for font Liberation Sans Bold 2.435546875, falling back to > /usr/share/fonts/google-noto-vf/NotoSans[w

Re: Tab notes before TabStaff

> Lucas, you may try https://lsr.di.unimi.it/LSR/Item?id=658 > The image there is wrong, though. > > Werner, this happened after I changed said snippet to make it more > obvious. What's wrong with the LSR?? I don't know, sorry. I see such a problem the very first time. Attached is an image how

Re: Question about color key signature

>> I don't see another possibility. But I'm willing to implement 2) if >> it fits your need. > > Maybe something like this? [...] Very nice! I think this would be a good snippet for the LSR. Werner

Re: Easy Editing web page, Frescobaldi entry out of date

>> What exactly means 'abandoned'? Isn't it possible to ask Wilbert >> to transfer the the domain name to the Frescobaldi development team >> so that a simple redirection could be added (and the old contents >> stored somewhere else for archival purposes)? > > I'm in touch with Wilbert. > > To

Re: Easy Editing web page, Frescobaldi entry out of date

>> ...the entry for Frescobaldi is out of date. First of all, it >> points to https://www.frescobaldi.org as the home page, but that >> site has been abandoned. What exactly means 'abandoned'? Isn't it possible to ask Wilbert to transfer the the domain name to the Frescobaldi development team

Re: Grob transformers

> I do not dispute that lambdas are essential tools in Scheme. My > point is that while great for programmers, they are not things that > Joe Public should have to know about. > > I still remember having to deal with Cobol programmers who could not > understand the notions of data types or of pa

Re: Grob transformers

> just as a gut reaction: I think this is a really great idea! Me too. Werner

Re: Grob transformers

> Speaking as a programmer of 60 years experience, lambdas give me the > willies - and I started with Jensen's Device in Algol60 when Algol60 > was new. > > Yes, lambdas are neat, but IMO they tend to be unreadable and > unmaintainable. If you like them, use them; but do not make them a > require

Re: Markup alignment question

>> > Should we change this to a public function? >> >> I think this might prove very useful. [...] > > Very nice! Indeed. Tina, do you have time and energy to submit a Merge Request, i.e., adding the necessary documentation strings, updating the `changes.tely` file, and probably adding exampl

Re: Markup alignment question

> `wordwrap-string-internal` is one of only three > markup-(list)-commands flagged "internal" and thus not documented, > but it _is_ a full blown, ready-to-use command. Should we change this to a public function? Werner

Re: How to place a custom copyright tagline at the bottom of the first page only?

> However, I noticed a new issue when embedding the score using > \lilypondfile inside a LaTeX document (as part of a book I’m > compiling). In this setup, both the copyright and tagline fields > completely disappear, even though they are correctly rendered when > compiling the score on its own.

Re: Ghostscript error using Fedora 42 lilypond

> I don't have any problem when I use lilypond.org binaries, but when > I compile this simple file using the lilypond provided by Fedora 42 > I get an error. Official binaries have gs 10.03.0 while Fedora is > using 10.05.0. I've just done a self compilation of LilyPond 'master' on my openSUSE

Re: Aleatoric section: how to desync vertical alignment and barlines?

> Some paper-variables are accepted in \layout. Among them is `indent`. > Iirc, this is documented already: [...] It is, and I've just submitted an MR to add an index entry for that (among other minor fixes). https://gitlab.com/lilypond/lilypond/-/merge_requests/2654 Werner

Re: Repeat barlines with "tails" in piano staff

>>> When using \bar ":|." in a piano staff the barline spans the two >>> staffs, but when using \bar ":|]" it does not - is there a way to >>> fix this? >> >> Does >> https://lsr.di.unimi.it/LSR/Item?id=1032 >> help? > > This looks very nice. IMHO, the current behaviour of LilyPond is > incorr

Re: help with translation

> Here are the Japanese translations [...] > Also, just to get things started with French [...] Thanks a lot! Werner

Re: help with translation

>> Oops, I mean >> >> 'Altres proves de regressió en PDF per a ' > > Yes, no problem. Either form would work. OK, thanks! Werner

Re: help with translation

> Should we thus use > > 'D\'altres proves de regressió en PDF per a ' > > to stay in sync? Oops, I mean 'Altres proves de regressió en PDF per a ' Werner

Re: help with translation

> Catalan translation: > > 'Altres proves de regressió per a ' > 'PDF d'altres proves de regressió per a ' Thanks a lot! A minor question: we already have, for example, 'MIDI Regression tests for ': 'Proves de regressió de MIDI per a ', 'PDF of MIDI regtests for ': 'Proves de regressió de M

help with translation

Folks, we need translations of the short strings listed below this e-mail; if you are a speaker of the mentioned language (especially Turkish) please send translations of them! * * * Here are the technical details. The strings are part of a Python script calle

Re: Repeat barlines with "tails" in piano staff

>> When using \bar ":|." in a piano staff the barline spans the two >> staffs, but when using \bar ":|]" it does not - is there a way to >> fix this? > > Does > https://lsr.di.unimi.it/LSR/Item?id=1032 > help? This looks very nice. IMHO, the current behaviour of LilyPond is incorrect, and we s

Re: Dotted notes and intervals of a second

>> If the dot placement is the problem, what about this: [...] > > Gould suggests putting the dotted noteheads a little further away > (see attached) with the option of doing what is the Lilypond default > if the dot could be confused with a staccato marking. You could > probably get away with

Re: Tie too short in certain circumstances

> In certain circumstances LilyPond will create a very short tie, so > short it looks like a dot. [...] > > This happens in LilyPond 2.25.24 too. Is it worth creating an issue? If you search the issue tracker with the keywords 'tie' and 'length', you'll find issue #14, the second most infamous

Re: Dotted notes and intervals of a second

> I've run into an interesting behavior of LilyPond (2.24.4 and > 2.25.24) when you have dotted notes in a chord with an interval of a > second. [...] > > My question is, does the modified way look better? No, it doesn't for me. A dot with such a large vertical distance is something I've never

Re: problem with `alignAboveContext`

>> Imagine a choir piece with three women voices, to be notated on two >> staves to save vertical space. To increase readability in the >> score it might make sense to position voices 1 and 2 in the upper >> staff and voice 3 into the lower one. Suddenly the musical >> structure changes, and it

Re: problem with `alignAboveContext`

>> > If you have two staves, and a voice were to change staves, would >> > you expect the lyrics to leap about too? >> >> Actually yes :-) Can you imagine a situation where this shouldn't >> happen? > > You're asking me to imagine something that doesn't make sense to me, > then to argue that this

Re: Box notation, 13 years later

>> (It would also be great to get this working with repeat barlines: > >> ||: music :||> > >> There's a hack in the lists somewhere, in which I draw >> barlines myself, but BarLine grobs are obviously needed >> instead.) > > Attached is my take on this, which has developed out of David's

Re: problem with `alignAboveContext`

>> In the Internals Reference, alignAboveContext only occurs under >> staff-ish contexts, not voice-ish ones, §2.1.x. > > OK, but this only gives indirect hints. I'll try to improve the > documentation, thanks. https://gitlab.com/lilypond/lilypond/-/merge_requests/2620 Werner

Re: problem with `alignAboveContext`

>> However, if I use `alignAboveContext = "V1"` instead, it doesn't >> work, and I get the warning >> >> ``` >> warning: alignAboveContext not found: V1 >> ``` >> >> Why? > > Does it make sense? If you have two staves, and a voice were to > change staves, would you expect the lyrics to leap about

Re: Release: backend for "vertical" navigation/measure insertion

> > One of the longstanding workflow limitations of LilyPond is the > difficulty of inserting or removing measures, stemming from an > inability to navigate "vertically" through a score's music input > code (i.e. cycling through the same rhythmic position in different > parts). I've been working

problem with `alignAboveContext`

Folks, consider the following example. ``` \version "2.25.25" \new Staff = "S" << \new Voice = "V1" { \voiceOne e''1 } \new Lyrics \with { alignAboveContext = "S" % alignAboveContext = "V1" } \lyricsto "V1" { Above } \new Voice = "V2" { \voiceTwo e'1 } \new Lyrics \lyricsto "

Re: Box notation, 13 years later

> Yes, some space should be the default, and my comment was > invalidated by some changes I made within the engraver. I've > attached a revision of the file for which the comment does again > make sense. The engraver now acknowledges objects with the > dynamic-line-spanner-interface. Great, tha

Re: Box notation, 13 years later

>> What is the current recommendation for aleatoric notation? >> Specifically, a group of cells to be performed in any order the >> player wishes. > > A few changes are needed. The attached should work for you: Very nice! While adapting the code to 2.25 and playing around I noticed the followi

Re: Wrong beam direction with scaled durations

>{ a16.*8/9 [32*4/3] 16.*8/9 32*4/3 > a16.*8/9 [32*4/3] 16.*8/9 [32*4/3] > ... Please be aware that LilyPond handles `[` and `]` as suffixes, i.e., they are to be *appended* to a note or chord. Attaching `[` to the left of the following note or chord might thus be conf

Re: Glissando to nothing example in docs

> [...] to enable the glissando to have more space I added a new > spacing section around it giving this example: > > 8><8><8><8><8><8><8><8><8><8><8><8><8><8>< > \version "2.25.18" > \relative c'' { > \time 3/4 > \override Glissando.style = #'zigzag > c4 c4 > \newSpacingSection > \overr

Re: BalloonText help

> Now, solution for this could be: > > * Check if event property `symbol` is an actual symbol, else issue a > reasonable warning > > * Set a reasonable value for symbol (e.g. as the post-event will > only really be useful to note and chord events set the default to > NoteColumn) > > Of cour

Re: BalloonText help

> I think that I would reverse the order of the clauses so that the > special case comes first, and reword slightly so as to make clear > that it is a special case: [...] Thanks; see https://gitlab.com/lilypond/lilypond/-/merge_requests/2605 Werner

Re: Glissando to nothing example in docs

> So one or other of those should replace the original example in NR > that is decidedly long in the tooth, dating from 2.12.0. > (Particularly as the original one doesn't really work.) Can you prepare a patch? Or maybe even an Merge Request? Werner

Re: BalloonText help

>> Use \balloonGrobText before a note or -\balloonText after a note >> within chords. > > NR 1.7.2 says "typically within chords,"; it does not say "only > within chords". Maybe the NR needs updating. It seems that you are a native speaker. Can you suggest a better wording? Werner

Re: Glissando to nothing example in docs

> The only documentation I have found for \after is > > \after delta (duration) ev (music) mus (music) ⇒ music > Add music ev with a delay of delta after the onset of mus If you look into the index for `\after` in the NR you will find cross references to some examples (at least in the develo

Re: Unicode sharps and flats in lyrics

>> While it is rather innocuous in this particular case it might be >> extremely frustrating for beginners to find out why LilyPond does >> this. > > I'm not sure I follow your thought process. What is it that you > worry would be confusing to beginners? Genuine question. Is it > something about

Re: \set Score.proportionalNotationDuration warning on LilyPond 2.25.23

>> Do you think this isn't prominently enough? If so, how could this >> be improved? > > I think that as with many warnings, the fact that it's always there > leads to it fading into the background for many readers, > particularly as they learn from experience that for *most* code, > *most* of

Re: Unicode sharps and flats in lyrics

Sorry for the late reply. >> > Why not add global text replacements substituting the accidental >> > markups in place of the Unicode characters? Personally I prefer >> > to type and read within my code the Unicode accidentals but I'd >> > always want the output to use Emmentaler. >> >> Sure! Thi

Re: \set Score.proportionalNotationDuration warning on LilyPond 2.25.23

>> if you have reasonable ideas how such API changes could be >> communicated better I am sure people would love to hear them and if >> feasible incorporate them. > > IMO one relatively simple change would be to add a note to the release > announcement email mentioning that users should expect to

Re: \set Score.proportionalNotationDuration warning on LilyPond 2.25.23

>> proportionalNotationDuration is not deprecated. Its type has been >> changed, therefore the warning about not accepting a moment is correct. > > that's what I was saying. Wouldn't it have been better to treat it > as a deprecated property with an appropriate warning, rather than as > an API b

Re: Unicode sharps and flats in lyrics

> Why not add global text replacements substituting the accidental > markups in place of the Unicode characters? Personally I prefer to > type and read within my code the Unicode accidentals but I'd always > want the output to use Emmentaler. Sure! This sounds like a nice contribution to the LS

Re: Unicode sharps and flats in lyrics

>> However, to get the text versions of LilyPond's accidental glyphs >> you have to either explicitly switch to the Emmentaler font, or you >> can use commands like `\text-flat` for that. [...] > > On my machine, the standard Emmentaler.ttf font does not contain > those signs [...] Text represe

Re: Unicode sharps and flats in lyrics

> However, to get the text versions of LilyPond's accidental glyphs you > have to either explicitly switch to the Emmentaler font, or you can > use commands like `\text-flat` for that. Example: > > \version "2.25.2" Oops, this should have been `\version "2.25.23"`. Attached is also an image of

Re: Unicode sharps and flats in lyrics

> I make a lot of teaching materials with lilypond, and in the past, > perhaps one year ago, I could use the unicodes for the sharp symbol > (♯), the flat symbol (♭) and the natural symbol (♮) within the > \addlyrics brackets and they would render correctly. > > With my most recent version of lil

Re: alignement problem when \remove "Clef_engraver" of a Tab.

> Then I check the LSR and found that : > > https://lsr.di.unimi.it/LSR/Item?id=550 > > should be corrected accordingly, as it cannot adapte to the exemple > I gave. Thanks, I've updated the LSR snippet. Werner

Re: Selecting font-series Black

> in the example below, why does overriding font-name work, but not > overriding font-series? The way Frescobaldi displays the available > fonts, it seems like the Black font weight is right there with the > other weights (bold and [medium]). > > Best, Simon > > \version "2.25.23" > > \paper {

Re: Align lyrics under the stem, not the notehead

> David's suggestion results in similar to your first suggestion - it > seems a bit too far to the left. self-alignment-X = #RIGHT works > for 1 character, but not for lyrics - for lyrics (when the drummer > is the vocalist), I had to use your method. `#RIGHT`, `#CENTER`, and `#LEFT` are the sa

Re: tabstaff and finger notation

> For example in the case of this thread where I hadn't come across or > noticed the keyword StrokeFinger I will have a line something like > below - just enough to remind me of related keywords to search for: In case you are using the current development version you probably might enjoy our 'vi

Re: tabstaff and finger notation

> StrokeFinger was the key piece I was not finding. Sometimes in > lilypond documentation it's a matter of finding the right keyword to > search for. What entries do you suggest to be added to the index? Werner

Re: About LilyPond music font format

> Currently I am working with a FontForge script to convert LilyPond > music fonts to SMuFL. There was/is a project to do that, see https://wolfgangsta.github.io/emmentaler-bravura/ It would be great if you could help with that. > The following table(s) in the font have been ignored by FontF

Re: White on black with whiteout

> But I think this opens up a route via overriding the whiteout-color > grob property and maybe also a property-defaults entry. I suggest to file an issue, and you are more than welcome to also provide a merge request :-) Werner

Re: White on black with whiteout

> I'm afraid so. Whiteout color white is hard-coded in > scm/stencil.scm. Are you looking at the current development version? In the 'changes' document you can find the following: • A new grob property `whiteout-color` is available to set the color used for white-out operations. Similarly

[no subject]

> I'd like to make my midi file with a metronome sound or click track, > but for this part to be completely absent from the PDF. I'd also > prefer to avoid custom-made solutions if I can, because of their > tendency to "rot" as new versions of Lilypond make them > obsolete. Can I just add an ordi

Re: how to modify `afterGraceFraction` mid-score?

>>> (Of course, the current implementation of afterGrace makes this >>> comparatively hard to achieve, since the fraction is used for >>> determining the length of a skip IIRC.) >> >> ...and came to the conclusion that a global variable is the easiest >> solution :-) > > I refuse that honor. :-

Re: how to modify `afterGraceFraction` mid-score?

>> you can use `set!`: Thanks! >> But note that this may cause race conditions, [...] Please explain and/or give an example. > The global variable afterGraceFraction has bothered me for some time > now. Shouldn't this be a context property? [...] I guess that David has thought about that.

how to modify `afterGraceFraction` mid-score?

In full scores it is sometimes necessary to adjust the value of `afterGraceFraction` so that it harmonizes with other notes and rhythms. However, saying ``` afterGraceFraction = ``` only works at top-level according to the documentation. How can I change this value mid-score? Werner

Re: Contemporary Notation Snippets

>> The best place to contribute to would be the LilyPond Notation >> Reference manual, whose Contemporary music section has been a stub >> for years: >> https://lilypond.org/doc/v2.25/Documentation/notation/contemporary-music > > I agree with this. +1 > Given that the examples that took so muc

Re: Translate any grob in a score without side effect in LilyPond

> Most GUI-based scorewriter applications allow users to drag items to > arbitrary positions and presumably, creates no side effect. [...] > > However, when searching for a method to do the same in LilyPond, I > cannot find a method that is working in general. [...] Try `extra-offset`.

Re: How to increase the distance between the last note of a measure and the following bar line

> In addition to that, the IR is a static document that *cannot* > reflect the state of LilyPond at an arbitrary point of time while > processing an input document. Instead, it presents LilyPond in a > pristine state, before any `*.ly` files has been loaded, more or > less (including LilyPond's

Re: How to increase the distance between the last note of a measure and the following bar line

Folks, please calm down. Nobody here is insinuating anything! As far as I can see, we have a clash of concepts that is probably not resolvable in *any* satisfying way. Consequently, the only way forward is to minimize the fallout, namely by providing explanations what a musical term 'foo' mea

Re: Some things need need to be fixed on the interfaces pages

>> I'm left-handed by myself (but playing the piano), and I don't feel >> offended 🙂 > > But aren't you playing a right-handed piano? I do. However, I'm not *completely* left-handed – AFAIK, completely left-handed people are quite rare. For example, while I write with my left hand or hold a sp

Re: Some things need need to be fixed on the interfaces pages

> *If* we had a page that showed all grob properties, then we could do > that. My bad, we actually have that :-) So yes, your suggestion is sound, and the list of grob properties could be amended accordingly. Werner

Re: Some things need need to be fixed on the interfaces pages

>>> There's a problem there, too, in that the default value depends on >>> the grob. >>> >>> In MeasureSpanner, the default value is (staff-bar . staff-bar) >>> >>> In PercentRepeat, it's (break-alignment . staff-bar) >> >> I don't see a problem here. > > You can't talk about *the* default value,

Re: What is the `bracket-text` property good for?

> Actually, the descriprion is wrong, imho. > > (bracket-text ,ly:grob? "The text for an analysis bracket.") > > should become something at he lines of: > > (bracket-text ,ly:grob? "The text-grob for an analysis bracket.") I plan to change the docstring to A pointer to the text grob of an a

Re: Some things need need to be fixed on the interfaces pages

> I mean should MMRs actually use centered-spanner-interface? MMRs are > after all spanners that are centered between spacing-pair. It looks > to me like the C++ code for MMRs does exactly the same offset > calculation as centered-spanner-interface::calc-x-offset, though not > all in one place.

Re: Some things need need to be fixed on the interfaces pages

>> Exactly this is not possible, because there exists only a single, >> global property called `spacing-pair`, which consequently has a >> single, global description. >> >> In other words, the auto-generated documentation sees that an >> interface uses `spacing-pair`, and it shows its description.

Re: Some things need need to be fixed on the interfaces pages

>> IIRC, a suggestion in the mentioned thread > > Do you know the name of that thread? I tried searching for it, but > couldn't come up with anything. It's mentioned at the top of https://gitlab.com/lilypond/lilypond/-/issues/6210 namely https://lists.gnu.org/archive/html/lilypond-user/2

Re: What is the `bracket-text` property good for?

>> What are these properties good for? What can they do what the >> `text` property of `HorizontalBracket` or `PianoPedalBracket` >> cannot? > > 'text is a grob-property to set the text for HorizontalBracketText. > 'bracket-text (as an internal property) is a pointer from > HorizontalBracket to

What is the `bracket-text` property good for?

It seems to me that the `bracket-text` property (as defined in `horizontal-bracket-engraver.cc`) is unused – it gets set (with `set_object()`) but never read. Ditto for `pedal-text` in `piano-pedal-bracket`. What are these properties good for? What can they do what the `text` property of `Horiz

Re: Some things need need to be fixed on the interfaces pages

>> The policy of LilyPond is to avoid different property names for >> similar functionality, which often leads to cryptic property >> descriptions to be as generic as possible. In this particular case >> an example is given, which is actually a good thing, but it doesn't >> cover the `centered-sp

Re: Some things need need to be fixed on the interfaces pages

> I went through the interfaces pages recently, and I found a couple of > things that need to be fixed (these is from the 2.25 version). > > (1) The centered-spanner-interface page talks about using it with > MultiMeasureRest, but MultiMeasureRest isn't among the list of > grobs at the b

Re: MacOS instalation

>> Maybe you are using something else? In particular, I couldn't >> find a definition of `\jazzOn`... > > That is in version 1.0, which has the different file LilyJAZZ.ily. > cf > https://lists.gnu.org/archive/html/lilypond-user/2014-05/msg00322.html Thanks. Well, I don't have sufficient ti

Re: MacOS instalation

> In creating a tiny working example, I focused on a few bars of the > composition and removed the rest of the code for the song. In the > process I discovered specifically that \include-ing LilyJAZZ.ily > seems to be the culprit- turn it off, the up-stem notes are rendered > correctly; turn it o

Re: Reducing the space in front of notes with accidentals

> Setting `Accidental.extra-spacing-width` property with a pair of > value works, but I am quite confused with what the first and second > value really mean in this pair. This property manipulates the horizontal interval spanned by the accidental (as mainly given by the accidental glyph's horizo

Re: Reducing the space in front of notes with accidentals

> The following image is an example of the space imbalance caused by > accidentals. You are not using the standard LilyPond music font. Do you get imbalanced accidentals with Emmentaler, too? Otherwise it might be that the font isn't set up properly for use with LilyPond. > I hope to reduce t

Re: MacOS instalation

> The Lilypond package seems to work well (with one exception, which > is that beamed stems facing up are printed with the note head > preceding and slightly disconnected from the stem, as if just > mirrored upwards). Details, please, with code and images (before and after). This might be a bug

Re: Suppressing a "programming error" message

>> Irrespective of the technical problems with LilyPond I would really >> like to see a scan of the printed score you want to replicate – up >> to now I've never experienced a piece that starts with grace notes >> only right before a bar line... > > Joachim Andersen no.22 of 24 Etudes for Flute.

Re: Suppressing a "programming error" message

> Alternatively, of course, perhaps someone can suggest a better way > of producing the grace notes and barline before the first main note. Irrespective of the technical problems with LilyPond I would really like to see a scan of the printed score you want to replicate – up to now I've never expe

Re: FYI: Nested Markuplist-Score-Midi Block Behavior

>> If you compile that you can see that the `\score` markup command >> suppresses page turns because they don't make sense in markup. > > And I suspect that that's why \score-lines isn't called \score as > well. Contrary to `\score` (the markup function), which returns a single markup, `\score-

Re: FYI: Nested Markuplist-Score-Midi Block Behavior

[Sending this e-mail again to the 'lilypond-user' list, which we forgot to include in our conversation.] >> Maybe you are mixing up the the `\score` *markup* command (to be >> used within `\markup` or `\markuplist`) with the 'normal', >> top-level `\score` command? > > My initial reaction to th

Re: FYI: Nested Markuplist-Score-Midi Block Behavior

> I don't know whether this is a bug or not, but if you put a score > block inside of a markuplist, you cannot export MIDI from it. If > it's not fixed, it should be documented at the website. > > Minimal(?) example: > > \markuplist { > \score { > { c1 } > \layout { } >

Re: Programmatically sized markup?

> Ah - it would appear that there is a typo on the doc page, which > refers to make-center-markup (which doesn’t exist) but > make-center-column-markup does. https://gitlab.com/lilypond/lilypond/-/merge_requests/2488 Werner

Re: How to Change the Stem Style for Half Notes in TabStaff to Use Single Stems Instead of Double Stems?

> Thank you for your response. Below are two examples that illustrate > the more traditional way of displaying half note stems [...] Thanks – so please open an issue :-) Werner

Re: How to Change the Stem Style for Half Notes in TabStaff to Use Single Stems Instead of Double Stems?

> My question is: Is there a setting or option in LilyPond that allows > for changing the default behavior of half note stems in TabStaff? > Specifically, I’m looking for a way to switch the current > double-stem display to the more traditional single, shorter stem > that’s commonly used for half

Re: (file-exists? and expanding search path --include=DIRECTORY

> First time post [...] Please resend your e-mail – your example came out completely scrambled. If you have an e-mail program that ruins copy-and-paste material (as it appears to be the case), please create an attachment instead to preserve good formatting of your example code. Werner

Re: merge parts/voices

> I'd be happy if an option to supress stemUp/stemDown altogether was > present; removing them is the first thing I do. Just say `musicxml2ly --help` and you will see, among other options, ``` --nsd --no-stem-directions ignore stem directions from MusicXML, use li

Re: merge parts/voices

> c) Full measure rests are now not gathered (e. g. R1 R1 R1 instead >of R1*3 in the earlier version) -- regression?? MusicXML test file, please. Werner

  1   2   3   4   5   6   7   8   9   10   >