Re: tied sharps after line break

[Martin Tarenskeen]

Ah I see. Yes that's the one.

Op zondag 3 maart 2024 om 18:21:59 +00:00:00 schreef Werner LEMBERG 
:



 2. LilyPond's default behaviour in this situation is (in my opinion)
 sub-optimal.


It's a bug known since 15 years...

  


Werner

Re: Help

[Karlin High]

On Sun, Mar 3, 2024 at 2:54 PM George  wrote:
> Thank you Karlin for the promptness with which you responded. I'm glad, but 
> unfortunately I can't benefit from your wonderful program because I use 
> Windows 7 and I don't have the resources for Windows 10. Anyway, thank you 
> and I wish you the best of luck in the future, George.
> God bless!

I am confident there is a way to get LilyPond running on Windows 7.

If not a current version, then one of the older ones.



PS: In future messages to the LilyPond community, use Reply All or
otherwise include lilypond-user@gnu.org in the list of recipients.
-- 
Karlin High
Missouri, USA

Re: Transpose tab into label forms

[Carl Sorensen]

What is "label form" for tablature?  I've never heard of it and couldn't find 
any information about it using Google.  So I don't know how to answer your 
question.

Carl



Get Outlook for Android

From: lilypond-user-bounces+carl.d.sorensen=gmail@gnu.org 
 on behalf of achar 

Sent: Sunday, March 3, 2024 8:10:36 AM
To: Lilypond User English 
Subject: Transpose tab into label forms

Hello to all.

With Frescobaldi I use the transpose tool to change the key of a piece.
One thing it doesn't do is transpose the tablatures into label form.
It would save me time.
Does anyone have any ideas or is this simply impossible?
Thank you for your attention . Good evening. Jean Pierre

Re: Using __ extender in lyrics

[Andy Bradford]

Thus said Hans Aikema on Sun, 03 Mar 2024 18:46:46 +0100:

> A solution to it is to put  an empty lyric ("") on the parenthesised f
> when there are no lyrics for it

That's so simple and I don't know  why I didn't think of doing just that
(hindsight  and  all  that)  instead  of trying  to  use  \skip  or  the
underscore.

Thanks,

Andy

Re: tied sharps after line break

[Werner LEMBERG]

> 2. LilyPond's default behaviour in this situation is (in my opinion)
> sub-optimal.

It's a bug known since 15 years...

  https://gitlab.com/lilypond/lilypond/-/issues/649


Werner

Re: tied sharps after line break

[Martin Tarenskeen]

Op zondag 3 maart 2024 om 18:58:45 +01:00:00 schreef Hans Aikema 
:
Does not yet cover the case Martin was looking for - omitting the 
second accidental in a situation of a line-break on a tied accidental.


Can be done however by an explicit \omit, which should be only \once, 
because otherwise it would omit accidentals from that point onwards.


The correct rendering (also showing the subsequent re-occurrence in 
the next bar) is done by this snippet:


%%%
\relative c' {
c4 c c cis ~ |
\break
cis \once \omit Accidental cis cis d | cis cis cis d
}
%%%

The disadvantage of it is that this can only be used with an explicit 
line break, as it will also be omitted if there is no linebreak on 
the tied note.


Ok, thank's a lot. That will do the trick for now but it also tells me 
2 things:

1. Anything is possible, but not always in the easiest way
2. LilyPond's default behaviour in this situation is (in my opinion) 
sub-optimal.


MT

Re: tied sharps after line break

[Hans Aikema]

Does not yet cover the case Martin was looking for - omitting the second 
accidental in a situation of a line-break on a tied accidental.

Can be done however by an explicit \omit, which should be only \once, because 
otherwise it would omit accidentals from that point onwards.

The correct rendering (also showing the subsequent re-occurrence in the next 
bar) is done by this snippet:

%%%
\relative c' {
c4 c c cis ~ |
\break
cis \once \omit Accidental cis cis d | cis cis cis d
}
%%%

The disadvantage of it is that this can only be used with an explicit line 
break, as it will also be omitted if there is no linebreak on the tied note.


> On 3 Mar 2024, at 18:47, Damian leGassick  wrote:
> 
> I had this yesterday, wasn’t immediately obvious but
> 
> https://lilypond.org/doc/v2.25/Documentation/notation/accidentals
> 
> hth
> 
> Damian
> 
>> On 3 Mar 2024, at 17:39, Martin Tarenskeen  wrote:
>> 
>> 
>> 
>> 
>> Op zondag 3 maart 2024 om 18:33:26 +01:00:00 schreef Hans Aikema 
>> :
>>> 
>>> 
>>> 
 On 3 Mar 2024, at 17:26, Martin Tarenskeen  wrote:
 
 
 Hi LilyPonders,
 
 I bumped into a situation similar to this tiny example (In the real score 
 the linebreak happened at such a situation without a forced \break but the 
 result was the same):
 
 \relative c' {
 c4 c c cis ~ |
 \break
 cis cis cis d |
 }
 
 the sharp sign in the 2nd bar is printed twice. I am not sure if that's 
 the correct behaviour?
 Without a \break the sharp is not printed for the tied 1st cis in the 2nd 
 bar, and only repeated for the 2nd cis in the 2nd bar.
  I can imagine the reason to print the sharp sign after a linebreak and/or 
 pagebreak. But in such a case I would not repeat the sharp on the snd 
 quarter.
>>> 
>>> The proposed behavior by Elain Gould in Behind bars (p 80) is to have a 
>>> single sharp, without braces, on the second line before the tied note.
 
>> 
>> Yes, that's what I had in mind. How can I prevent LilyPond from printing a 
>> second sharp in the second bar?
>> 
>> MT

Re: tied sharps after line break

[Damian leGassick]

I had this yesterday, wasn’t immediately obvious butAccidentals (LilyPond Notation Reference)lilypond.orghthDamianOn 3 Mar 2024, at 17:39, Martin Tarenskeen  wrote:Op zondag 3 maart 2024 om 18:33:26 +01:00:00 schreef Hans Aikema :On 3 Mar 2024, at 17:26, Martin Tarenskeen  wrote:Hi LilyPonders,I bumped into a situation similar to this tiny example (In the real score the linebreak happened at such a situation without a forced \break but the result was the same):\relative c' {c4 c c cis ~ |\breakcis cis cis d |}the sharp sign in the 2nd bar is printed twice. I am not sure if that's the correct behaviour?Without a \break the sharp is not printed for the tied 1st cis in the 2nd bar, and only repeated for the 2nd cis in the 2nd bar. I can imagine the reason to print the sharp sign after a linebreak and/or pagebreak. But in such a case I would not repeat the sharp on the snd quarter.The proposed behavior by Elain Gould in Behind bars (p 80) is to have a single sharp, without braces, on the second line before the tied note.Yes, that's what I had in mind. How can I prevent LilyPond from printing a second sharp in the second bar?MT

Re: Using __ extender in lyrics

[Hans Aikema]

> On 3 Mar 2024, at 18:01, Andy Bradford 
>  wrote:
> 
> Hello,
> 
> I  seem to  have some  fundamental  misunderstanding about  how the  __ 
> extender is to  be used in lyrics. It seems  that under some conditions 
> it doesn't behave as I would expect but I may be doing it wrong.


The __ will make the extender extend across any tied/slurred notes as well as 
any \skip-ped notes. Subsequent _ will extend the extender across 
non-tied/slurred non-skipped notes.

Therefor  your constructs tried in the other stanzas extended the extender to 
cover the parenthesised f.

A solution to it is to put an empty lyric (“”) on the parenthesised f when 
there are no lyrics for it

The modified example:


\version "2.22.2"

\paper {
  #(set-paper-size "letter")
}

\score {
  <<
\new ChoirStaff {
  <<
\new Staff {
  <<
\time 12/8
\new Voice = "voice" {
  \relative c'' {
a8 b c r4. r a8 b c
d,( e4~) e4. r4 \parenthesize f8 g g a
g2. r
  }
}
  >>
}
\new Lyrics \lyricsto "voice" {
  \set stanza = "1. " Sing -- ing o sing -- ing a |
  song, __ "" sing -- ing a
  song.
}
\new Lyrics \lyricsto "voice" {
  \set stanza = "2. " Some -- one sang.  They sang a
  song, __ "" a -- bout no --
  thing.
}
\new Lyrics \lyricsto "voice" {
  \set stanza = "3. " Sang a song? Who sang a |
  song? __ I sang a long
  song.
}
\new Lyrics \lyricsto "voice" {
  \set stanza = "4. " Here a song.  The song is |
  "gone," __ "" I can -- not
  sing.
}
  >>
}
  >>
}



> Thanks,
> 
> Andy

Re: tied sharps after line break

[Martin Tarenskeen]

Op zondag 3 maart 2024 om 18:33:26 +01:00:00 schreef Hans Aikema 
:




On 3 Mar 2024, at 17:26, Martin Tarenskeen  
wrote:



Hi LilyPonders,

I bumped into a situation similar to this tiny example (In the real 
score the linebreak happened at such a situation without a forced 
\break but the result was the same):


\relative c' {
c4 c c *cis* *~* |
\break
*cis* *cis* cis d |
}

the sharp sign in the 2nd bar is printed twice. I am not sure if 
that's the correct behaviour?
Without a \break the sharp is not printed for the tied 1st cis in 
the 2nd bar, and only repeated for the 2nd cis in the 2nd bar.
 I can imagine the reason to print the sharp sign after a linebreak 
and/or pagebreak. But in such a case I would not repeat the sharp on 
the snd quarter.


The proposed behavior by Elain Gould in Behind bars (p 80) is to have 
a single sharp, without braces, on the second line before the tied 
note.




Yes, that's what I had in mind. How can I prevent LilyPond from 
printing a second sharp in the second bar?


MT

Re: Multiple connected slurs

[Jean Brefort]

Try this:
  c''1:32( | c1:32 )( |  c1:32 )( | c4 ) r4 r2 |

you only need three slurs not four.

Hope this helps,
Jean Brefort (not the

Le dimanche 03 mars 2024 à 18:20 +0100, Gerardo Ballabio a écrit :
> Hello,
> please what is the correct way to draw multiple slurs connected to
> each other? Look at example below to see what I mean (result
> attached).
> 
> The following code does what I want but it gives multiple warnings
> like these:
> 
> Parsing...
> slur.ly:4:3: warning: Unattached SlurEvent
> Interpreting music...
> slur.ly:4:13: warning: cannot end slur
> 
> I tried using ties instead of slurs, that doesn't give warnings, but
> it doesn't look quite the same.
> 
> Thanks
> Gerardo
> 
> % slur.ly
> %%
> \version "2.24.1"
> 
> \new Staff \relative {
>   ( c''1:32 ) | ( c1:32 ) | ( c1:32 ) | ( c4 ) r4 r2 |
> }
> %%
> 
> % tie.ly
> %%
> \version "2.24.1"
> 
> \new Staff \relative {
>   c''1:32~ | c1:32~ | c1:32~ | c4 r4 r2 |
> }
> %%

Re: tied sharps after line break

[Hans Aikema]

> On 3 Mar 2024, at 17:26, Martin Tarenskeen  wrote:
> 
> 
> Hi LilyPonders,
> 
> I bumped into a situation similar to this tiny example (In the real score the 
> linebreak happened at such a situation without a forced \break but the result 
> was the same):
> 
> \relative c' {
> c4 c c cis ~ |
> \break
> cis cis cis d |
> }
> 
> the sharp sign in the 2nd bar is printed twice. I am not sure if that's the 
> correct behaviour?
> Without a \break the sharp is not printed for the tied 1st cis in the 2nd 
> bar, and only repeated for the 2nd cis in the 2nd bar.
>  I can imagine the reason to print the sharp sign after a linebreak and/or 
> pagebreak. But in such a case I would not repeat the sharp on the snd quarter.

The proposed behavior by Elain Gould in Behind bars (p 80) is to have a single 
sharp, without braces, on the second line before the tied note.

> 
> Is this a bug or a discussable way to interpret the conventions? 
> And: how can I override the current behaviour and choose where to print or 
> not print sharps whenever I want to?
> 
> MT
> 
> 
> 
> 

Re: Multiple connected slurs

[David Kastrup]

Gerardo Ballabio  writes:

> Hello,
> please what is the correct way to draw multiple slurs connected to
> each other? Look at example below to see what I mean (result
> attached).
>
> The following code does what I want but it gives multiple warnings like these:
>
> Parsing...
> slur.ly:4:3: warning: Unattached SlurEvent
> Interpreting music...
> slur.ly:4:13: warning: cannot end slur
>
> I tried using ties instead of slurs, that doesn't give warnings, but
> it doesn't look quite the same.
>
> Thanks
> Gerardo
>
> % slur.ly
> %%
> \version "2.24.1"
>
> \new Staff \relative {
>   ( c''1:32 ) | ( c1:32 ) | ( c1:32 ) | ( c4 ) r4 r2 |
> }
> %%

You need to use the correct syntax for slurs in the first place.  Both (
and ) come right after the note they connect to, and the reason for that
is exactly because it makes it easy to make properly connected adjacent
slurs.

You should not ignore syntax warnings LilyPond gives you: they indicate
a problem with your source file.

-- 
David Kastrup

Multiple connected slurs

[Gerardo Ballabio]

Hello,
please what is the correct way to draw multiple slurs connected to
each other? Look at example below to see what I mean (result
attached).

The following code does what I want but it gives multiple warnings like these:

Parsing...
slur.ly:4:3: warning: Unattached SlurEvent
Interpreting music...
slur.ly:4:13: warning: cannot end slur

I tried using ties instead of slurs, that doesn't give warnings, but
it doesn't look quite the same.

Thanks
Gerardo

% slur.ly
%%
\version "2.24.1"

\new Staff \relative {
  ( c''1:32 ) | ( c1:32 ) | ( c1:32 ) | ( c4 ) r4 r2 |
}
%%

% tie.ly
%%
\version "2.24.1"

\new Staff \relative {
  c''1:32~ | c1:32~ | c1:32~ | c4 r4 r2 |
}
%%


slur.pdf
Description: Adobe PDF document


tie.pdf
Description: Adobe PDF document

Using __ extender in lyrics

[Andy Bradford]

Hello,

I  seem to  have some  fundamental  misunderstanding about  how the  __ 
extender is to  be used in lyrics. It seems  that under some conditions 
it doesn't behave as I would expect but I may be doing it wrong.

Given the  following example, what am  I doing wrong? It  works fine for
stanza 3 as I  would expect, but for stanzas 1 and 2  it seems that what
I'm doing causes the extender to go beyond where I would expect it.

It there any better way than what  was done in stanza 4 because the fake
extender never seems to have  the correct length---it's either too short
or  too long?  Perhaps  something  could be  done  differently with  the
musical expression?

%%%
\version "2.22.2"

\paper {
  #(set-paper-size "letter")
}

\score {
  <<
\new ChoirStaff {
  <<
\new Staff {
  <<
\time 12/8
\new Voice = "voice" {
  \relative c'' {
a8 b c r4. r a8 b c
d,( e4~) e4. r4 \parenthesize f8 g g a
g2. r
  }
}
  >>
}
\new Lyrics \lyricsto "voice" {
  \set stanza = "1. " Sing -- ing o sing -- ing a |
  song, __ _ sing -- ing a
  song.
}
\new Lyrics \lyricsto "voice" {
  \set stanza = "2. " Some -- one sang.  They sang a
  song, __ \skip 1 a -- bout no --
  thing.
}
\new Lyrics \lyricsto "voice" {
  \set stanza = "3. " Sang a song? Who sang a |
  song? __ I sang a long
  song.
}
\new Lyrics \lyricsto "voice" {
  \set stanza = "4. " Here a song.  The song is |
  "gone,_" _ I can -- not
  sing.
}
  >>
}
  >>
}
%%%

