Re: functions with multiple arguments

2021-01-03 Thread Tom Sgouros
Aha!

Thank you, I could have looked at that for a week without realizing it's
supposed to be a list of functions not a list of function calls.

 -Tom

On Sun, Jan 3, 2021 at 7:46 PM Knute Snortum  wrote:

> I think this is the correct syntax:
>
> rpt =
> #(define-music-function
>  (parser location note1 note2)
>  (ly:pitch? ly:pitch?)
>#{
>  $note1 1 $note2 1
>#})
> \rpt a bes
>
> --
> Knute Snortum
>
> On Sun, Jan 3, 2021 at 4:04 PM Tom Sgouros  wrote:
> >
> > Hello all:
> >
> > This works:
> >
> > rpt =
> > #(define-music-function
> >  (parser location note1)
> >  (ly:pitch?)
> >#{
> >  $note1 1
> >#})
> > \rpt a
> >
> > Why doesn't this? ("Wrong number of arguments to # location note1 note2)>") What am I missing?
> >
> > rpt =
> > #(define-music-function
> >  (parser location note1 note2)
> >  (ly:pitch?) (ly:pitch?)
> >#{
> >  $note1 1 note2 1
> >#})
> > \rpt a bes
> >
> > I was imagining I could use a function like this to generate groups of
> sextets efficiently, with four notes input to make the groups of six and
> making the arpeggio automatically. Perhaps barking up the wrong tree?
> >
> > Thank you,
> >
> >  -Tom
>


Re: functions with multiple arguments

2021-01-03 Thread Knute Snortum
I think this is the correct syntax:

rpt =
#(define-music-function
 (parser location note1 note2)
 (ly:pitch? ly:pitch?)
   #{
 $note1 1 $note2 1
   #})
\rpt a bes

--
Knute Snortum

On Sun, Jan 3, 2021 at 4:04 PM Tom Sgouros  wrote:
>
> Hello all:
>
> This works:
>
> rpt =
> #(define-music-function
>  (parser location note1)
>  (ly:pitch?)
>#{
>  $note1 1
>#})
> \rpt a
>
> Why doesn't this? ("Wrong number of arguments to # location note1 note2)>") What am I missing?
>
> rpt =
> #(define-music-function
>  (parser location note1 note2)
>  (ly:pitch?) (ly:pitch?)
>#{
>  $note1 1 note2 1
>#})
> \rpt a bes
>
> I was imagining I could use a function like this to generate groups of 
> sextets efficiently, with four notes input to make the groups of six and 
> making the arpeggio automatically. Perhaps barking up the wrong tree?
>
> Thank you,
>
>  -Tom



functions with multiple arguments

2021-01-03 Thread Tom Sgouros
Hello all:

This works:

rpt =
#(define-music-function
 (parser location note1)
 (ly:pitch?)
   #{
 $note1 1
   #})
\rpt a

Why doesn't this? ("Wrong number of arguments to #") What am I missing?

rpt =
#(define-music-function
 (parser location note1 note2)
 (ly:pitch?) (ly:pitch?)
   #{
 $note1 1 note2 1
   #})
\rpt a bes

I was imagining I could use a function like this to generate groups of
sextets efficiently, with four notes input to make the groups of six and
making the arpeggio automatically. Perhaps barking up the wrong tree?

Thank you,

 -Tom


Re: \beamExeceptions problem

2021-01-03 Thread David Kastrup
Richard Shann  writes:

> My understanding of the \beamExceptions function in 2.20 was that you
> should be able to pass it a complete bar beamed as you would wish and
> expect other bars with the same beat structure to be beamed to match.

But you did not pass \beamExceptions a bar beamed as you would wish.
You passed it a bar with beaming depending on a combination of automatic
beaming and beaming exceptions.

That doesn't work since at the current point of time, beaming exceptions
_only_ affect beam ends.

> In this example barOne and barTwo have the same rhythm but only barOne
> is beamed as desired.
> What have I got wrong?
>
> Richard Shann
> 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
> \version "2.20"
>
> barOne = {g'16 b' b'[( a'32 g']) d'16[ c''16] c''16[( b'32 a'])}

Beaming for 1/16 notes ends here after c''16] and nowhere else.  Beaming
for 32nd notes ends after g'32]) and a'32]) and nowhere else.  Those are
the beaming exceptions being generated by

\beamExceptions \barOne

as you can verify with

\void \displayScheme \beamExceptions \barOne

-- 
David Kastrup



Re: Text beside staff

2021-01-03 Thread Ahanu Banerjee
Thanks all, instrumentName seems to be the best solution!

-Ahanu


On Sun, Jan 3, 2021 at 5:00 PM Ahanu Banerjee  wrote:

> Hi,
>
> I'm typesetting a book of études. I am currently putting the number of the
> etude (1-2 digits) in the header as a title, but I would like to put it to
> the left of the first staff, in the indented white space. It should be
> center-aligned between the left margin and the first staff, and vertically
> centered about the staff.
>
> Can someone provide a tidy way to do this?
>
> Thank you!!
>
> \version "2.20.0"
> \header {
>   title = "1"
>   subtitle = "A female deer"
> }
>
> {\repeat unfold 16 c' \break
> \repeat unfold 20 c'}
>


Re: Text beside staff

2021-01-03 Thread Knute Snortum
I think the best way to do this is to use the instrument name:

\score {
  \new PianoStaff \with { instrumentName = \markup \huge "No. 4" }
  <<
  ...
  >>
}

--
Knute Snortum

On Sun, Jan 3, 2021 at 2:01 PM Ahanu Banerjee  wrote:
>
> Hi,
>
> I'm typesetting a book of études. I am currently putting the number of the 
> etude (1-2 digits) in the header as a title, but I would like to put it to 
> the left of the first staff, in the indented white space. It should be 
> center-aligned between the left margin and the first staff, and vertically 
> centered about the staff.
>
> Can someone provide a tidy way to do this?
>
> Thank you!!
>
> \version "2.20.0"
> \header {
>   title = "1"
>   subtitle = "A female deer"
> }
>
> {\repeat unfold 16 c' \break
> \repeat unfold 20 c'}



Text beside staff

2021-01-03 Thread Ahanu Banerjee
Hi,

I'm typesetting a book of études. I am currently putting the number of the
etude (1-2 digits) in the header as a title, but I would like to put it to
the left of the first staff, in the indented white space. It should be
center-aligned between the left margin and the first staff, and vertically
centered about the staff.

Can someone provide a tidy way to do this?

Thank you!!

\version "2.20.0"
\header {
  title = "1"
  subtitle = "A female deer"
}

{\repeat unfold 16 c' \break
\repeat unfold 20 c'}


Re: \beamExeceptions problem

2021-01-03 Thread Xavier Scheuer
On Sun, 3 Jan 2021 at 18:04, Richard Shann  wrote:
>
> My understanding of the \beamExceptions function in 2.20 was that you
> should be able to pass it a complete bar beamed as you would wish and
> expect other bars with the same beat structure to be beamed to match.
> In this example barOne and barTwo have the same rhythm but only barOne
> is beamed as desired.
> What have I got wrong?

Hello Richard,

I learned this \beamExceptions function thanks to you, thank you.
If you replace  \beamExceptions \barOne by
\beamExceptions { 16[ 16] 16[ 32 32] 16[ 16] 16[ 32 32] }
you get the desired output.

Not sure what's going on, but when putting only rhythm in the pattern (like
the example in the documentation) it seems to work.

Cheers,
Xavier

-- 
Xavier Scheuer 


Re: Lyrics for ossia staff

2021-01-03 Thread JxStarks
Remy,

Thanks for the suggestion, but I have the same problem with this that I
have with the Documentation: it works fine as a snippet, but when I put it
in the entire piece, the ossia staff is below the bass staff, and the ossia
lyrics are beneath the soprano lyrics under the top staff. I need to have
the "ossia" staff above the top (soprano) staff, and the ossia lyrics
associated with the ossia staff.

Jerry

On Sun, Jan 3, 2021 at 2:58 PM JxStarks  wrote:

> Got it, thanks! I'll try it out now.
>
> On Sun, Jan 3, 2021 at 1:31 PM Remy CLAVERIE 
> wrote:
>
>> Hi Jerry,
>>
>>
>>
>> Here is a MWE with ossia/lyrics:
>>
>>
>>
>> \version "2.18.2"
>>
>> OssiaLyrics = \lyricmode {
>>   Ma -- gni -- fi -- cat
>> }
>>
>> \new Staff
>> <<
>>   \new Voice \relative c {
>> c''4 b d c
>> <<
>>   { c4 b d c }
>> \new Staff
>> <<
>>   \new Voice = "V" \relative c'' { e4 d f e }
>> >>
>> >>
>> c4 b c2
>>   }
>>   \new Lyrics \lyricsto "V" \OssiaLyrics
>> >>
>>
>>
>>
>> HTH,
>>
>>
>>
>> Rémy
>>
>> > Message du 03/01/21 18:22
>> > De : "JxStarks" 
>> > A : "lilypond-user" 
>> > Copie à :
>> > Objet : Lyrics for ossia staff
>> >
>> >
>> Hi all,
>>
>> >
>> I expect this has been solved somewhere, but I can't find it. The
>> documentation is good at explaining how to do something in isolation, but
>> not so good at explaining how to do something in the middle of a different
>> structure, such as a choir staff.
>>
>> >
>> Anyway, I have a choir staff to which I want to add an extra staff for
>> the Soprano I voices. I want the staff to appear at measure 27 and continue
>> until measure 41 and then stop. I want the extra staff to contain both
>> music and lyrics.
>> >
>>
>> >
>> I was able to get the staff and music to work fairly well using a
>> structure suggested in a previous discussion on ossia staves. How can I get
>> lyrics to go with it? The structure follows. Sorry it's so long: I'm not
>> sure where all the commands need to be placed. If there's a more elegant
>> solution, I'm all in favor of it, even if it means restructuring the whole
>> piece:
>> >
>>
>> >
>>
>> \version "2.18.2"
>>
>>
>>
>> \header { }
>>
>>
>>
>> global = {
>>
>>   \key d \major
>>
>>   \time 4/4
>>
>>   \tempo 4=69
>>
>>   \set Score.markFormatter = #format-mark-box-alphabet }
>>
>>
>>
>> sopI = \relative c'' {
>>
>>   \global
>>
>>   \dynamicUp
>>
>> *  Notes and rests.*
>>
>> }
>>
>>
>>
>> ossia = \relative c’’ { \stopStaff s1*25 \startStaff
>>
>>*Notes and rests for auxiliary staff *
>>
>>\stopStaff
>>
>> }
>>
>>
>>
>> verseSopranoVoice = \lyricmode {  *Lyrics here*. }
>>
>>
>>
>> olyrics = \lyricmode { *Auxiliary lyrics here.* }
>>
>>
>>
>> altoVoice = *same setup as sopI*
>>
>>   verseAltoVoice = *same setup as sopI*
>>
>> tenorVoice = *same setup as sopI*
>>
>>   verseTenorVoice = *same setup as sopI*
>>
>> bassVoice = *same setup as sopI*
>>
>>   verseBassVoice = *same setup as sopI*
>>
>>
>>
>> sopranoVoicePart = <<
>>
>>   \context Staff  = “top” \with {
>>
>> instrumentName = "Sopranos"
>>
>> shortInstrumentName = \markup \center-column { "S1" "S2" }
>>
>> midiInstrument = "choir aahs"
>>
>> }  { \new Voice = “1” \sopI }
>>
>>   <<
>>
>> \lyrics {
>>
>>\new Lyrics \lyricsto “1” \verseSopranoVoice }
>>
>>  \new Staff \with {
>>
>>alignAbove Context = #”top”
>>
>> \remove “Time_signature_engraver”
>>
>> \override Clef #’transparent = ##t
>>
>>} { \ossia }
>>
>>   >>
>>
>> }
>>
>> >>
>>
>>
>>
>> altoVoicePart = \new Staff \with {
>>
>>   instrumentName = “Altos”
>>
>>   shortInstrumentName \ \markup \center-column { “A1” “A2” }
>>
>>   midiInstrument = “choir aahs”
>>
>> } { \altoVoice }
>>
>>  \addlyrics { \verseAltoVoice }
>>
>>
>>
>> tenorVoicePart = *same setup as altoVoicePart*
>>
>> bassVoicePart = *same setup as altoVoicePart*
>>
>>
>>
>> \score {
>>
>>   <<
>>
>> \sopranoVoicePart
>>
>> \altoVoicePart
>>
>> \tenorVoicePart
>>
>> \bassVoicePart
>>
>>   >>
>>
>>   \layout { }
>>
>>   \midi { }
>>
>> }
>>
>>
>> >
>>
>> Thanks,
>>
>> Jerry Starks
>> >
>>
>>
>>
>>


Re: Lyrics for ossia staff

2021-01-03 Thread Guy Stalnaker
Here is another way (especially if one uses Frescobaldi and its Score
Wizard to create the score structure:

%% CODE %%

\version "2.19"
\language "english"
soprano = {
  a'2.
  <<
{
  f'4( ~ |
  f'4. g'8 a'4 f' ~ |
}
\new Staff = "Solo" \with { alignAboveContext = #"sopranos" }
{
  \partial 4 \key f \major a'4^"Solo" \bar "||"
  a'4. bf'8 c''4 a' |
}
\addlyrics \with { alignBelowContext = #"Solo" } {
  Yet what I can I give Him,
  Give my heart.
}
  >>
  \bar "|."
 }
verseSopranoVoice = \lyricmode {
  % Lyrics follow here.
 heart. Ooh __
}
sopranoVoicePart = \new Staff = "sopranos" \with {
} { \soprano }
\addlyrics { \verseSopranoVoice }
\score {
  \new ChoirStaff <<
\sopranoVoicePart
  >>
  \layout { }
}

%%CODE%%


--

“Happiness is the meaning and the purpose of life, the whole aim and end of
human existence.”

― Aristotle


On Sun, Jan 3, 2021 at 11:21 AM JxStarks  wrote:

> Hi all,
>
> I expect this has been solved somewhere, but I can't find it. The
> documentation is good at explaining how to do something in isolation, but
> not so good at explaining how to do something in the middle of a different
> structure, such as a choir staff.
>
> Anyway, I have a choir staff to which I want to add an extra staff for the
> Soprano I voices. I want the staff to appear at measure 27 and continue
> until measure 41 and then stop. I want the extra staff to contain both
> music and lyrics.
>
> I was able to get the staff and music to work fairly well using a
> structure suggested in a previous discussion on ossia staves. How can I get
> lyrics to go with it? The structure follows. Sorry it's so long: I'm not
> sure where all the commands need to be placed. If there's a more elegant
> solution, I'm all in favor of it, even if it means restructuring the whole
> piece:
>
> \version "2.18.2"
>
>
>
> \header { }
>
>
>
> global = {
>
>   \key d \major
>
>   \time 4/4
>
>   \tempo 4=69
>
>   \set Score.markFormatter = #format-mark-box-alphabet }
>
>
>
> sopI = \relative c'' {
>
>   \global
>
>   \dynamicUp
>
> *  Notes and rests.*
>
> }
>
>
>
> ossia = \relative c’’ { \stopStaff s1*25 \startStaff
>
>*Notes and rests for auxiliary staff *
>
>\stopStaff
>
> }
>
>
>
> verseSopranoVoice = \lyricmode {  *Lyrics here*. }
>
>
>
> olyrics = \lyricmode { *Auxiliary lyrics here.* }
>
>
>
> altoVoice = *same setup as sopI*
>
>   verseAltoVoice = *same setup as sopI*
>
> tenorVoice = *same setup as sopI*
>
>   verseTenorVoice = *same setup as sopI*
>
> bassVoice = *same setup as sopI*
>
>   verseBassVoice = *same setup as sopI*
>
>
>
> sopranoVoicePart = <<
>
>   \context Staff  = “top” \with {
>
> instrumentName = "Sopranos"
>
> shortInstrumentName = \markup \center-column { "S1" "S2" }
>
> midiInstrument = "choir aahs"
>
> }  { \new Voice = “1” \sopI }
>
>   <<
>
> \lyrics {
>
>\new Lyrics \lyricsto “1” \verseSopranoVoice }
>
>  \new Staff \with {
>
>alignAbove Context = #”top”
>
> \remove “Time_signature_engraver”
>
> \override Clef #’transparent = ##t
>
>} { \ossia }
>
>   >>
>
> }
>
> >>
>
>
>
> altoVoicePart = \new Staff \with {
>
>   instrumentName = “Altos”
>
>   shortInstrumentName \ \markup \center-column { “A1” “A2” }
>
>   midiInstrument = “choir aahs”
>
> } { \altoVoice }
>
>  \addlyrics { \verseAltoVoice }
>
>
>
> tenorVoicePart = *same setup as altoVoicePart*
>
> bassVoicePart = *same setup as altoVoicePart*
>
>
>
> \score {
>
>   <<
>
> \sopranoVoicePart
>
> \altoVoicePart
>
> \tenorVoicePart
>
> \bassVoicePart
>
>   >>
>
>   \layout { }
>
>   \midi { }
>
> }
>
>
> Thanks,
>
> Jerry Starks
>
>


Re: Lyrics for ossia staff

2021-01-03 Thread JxStarks
Got it, thanks! I'll try it out now.

On Sun, Jan 3, 2021 at 1:31 PM Remy CLAVERIE 
wrote:

> Hi Jerry,
>
>
>
> Here is a MWE with ossia/lyrics:
>
>
>
> \version "2.18.2"
>
> OssiaLyrics = \lyricmode {
>   Ma -- gni -- fi -- cat
> }
>
> \new Staff
> <<
>   \new Voice \relative c {
> c''4 b d c
> <<
>   { c4 b d c }
> \new Staff
> <<
>   \new Voice = "V" \relative c'' { e4 d f e }
> >>
> >>
> c4 b c2
>   }
>   \new Lyrics \lyricsto "V" \OssiaLyrics
> >>
>
>
>
> HTH,
>
>
>
> Rémy
>
> > Message du 03/01/21 18:22
> > De : "JxStarks" 
> > A : "lilypond-user" 
> > Copie à :
> > Objet : Lyrics for ossia staff
> >
> >
> Hi all,
>
> >
> I expect this has been solved somewhere, but I can't find it. The
> documentation is good at explaining how to do something in isolation, but
> not so good at explaining how to do something in the middle of a different
> structure, such as a choir staff.
>
> >
> Anyway, I have a choir staff to which I want to add an extra staff for the
> Soprano I voices. I want the staff to appear at measure 27 and continue
> until measure 41 and then stop. I want the extra staff to contain both
> music and lyrics.
> >
>
> >
> I was able to get the staff and music to work fairly well using a
> structure suggested in a previous discussion on ossia staves. How can I get
> lyrics to go with it? The structure follows. Sorry it's so long: I'm not
> sure where all the commands need to be placed. If there's a more elegant
> solution, I'm all in favor of it, even if it means restructuring the whole
> piece:
> >
>
> >
>
> \version "2.18.2"
>
>
>
> \header { }
>
>
>
> global = {
>
>   \key d \major
>
>   \time 4/4
>
>   \tempo 4=69
>
>   \set Score.markFormatter = #format-mark-box-alphabet }
>
>
>
> sopI = \relative c'' {
>
>   \global
>
>   \dynamicUp
>
> *  Notes and rests.*
>
> }
>
>
>
> ossia = \relative c’’ { \stopStaff s1*25 \startStaff
>
>*Notes and rests for auxiliary staff *
>
>\stopStaff
>
> }
>
>
>
> verseSopranoVoice = \lyricmode {  *Lyrics here*. }
>
>
>
> olyrics = \lyricmode { *Auxiliary lyrics here.* }
>
>
>
> altoVoice = *same setup as sopI*
>
>   verseAltoVoice = *same setup as sopI*
>
> tenorVoice = *same setup as sopI*
>
>   verseTenorVoice = *same setup as sopI*
>
> bassVoice = *same setup as sopI*
>
>   verseBassVoice = *same setup as sopI*
>
>
>
> sopranoVoicePart = <<
>
>   \context Staff  = “top” \with {
>
> instrumentName = "Sopranos"
>
> shortInstrumentName = \markup \center-column { "S1" "S2" }
>
> midiInstrument = "choir aahs"
>
> }  { \new Voice = “1” \sopI }
>
>   <<
>
> \lyrics {
>
>\new Lyrics \lyricsto “1” \verseSopranoVoice }
>
>  \new Staff \with {
>
>alignAbove Context = #”top”
>
> \remove “Time_signature_engraver”
>
> \override Clef #’transparent = ##t
>
>} { \ossia }
>
>   >>
>
> }
>
> >>
>
>
>
> altoVoicePart = \new Staff \with {
>
>   instrumentName = “Altos”
>
>   shortInstrumentName \ \markup \center-column { “A1” “A2” }
>
>   midiInstrument = “choir aahs”
>
> } { \altoVoice }
>
>  \addlyrics { \verseAltoVoice }
>
>
>
> tenorVoicePart = *same setup as altoVoicePart*
>
> bassVoicePart = *same setup as altoVoicePart*
>
>
>
> \score {
>
>   <<
>
> \sopranoVoicePart
>
> \altoVoicePart
>
> \tenorVoicePart
>
> \bassVoicePart
>
>   >>
>
>   \layout { }
>
>   \midi { }
>
> }
>
>
> >
>
> Thanks,
>
> Jerry Starks
> >
>
>
>
>


Re: Please help

2021-01-03 Thread David Wright
On Sun 03 Jan 2021 at 18:17:37 (+0100), Lilypond-User wrote:
> Is it good enough to add this to your file?
> 
> \version "2.XXX"

The source file is available from the fourth link next to the score on
CPDL. It *has* a version number, and convert-ly will convert the file
to a more current version. I've just converted and compiled it for
2.21.80 successfully.

> Le 03/01/2021 à 17:58, Hans Kraus a écrit :
> > I would like to get in touch with J. B. He did/engraved (?) "Du
> > süße Lieb, schenk uns deine Gunst" by LilyPond on 27. 8. 12. On
> > the score sheet it says "Music engraving by LilyPond 2.16.0.
> > (Would this information help?)

Cheers,
David.



re: Lyrics for ossia staff

2021-01-03 Thread Remy CLAVERIE
Hi Jerry,

 

Here is a MWE with ossia/lyrics:

 

\version "2.18.2"

OssiaLyrics = \lyricmode {
  Ma -- gni -- fi -- cat
}

\new Staff 
<<
  \new Voice \relative c {
    c''4 b d c
    <<
  { c4 b d c }
    \new Staff
    <<
  \new Voice = "V" \relative c'' { e4 d f e }
    >>
    >>
    c4 b c2 
  }
  \new Lyrics \lyricsto "V" \OssiaLyrics
>>

 

HTH,

 

Rémy

> Message du 03/01/21 18:22
> De : "JxStarks" 
> A : "lilypond-user" 

> Copie à : 
> Objet : Lyrics for ossia staff
> 
>

Hi all,

>
I expect this has been solved somewhere, but I can't find it. The documentation 
is good at explaining how to do something in isolation, but not so good at 
explaining how to do something in the middle of a different structure, such as 
a choir staff.

>
Anyway, I have a choir staff to which I want to add an extra staff for the 
Soprano I voices. I want the staff to appear at measure 27 and continue until 
measure 41 and then stop. I want the extra staff to contain both music and 
lyrics. 
>

>
I was able to get the staff and music to work fairly well using a structure 
suggested in a previous discussion on ossia staves. How can I get lyrics to go 
with it? The structure follows. Sorry it's so long: I'm not sure where all the 
commands need to be placed. If there's a more elegant solution, I'm all in 
favor of it, even if it means restructuring the whole piece: 
>

>

\version "2.18.2"

 

\header { }

 

global = {

  \key d \major

  \time 4/4

  \tempo 4=69

  \set Score.markFormatter = #format-mark-box-alphabet }

 

sopI = \relative c'' {

  \global

  \dynamicUp 

  Notes and rests.

}

 

ossia = \relative c’’ { \stopStaff s1*25 \startStaff 

   Notes and rests for auxiliary staff 

   \stopStaff

}

 

verseSopranoVoice = \lyricmode {  Lyrics here. }

 

olyrics = \lyricmode { Auxiliary lyrics here. }

 

altoVoice = same setup as sopI

  verseAltoVoice = same setup as sopI

tenorVoice = same setup as sopI

  verseTenorVoice = same setup as sopI

bassVoice = same setup as sopI

  verseBassVoice = same setup as sopI

 

sopranoVoicePart = << 

  \context Staff  = “top” \with { 

    instrumentName = "Sopranos"

    shortInstrumentName = \markup \center-column { "S1" "S2" }

    midiInstrument = "choir aahs"

}  { \new Voice = “1” \sopI }

  << 

    \lyrics { 

   \new Lyrics \lyricsto “1” \verseSopranoVoice }

 \new Staff \with {

   alignAbove Context = #”top”

    \remove “Time_signature_engraver”

    \override Clef #’transparent = ##t 

   } { \ossia } 

  >>  

}  

>> 

 

altoVoicePart = \new Staff \with { 

  instrumentName = “Altos”

  shortInstrumentName \ \markup \center-column { “A1” “A2” }

  midiInstrument = “choir aahs”

} { \altoVoice }

 \addlyrics { \verseAltoVoice }

 

tenorVoicePart = same setup as altoVoicePart

bassVoicePart = same setup as altoVoicePart

 

\score {

  <<

    \sopranoVoicePart

    \altoVoicePart

    \tenorVoicePart

    \bassVoicePart

  >>

  \layout { }

  \midi { }

}


>

Thanks,

Jerry Starks
>

 





Re: Spacing between clef and first note without time signature

2021-01-03 Thread Jay Anderson
On Fri, Jan 1, 2021 at 3:27 AM Xavier Scheuer  wrote:

> The space between Clef and first-note is documented in the Internals
> References manual,
> IR 3.1.26 Clef
> http://lilypond.org/doc/v2.20/Documentation/internals/clef
>
> You can modify the space-alist property for the first-note item. Either by
> changing the spacing-style to a stretchable (or semi-fixed) space or by
> reducing the value of minimum-fixed-space.
>

Thanks for pointing that out. It worked perfectly. Here's what I finally
had:

  \score {
\new Staff { c''2 r }
\layout {
  ragged-right = ##t
  indent = 0\cm
  line-width = 1.5\cm
  \context {
\Staff
\omit TimeSignature
\override Clef.space-alist.first-note = #'(minimum-fixed-space
. 3.0)
  }
  #(layout-set-staff-size 14)
}

-Jay


Re: Please help

2021-01-03 Thread Werner LEMBERG

> I would like to get in touch with J. B. He did/engraved (?) "Du süße
> Lieb, schenk uns deine Gunst" by LilyPond on 27. 8. 12.  On the
> score sheet it says "Music engraving by LilyPond 2.16.0. (Would this
> information help?)

No, this is doesn't help.

However, a quick search in the internet for your information bits
yields this:

  
https://www.cpdl.org/wiki/index.php/Gott_ist_unsre_Zuversicht,_BWV_197_(Johann_Sebastian_Bach)

Clicking on the name (Johannes Becker) you even get his e-mail
address...


Werner


Re: Placement of tuplet brackets

2021-01-03 Thread Werner LEMBERG


> I am trying to build a package for Persian percussion (for tombak
> and daf instruments) while learning Lilypond.

Interesting!

> Back to my current struggle with tuplets: I cannot find a way to
> tweak Lilypond through its tuplet-bracket interface (or any other)
> to place tuplet brackets where I want them.  [...]

Please post images of what you get (ideally posting a MWE), and what
you expect.


Werner



Lyrics for ossia staff

2021-01-03 Thread JxStarks
Hi all,

I expect this has been solved somewhere, but I can't find it. The
documentation is good at explaining how to do something in isolation, but
not so good at explaining how to do something in the middle of a different
structure, such as a choir staff.

Anyway, I have a choir staff to which I want to add an extra staff for the
Soprano I voices. I want the staff to appear at measure 27 and continue
until measure 41 and then stop. I want the extra staff to contain both
music and lyrics.

I was able to get the staff and music to work fairly well using a structure
suggested in a previous discussion on ossia staves. How can I get lyrics to
go with it? The structure follows. Sorry it's so long: I'm not sure where
all the commands need to be placed. If there's a more elegant solution, I'm
all in favor of it, even if it means restructuring the whole piece:

\version "2.18.2"



\header { }



global = {

  \key d \major

  \time 4/4

  \tempo 4=69

  \set Score.markFormatter = #format-mark-box-alphabet }



sopI = \relative c'' {

  \global

  \dynamicUp

*  Notes and rests.*

}



ossia = \relative c’’ { \stopStaff s1*25 \startStaff

   *Notes and rests for auxiliary staff *

   \stopStaff

}



verseSopranoVoice = \lyricmode {  *Lyrics here*. }



olyrics = \lyricmode { *Auxiliary lyrics here.* }



altoVoice = *same setup as sopI*

  verseAltoVoice = *same setup as sopI*

tenorVoice = *same setup as sopI*

  verseTenorVoice = *same setup as sopI*

bassVoice = *same setup as sopI*

  verseBassVoice = *same setup as sopI*



sopranoVoicePart = <<

  \context Staff  = “top” \with {

instrumentName = "Sopranos"

shortInstrumentName = \markup \center-column { "S1" "S2" }

midiInstrument = "choir aahs"

}  { \new Voice = “1” \sopI }

  <<

\lyrics {

   \new Lyrics \lyricsto “1” \verseSopranoVoice }

 \new Staff \with {

   alignAbove Context = #”top”

\remove “Time_signature_engraver”

\override Clef #’transparent = ##t

   } { \ossia }

  >>

}

>>



altoVoicePart = \new Staff \with {

  instrumentName = “Altos”

  shortInstrumentName \ \markup \center-column { “A1” “A2” }

  midiInstrument = “choir aahs”

} { \altoVoice }

 \addlyrics { \verseAltoVoice }



tenorVoicePart = *same setup as altoVoicePart*

bassVoicePart = *same setup as altoVoicePart*



\score {

  <<

\sopranoVoicePart

\altoVoicePart

\tenorVoicePart

\bassVoicePart

  >>

  \layout { }

  \midi { }

}


Thanks,

Jerry Starks


Re: Please help

2021-01-03 Thread Deneufchâtel Matthieu via LilyPond user discussion

Is it good enough to add this to your file?

\version "2.XXX"

Matthieu

Le 03/01/2021 à 17:58, Hans Kraus a écrit :

Dear Ladies and Gentlemen,

I would like to get in touch with J. B. He did/engraved (?) "Du süße 
Lieb, schenk uns deine Gunst" by LilyPond on 27. 8. 12. On the score 
sheet it says "Music engraving by LilyPond 2.16.0. (Would this 
information help?)

Thanks a lot for your answer in advance.

Best musical regards,
Hans Kraus
--
Hans Kraus
Ulmenweg 4
96123 Naisa
Tel 09505-1778
+49  163 1299 569
hans_kr...@yahoo.de

Hans auf drei acht  

Hans Kraus singt die 7. Strophe des Frankenliedes  



Please help

2021-01-03 Thread Hans Kraus

  
  
Dear Ladies and Gentlemen,

I would like to get in touch with J. B. He did/engraved (?) "Du süße
Lieb, schenk uns deine Gunst" by LilyPond on 27. 8. 12. On the score
sheet it says "Music engraving by LilyPond 2.16.0. (Would this
information help?)
Thanks a lot for your answer in advance. 

Best musical regards,
Hans Kraus
-- 
  
  
  Hans Kraus
Ulmenweg 4
96123 Naisa
Tel 09505-1778
+49  163 1299 569
hans_kr...@yahoo.de

Hans auf drei acht
  Hans Kraus singt die 7. Strophe des Frankenliedes


  





\beamExeceptions problem

2021-01-03 Thread Richard Shann
My understanding of the \beamExceptions function in 2.20 was that you
should be able to pass it a complete bar beamed as you would wish and
expect other bars with the same beat structure to be beamed to match.
In this example barOne and barTwo have the same rhythm but only barOne
is beamed as desired.
What have I got wrong?

Richard Shann
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
\version "2.20"

barOne = {g'16 b' b'[( a'32 g']) d'16[ c''16] c''16[( b'32 a'])}

barTwo = {g'16 b' b'( a'32 g') d'16 c''16 c''16( b'32 a')}


Music = {
  \barOne
  \barTwo   
}

\score { %Start of Movement
  <<
\new Staff { 
   \time 2/4 \Music
}
  >>

  \layout {
  \overrideTimeSignatureSettings 2/4 1/4 #'(1 1) 
  \beamExceptions \barOne
  }
   }
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><



Placement of tuplet brackets

2021-01-03 Thread Farhad Arbab
I am trying to build a package for Persian percussion (for tombak and 
daf instruments) while learning Lilypond.  My  basic layout uses single 
staff drum mode, note stems up.  Traditionally, virtually every note is 
adorned with special symbols and finger numbers written above note stems.


I now have a set of music-functions that use \markup commands to place 
these symbols over the bd notes  in drummode of Lilypond. So, for notes 
commonly referred to as tom, bak, ka, tomka, baka, snap2 snap3, etc., I 
now enter "\drummode { \tom bd4 \bak bd8 \ka bd8 \tomka bd4 \baka bd4 
\snap2 bd16 \snap3 bd }", etc.


As an aside, I do not like my current set up and would like to have 
custom-made modes tombakmode and dafmode where I can simply enter 
"\tombakmode { tom4, bak8, ka8, tomka4, baka4, snap2 16 snap3 }", etc.  
As a novice, I do not know how I can define my own mode, so I leave this 
as a future project for now.  Nevertheless, I appreciate any help, 
comments, pointer on this future project of mine.


Back to my current struggle with tuplets: I cannot find a way to tweak 
Lilypond through its tuplet-bracket interface (or any other) to place 
tuplet brackets where I want them.


Where Lilypond places tuplet brackets now is above note stems, below all 
special symbols that I add to the notes (with markup). The problem with 
this is that those special symbols are really an integral part of each 
note and must not be separated from the note stems by tuplet brackets or 
anything else.  I can think of two alternatives for placement of tuplet 
brackets, but I am unable to tweak Lilypond to do either one.


The first (less desirable) alternative is to get Lilypond place tuplet 
brackets above all special markup on top of note stems. Even if I can do 
this, it is not ideal, because with so many symbols stacked on top of 
one another over note stems, it gets too crowded up there.


The second alternative is to get Lilypond to place tuplet brackets below 
the note heads (i.e., between the note heads and ties or hairpins).  
This area is far less crowded (sometimes we get hairpins or ties there, 
but not often). Not surprisingly, this is where traditionally people 
write tuplet brackets for such scores, anyway.


Cheers,

Farhad




Repeats with bar-engraver removed

2021-01-03 Thread J Stasko
I need to be able to engrave repeats, but I fear that the bar-engraver,
which I turned off for chant music, is responsible for engraving the
repeats: when I turn it back on, then the repeats appear, but since the
music is chant, it runs off the page.

How to do this?

The work is attached.

Thank you.


velikoye-slavosloviye.ly
Description: Binary data


Re: New version of Spontini-Editor with many new features

2021-01-03 Thread Paolo Prete
Thank you!

On Sun, Jan 3, 2021 at 3:18 PM Knute Snortum  wrote:

> I don't have a  "spontinivenv" directory inside lib/python.  I'll open
> a GitHub issue.
>
> --
> Knute Snortum
>
> On Sat, Jan 2, 2021 at 11:49 PM Paolo Prete  wrote:
> >
> > Hello,
> >
> > Please delete the "spontinivenv" directory inside lib/python and run
> again the program.
> > If this doesn't solve, file an issue in github.
> >
> > On Saturday, January 2, 2021, Knute Snortum  wrote:
> >>
> >> This is my experience with installing Spontini:
> >>
> >> $ 6 Feb  1  2020
> >> /usr/share/bash-completion/completions/pyvenv-3.8 -> pyvenv
> >>
> >> So the link reference is circular. I'm not even sure who to report
> >> this to.  But there you have it.
> >>
> >> --
> >> Knute Snortum
> >>
> >>
>


Re: New version of Spontini-Editor with many new features

2021-01-03 Thread Knute Snortum
I don't have a  "spontinivenv" directory inside lib/python.  I'll open
a GitHub issue.

--
Knute Snortum

On Sat, Jan 2, 2021 at 11:49 PM Paolo Prete  wrote:
>
> Hello,
>
> Please delete the "spontinivenv" directory inside lib/python and run again 
> the program.
> If this doesn't solve, file an issue in github.
>
> On Saturday, January 2, 2021, Knute Snortum  wrote:
>>
>> This is my experience with installing Spontini:
>>
>> $ 6 Feb  1  2020
>> /usr/share/bash-completion/completions/pyvenv-3.8 -> pyvenv
>>
>> So the link reference is circular. I'm not even sure who to report
>> this to.  But there you have it.
>>
>> --
>> Knute Snortum
>>
>>