Re: avoid alignment of hairpin and dynamic text

>> How can I avoid the vertical alignment of a hairpin and a dynamic >> text that starts or stops the hairpin? For example, in this >> situation >> >>{ f1\< | e''\p } >> >> I want to make LilyPond position the `\p` independently of the the >> crescendo – in particular, I don't want to fiddle

avoid alignment of hairpin and dynamic text

How can I avoid the vertical alignment of a hairpin and a dynamic text that starts or stops the hairpin? For example, in this situation { f1\< | e''\p } I want to make LilyPond position the `\p` independently of the the crescendo – in particular, I don't want to fiddle with `padding`,

Re: LilyPond on macOS 11 with Apple M1 Processor

> has anyone already tried to run LilyPond and MacPorts on an Apple M1? https://ports.macports.org/port/lilypond/summary Werner

lilypond on Apple silicon

According to https://ports.macports.org/port/lilypond/summary the problems with the dependencies have been fixed; this means that lilypond should now install fine using MacPorts on Apple silicon. Werner

Re: Why does -dbackend=svg -dcrop remove system-system-spacing?

>> Oh, sorry, I thought it was obvious. I vote against adding a new >> argument to `-dcrop`. > > Why? The description quoted shows that an argumant is optional. My objection is by principle. Backward compatibility doesn't make sense to me for situations that are (a) completely buggy, and (b)

Re: Why does -dbackend=svg -dcrop remove system-system-spacing?

>> > Perhaps the syntax and functionality of -dcrop could be extended to >> > include: >> > >> > ie default #f: as now, no cropped output >> > -dcrop ie #t: preserve whitespace, set as one long cropped >> > *page* >> > -dcrop num separate cropped *systems* by num mm

Re: Why does -dbackend=svg -dcrop remove system-system-spacing?

> Perhaps the syntax and functionality of -dcrop could be extended to > include: > > ie default #f: as now, no cropped output > -dcrop ie #t: preserve whitespace, set as one long cropped *page* > -dcrop num separate cropped *systems* by num mm of whitespace > (mm is

Re: convert-ly error

> `convert-ly` is a python script. For Windows, rename the file > > c:\Program Files (x86)\usr\bin\convert-ly > > to > > convert-ly.py > > Then Windows will know to run the python interpreter on this file. > > NOTE: This script works as is on Linux because the first line of the > script

Re: Why does -dbackend=svg -dcrop remove system-system-spacing?

> In the upcoming release of Abjad’s docs, my workaround has been to > add transparent markup “struts” above notes in the top system, [...] Nice idea! For multi-system cropped output this is a good temporary workaround IMHO. > Knowing all this, would it be possible to allow for a >

Re: Why does -dbackend=svg -dcrop remove system-system-spacing?

>> For me, it's a bug, mainly because the behaviour is completely >> unexpected. Also, `-dhelp` says >> >> crop (#f)Match the size of the normal output to the >>typeset image. >> >> which differs from the reality. Note the words 'normal output'.

Re: Why does -dbackend=svg -dcrop remove system-system-spacing?

>> $ lilypond-2.21.80-1.linux-64/bin/lilypond --svg -dcrop Bača.ly >> will produce the tightly packed: >> E ┌──┐ >> │▒▒│ >> │▒▒│ >> │▒▒│ >> └──┘ >> which is what you implied you didn't want (by saying "Is this >>

Re: Staff space size

> On 2021-01-06 6:41 pm, Andrew Bernard wrote: >> If staff height is 20 points, then what is the staff space size? Maybe >> I am overthinking this but suddenly I thought there may be some factor >> of including or not including the staff lines in the measurement. It >> is not immediately apparent

Re: Please help

> I would like to get in touch with J. B. He did/engraved (?) "Du süße > Lieb, schenk uns deine Gunst" by LilyPond on 27. 8. 12. On the > score sheet it says "Music engraving by LilyPond 2.16.0. (Would this > information help?) No, this is doesn't help. However, a quick search in the internet

Re: Placement of tuplet brackets