Thanks,

Andy

tied sharps after line break

[Martin Tarenskeen]

Hi LilyPonders,

I bumped into a situation similar to this tiny example (In the real 
score the linebreak happened at such a situation without a forced 
\break but the result was the same):


\relative c' {
   c4 c c *cis* *~* |
   \break
   *cis* *cis* cis d |
}

the sharp sign in the 2nd bar is printed twice. I am not sure if that's 
the correct behaviour?
Without a \break the sharp is not printed for the tied 1st cis in the 
2nd bar, and only repeated for the 2nd cis in the 2nd bar.
I can imagine the reason to print the sharp sign after a linebreak 
and/or pagebreak. But in such a case I would not repeat the sharp on 
the snd quarter.


Is this a bug or a discussable way to interpret the conventions?
And: how can I override the current behaviour and choose where to print 
or not print sharps whenever I want to?


MT





test-tie.pdf
Description: Adobe PDF document
\version "2.23.1"

\relative c' {
  c4 c c cis ~ |
  \break
  cis cis cis d |
}

Re: Make D.S. and Coda objects RED

[Sebastien Richard]

Hello all,

You can also use something like :

\override Staff.StaffSymbol.color = #(x11-color 'SlateBlue1)


See https://en.wikipedia.org/wiki/X11_color_names for an extensive explanation 
of the name colors

BR

---
 Sébastien


From: lilypond-user-bounces+richardsgjm=hotmail@gnu.org 
 on behalf of Kieren 
MacMillan 
Sent: Sunday, March 3, 2024 14:41
To: Laurie Savage 
Cc: gehent...@gmail.com ; Jeff Kopmanis 
; Lilypond-User Mailing List 
Subject: Re: Make D.S. and Coda objects RED

Hi Laurie,

> When I copied your layout block into my score (2.25.12) I get this error
> error: syntax error, unexpected SYMBOL, expecting '='
>   CodaMark
>color = "tomato"

Sorry… didn’t test. Should have been

\layout {
  \context {
\Score
\compressEmptyMeasures
\override MultiMeasureRest.expand-limit = #2
\override CodaMark.color = "tomato"
\override SegnoMark.color = "tomato"
\override SectionLabel.color = "tomato"
% \override RehearsalMark.color = "tomato"
\override JumpScript.color = "tomato"
rehearsalMarkFormatter = #format-mark-box-alphabet
  }
}

Best,
Kieren.
__

My work day may look different than your work day. Please do not feel obligated 
to read or respond to this email outside of your normal working hours.

Transpose tab into label forms

[achar]

Hello to all.

With Frescobaldi I use the transpose tool to change the key of a piece. 
One thing it doesn't do is transpose the tablatures into label form. It 
would save me time. Does anyone have any ideas or is this simply 
impossible? Thank you for your attention . Good evening. Jean Pierre

Re: Make D.S. and Coda objects RED

[Kieren MacMillan]

Hi Laurie,

> When I copied your layout block into my score (2.25.12) I get this error
> error: syntax error, unexpected SYMBOL, expecting '='
>   CodaMark 
>color = "tomato"

Sorry… didn’t test. Should have been

\layout {
  \context {
\Score
\compressEmptyMeasures
\override MultiMeasureRest.expand-limit = #2
\override CodaMark.color = "tomato"
\override SegnoMark.color = "tomato"
\override SectionLabel.color = "tomato"
% \override RehearsalMark.color = "tomato"
\override JumpScript.color = "tomato"
rehearsalMarkFormatter = #format-mark-box-alphabet
  }
}

Best,
Kieren.
__

My work day may look different than your work day. Please do not feel obligated 
to read or respond to this email outside of your normal working hours.