Re: how to implement the snippet in the attachment

[Kieren MacMillan]

Hi Jinsong,

> Thank you very much for the help. It works well.

I’m glad!

> I don't understand the \new Voice

If you do a web search for

   \new Voice lilypond

the first hit is: 
.

> and \voiceTwo

A web search for

\voiceTwo lilypond

returns the same page as above.

That page of the documentation describes both commands.

Hope that helps!
Kieren.

Re: how to implement the snippet in the attachment

[Jinsong Zhao]

On 2019/10/31 22:22, Kieren MacMillan wrote:

Hi,


I don't figure out a way to implement it.


Something like this, maybe?

\version "2.19.83"

{
   \key f \major
   <<
 { bes'2 ~ 8[ ] } \\
 \new Voice  { \voiceTwo r4  ~ \once \hideNotes q8 }
   >>
   4
}

Hope that helps!
Kieren.


Thank you very much for the help. It works well.

However, I don't understand the code well. In fact, I don't understand 
the \new Voice and \voiceTwo here.


Thanks again.

Best,
Jinsong

Re: Ricochet bowing articulations

[Pierre Perol-Schneider]

Some tests:

#(define-markup-command (ric layout props note)(ly:music?)
  (interpret-markup layout props
   #{
 \markup {
\override #'(baseline-skip . 1.5)
\left-column {
  \line { \hspace #2 \teeny\bold "ric." }
  \score {
\fixed b' {
  \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
  \cadenzaOn
  #note
  r1
}
\layout {
  \context {
\Score
proportionalNotationDuration = #(ly:make-moment 1/7)
  }
  \context {
\Staff
\omit Clef
\omit TimeSignature
\omit Stem
\omit Flag
\omit Beam
\omit Rest
\override Rest.X-extent = #'(0 . .5)
\override StaffSymbol.line-positions = #'(0)
\override StaffSymbol.stencil = ##f
\override NoteHead.stencil = #(lambda (grob)
  (grob-interpret-markup grob #{ \markup\musicglyph
#"dots.dot" #}))
  }
}
  }
}
  } #}))

% Tests:
{
  d''4 ^\markup \ric ##{ b16( 16 8 16 16 8 16 16 16) #} s2.
  d''4 ^\markup \ric ##{ b16( 16 16 16 16 16 16 16) #} s2.
  d''4 ^\markup \ric ##{ b8( 8 8 8 8 8 8 8 8 8 16) #} s1 s
  d''4 ^\markup \ric ##{ b4( 4 16) #}
}

Le ven. 1 nov. 2019 à 00:44, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> a écrit :

> " \override Slur.positions = #'(0 . -3)" should be removed, not needed.
>
> Le ven. 1 nov. 2019 à 00:38, Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com> a écrit :
>
>> This should work:
>> #(define-markup-command (ric layout props note)(ly:music?)
>>   (interpret-markup layout props
>>#{
>>  \markup {
>> \override #'(baseline-skip . 1)
>> \left-column {
>>   \line { \hspace #2 \teeny\bold "ric." }
>>   \score {
>> \fixed b' {
>>   \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
>>   #note
>>   r1
>> }
>> \layout {
>>   \context {
>> \Score
>> proportionalNotationDuration = #(ly:make-moment 1/10)
>>   }
>>   \context {
>> \Staff
>> \omit Clef
>> \omit TimeSignature
>> \omit Stem
>> \omit Flag
>> \omit Beam
>> \omit BarLine
>> \omit Rest
>> \override Rest.X-extent = #'(0 . .5)
>> \override StaffSymbol.line-positions = #'(0)
>> \override StaffSymbol.stencil = ##f
>> \override Slur.positions = #'(0 . -3)
>> \override NoteHead.stencil = #(lambda (grob)
>>   (grob-interpret-markup grob #{ \markup\musicglyph
>> #"dots.dot" #}))
>>   }
>> }
>>   }
>> }
>>   } #}))
>>
>> % Test:
>> { d'' ^\markup \ric ##{ b16( 16 8 16 16 8 16 16 16) #} }
>>
>> Le jeu. 31 oct. 2019 à 23:58, Pierre Perol-Schneider <
>> pierre.schneider.pa...@gmail.com> a écrit :
>>
>>> PS. You can remove "\omit SystemStartBar", no need here.
>>>
>>> Le jeu. 31 oct. 2019 à 23:55, Pierre Perol-Schneider <
>>> pierre.schneider.pa...@gmail.com> a écrit :
>>>
 I was thinking of something just before going to bed:

 {
   d''4^\markup {
 \override #'(baseline-skip . 1)
 \left-column {
   \line { \hspace #2 \teeny\bold "ric." }
   \score {
 \fixed b' {
   \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
   { b16( 16 8 16 16 8 16 16 8 16 16 8) } % <= input the
 rhythm needed
   r1
 }
 \layout {
   \context {
 \Score
 proportionalNotationDuration = #(ly:make-moment 1/10)
 \omit SystemStartBar
   }
   \context {
 \Staff
 \omit Clef
 \omit TimeSignature
 \omit Stem
 \omit Flag
 \omit Beam
 \omit BarLine
 \omit Rest
 \override Rest.X-extent = #'(0 . .5)
 \override StaffSymbol.line-positions = #'(0)
 \override StaffSymbol.stencil = ##f
 \override Slur.positions = #'(0 . -3)
 \override NoteHead.stencil = #(lambda (grob)
   (grob-interpret-markup grob #{ \markup\musicglyph
 #"dots.dot" #}))
   }
 }
   }
 }
   }
 }

 Now, for some reason, I did not succeed any markup function; this does

Re: octavating slurs

[David Olson]

Thank you David !

^(_( works perfectly 

-- david olson

- Original Message -
From: "David Kastrup" 
To: "dadadharma @dslextreme.com" 
Cc: "lilypond-user" 
Sent: Thursday, October 31, 2019 4:42:46 PM
Subject: Re: octavating slurs

David Olson  writes:

> Hello Lilyponders, 
>
> If the basses are octivating, and I want a slurrish curve for the top note, 
>
> and another slur for the bottom, 
>
> is this possible? 
>
> ( ) 
>
> • This only gives one slur, from the "a" at the top of the staff to
> the "b" also at the top.
>
> • It would be elegant to have the slur repeated below. 
>
> Similarly for 
>
> d4( ) 
>
> • it would be nice to have two slurs originating from the "d".

There is the doubleSlurs property you can set.  But you can also write
explicitly

d4^(_( )

to get slurs above and below.

-- 
David Kastrup

Re: octavating slurs

[David Kastrup]

David Olson  writes:

> Hello Lilyponders, 
>
> If the basses are octivating, and I want a slurrish curve for the top note, 
>
> and another slur for the bottom, 
>
> is this possible? 
>
> ( ) 
>
> • This only gives one slur, from the "a" at the top of the staff to
> the "b" also at the top.
>
> • It would be elegant to have the slur repeated below. 
>
> Similarly for 
>
> d4( ) 
>
> • it would be nice to have two slurs originating from the "d".

There is the doubleSlurs property you can set.  But you can also write
explicitly

d4^(_( )

to get slurs above and below.

-- 
David Kastrup

Re: Ricochet bowing articulations

[Pierre Perol-Schneider]

" \override Slur.positions = #'(0 . -3)" should be removed, not needed.

Le ven. 1 nov. 2019 à 00:38, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> a écrit :

> This should work:
> #(define-markup-command (ric layout props note)(ly:music?)
>   (interpret-markup layout props
>#{
>  \markup {
> \override #'(baseline-skip . 1)
> \left-column {
>   \line { \hspace #2 \teeny\bold "ric." }
>   \score {
> \fixed b' {
>   \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
>   #note
>   r1
> }
> \layout {
>   \context {
> \Score
> proportionalNotationDuration = #(ly:make-moment 1/10)
>   }
>   \context {
> \Staff
> \omit Clef
> \omit TimeSignature
> \omit Stem
> \omit Flag
> \omit Beam
> \omit BarLine
> \omit Rest
> \override Rest.X-extent = #'(0 . .5)
> \override StaffSymbol.line-positions = #'(0)
> \override StaffSymbol.stencil = ##f
> \override Slur.positions = #'(0 . -3)
> \override NoteHead.stencil = #(lambda (grob)
>   (grob-interpret-markup grob #{ \markup\musicglyph
> #"dots.dot" #}))
>   }
> }
>   }
> }
>   } #}))
>
> % Test:
> { d'' ^\markup \ric ##{ b16( 16 8 16 16 8 16 16 16) #} }
>
> Le jeu. 31 oct. 2019 à 23:58, Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com> a écrit :
>
>> PS. You can remove "\omit SystemStartBar", no need here.
>>
>> Le jeu. 31 oct. 2019 à 23:55, Pierre Perol-Schneider <
>> pierre.schneider.pa...@gmail.com> a écrit :
>>
>>> I was thinking of something just before going to bed:
>>>
>>> {
>>>   d''4^\markup {
>>> \override #'(baseline-skip . 1)
>>> \left-column {
>>>   \line { \hspace #2 \teeny\bold "ric." }
>>>   \score {
>>> \fixed b' {
>>>   \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
>>>   { b16( 16 8 16 16 8 16 16 8 16 16 8) } % <= input the
>>> rhythm needed
>>>   r1
>>> }
>>> \layout {
>>>   \context {
>>> \Score
>>> proportionalNotationDuration = #(ly:make-moment 1/10)
>>> \omit SystemStartBar
>>>   }
>>>   \context {
>>> \Staff
>>> \omit Clef
>>> \omit TimeSignature
>>> \omit Stem
>>> \omit Flag
>>> \omit Beam
>>> \omit BarLine
>>> \omit Rest
>>> \override Rest.X-extent = #'(0 . .5)
>>> \override StaffSymbol.line-positions = #'(0)
>>> \override StaffSymbol.stencil = ##f
>>> \override Slur.positions = #'(0 . -3)
>>> \override NoteHead.stencil = #(lambda (grob)
>>>   (grob-interpret-markup grob #{ \markup\musicglyph
>>> #"dots.dot" #}))
>>>   }
>>> }
>>>   }
>>> }
>>>   }
>>> }
>>>
>>> Now, for some reason, I did not succeed any markup function; this does
>>> not work:
>>>
>>> #(define-markup-command (ric layout props note)(ly:music?)
>>>   (interpret-markup layout props
>>>#{
>>>  \markup {
>>> \override #'(baseline-skip . 1)
>>> \left-column {
>>>   \line { \hspace #2 \teeny\bold "ric." }
>>>   \score {
>>> \fixed b' {
>>>   \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
>>>   { #note }
>>>   r1
>>> }
>>> \layout {
>>>   \context {
>>> \Score
>>> proportionalNotationDuration = #(ly:make-moment 1/10)
>>> \omit SystemStartBar
>>>   }
>>>   \context {
>>> \Staff
>>> \omit Clef
>>> \omit TimeSignature
>>> \omit Stem
>>> \omit Flag
>>> \omit Beam
>>> \omit BarLine
>>> \omit Rest
>>> \override Rest.X-extent = #'(0 . .5)
>>> \override StaffSymbol.line-positions = #'(0)
>>> \override StaffSymbol.stencil = ##f
>>> \override Slur.positions = #'(0 . -3)
>>> \override NoteHead.stencil = #(lambda (grob)
>>>   (grob-interpret-markup grob #{ \markup\musicglyph
>>> #"dots.dot" #}))
>>>   }
>>> }
>>>   }
>>> }
>>>   } #}))
>>>
>>> { d'' ^\markup  { \ric b16 16 8 } }
>>>
>>> Good night to you, cheers,
>>> Pierre
>>>
>>>
>>> Le jeu. 31 oct. 2019 à 20:26, Ben  a écrit :
>>>
 On 10/31/2019 

Re: Ricochet bowing articulations

[Pierre Perol-Schneider]

This should work:
#(define-markup-command (ric layout props note)(ly:music?)
  (interpret-markup layout props
   #{
 \markup {
\override #'(baseline-skip . 1)
\left-column {
  \line { \hspace #2 \teeny\bold "ric." }
  \score {
\fixed b' {
  \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
  #note
  r1
}
\layout {
  \context {
\Score
proportionalNotationDuration = #(ly:make-moment 1/10)
  }
  \context {
\Staff
\omit Clef
\omit TimeSignature
\omit Stem
\omit Flag
\omit Beam
\omit BarLine
\omit Rest
\override Rest.X-extent = #'(0 . .5)
\override StaffSymbol.line-positions = #'(0)
\override StaffSymbol.stencil = ##f
\override Slur.positions = #'(0 . -3)
\override NoteHead.stencil = #(lambda (grob)
  (grob-interpret-markup grob #{ \markup\musicglyph
#"dots.dot" #}))
  }
}
  }
}
  } #}))

% Test:
{ d'' ^\markup \ric ##{ b16( 16 8 16 16 8 16 16 16) #} }

Le jeu. 31 oct. 2019 à 23:58, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> a écrit :

> PS. You can remove "\omit SystemStartBar", no need here.
>
> Le jeu. 31 oct. 2019 à 23:55, Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com> a écrit :
>
>> I was thinking of something just before going to bed:
>>
>> {
>>   d''4^\markup {
>> \override #'(baseline-skip . 1)
>> \left-column {
>>   \line { \hspace #2 \teeny\bold "ric." }
>>   \score {
>> \fixed b' {
>>   \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
>>   { b16( 16 8 16 16 8 16 16 8 16 16 8) } % <= input the
>> rhythm needed
>>   r1
>> }
>> \layout {
>>   \context {
>> \Score
>> proportionalNotationDuration = #(ly:make-moment 1/10)
>> \omit SystemStartBar
>>   }
>>   \context {
>> \Staff
>> \omit Clef
>> \omit TimeSignature
>> \omit Stem
>> \omit Flag
>> \omit Beam
>> \omit BarLine
>> \omit Rest
>> \override Rest.X-extent = #'(0 . .5)
>> \override StaffSymbol.line-positions = #'(0)
>> \override StaffSymbol.stencil = ##f
>> \override Slur.positions = #'(0 . -3)
>> \override NoteHead.stencil = #(lambda (grob)
>>   (grob-interpret-markup grob #{ \markup\musicglyph
>> #"dots.dot" #}))
>>   }
>> }
>>   }
>> }
>>   }
>> }
>>
>> Now, for some reason, I did not succeed any markup function; this does
>> not work:
>>
>> #(define-markup-command (ric layout props note)(ly:music?)
>>   (interpret-markup layout props
>>#{
>>  \markup {
>> \override #'(baseline-skip . 1)
>> \left-column {
>>   \line { \hspace #2 \teeny\bold "ric." }
>>   \score {
>> \fixed b' {
>>   \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
>>   { #note }
>>   r1
>> }
>> \layout {
>>   \context {
>> \Score
>> proportionalNotationDuration = #(ly:make-moment 1/10)
>> \omit SystemStartBar
>>   }
>>   \context {
>> \Staff
>> \omit Clef
>> \omit TimeSignature
>> \omit Stem
>> \omit Flag
>> \omit Beam
>> \omit BarLine
>> \omit Rest
>> \override Rest.X-extent = #'(0 . .5)
>> \override StaffSymbol.line-positions = #'(0)
>> \override StaffSymbol.stencil = ##f
>> \override Slur.positions = #'(0 . -3)
>> \override NoteHead.stencil = #(lambda (grob)
>>   (grob-interpret-markup grob #{ \markup\musicglyph
>> #"dots.dot" #}))
>>   }
>> }
>>   }
>> }
>>   } #}))
>>
>> { d'' ^\markup  { \ric b16 16 8 } }
>>
>> Good night to you, cheers,
>> Pierre
>>
>>
>> Le jeu. 31 oct. 2019 à 20:26, Ben  a écrit :
>>
>>> On 10/31/2019 3:07 PM, Pierre Perol-Schneider wrote:
>>>
>>> Manually you could do:
>>>
>>> {
>>>   d''^\markup
>>>\override #'(baseline-skip . 1.5)
>>>\left-column {
>>>  \line { \hspace #2 \teeny\bold "ric." }
>>>  \line {
>>> " "
>>> \overtie\concat {
>>>   " " \pattern #3 #X #1 \musicglyph #"dots.dot"
>>> 

octavating slurs

[David Olson]

Hello Lilyponders, 

If the basses are octivating, and I want a slurrish curve for the top note, 

and another slur for the bottom, 

is this possible? 

( ) 

• This only gives one slur, from the "a" at the top of the staff to the "b" 
also at the top. 

• It would be elegant to have the slur repeated below. 

Similarly for 

d4( ) 

• it would be nice to have two slurs originating from the "d". 


This is for sight-singing fun; I'll hand out a song sheet, we'll spend 2 or 3 
minutes on this, once through, then sing something else. 

So, for the basses who take the profound option, it would be nice if there was 
a slur symbol right where their eyes are focused 

If it can't be done, we'll live with it... 


TIA, 

David Olson 

Re: Ricochet bowing articulations

[Pierre Perol-Schneider]

PS. You can remove "\omit SystemStartBar", no need here.

Le jeu. 31 oct. 2019 à 23:55, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> a écrit :

> I was thinking of something just before going to bed:
>
> {
>   d''4^\markup {
> \override #'(baseline-skip . 1)
> \left-column {
>   \line { \hspace #2 \teeny\bold "ric." }
>   \score {
> \fixed b' {
>   \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
>   { b16( 16 8 16 16 8 16 16 8 16 16 8) } % <= input the rhythm
> needed
>   r1
> }
> \layout {
>   \context {
> \Score
> proportionalNotationDuration = #(ly:make-moment 1/10)
> \omit SystemStartBar
>   }
>   \context {
> \Staff
> \omit Clef
> \omit TimeSignature
> \omit Stem
> \omit Flag
> \omit Beam
> \omit BarLine
> \omit Rest
> \override Rest.X-extent = #'(0 . .5)
> \override StaffSymbol.line-positions = #'(0)
> \override StaffSymbol.stencil = ##f
> \override Slur.positions = #'(0 . -3)
> \override NoteHead.stencil = #(lambda (grob)
>   (grob-interpret-markup grob #{ \markup\musicglyph
> #"dots.dot" #}))
>   }
> }
>   }
> }
>   }
> }
>
> Now, for some reason, I did not succeed any markup function; this does not
> work:
>
> #(define-markup-command (ric layout props note)(ly:music?)
>   (interpret-markup layout props
>#{
>  \markup {
> \override #'(baseline-skip . 1)
> \left-column {
>   \line { \hspace #2 \teeny\bold "ric." }
>   \score {
> \fixed b' {
>   \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
>   { #note }
>   r1
> }
> \layout {
>   \context {
> \Score
> proportionalNotationDuration = #(ly:make-moment 1/10)
> \omit SystemStartBar
>   }
>   \context {
> \Staff
> \omit Clef
> \omit TimeSignature
> \omit Stem
> \omit Flag
> \omit Beam
> \omit BarLine
> \omit Rest
> \override Rest.X-extent = #'(0 . .5)
> \override StaffSymbol.line-positions = #'(0)
> \override StaffSymbol.stencil = ##f
> \override Slur.positions = #'(0 . -3)
> \override NoteHead.stencil = #(lambda (grob)
>   (grob-interpret-markup grob #{ \markup\musicglyph
> #"dots.dot" #}))
>   }
> }
>   }
> }
>   } #}))
>
> { d'' ^\markup  { \ric b16 16 8 } }
>
> Good night to you, cheers,
> Pierre
>
>
> Le jeu. 31 oct. 2019 à 20:26, Ben  a écrit :
>
>> On 10/31/2019 3:07 PM, Pierre Perol-Schneider wrote:
>>
>> Manually you could do:
>>
>> {
>>   d''^\markup
>>\override #'(baseline-skip . 1.5)
>>\left-column {
>>  \line { \hspace #2 \teeny\bold "ric." }
>>  \line {
>> " "
>> \overtie\concat {
>>   " " \pattern #3 #X #1 \musicglyph #"dots.dot"
>>   \hspace #10
>>   \concat {
>> " " \pattern #3 #X #1 \musicglyph #"dots.dot"
>> " "
>>   }
>> }
>>  }
>>}
>> }
>>
>> Automagically, no time enough tonight, sorry...
>> Cheers,
>> Pierre
>>
>> Many thanks for your help and time, Pierre :) Have a good night.
>>
>>
>> Le jeu. 31 oct. 2019 à 20:05, Ben  a écrit :
>>
>>> On 10/31/2019 2:50 PM, Pierre Perol-Schneider wrote:
>>>
>>> Oops, I miss something, here it goes:
>>>
>>> \version "2.19.83"
>>>
>>> #(define-markup-command (ricochet layout props nb spce) (integer?
>>> number?)
>>>   (interpret-markup layout props
>>> #{ \markup
>>>\override #'(baseline-skip . 1.5)
>>>\left-column {
>>>  \line { \hspace #2 \teeny\bold "ric." }
>>>  \line {
>>> " "
>>> \overtie\concat {
>>>   " " \pattern #nb #X #spce \musicglyph #"dots.dot"
>>>   " "
>>> }
>>>  }
>>>} #}))
>>>
>>> {
>>>   d''^\markup\ricochet #7 #1 s s s
>>>   d''^\markup\ricochet #3 #3
>>> }
>>>
>>> Cheers,
>>> Pierre
>>>
>>> Le jeu. 31 oct. 2019 à 19:45, Pierre Perol-Schneider <
>>> pierre.schneider.pa...@gmail.com> a écrit :
>>>
 Hi Ben,
 How about:

 \version "2.19.83"

 #(define-markup-command (ricochet layout props nb spce) (integer?
 number?)
   (interpret-markup layout props
 #{ \markup {
   " "
   \overtie\concat {
 

Re: Ricochet bowing articulations

[Pierre Perol-Schneider]

I was thinking of something just before going to bed:

{
  d''4^\markup {
\override #'(baseline-skip . 1)
\left-column {
  \line { \hspace #2 \teeny\bold "ric." }
  \score {
\fixed b' {
  \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
  { b16( 16 8 16 16 8 16 16 8 16 16 8) } % <= input the rhythm
needed
  r1
}
\layout {
  \context {
\Score
proportionalNotationDuration = #(ly:make-moment 1/10)
\omit SystemStartBar
  }
  \context {
\Staff
\omit Clef
\omit TimeSignature
\omit Stem
\omit Flag
\omit Beam
\omit BarLine
\omit Rest
\override Rest.X-extent = #'(0 . .5)
\override StaffSymbol.line-positions = #'(0)
\override StaffSymbol.stencil = ##f
\override Slur.positions = #'(0 . -3)
\override NoteHead.stencil = #(lambda (grob)
  (grob-interpret-markup grob #{ \markup\musicglyph
#"dots.dot" #}))
  }
}
  }
}
  }
}

Now, for some reason, I did not succeed any markup function; this does not
work:

#(define-markup-command (ric layout props note)(ly:music?)
  (interpret-markup layout props
   #{
 \markup {
\override #'(baseline-skip . 1)
\left-column {
  \line { \hspace #2 \teeny\bold "ric." }
  \score {
\fixed b' {
  \shape #'(((-1 . -.5) (0 . -.5) (0 . -.5) (1 . -.5))) Slur
  { #note }
  r1
}
\layout {
  \context {
\Score
proportionalNotationDuration = #(ly:make-moment 1/10)
\omit SystemStartBar
  }
  \context {
\Staff
\omit Clef
\omit TimeSignature
\omit Stem
\omit Flag
\omit Beam
\omit BarLine
\omit Rest
\override Rest.X-extent = #'(0 . .5)
\override StaffSymbol.line-positions = #'(0)
\override StaffSymbol.stencil = ##f
\override Slur.positions = #'(0 . -3)
\override NoteHead.stencil = #(lambda (grob)
  (grob-interpret-markup grob #{ \markup\musicglyph
#"dots.dot" #}))
  }
}
  }
}
  } #}))

{ d'' ^\markup  { \ric b16 16 8 } }

Good night to you, cheers,
Pierre


Le jeu. 31 oct. 2019 à 20:26, Ben  a écrit :

> On 10/31/2019 3:07 PM, Pierre Perol-Schneider wrote:
>
> Manually you could do:
>
> {
>   d''^\markup
>\override #'(baseline-skip . 1.5)
>\left-column {
>  \line { \hspace #2 \teeny\bold "ric." }
>  \line {
> " "
> \overtie\concat {
>   " " \pattern #3 #X #1 \musicglyph #"dots.dot"
>   \hspace #10
>   \concat {
> " " \pattern #3 #X #1 \musicglyph #"dots.dot"
> " "
>   }
> }
>  }
>}
> }
>
> Automagically, no time enough tonight, sorry...
> Cheers,
> Pierre
>
> Many thanks for your help and time, Pierre :) Have a good night.
>
>
> Le jeu. 31 oct. 2019 à 20:05, Ben  a écrit :
>
>> On 10/31/2019 2:50 PM, Pierre Perol-Schneider wrote:
>>
>> Oops, I miss something, here it goes:
>>
>> \version "2.19.83"
>>
>> #(define-markup-command (ricochet layout props nb spce) (integer? number?)
>>   (interpret-markup layout props
>> #{ \markup
>>\override #'(baseline-skip . 1.5)
>>\left-column {
>>  \line { \hspace #2 \teeny\bold "ric." }
>>  \line {
>> " "
>> \overtie\concat {
>>   " " \pattern #nb #X #spce \musicglyph #"dots.dot"
>>   " "
>> }
>>  }
>>} #}))
>>
>> {
>>   d''^\markup\ricochet #7 #1 s s s
>>   d''^\markup\ricochet #3 #3
>> }
>>
>> Cheers,
>> Pierre
>>
>> Le jeu. 31 oct. 2019 à 19:45, Pierre Perol-Schneider <
>> pierre.schneider.pa...@gmail.com> a écrit :
>>
>>> Hi Ben,
>>> How about:
>>>
>>> \version "2.19.83"
>>>
>>> #(define-markup-command (ricochet layout props nb spce) (integer?
>>> number?)
>>>   (interpret-markup layout props
>>> #{ \markup {
>>>   " "
>>>   \overtie\concat {
>>> " " \pattern #nb #X #spce \musicglyph #"dots.dot"
>>> " "
>>>   }
>>> } #}))
>>>
>>> {
>>>   d''^\markup\ricochet #7 #1 s s s
>>>   d''^\markup\ricochet #3 #3
>>> }
>>>
>>> HTH, cheers,
>>> Pierre
>>>
>>> Le jeu. 31 oct. 2019 à 15:45, Ben  a écrit :
>>>
 Good morning!

 How would it be possible to create the attached ricochet articulation
 in LilyPond?

 Also, I'm 

Re: LilyPond, LilyPond snippets and the GPL

[Hans Åberg]

> On 31 Oct 2019, at 22:10, David Kastrup  wrote:
> 
> Hans Åberg  writes:
> 
>>> On 31 Oct 2019, at 21:31, David Kastrup  wrote:
>>> 
 All those parts should be LGPL, and also included headers, I believe:
 Not GPL, because that would legal technically force copyright
 limitations on the output, and not public domain, because then one
 could exploit the inputs in ways you do not want. But check with the
 experts.
>>> 
>>> I think this kind of stuff should just be exempt from licensing (namely
>>> declared public domain) like stub code in GCC.  It doesn't survive into
>>> PDF anyway (since PDF is not programmable and so the PostScript-to-PDF
>>> conversion executes the code in question rather than converting it) and
>>> it is very unusual to distribute PostScript these days instead of
>>> executing it right away in the form of some document processing
>>> workflow.
>>> 
>>> So that is indeed something that would warrant getting separate
>>> appropriate licensing attention, but in most use cases it would end up
>>> not being relevant since there are few workflows where a PostScript file
>>> ends up as something to be distributed.
>> 
>> It is only a problem if code survives in the output and is
>> copyrightable. Like glyph designs, for example, there are in the works
>> new microtonal accidentals, the design of which I figure would be
>> copyrightable, and take a long time to develop. Would you want them to
>> be in the public domain? It would mean that the design could be
>> exploited freely without acknowledgement. With LGPL, any altered
>> design must have the same license, but the glyphs can be used freely
>> in publications.
> 
> If I remember correctly, our fonts have already been relicensed under
> some typical free font license several years ago.

That is good. I merely wanted to illustrate the principle, that some stuff may 
survive into the output in copyrightable form. The most explicit example I have 
in my mind is the Bison skeleton file that originally was mostly verbatim, but 
now is processed using M4, and needs to be LGPL, not GPL, nor public domain.

Re: LilyPond, LilyPond snippets and the GPL

[David Kastrup]

Hans Åberg  writes:

>> On 31 Oct 2019, at 21:31, David Kastrup  wrote:
>> 
>>> All those parts should be LGPL, and also included headers, I believe:
>>> Not GPL, because that would legal technically force copyright
>>> limitations on the output, and not public domain, because then one
>>> could exploit the inputs in ways you do not want. But check with the
>>> experts.
>> 
>> I think this kind of stuff should just be exempt from licensing (namely
>> declared public domain) like stub code in GCC.  It doesn't survive into
>> PDF anyway (since PDF is not programmable and so the PostScript-to-PDF
>> conversion executes the code in question rather than converting it) and
>> it is very unusual to distribute PostScript these days instead of
>> executing it right away in the form of some document processing
>> workflow.
>> 
>> So that is indeed something that would warrant getting separate
>> appropriate licensing attention, but in most use cases it would end up
>> not being relevant since there are few workflows where a PostScript file
>> ends up as something to be distributed.
>
> It is only a problem if code survives in the output and is
> copyrightable. Like glyph designs, for example, there are in the works
> new microtonal accidentals, the design of which I figure would be
> copyrightable, and take a long time to develop. Would you want them to
> be in the public domain? It would mean that the design could be
> exploited freely without acknowledgement. With LGPL, any altered
> design must have the same license, but the glyphs can be used freely
> in publications.

If I remember correctly, our fonts have already been relicensed under
some typical free font license several years ago.

-- 
David Kastrup

Re: LilyPond, LilyPond snippets and the GPL

[Hans Åberg]

> On 31 Oct 2019, at 21:31, David Kastrup  wrote:
> 
>> All those parts should be LGPL, and also included headers, I believe:
>> Not GPL, because that would legal technically force copyright
>> limitations on the output, and not public domain, because then one
>> could exploit the inputs in ways you do not want. But check with the
>> experts.
> 
> I think this kind of stuff should just be exempt from licensing (namely
> declared public domain) like stub code in GCC.  It doesn't survive into
> PDF anyway (since PDF is not programmable and so the PostScript-to-PDF
> conversion executes the code in question rather than converting it) and
> it is very unusual to distribute PostScript these days instead of
> executing it right away in the form of some document processing
> workflow.
> 
> So that is indeed something that would warrant getting separate
> appropriate licensing attention, but in most use cases it would end up
> not being relevant since there are few workflows where a PostScript file
> ends up as something to be distributed.

It is only a problem if code survives in the output and is copyrightable. Like 
glyph designs, for example, there are in the works new microtonal accidentals, 
the design of which I figure would be copyrightable, and take a long time to 
develop. Would you want them to be in the public domain? It would mean that the 
design could be exploited freely without acknowledgement. With LGPL, any 
altered design must have the same license, but the glyphs can be used freely in 
publications.

Re: LilyPond, LilyPond snippets and the GPL

[David Kastrup]

Hans Åberg  writes:

>> On 31 Oct 2019, at 03:15, Carl Sorensen  wrote:
>> 
>>> On 10/30/19, 5:13 PM, "Hans Åberg"  wrote:
>>> 
 On 30 Oct 2019, at 22:14, Carl Sorensen  wrote:
 
   The snippets should be LGPL for being includable under other
 licenses, I believe, because the processed part remains in the
 output, and thus copyrightable. Thus, they play the same role as
 the Bison skeleton file and GCC libraries.
 
 What processed part remains in the output?
>>> 
>>>If say somebody makes a snippet on how to make special type of
>>> clef, then that is copyrightable, just as a font and its glyphs
>>> are, it would seem, and that copyright will remain if
>>> copy-and-pasted into user code.
>> 
>> In the US, a typeface is not copyrightable.  But a computer program
>> that makes a font or its glyphs is copyrightable.  I can see your
>> argument here.  But if this argument is true, then it seems that all
>> music set with LilyPond is GPL3, because the code for drawing beams,
>> stems, staff lines, and straight flags is in LilyPond and is
>> licensed under GPL3.  I find it very hard to believe that this is
>> true.  And certainly, as far as the FSF is concerned, this is not
>> true.
>
> All those parts should be LGPL, and also included headers, I believe:
> Not GPL, because that would legal technically force copyright
> limitations on the output, and not public domain, because then one
> could exploit the inputs in ways you do not want. But check with the
> experts.

I think this kind of stuff should just be exempt from licensing (namely
declared public domain) like stub code in GCC.  It doesn't survive into
PDF anyway (since PDF is not programmable and so the PostScript-to-PDF
conversion executes the code in question rather than converting it) and
it is very unusual to distribute PostScript these days instead of
executing it right away in the form of some document processing
workflow.

So that is indeed something that would warrant getting separate
appropriate licensing attention, but in most use cases it would end up
not being relevant since there are few workflows where a PostScript file
ends up as something to be distributed.

-- 
David Kastrup

Re: Ricochet bowing articulations

[Ben]

On 10/31/2019 3:07 PM, Pierre Perol-Schneider wrote:

Manually you could do:

{
  d''^\markup
       \override #'(baseline-skip . 1.5)
       \left-column {
         \line { \hspace #2 \teeny\bold "ric." }
         \line {
            " "
            \overtie\concat {
              " " \pattern #3 #X #1 \musicglyph #"dots.dot"
              \hspace #10
              \concat {
                " " \pattern #3 #X #1 \musicglyph #"dots.dot"
                " "
              }
            }
         }
       }
}

Automagically, no time enough tonight, sorry...
Cheers,
Pierre


Many thanks for your help and time, Pierre :) Have a good night.


Le jeu. 31 oct. 2019 à 20:05, Ben > a écrit :


On 10/31/2019 2:50 PM, Pierre Perol-Schneider wrote:

Oops, I miss something, here it goes:

\version "2.19.83"

#(define-markup-command (ricochet layout props nb spce) (integer?
number?)
  (interpret-markup layout props
    #{ \markup
       \override #'(baseline-skip . 1.5)
       \left-column {
         \line { \hspace #2 \teeny\bold "ric." }
         \line {
            " "
            \overtie\concat {
              " " \pattern #nb #X #spce \musicglyph #"dots.dot"
              " "
            }
         }
       } #}))

{
  d''^\markup\ricochet #7 #1 s s s
  d''^\markup\ricochet #3 #3
}

Cheers,
Pierre

Le jeu. 31 oct. 2019 à 19:45, Pierre Perol-Schneider
mailto:pierre.schneider.pa...@gmail.com>> a écrit :

Hi Ben,
How about:

\version "2.19.83"

#(define-markup-command (ricochet layout props nb spce)
(integer? number?)
  (interpret-markup layout props
    #{ \markup {
          " "
          \overtie\concat {
            " " \pattern #nb #X #spce \musicglyph #"dots.dot"
            " "
          }
        } #}))

{
  d''^\markup\ricochet #7 #1 s s s
  d''^\markup\ricochet #3 #3
}

HTH, cheers,
Pierre

Le jeu. 31 oct. 2019 à 15:45, Ben mailto:soundsfromso...@gmail.com>> a écrit :

Good morning!

How would it be possible to create the attached ricochet
articulation in LilyPond?

Also, I'm looking for a way to be able to modify the dots
in two ways, for example: add/remove the number of dots
(3-6) per articulation instance, and add some space in
between several of the dots to suggest a certain 'rhythm'
to the ricochet.

Any suggestions would be appreciated. :)

Thanks!



Maybe something like this, where you can group dots and then add
space?

c''2^\markup\ricochet #2  #1 #4 s2 |

(   group 2 dots    <1 space>    group 4 dots |   )

Is this doable?

Re: Ricochet bowing articulations

[Pierre Perol-Schneider]

Manually you could do:

{
  d''^\markup
   \override #'(baseline-skip . 1.5)
   \left-column {
 \line { \hspace #2 \teeny\bold "ric." }
 \line {
" "
\overtie\concat {
  " " \pattern #3 #X #1 \musicglyph #"dots.dot"
  \hspace #10
  \concat {
" " \pattern #3 #X #1 \musicglyph #"dots.dot"
" "
  }
}
 }
   }
}

Automagically, no time enough tonight, sorry...
Cheers,
Pierre

Le jeu. 31 oct. 2019 à 20:05, Ben  a écrit :

> On 10/31/2019 2:50 PM, Pierre Perol-Schneider wrote:
>
> Oops, I miss something, here it goes:
>
> \version "2.19.83"
>
> #(define-markup-command (ricochet layout props nb spce) (integer? number?)
>   (interpret-markup layout props
> #{ \markup
>\override #'(baseline-skip . 1.5)
>\left-column {
>  \line { \hspace #2 \teeny\bold "ric." }
>  \line {
> " "
> \overtie\concat {
>   " " \pattern #nb #X #spce \musicglyph #"dots.dot"
>   " "
> }
>  }
>} #}))
>
> {
>   d''^\markup\ricochet #7 #1 s s s
>   d''^\markup\ricochet #3 #3
> }
>
> Cheers,
> Pierre
>
> Le jeu. 31 oct. 2019 à 19:45, Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com> a écrit :
>
>> Hi Ben,
>> How about:
>>
>> \version "2.19.83"
>>
>> #(define-markup-command (ricochet layout props nb spce) (integer? number?)
>>   (interpret-markup layout props
>> #{ \markup {
>>   " "
>>   \overtie\concat {
>> " " \pattern #nb #X #spce \musicglyph #"dots.dot"
>> " "
>>   }
>> } #}))
>>
>> {
>>   d''^\markup\ricochet #7 #1 s s s
>>   d''^\markup\ricochet #3 #3
>> }
>>
>> HTH, cheers,
>> Pierre
>>
>> Le jeu. 31 oct. 2019 à 15:45, Ben  a écrit :
>>
>>> Good morning!
>>>
>>> How would it be possible to create the attached ricochet articulation in
>>> LilyPond?
>>>
>>> Also, I'm looking for a way to be able to modify the dots in two ways,
>>> for example: add/remove the number of dots (3-6) per articulation instance,
>>> and add some space in between several of the dots to suggest a certain
>>> 'rhythm' to the ricochet.
>>>
>>> Any suggestions would be appreciated. :)
>>>
>>> Thanks!
>>>
>>
> Maybe something like this, where you can group dots and then add space?
>
> c''2^\markup\ricochet #2  #1 #4 s2 |
>
> (   group 2 dots<1 space>group 4 dots|   )
>
> Is this doable?
>
>
>

Re: Ricochet bowing articulations

[Ben]

On 10/31/2019 2:50 PM, Pierre Perol-Schneider wrote:

Oops, I miss something, here it goes:

\version "2.19.83"

#(define-markup-command (ricochet layout props nb spce) (integer? number?)
  (interpret-markup layout props
    #{ \markup
       \override #'(baseline-skip . 1.5)
       \left-column {
         \line { \hspace #2 \teeny\bold "ric." }
         \line {
            " "
            \overtie\concat {
              " " \pattern #nb #X #spce \musicglyph #"dots.dot"
              " "
            }
         }
       } #}))

{
  d''^\markup\ricochet #7 #1 s s s
  d''^\markup\ricochet #3 #3
}

Cheers,
Pierre

Le jeu. 31 oct. 2019 à 19:45, Pierre Perol-Schneider 
> a écrit :


Hi Ben,
How about:

\version "2.19.83"

#(define-markup-command (ricochet layout props nb spce) (integer?
number?)
  (interpret-markup layout props
    #{ \markup {
          " "
          \overtie\concat {
            " " \pattern #nb #X #spce \musicglyph #"dots.dot"
            " "
          }
        } #}))

{
  d''^\markup\ricochet #7 #1 s s s
  d''^\markup\ricochet #3 #3
}

HTH, cheers,
Pierre

Le jeu. 31 oct. 2019 à 15:45, Ben mailto:soundsfromso...@gmail.com>> a écrit :

Good morning!

How would it be possible to create the attached ricochet
articulation in LilyPond?

Also, I'm looking for a way to be able to modify the dots in
two ways, for example: add/remove the number of dots (3-6) per
articulation instance, and add some space in between several
of the dots to suggest a certain 'rhythm' to the ricochet.

Any suggestions would be appreciated. :)

Thanks!



Maybe something like this, where you can group dots and then add space?

c''2^\markup\ricochet #2  #1 #4 s2 |

(   group 2 dots    <1 space>    group 4 dots    |   )

Is this doable?

Re: Ricochet bowing articulations

[Ben]

On 10/31/2019 2:50 PM, Pierre Perol-Schneider wrote:

Oops, I miss something, here it goes:

\version "2.19.83"

#(define-markup-command (ricochet layout props nb spce) (integer? number?)
  (interpret-markup layout props
    #{ \markup
       \override #'(baseline-skip . 1.5)
       \left-column {
         \line { \hspace #2 \teeny\bold "ric." }
         \line {
            " "
            \overtie\concat {
              " " \pattern #nb #X #spce \musicglyph #"dots.dot"
              " "
            }
         }
       } #}))

{
  d''^\markup\ricochet #7 #1 s s s
  d''^\markup\ricochet #3 #3
}

Cheers,
Pierre

Le jeu. 31 oct. 2019 à 19:45, Pierre Perol-Schneider 
> a écrit :


Hi Ben,
How about:

\version "2.19.83"

#(define-markup-command (ricochet layout props nb spce) (integer?
number?)
  (interpret-markup layout props
    #{ \markup {
          " "
          \overtie\concat {
            " " \pattern #nb #X #spce \musicglyph #"dots.dot"
            " "
          }
        } #}))

{
  d''^\markup\ricochet #7 #1 s s s
  d''^\markup\ricochet #3 #3
}

HTH, cheers,
Pierre

Le jeu. 31 oct. 2019 à 15:45, Ben mailto:soundsfromso...@gmail.com>> a écrit :

Good morning!

How would it be possible to create the attached ricochet
articulation in LilyPond?

Also, I'm looking for a way to be able to modify the dots in
two ways, for example: add/remove the number of dots (3-6) per
articulation instance, and add some space in between several
of the dots to suggest a certain 'rhythm' to the ricochet.

Any suggestions would be appreciated. :)

Thanks!


Hi Pierre!

This looks so great, wow. Thank you!

How exactly would I be able to modify the dot spread though? I don't 
follow how to change this as needed, as with spacers, etc.?


For example, how would I create a half note with 6 dots above, grouped as:

3 dots  4 dots

or

1 dot  5 dots

I don't see how to input the appropriate number of spacers so the 
following notes are not "under" the ricochet in the same measure.


Thanks for this!

Re: Ricochet bowing articulations

[Pierre Perol-Schneider]

Oops, I miss something, here it goes:

\version "2.19.83"

#(define-markup-command (ricochet layout props nb spce) (integer? number?)
  (interpret-markup layout props
#{ \markup
   \override #'(baseline-skip . 1.5)
   \left-column {
 \line { \hspace #2 \teeny\bold "ric." }
 \line {
" "
\overtie\concat {
  " " \pattern #nb #X #spce \musicglyph #"dots.dot"
  " "
}
 }
   } #}))

{
  d''^\markup\ricochet #7 #1 s s s
  d''^\markup\ricochet #3 #3
}

Cheers,
Pierre

Le jeu. 31 oct. 2019 à 19:45, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> a écrit :

> Hi Ben,
> How about:
>
> \version "2.19.83"
>
> #(define-markup-command (ricochet layout props nb spce) (integer? number?)
>   (interpret-markup layout props
> #{ \markup {
>   " "
>   \overtie\concat {
> " " \pattern #nb #X #spce \musicglyph #"dots.dot"
> " "
>   }
> } #}))
>
> {
>   d''^\markup\ricochet #7 #1 s s s
>   d''^\markup\ricochet #3 #3
> }
>
> HTH, cheers,
> Pierre
>
> Le jeu. 31 oct. 2019 à 15:45, Ben  a écrit :
>
>> Good morning!
>>
>> How would it be possible to create the attached ricochet articulation in
>> LilyPond?
>>
>> Also, I'm looking for a way to be able to modify the dots in two ways,
>> for example: add/remove the number of dots (3-6) per articulation instance,
>> and add some space in between several of the dots to suggest a certain
>> 'rhythm' to the ricochet.
>>
>> Any suggestions would be appreciated. :)
>>
>> Thanks!
>>
>

Re: Ricochet bowing articulations

[Pierre Perol-Schneider]

Hi Ben,
How about:

\version "2.19.83"

#(define-markup-command (ricochet layout props nb spce) (integer? number?)
  (interpret-markup layout props
#{ \markup {
  " "
  \overtie\concat {
" " \pattern #nb #X #spce \musicglyph #"dots.dot"
" "
  }
} #}))

{
  d''^\markup\ricochet #7 #1 s s s
  d''^\markup\ricochet #3 #3
}

HTH, cheers,
Pierre

Le jeu. 31 oct. 2019 à 15:45, Ben  a écrit :

> Good morning!
>
> How would it be possible to create the attached ricochet articulation in
> LilyPond?
>
> Also, I'm looking for a way to be able to modify the dots in two ways, for
> example: add/remove the number of dots (3-6) per articulation instance, and
> add some space in between several of the dots to suggest a certain 'rhythm'
> to the ricochet.
>
> Any suggestions would be appreciated. :)
>
> Thanks!
>

Re: how to implement the snippet in the attachment

[DJF]

On Oct 31, 2019, at 10:02 AM, Jinsong Zhao  wrote:
> 
> hi there,
> I am trying to transcribe a music sheet.  I have encountered the snippet in 
> the attachment.  I don't figure out a way to implement it.  I am now using an 
> alternative way like:

Use hidden notes in the second voice to accomplish this.

\relative c'' {
\key f \major
<<{bes2 ~ 8  4} \\
{r4  ~ \hideNotes 8 \unHideNotes s8 s4 } >>
}

--
Dan

Re: testing the reachable of my post

[Leo Correia de Verdier]

I would do it like:

\relative c' {
<< { f8 d f a~   4 } \\
   { 4. 8~ \hideNotes  s4. } >> 
c'2. b4
}


> 31 okt. 2019 kl. 08:20 skrev Jinsong Zhao :
> 
> Hi there,
> 
> Sorry for the disturbance.
> 
> I have tried several times to post my question to the mailing list. However, 
> I have not found it posted in the mailing list yet.
> 
> --
> In the following two pieces of codes, they are should the same. The only 
> difference is the the second code combined  the same rhythm into a single 
> voice.
> 
> \relative c' {
> << { f8 d f a  ~ a f a4 } \\
>   {4. 8 ~ 8 c 4 }>> c'2. b4
> }
> 
> \relative c'{
> << {f8 d f a } \\
>{ 4. 8 } >>
> 8  4 c2. b4
> }
> 
> My questions is how to add slur in the second code as those in the first one.
> 
> Thanks in advance.
> 
> Best,
> Jinsong
> 
> 
> 

Ricochet bowing articulations

[Ben]

Good morning!

How would it be possible to create the attached ricochet articulation in 
LilyPond?


Also, I'm looking for a way to be able to modify the dots in two ways, 
for example: add/remove the number of dots (3-6) per articulation 
instance, and add some space in between several of the dots to suggest a 
certain 'rhythm' to the ricochet.


Any suggestions would be appreciated. :)

Thanks!

Re: how to implement the snippet in the attachment

[Kieren MacMillan]

Hi,

> I don't figure out a way to implement it.

Something like this, maybe?

\version "2.19.83"

{
  \key f \major
  <<
{ bes'2 ~ 8[ ] } \\
\new Voice  { \voiceTwo r4  ~ \once \hideNotes q8 }
  >>
  4
}

Hope that helps!
Kieren.

how to implement the snippet in the attachment

[Jinsong Zhao]

hi there,
I am trying to transcribe a music sheet. I have encountered the snippet 
in the attachment. I don't figure out a way to implement it. I am 
now using an alternative way like:


\version "2.19.83"
\relative c'' {
\key f \major
<<{bes2 ~ bes8 g a4} \\
{r4 <>

Re: LilyPond, LilyPond snippets and the GPL

[Hans Åberg]

> On 31 Oct 2019, at 03:15, Carl Sorensen  wrote:
> 
>> On 10/30/19, 5:13 PM, "Hans Åberg"  wrote:
>> 
>>> On 30 Oct 2019, at 22:14, Carl Sorensen  wrote:
>>> 
>>>   The snippets should be LGPL for being includable under other licenses, I 
>>> believe, because the processed part remains in the output, and thus 
>>> copyrightable. Thus, they play the same role as the Bison skeleton file and 
>>> GCC libraries.
>>> 
>>> What processed part remains in the output?
>> 
>>If say somebody makes a snippet on how to make special type of clef, then 
>> that is copyrightable, just as a font and its glyphs are, it would seem, and 
>> that copyright will remain if copy-and-pasted into user code.
> 
> In the US, a typeface is not copyrightable.  But a computer program that 
> makes a font or its glyphs is copyrightable.  I can see your argument here.  
> But if this argument is true, then it seems that all music set with LilyPond 
> is GPL3,  because the code for drawing beams, stems, staff lines, and 
> straight flags is in LilyPond and is licensed under GPL3.  I find it very 
> hard to believe that this is true.  And certainly, as far as the FSF is 
> concerned, this is not true.  

All those parts should be LGPL, and also included headers, I believe: Not GPL, 
because that would legal technically force copyright limitations on the output, 
and not public domain, because then one could exploit the inputs in ways you do 
not want. But check with the experts.

Re: Hairpin.minimum-length gives wrong output

[Peter Toye]

Thanks, that works brilliantly. It's a bit of a kludge, but will do for now.

I don't see why the original didn't work, and I think it's a bug, so will 
report it there.

Best regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

-
Wednesday, October 30, 2019, 4:06:31 PM, Phil Holmes wrote:


Try s8\sf\> s8-\hide\p s4 | s2 2 2 2 2 2 2 2 2 2 2 2

--
Phil Holmes
 
 

- Original Message -
From: Peter Toye
To: Phil Holmes; lilypond-user@gnu.org
Sent: Wednesday, October 30, 2019 3:51 PM
Subject: Re: Hairpin.minimum-length gives wrong output

Sorry, a typo. Both lines should have \! rather than \p. What I want is the 
first quaver sf and the hairpin to finish before the next quaver, so that the 
3rd quaver is at the same dynamic  as the 2nd one.

Here's a better MWV

\version "2.19.52"
\language "english"
{
  <<
\new Staff {
  \time 2/4
  \clef "treble"
  c''8 8 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4\break
  c''8 8 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4\break
  c''8 8 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4\break
  c''8 8 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
}
\new Dynamics {
  s8\sf\> s8\! s4 | s2 2 2 2 2 2 2 2 2 2 2 2
  s8\sf\> s8\p s4 | s2 2 2 2 2 2 2 2 2 2 2 2
  \override Hairpin.minimum-length = #10
  s8\sf\> s8\! s4 | s2 2 2 2 2 2 2 2 2 2 2 2
  s8\sf\> s8\p s4 | s2 2 2 2 2 2 2 2 2 2
}
  >>
}

Line 1 has the hairpin too late at both the start and endpoints. Line 2 has a 
warning that the hairpin is too small. Line 3 has the end of the hairpin too 
late. Line 4 is fine.

Best regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

-
Wednesday, October 30, 2019, 3:24:52 PM, Phil Holmes wrote:


Not quite sure of the output you want here.  Your 2 lines of your example 
aren't the same since the top line has a piano dynamic on it and the lower line 
doesn't.  Is the first quaver supposed to have the sf immediately below it?  If 
so, where do you expect the p dynamic to be?  If it's below the second quaver, 
all lily can try to do is space the quavers to fit in the minimum length of 
your hairpin, which it does.

--
Phil Holmes
 
 

- Original Message -
From: Peter Toye
To: lilypond-user@gnu.org
Sent: Wednesday, October 30, 2019 3:14 PM
Subject: Hairpin.minimum-length gives wrong output

This minimal criminal seems to give  wrong output. I want to make sure that the 
hairpin lasts for exactly one quaver (1/8 note). The first line gives a warning 
message that the hairpin is too short. The second line adjusts the length of 
the hairpin but it's now too long.

To try it out you may need to modify the number of notes depending on the paper 
size.

\version "2.19.52"

\language "english"

{
  <<
\new Staff {
  \time 2/4
  \clef "treble"
  c''8 8 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4\break
  c''8 8 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
}
\new Dynamics {
  s8\sf\> s8\p s4 | s2 2 2 2 2 2 2 2 2 2 2 2
   \override Hairpin.minimum-length = #5
  s8\sf\> s8\! s4 | s2 2 2 2 2 2 2 2 2 2
}
  >>
}
 
Regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

testing the reachable of my post

[Jinsong Zhao]

Hi there,

Sorry for the disturbance.

I have tried several times to post my question to the mailing list. 
However, I have not found it posted in the mailing list yet.


--
In the following two pieces of codes, they are should the same. The only 
difference is the the second code combined  the same rhythm into a 
single voice.


\relative c' {
<< { f8 d f a  ~ a f a4 } \\
   {4. 8 ~ 8 c 4 }>> c'2. b4
}

\relative c'{
 << {f8 d f a } \\
{ 4. 8 } >>
 8  4 c2. b4
}

My questions is how to add slur in the second code as those in the first 
one.


Thanks in advance.

Best,
Jinsong

Re: Chop Notation Symbols

[Andrew Bernard]

Are they already in SMuFL? If so, there is a simple way to include them
using openlilylib.

If not, submit them to SMuFL! (seriously).

Andrew


On Thu, 31 Oct 2019 at 05:38, Gregory Hollands 
wrote:

> Casey Driessen and Oriole Saña have developed some new symbols for
> notating the violin/fiddle technique called chopping.
>
>