Bevan:
Look up
\repeatTie
in the documentation for your version of Lilypond.
Mark
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
On Behalf Of Bevan Broun
Sent: Friday, October 20, 2023 5:48 PM
To: lilypond-user@gnu.org
Subject: slur at end of repeat on start?
Hi
I
Hi
I have a slur at the end of a repeat that needs to go on the the start of
the repeat. In the source document, the slur at the end extends to the
repeat bar line - not just the last note of the repeat.
any ideas?
Thanks
Bevan
Try
```
\displayMusic c'!
```
This shows you that the `!` syntax corresponds to setting
the `force-accidental` property to true. Thus, if you have
identified the note events you want to force accidentals
on, you can do
```
(ly:music-set-property! the-note-event 'force-accidental #t)
```
on
I have a piece that is in the following scale:
c d e fis g aes bes b
Is it possible to force the accidentals just for the bes and the b?
But here is the catch...
I am both transposing the part and respelling pitch-classes as show below. The
scale above is actually the resulting printed set of
> On 20 Oct 2023, at 16:19, John Bryant wrote:
>
>
> Hey lilypond users,
>
> My friend is creating hymns in their unicode non-roman script and they would
> like to increase the space a bit between the lines of lyrics. I saw that you
> can increase space between words but I couldn't find
David,
thanks for this. I had abandoned the melismaBusy method, as it was
throwing up all sorts of artefacts (blank bars and partially-blank
bars, etc.) when applied in a polyphonic setting. And the fixes for
parts starting with rests were beginning to make the source file rather
I have used tupletFullLength extensively, and it mostly does what I need
correctly. However, the illustration here shows the remaining issue with it -
which is specific to line breaks. Within a line, the RH end of the bracket is
correctly placed just before the bar line, but at a break it is
Mark Knoop writes:
> At 05:33 on 20 Oct 2023, Werner LEMBERG wrote:
>>> Shouldn't both tuplet brackets span every notecolumn within the
>>> purview of the last note's duration?
>
>> Yes, at least according to Gould. Using `tupletFullLength` helps, but
>> now tuplet brackets are too long:
>
>
At 05:33 on 20 Oct 2023, Werner LEMBERG wrote:
>> Shouldn't both tuplet brackets span every notecolumn within the
>> purview of the last note's duration?
> Yes, at least according to Gould. Using `tupletFullLength` helps, but
> now tuplet brackets are too long:
Since 2.25 there is also:
