Hi Rachael, per default, LilyPond prints _one_slur between legato-chords. This is common praxis in nearly all printed editions. LilyPond provides the possibility to tweak the slurs via their 'contro
2013/6/27 Rachael Thomas Carlson <address@hidden>: Hi Rachael, per default, LilyPond prints _one_slur between legato-chords. This is common praxis in nearly all printed editions. LilyPond provides th
There might be another point of interest: How to reset? I'm aware it could be done with a new #(assoc-set! ... ) using default values. I was wrong: This doesn't work! Sorry! Yes, if you set the 'padd
2011/9/23 eluze <address@hidden> i'm neither expert nor knowledgeable with scheme but i would prefer a solution that lets you define your own preferences and include them with -dinclude-settings=….
Am Fr., 19. Apr. 2019 um 23:37 Uhr schrieb Trevor <address@hidden>: Hi Trevor, yep, it's the same concern Lukas already raised. Attached the next iteration of the code. arrow-left/right will now oper
2018-03-04 0:03 GMT+01:00 Lucas Werkmeister <address@hidden>: Hi everyone, I stumbled across a bug where Lilypond generates a bad slur if the slur crosses a line break and there is a simultaneous cle
Hello all! Up until now I have never really dealt with chords using slurs and acciaccatura. I can't seem to get it to goto the proper note easily. When I do there is little to no consistency betwee
Aaron, Harm Could I please comment on just one feature? The overrides to add or inhibit arrow-heads at the left and right ends of the Slur are: \override Slur.details.arrow-left = #LEFT \overri
Am Mo., 15. Apr. 2019 um 19:26 Uhr schrieb Lukas-Fabian Moser <address@hidden>: Hi Lukas, I started to implement the functionality, finally I more or less rewrote anything. As David K once said: rewr
Risto, Not knowing the requirements/necessity of your putting the slur above the beam, I would put the slur down – closer to the note heads. This would/does avoid conflict with the number. Mark Fro
Hey, thanks for all the help everyone. I had the "cannot end slur" warning a lot of places in a previous score, and I'm pretty sure it was all due to the nested slur in the \acciaccatura. Best, Jonat
Hi there! I'm not very experienced with this command but I'll give it a try: If I understand this command correctly, it'll tell Lily how far away from the notehead or stem the slur will start or end.
Firstly, know that slurs are not the only way to define melismata. You can instruct LilyPond to have a single lyric syllable span multiple notes using \melisma and \melismaEnd: %%%% \version "2.20.0"
Hi Lucas, 2018-03-04 0:03 GMT+01:00 Lucas Werkmeister <address@hidden>: It's https://sourceforge.net/p/testlilyissues/issues/3287/ not fixed yet For this purpose the shape-command was developed, than
\override Slur.details.region-size = #5 \override Slur.details.accidental-collision = #1000 Thanks, all, for the suggestions. Increasing the slur region ended up pushing the slur rather high. So I en
Setting the control points of a slur manually [0.07280] Am 04.09.2013 16:17, schrieb MING TSANG: Hi, Urs: Thank you for the info pertain to phrasing slurs. I don't know how to code \change Staff in c
Ah – Perfect. Thank you. When I first learned lilypond it was around 2.18. I forgot this got added in the last couple of years. Thank you! From: Jean Abou Samra <jean@abou-samra.fr> Date: Wednesday
Folks, in https://archiv.lilypondforum.de/index.php?topic=1744.msg9669#msg9669, Harm invented a truly wonderful new feature allowing to add an arrow head to the right end of a Slur (or, for that matt
Hi David, thank you for now. This is proof that one can at least *get* to the right information, and when the use-case is clearer one may also find a more efficient approach if possible. Just one mor