> I am trying to build a package for Persian percussion (for tombak > and daf instruments) while learning Lilypond. Interesting! > Back to my current struggle with tuplets: I cannot find a way to > tweak Lilypond through its tuplet-bracket interface (or any other) > to place tuplet brackets

Re: A comment about the documentation

> Perhaps Hans can help you do the build using MacPorts. BTW, all ingredients for building the complete documentation on a mac with MacPorts are there, AFAIK – except texi2html 1.82, for which no MacPorts package exists (yet). Werner

Re: Use TTF font for text in working directory?

> Is it somehow possible to tell Lilypond to look for the .ttf file in > the working directory, ie. the directory in which the .ly file is > that is being compiled? Yes. Here's some documentation from the current development version; the two mentioned scheme functions, however, are present in

Re: Summer of Code 2021

> Dear list, will the Lilypond google "summer of code" program run in > summer 2021? Probably yes. > Who should I be in touch with regarding possible projects and > preparation? I suggest that you contact the 'lilypond-devel' list. Werner

Re: OTF text font family with optical sizes : unable to access regular font

> No, I haven’t. See the attachment. Thanks. Looking around in the internet, searching for "Arno Pro" fontconfig I found the following. https://github.com/gadmm/fix-fontconfig-opentype-size It looks to me that this is exactly what you need. Werner

Re: OTF text font family with optical sizes : unable to access regular font

>> I’m having an issue using the Arno Pro typeface as a text font in >> LilyPond. [...] Have you already sent us the output of fc-list | grep 'Arno Pro' ? Werner

Re: vertical positioning of text spanners and hairpins

