Hello list, hello Han-Wen, I did ask me - without any answer - why You threw off this feature of slurattachment-offset. For me lilypond would be missing some important, if it wouldn't be possible to
Thank you for all the answers but I couldn't find a solution to my slur tuning problem. The control-points property is indeed very difficult to use and too rigid. 1. I think it is necessary to re imp
Thank you very much. I've just installed version 2.6.3 and many slurs look a little better. But still they need some predefinitions, so I didn't remove commands \override. They work still. Best regar
The slur support has been reimplemented in version 2.6 and further improved in the latest development versions, 2.7.9 or later. Before you invest too much time on tweaking the output of version 2.4,
Dear Mats, Thank you ever so much for your help. Your comments have been very enlightening and your code clean and efficient. I would have sweared that I had tried << g4 \\ g >> for the note with two
It depends how you far you want to go. The best option would be an S style slur, ie. _________________________/ / but that is not supported by Lilypond out of the box. (Your slur really is too diffic
Hi List, Here is something that pops up now and then when I'm engraving with LilyPond: if a key signature has a lot of sharps, like the key of e major, sometimes a continuation slur will be too clos
Hello, Could you, please, provide guidance on how to manage the repeated slure in \volta 2? Problem There is no simple and convenient way to repeat a slur in \volta 2, while the slure from the \repea
Hi everyone, Is there any way to place an elision slur below an entire syllable (not between syllables), as shown in the example? And does anybody know the proper name for this thing? Since I'm not
Well, if we’re doing everything the way Elaine Gould wants us to, then: - articulation should go generally go next to the notehead, not next to the stem; but - the marcato mark usually goes above t
Mike Any requirement that the marcato to be below the note? Mark The following code \relative c' { d4-^( e4 f4-.) r4 } produces a slur with all articulation marks “inside” the slur. Typically, ho
Le 19/10/2020 à 23:43, Marc Shepherd a écrit : In the example shown below, notice that the slur is incorrectly pointing upward, and "crashing" into the tuplet bracket. It only happens with both th
On 2020-09-12 7:58 am, Luca Rossetto Casel wrote: I'd like to express a huge *thanks!* to all you you for the marvellous work! As Kieren, I'd also find very useful being able to choose between rotate
I’ve come back to this after a bit and have found a deal breaker of a problem: when the slur spans over notes which go both up and down, the note heads after the turn around collide. See attached e
<snip> That's about as much as I can contribute, I guess. Does anybody have an idea what precisely is causing the problem? Hmm, this works for me on 2.19.82 running on OSX under Frescobaldi. No extra
Am Fr., 19. Apr. 2019 um 18:01 Uhr schrieb Aaron Hill <address@hidden>: Look at the attached images, the one with fixed font-sizes does not respond to changed staff-space staffSize = #(define-music-f
Beziers are one way to generalize simple linear interpolation to higher orders, and they have a rather curious recursive relationship which my code exploits. In linear interpolation, we only have two
Am Mi., 17. Apr. 2019 um 10:13 Uhr schrieb Lukas-Fabian Moser <address@hidden>: Hi Lukas, Well, it's a little cheating involved :) LilyPond does checks for grob-properties, you can't write \override