>> So one would *think* the following would work: >> >> \new Dynamics { >> s2\tweak DynamicLineSpanner.outside-staff-priority #1000 \< >> s2\tweak outside-staff-priority #0 >> \tweak bound-details.left.text "rit." >> \startTextSpan | >> s1\!\stopTextSpan >> } >> >> However, there’s

Re: how to give more horizontal space to the voice follower

>> Looking up the e-mail archive for 'lilypond-devel' I couldn't find >> relevant info. Do you have a link? > > Have a look at > https://lilypond.org/doc/v2.21/Documentation/notation/spanners.fr.html > > Apparently some spacing calculations need to be triggeredby hand. Well, that's exactly

Re: how to give more horizontal space to the voice follower

>> >> \override VoiceFollower.springs-and-rods = #ly:spanner::set-spacing-rods >> >> In case there aren't serious reasons against doing it I suggest to >> change the default; I would also prepare a patch. > > I vaguely remember having #ly:spanner::set-spacing-rods the default > caused

Re: how to give more horizontal space to the voice follower

>>> Why doesn't the `VoiceFollower` grob obey the `minimum-length` >>> property (inspite of supporting the `spanner-interface`)? What am >>> I missing? >> >> add >> >> \override VoiceFollower.springs-and-rods = #ly:spanner::set-spacing-rods What's actually the reason to not have this set by

Re: how to give more horizontal space to the voice follower

>> Why doesn't the `VoiceFollower` grob obey the `minimum-length` >> property (inspite of supporting the `spanner-interface`)? What am I >> missing? > > add > \override VoiceFollower.springs-and-rods = #ly:spanner::set-spacing-rods > ;) Thanks! Werner

how to give more horizontal space to the voice follower

Dear LilyPond community, please consider this MWE: << \new Staff = "R" { \showStaffSwitch s2. c'''4 | \change Staff = "L" a4 \override VoiceFollower.minimum-length = #20 s2 a4 | \change Staff = "R" c'''4 } \new Staff = "L" { s1 | s1 | s4 } >>

Re: Point & Click with Atom

> ¹ I'm not sure of the distinction between Character and Column in the > textedit string. Perhaps it's used by spreadsheets or something. There exist 'wide characters', for example CJKV ideographs, which use two columns per character on the terminal. Werner

Re: vertical positioning of text spanners and hairpins

> From > : > "changing outside-staff-priority of the Hairpin object will have no > effect on the vertical positioning of hairpins – you must change > outside-staff-priority of the associated DynamicLineSpanner object

Re: vertical positioning of text spanners and hairpins

>>> how can I make the 'rit.' appear below the hairpin? >> >> WARNING: HACK AHEAD! SOLUTION MAY NOT WORK BEYOND MWE!! >> >> \new Dynamics { >>s2\tweak outside-staff-priority #1000 \< >>s2_\tweak outside-staff-priority #2000 >> \tweak bound-details.left.text "rit." >>

Re: vertical positioning of text spanners and hairpins

>> how can I make the 'rit.' appear below the hairpin? > > WARNING: HACK AHEAD! SOLUTION MAY NOT WORK BEYOND MWE!! > > \new Dynamics { >s2\tweak outside-staff-priority #1000 \< >s2_\tweak outside-staff-priority #2000 > \tweak bound-details.left.text "rit." > \startTextSpan |

vertical positioning of text spanners and hairpins

[lilypond 2.23.0] Folks, how can I make the 'rit.' appear below the hairpin? Any value of `outside-staff-priority` seems to be ignored... \new Dynamics { s2\tweak outside-staff-priority #1000 \< s2\tweak outside-staff-priority #2000 \tweak bound-details.left.text "rit."

Re: Questions From a New User

> [...] I take it the "angle brackets" are the < and > symbols? The > reason I ask is because screen readers often read these out as > "less" and "greater". Yes. The terminology is a bit unfortunate – indeed, “less than” and “greater than” are the correct names for the ASCII characters < and

Re: Questions From a New User

> After looking into several different score-writing software, I am > now studying LilyPond to see how I could use it to produce music > scores. [...] > > We have been making our way through the Learning Manual and are > struggling with the concepts underlying the construction of chords, >

Re: Some wild considerations and a question

Hello Jacques, > There have been very interesting discussions about all this at the > Salzburg conference last January, which lead me to dream of things > being done another way in an ideal world: [...] > > - switch to another, easier to read and write extension language. > Someone suggested

Re: No ledger for custodes beyond 5-line staff

>> I was engraving a piece of chant in modern notation recently, and >> discovered that none of the custodes will draw a ledger for middle >> C (C4) or A5, notes beyond the 5-line staff. These notes do occur >> in chant and polyphony. [...] > > Perhaps this: [...] > > The above hack does

Re: Tremolo in MIDI

> Ah. It's described in A.19 Available Music Functions. Hard to find > because not indexed. Really? In my locally generated PDF of the NR the entry in the appendix *is* indexed. Werner

Re: Tremolo in MIDI

> Where is \unfoldRepeats in the NR? Its usage is described in section 3.5.6, “Using repeats with MIDI” – it's also in the index... Werner

Re: Future of openLilyLib

>> \reshape ? > > Dude… nice work. =) Care to submit a MR? Werner

Re: Setting Gregorian chant: Note spacing for two note neumes seem to depend on length of lyric text

> I disagree with the approach the NR demonstrates. [...] Could you submit a patch that improves that? Werner

Re: Export to musicxml

> What is the current state of the art with musicxml export? Any work > being done on that? I think the best stuff currently avaible is what Jacques is working on in the (external) `libmusicxml` git repository (in the `lilypond` branch). Werner

Re: organ - off topic

>>> * The _soft_ pedal (left, una corda) does indeed have a rough >>>equivalent on many organs, namely the "Schweller": >>>https://en.wikipedia.org/wiki/Swell_box There is another one: The most natural damper for an organ is the main entrance door of a church... Werner

Re: Request for East Asian emphasis points

> Does that idea gazump my offer to put it in OLL? I'd really like to > see it there. LSR and OLL are certainly not exclusive :-) I know that your code fits well to the former, but I have no idea about the latter. Werner

Re: Request for East Asian emphasis points

> The new \text-emphasis markup command mostly maps to the CSS style > of the same name but does not have full feature parity. Of note, > the markup command will apply the emphasis mark to any character, > whereas the CSS standard says to omit marks for certain character > classes (Z* and P*, in

Re: Request for East Asian emphasis points

> Yes, but I can exactly see that one of the few places > Japanese/Chinese emphasis dots may be used is in lyrics, which I > guess is the OP's intent. Also having a (minor) Sinology background, I've never seen emphasis dots in scores from Taiwan, including music using the jiǎnpǔ notation. I

Re: Request for East Asian emphasis points

> I would like to request an implementation for text emphasis points > native to East Asian scripts. Please give an example how this is used. And with “example” I mean a real-word example like existing scores. Note also that LilyPond is *not* suited for large textual works. Support for text is

Re: A slur enclosed by parentheses or brackets

>> Is there an easy way to have a slur enclosed by parentheses or >> brackets? Some urtext editions use parenthesized slurs to indicate >> editorial additions. > > \parenthesize does not currently handle spanners, so you would need to > do some manual work. > > Consider: [...] Here is a

Re: macro for \once\override

> \propertyTweak finger-code #'below-string > FretBoard.fret-diagram-details > > is completely indistinguishable from > > \propertyTweak fret-diagram-details.finger-code #'below-string > FretBoard > > So any commands stacked before this last \propertyTweak command have > no way of knowing

Re: macro for \once\override

>> BTW, would it be possible to enhance `\propertyTweak` to write >> >> \propertyTweak fret-diagram-details.dot-color #'white >> FretBoard >> >> as >> >> \propertyTweak dot-color #'white >> FretBoard.fret-diagram-details ? > > Have you even tried? Only

Re: macro for \once\override

> Maybe > > \void \displayLilyMusic > \once > \propertyTweak color #red > \propertyTweak font-size #3 > \propertyTweak direction #UP Voice.Slur > > helps? It does, thanks a lot! I didn't have this function on my radar, and it isn't documented in the NR at all. Attached a version using

Re: macro for \once\override

> No. I'm against it. Introducing abbreviations into examples is a > slippery slope and sets a bad precedent. In my scores I use \t for > \tuplet, but I would never inflict that on any public example, even > to save space. Wrapped lines are not a visual or semantic issue to > me at least.

Re: macro for \once\override

>> Well, we have to make a compromise. The PDF document has a small >> line width, and you can't scroll horizontally... > > Then you just have to wrap the line. I'm Mr. Wrap-Line, as can be seen by many of my commits. If I think that wrapping is suboptimal and reduces legibility I hope you

Re: macro for \once\override

>> Well, we have to make a compromise. The PDF document has a small line >> width, and you can't scroll horizontally... >> >> Theoretically, the snippet could be printed with a smaller font size, >> but this doesn't look very pretty IMHO. I consider the `\oo` >> shorthand both innocuous and

Re: macro for \once\override

>> However, saying >> >> \oo VeryLong.Grob.PropertyToBeChanged = foo >> >> for this (and only this) snippet is just fine. > > I don't think that it makes sense for snippets to introduce > convenience shorthands unless the snippet in itself tries is about > showcasing the shorthand. It detracts

Re: macro for \once\override

>> Because right now LSR is still using this version. > > Then that means we have to use that oo code in the NR? I am not sure > I follow. I'd rather not please. Right now I'm checking the NR for bad typography in the PDF version, which usually means overlong lines. A lot of snippets are

Re: macro for \once\override

> oo = #(define-music-function (parser location prop value) >(symbol-list? scheme?) > #{ \once \override #prop = #value #}) > > should likely work fine in 2.18. Thanks! Aaron provided this version oo = #(define-music-function (parser location prop value) (list?

Re: macro for \once\override

> I side step the whole thing by having dynamic expanable macros in > the text editor. But this gives overlong lines, which I want to avoid for snippets taken from the LSR and being part of the NR. > And why use 2.18? Because right now LSR is still using this version. Werner

Re: macro for \once\override

> Like this, I would imagine: > > > \version "2.18.2" > > oo = > #(define-music-function > (parser location grob-path value) > (list? scheme?) > #{ \once \override $grob-path = #value #}) Great, thanks! Werner

Re: macro for \once\override

>> I wonder whether there is a possibility to have a working equivalent >> to >> >> oo = \once\override >> >> so that I can say >> >> \oo foo.bar = #'baz . > > The best you can aim for is > > \oo foo.bar #'baz This would be just fine. The thing is to replace `\once\override` with

macro for \once\override

Folks, I wonder whether there is a possibility to have a working equivalent to oo = \once\override so that I can say \oo foo.bar = #'baz . It should work with LilyPond 2.18, BTW. A quick search in the internet didn't bring something relevant. Help would be much appreciated.

Re: accidentals and broken bars

>> Is there a possibility to automatically get a sharp accidental for >> the third quarter note? I could neither find a hint in the manual >> nor in the regression tests... > > Accident rules are implemented before line-breaking. If they were > to take line-breaking into account, they'd need

Re: accidentals and broken bars

> That's a pity, I guess, but seeing that you're manually putting a > mid-bar break, it makes sense to manually mark the needed accidental > as well. For my use case I really would like to have automatic behaviour. The example sent to the list was just for demonstration purposes; in reality

Re: accidentals and broken bars

> If you need it automatically, I'm not sure if \accidentalStyle > "neo-modern" repeats the accidental after a break. Thanks for the idea, but no, it doesn't. As far as I can see, broken bars aren't covered at all by the available accidental rules. Werner

accidentals and broken bars

Folks, look at this example: \paper { line-width = 50\mm } { c'4 cis' \bar "" \break cis' c' } Is there a possibility to automatically get a sharp accidental for the third quarter note? I could neither find a hint in the manual nor in the regression tests... Werner

Re: partially parenthizing a chord

> ParenthesesItem.stencils relies on > "accidentals.leftparen"/"accidentals.rightparen". The size is > usually done via ParenthesesItem.fontsize. I often find this not > convincing, especially for huge Parens. Why not build the stencils > using (improved) parenthesize-stencil? Including sort

Re: partially parenthizing a chord

> Here is a version that still relies on scaling, but does so in a > hopefully more visually appealing manner. Note that I am using the > square root of the y-scaling factor for the x-scaling factor, as 1:1 > scaling made the parens too fat in my opinion. Brilliant, thanks a lot! Please

Re: partially parenthizing a chord

>> I would like to parenthesize the lower two notes of the chord. >> There should be a single parenthesis to the left and right >> (contrary to what `\parenthesize` does). > > Does something like this help? Yes, very nice! > (The logic here is for the engraver to generate a single >

partially parenthizing a chord

Consider the following chord: { } I would like to parenthesize the lower two notes of the chord. There should be a single parenthesis to the left and right (contrary to what `\parenthesize` does). Looking up the LSR I couldn't find a generic solution that isn't an ad-hoc trickery, thus I'm

Re: adjusting vertical positions of start and end of tie

> you could translate the control-points _iff_ left/right-bound's > staff-positions are not equal. Thanks a lot for the code! It's something to have in mind if it becomes *really* necessary. Werner

Re: adjusting vertical positions of start and end of tie

> I don't find that Tie supports 'positions. Strange. Seeing Gould's advice it's not so surprising. On the other hand, I'm actually in favor of adding it, for very special situations. > You could do this with \shape used as a tweak. Roughly: > > \relative c' { > \clef "alto" d'2 \shape

Re: adjusting vertical positions of start and end of tie

> o "incorrect" has a tie winding its way from one vertical position > to another, in the process wrapping around the new clef sign. Thanks for the info! I just want to mention that in complex piano music even the 'incorrect' solution has to be used from time to time. Note that the problem to

Re: adjusting vertical positions of start and end of tie

> I see at least three options: > > - The tie should be sloped like a slur. If you really have to do that (for whatever reason), this is the solution to go IMHO. > - The tie should be split into a two halves (possibly > dotted/dashed), each half attached to the terminal notes but >

Re: adjusting vertical positions of start and end of tie

> Look at this example > > > \relative c' { > \clef "alto" d'2 \tweak positions #'(8 . 4) ~ > \clef "treble" d2 > } > > The `\tweak positions` doesn't work – which is kind-of expected. > However, for this very situation it would be nice if I could change > the start and end

adjusting vertical positions of start and end of tie

Look at this example \relative c' { \clef "alto" d'2 \tweak positions #'(8 . 4) ~ \clef "treble" d2 } The `\tweak positions` doesn't work – which is kind-of expected. However, for this very situation it would be nice if I could change the start and end position of the slur

Re: What happened to INSTALL.txt?

>> Seems to me like kind of a chicken-and-egg problem, though. In >> order to build lilypond I need to read INSTALL.txt, but in order to >> read INSTALL.txt, I need to build lilypond first... I ended up >> googling for the file on the website and following the steps from >> there instead. > >

Re: 2.21.3 build problem on Mac OS X Mojave

> In fact I did the ‘git clone’ afresh, moving aside previous > attempts. Thus the contents of ‘build’ on both OSes is the result of > the commands I showed, up to '../configure'. > > That’s why I don’t get what happens… For me, using an up-to-date MacPorts system, compilation of LilyPond from

Re: 2.21.3 build problem on Mac OS X Mojave

> I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and > Mac OS X 10.14.6 (Mojave). On the latter, I installed Apple’s > XCode, the needed tools in /opt with MacPorts, and the needed fonts > in /opt/local/share/fonts/urw-core35-fonts. You might apply

Re: Text spanner with centred text state of the art

> On this perennial topic, it would be great if this function could be > in baseline lilypond. It's in countless scores, and I know people > want it. Assuming that your problem can't be handled in current lilypond I'm rather sure that a merge request prepared by you will go into the git

Re: bug in \caps

>> > \caps does not work with non ASCII characters: >> >> Irrespective of the problem, the character 'é' is *not* part of >> ASCII. The ASCII character is quite an old 7bit character set, >> approximately what we have today in Unicode at positions U+ to >> U+007F. > > yes, this is why I

Re: bug in \caps

> \caps does not work with non ASCII characters: > \version "2.19.84" > \markup { \caps "Blée" } > In this example, the 3rd character "é" is not converted to É. > Kind regards, Irrespective of the problem, the character 'é' is *not* part of ASCII. The ASCII character is quite an old 7bit

Re: Fonts for text

>> The "," trigger the magic. However, I do not find the document about it. >> Maybe I am in a wrong way. > > In > http://lilypond.org/doc/v2.20/Documentation/notation/fonts#single-entry-fonts > there's: > "font-name can be described using a comma-separated list of ‘fonts’ > and a white-space

Re: SVG style and contributing barrier to entry

> In any case, I'm subscribed so I'll cross-post and CC James so > that the patch (which looks correct to me) is not lost. I've just applied it to staging. Werner

Re: SVG style and contributing barrier to entry

> I just discovered that the “style” tag created inside svg output > uses the wrong syntax, [...] > > A trivial one-line patch to fix this (based on git master): [...] Thanks. > Wanting to submit this patch, I've looked at the LilyPond > Contributor's guide¹, and frankly, I'm amazed by the

Re: Internet-style quoting

> Unfortunately, as is shown in the thread that Aaron refers to in his > excellent response, Outlook for Mac does not support setting the > indent character; the only thing we have available is indentation. > > After all, why would anybody want to do anything other than > top-posting? ( Then

Re: A request on behalf of Turkish Music

[Carl, could you somehow improve the layout of your responses? If I view the plain text version of your e-mails, it's completely impossible to differentiate between quoted material and your reply. But even in the HTML version I have such difficulties... What about using the classic '>'

Re: A request on behalf of Turkish Music

> If a pattern like TFM.LY (Turkish Fol Music) is created, I think it > will be a more rational and progressive solution like MAKAM.LY. I > think the use of numbers for every flat and sharp in the work will > make things more difficult. I don't understand the last sentence. Please elaborate.

Re: A request on behalf of Turkish Music

> A combination of makam.ly and this definitions.ily should be easy to > do. But as Werner said, having them in the Emmentaler font (one way > or the other) would be better. Well, here's the question: Shall we add such glyphs at all? A cautionary and a digit can easily be combined on the

Re: A request on behalf of Turkish Music

Hello Emre, > [...] Turkish Folk Music has its own flat and sharps. > > How can I add this fonts/graphs to lilypond system This should be rather easy, I think – however, some information is missing. * Is it correct that the 'Dort' sharp doesn't have number 4 assigned to it? * In the

Re: Unwanted warnings/errors on pedals for multiple voices

>> I never saw any music engraver who uses it. > > and most of my piano scores of publishing houses do it like this. I > have examples here by Schott and Henle. I think this dispute deserves an issue in our tracker. Obviously, there are two engraving schools, an older one to which Paolo

Re: MacPorts stable version lacks mactex variant

> The lilypond port for MacPorts (i.e. the stable version) doesn’t > have a mactex variant like lilypond-devel and thus will end up > installing several the MacPorts texlive packages which are redundant > on systems which already have MacTex installed. Should I be > reporting this to the

Re: Peculiar behavior of barlines

> [...] This is the snippet! I know that it would do a lot for people > like me, maybe it should be included in the section about barlines? Mhmm, this is very special, and LilyPond's documentation is already more than 2000 pages... I rather suggest that you contribute a well-documented snippet

Re: Peculiar behavior of barlines

> The reason for the not minimal example is because each staff has its > own timing. [...] Well, the problem at hand is not related to polymetric notation at all, AFAICS; you can use standard stuff also to demonstrate the problem... Werner

Re: In TabVoice - how to avoid: "programming error: side-axis not set for grob StrokeFinger"

>> Or maybe there is a bug somewhere? I think not having to think >> about the order would be quite beneficial. > > I totally agree there, but the New_fingering_engraver has been > designed that way and it's complicated enough. It'd be great of > course if someone had a good idea how to get

Re: In TabVoice - how to avoid: "programming error: side-axis not set for grob StrokeFinger"

> In order to avoid this problem of sequence, I've first removed > Script_column_engraver and appended it again /after/ > New_fingering_engraver. Looks funny but actually solves the > problem. > > [...] > \remove "Script_column_engraver" > \consists "New_fingering_engraver" % *before*

Re: Testing dynamic-markup

> I had gonville- and emmentaler-fonts in two directories: > ~/fonts and ~/.local/share/fonts > (I probably may have put them in there for some tests long time > ago...) Deleting all of them there solved the issue. > > Anyway, I think LilyPond should be able to always pick emmentaler as >

Re: Clef "treble_8"

> thank you for your positive reaction. There are 3 files¹: > > - a cheat sheet: https://joramberger.de/files/lilypond_sheet_2.18_en.pdf > - “visual index”: https://joramberger.de/files/lilypond_visualindex.pdf > - spacing overview: https://joramberger.de/files/LilypondSpacing.pdf All of them

Re: key change at end of snippet

From: David Kastrup Subject: Re: key change at end of snippet Date: Sat, 25 Jan 2020 09:41:45 +0100 > \relative c' { > \key d \major > d1 > \key c \major > \grace s256 > } Thanks for the suggestion! I'm now trying Thomas's route. Werner

Re: key change at end of snippet

>> I have to typeset a snippet that is an excerpt of a longer piece, >> and this snippet ends with a key change: >> >> \relative c' { >> \key d \major >> d1 >> \key c \major >> } >> >> However, the staff stops right before the key change, see attached >> image. What can I do to

Re: key change at end of snippet

>> I think it is necessary to somehow keep the staff line alive – I >> guess I can probably fake a solution by adding another bar with a >> suppressed bar line that contains some invisible music. Not sure >> yet whether this is sensible, and if yes, how to make the width of >> this extra bar

Re: key change at end of snippet

> \once \override Score.BreakAlignment #'break-align-orders = > #(make-vector 3 '( staff-bar > clef > span-bar > breathing-sign > ... > key > time-signature)), > > To

key change at end of snippet

I have to typeset a snippet that is an excerpt of a longer piece, and this snippet ends with a key change: \relative c' { \key d \major d1 \key c \major } However, the staff stops right before the key change, see attached image. What can I do to avoid that? Werner

Re: repeated accidental after tie crossing bar

>> some publishers repeat accidentals not only if a tie gets broken >> between staves but also if it crosses a bar line: >> >> ||| >>#o| #o >> \/ >> >> Is there a property in LilyPond to automatically activate this? > > probably: > > { > \override

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