Re: \with-url for markup that is \epsfile doesn't work.

[Richard Shann]

Thanks - your file works for me too, and exploring I find, as you did,
that most eps *do* work, I was unlucky. 
One thing I recall is that on the file that doesn't work the mouse
pointer changes to a text insertion pointer, so it would seem to be that
there is some text attribute, present in the eps, which the display
library (libevince) is prioritising over the link.
I noticed that Inkscape offered options to do with text while saving
encapsulated postscript, so it may be the solution is in there.
Thank you once more

Richard




On Sun, 2014-06-08 at 19:31 +0200, Thomas Morley wrote:
> 2014-06-08 17:39 GMT+02:00 Richard Shann :
> > If I put some markup at the end of a score like this
> >
> > \markup {\with-url #'"some url" \epsfile #X #100 #"filename.eps" }
> >
> > the filename.eps is displayed after the music, but there is no hotspot
> > for the link as there would be if it was just some text there.
> >
> > It would be nice if the user could click anywhere on the image to
> > activate the url, is there a way round this?
> >
> > Richard
> 
> Hi Richard,
> 
> I had no problems with:
> 
> \markup {
> \with-url #"http://lilypond.org/";
> \epsfile #X #5 #"note.eps"
> }
> 
> and the attached eps-file.
> Though, I seem to remember that sometimes certain eps-files don't work.
> Try to redo creating the eps
> 
> HTH,
>   Harm



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Fwd: Lilypond as a library

[Ole Schmidt]

Anfang der weitergeleiteten Nachricht:

> Von: Mike Solomon 
> Betreff: Aw: Lilypond as a library
> Datum: 8. Juni 2014 10:37:49 MESZ
> An: Mauren Berti 
> Kopie: lilypond-user , Dominique Fober 
> 
> 
> On Jun 7, 2014, at 10:43 PM, Mauren Berti  wrote:
> 
>> Hello!
>> 
>> I am writing a software as my graduation project which captures audio and 
>> generates a .ly file. I'd like to embed Lilypond as a library in my 
>> software, so that it can generate the .pdf file directly, but was not able 
>> to find a library-like compilation of Lilypond. Is there such a thing?
>> 
>> Thanks in advance!
>> Mauren.
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> Dear Maruen,
> 
> You may want to check out Guido, which is (as far as I know) the only 
> embeddable music engraving library:
> 
> http://sourceforge.net/p/guidolib
> 
> Cheers,
> MS
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


There is also fomus (http://fomus.sourceforge.net)..


best

ole


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

SystemStartBracket/Brace

[b...@wolfcomposer.com]

Hello, All--

To start, i'm using LilyPond 2.18.2.  To keep this short, here is how i've set
up my score:

\score {

  \new GrandStaff
<<
\set GrandStaff.connectArpeggios = ##t

   \new PianoStaff
   \set PianoStaff.connectArpeggios = ##t
 <<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
 >>

   \new Staff = "feet" \feet

>>

}

Many will recognize this as a modification of the "organ template" in section
3.4.3 of the Learning Manual.  i put the entire system in a GrandStaff because i
found it the only way to connect an arpeggio across all three staves.

But getting to the point:  i would like the SystemStartBrace of the GrandStaff
to span only the top two staves.  When i remove the
System_start_delimiter_engraver from the GrandStaff and put it in the
PianoStaff, i get no SystemStartBrace at all.  If i try \override
GrandStaff.SystemStartBrace.collapse-height = #10, the SystemStartBrace never
changes size, still spanning over all three staves.

The last option has led to some behaviour that i just don't understand.  i can
set the collapse-height number to as large as 21, and the brace remains.  If i
set the number to 22, the brace disappears.  Given that the total number of
staff lines is 15, i don't see how that is conistent with this statement:  %
Must be lower than the actual number of staff lines.  The quote came from the
section of the Snippets manual on how to display a bracket with only one staff
in a system.  Can i assume that the collapse-height property only works with one
staff in a system, as per the snippet?  If not, then why did the property behave
as it did in my override?  After all, both 21 and 22 are greater than 15, so the
brace should have disappeared when i set the collapse-height property to 16.  As
i said, i don't understand, no matter how much i read.

One more thing.  i nested all brackets and braces, defining the "feet" staff as
a single staff in a system (as per the snippet mentioned above), attempting to
get everything to print.  Only the brace for the GrandStaff and the bracket for
the "feet" staff printed.  The brace for the PianoStaff did not print.  In fact,
in my setup, it never prints--ever.  i even changed PianoStaff to StaffGroup,
specifying a bracket instead of a brace, and still the bracket wouldn't print.
 It appears to be ignored in the nesting procedure.

So, after about fifteen hours struggling with this, i've taken to the group.  i
apologize for the length, but i wanted to be as thorough as possible.  i
appreciate any and all help not just solving this problem, but also
understanding what's happening.  Thank you, much!

bill___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Lilypond-book and Default Staff Size

[Br. Samuel Springuel]

I'm creating a document with Lilypond book and want all the musical 
systems in the document to be the same size, but also want to be able to 
tune the size to match the document font size settings (I have to 
produce the document in both a "normal" version and a "large type" 
version).  So far, I've been placing a "staffsize=#" option on each 
snippet, but as the number of snippets is proliferating, this is getting 
cumbersome.  Is there a way to globally set the staff size for all 
lilypond snippets in a document?

--
✝
Br. Samuel, OSB
(R. Padraic Springuel)

PAX ☧ ΧΡΙΣΤΟΣ

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: SystemStartBracket/Brace

[David Kastrup]

"b...@wolfcomposer.com"  writes:

> Hello, All--
>
> To start, i'm using LilyPond 2.18.2.  To keep this short, here is how i've set
> up my score:
>
> \score {
>
>   \new GrandStaff
> <<
> \set GrandStaff.connectArpeggios = ##t
>
>\new PianoStaff
>\set PianoStaff.connectArpeggios = ##t
>  <<
> \new Staff = "upper" \upper
> \new Staff = "lower" \lower
>  >>
>
>\new Staff = "feet" \feet
>
> >>
>
> }
>
> Many will recognize this as a modification of the "organ template" in
> section 3.4.3 of the Learning Manual.  i put the entire system in a
> GrandStaff because i found it the only way to connect an arpeggio
> across all three staves.

Huh?

upper = c''4\arpeggio
lower = c'4\arpeggio
feet = { \clef bass c4\arpeggio }

\score {
  \new Score \with { \consists Span_arpeggio_engraver
 connectArpeggios = ##t }
  {
<<
  \new PianoStaff
  <<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>
  
  \new Staff = "feet" \feet
>>
  }
}

> GrandStaff.SystemStartBrace.collapse-height = #10, the SystemStartBrace never
> changes size, still spanning over all three staves.
>
> The last option has led to some behaviour that i just don't understand.  i can
> set the collapse-height number to as large as 21, and the brace remains.  If i
> set the number to 22, the brace disappears.

More accurately, it collapses.

> Given that the total number of staff lines is 15, i don't see how that
> is conistent with this statement: % Must be lower than the actual
> number of staff lines.

How about "must be lower than the actual total height measured in staff
lines"?

> The quote came from the section of the Snippets manual on how to
> display a bracket with only one staff in a system.  Can i assume that
> the collapse-height property only works with one staff in a system, as
> per the snippet?

No.

> One more thing.  i nested all brackets and braces, defining the "feet" staff 
> as
> a single staff in a system (as per the snippet mentioned above), attempting to
> get everything to print.  Only the brace for the GrandStaff and the bracket 
> for
> the "feet" staff printed.  The brace for the PianoStaff did not print.  In 
> fact,
> in my setup, it never prints--ever.  i even changed PianoStaff to StaffGroup,
> specifying a bracket instead of a brace, and still the bracket wouldn't print.
>  It appears to be ignored in the nesting procedure.

If you set it after the staff is created, it is too late.  So try using
\new PianoStaff \with { ... }
for setting such properties.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: SystemStartBracket/Brace

[Thomas Morley]

2014-06-09 15:39 GMT+02:00 b...@wolfcomposer.com :
> Hello, All--
>
> To start, i'm using LilyPond 2.18.2.  To keep this short, here is how i've
> set up my score:
>
> \score {
>
>   \new GrandStaff
> <<
> \set GrandStaff.connectArpeggios = ##t
>
>\new PianoStaff
>\set PianoStaff.connectArpeggios = ##t
>  <<
> \new Staff = "upper" \upper
> \new Staff = "lower" \lower
>  >>
>
>\new Staff = "feet" \feet
>
> >>
>
> }
>
> Many will recognize this as a modification of the "organ template" in
> section 3.4.3 of the Learning Manual.  i put the entire system in a
> GrandStaff because i found it the only way to connect an arpeggio across all
> three staves.
>
> But getting to the point:  i would like the SystemStartBrace of the
> GrandStaff to span only the top two staves.  When i remove the
> System_start_delimiter_engraver from the GrandStaff and put it in the
> PianoStaff, i get no SystemStartBrace at all.  If i try \override
> GrandStaff.SystemStartBrace.collapse-height = #10, the SystemStartBrace
> never changes size, still spanning over all three staves.
>
> The last option has led to some behaviour that i just don't understand.  i
> can set the collapse-height number to as large as 21, and the brace remains.
> If i set the number to 22, the brace disappears.  Given that the total
> number of staff lines is 15, i don't see how that is conistent with this
> statement:  % Must be lower than the actual number of staff lines.  The
> quote came from the section of the Snippets manual on how to display a
> bracket with only one staff in a system.  Can i assume that the
> collapse-height property only works with one staff in a system, as per the
> snippet?  If not, then why did the property behave as it did in my override?
> After all, both 21 and 22 are greater than 15, so the brace should have
> disappeared when i set the collapse-height property to 16.  As i said, i
> don't understand, no matter how much i read.
>
> One more thing.  i nested all brackets and braces, defining the "feet" staff
> as a single staff in a system (as per the snippet mentioned above),
> attempting to get everything to print.  Only the brace for the GrandStaff
> and the bracket for the "feet" staff printed.  The brace for the PianoStaff
> did not print.  In fact, in my setup, it never prints--ever.  i even changed
> PianoStaff to StaffGroup, specifying a bracket instead of a brace, and still
> the bracket wouldn't print.  It appears to be ignored in the nesting
> procedure.
>
> So, after about fifteen hours struggling with this, i've taken to the group.
> i apologize for the length, but i wanted to be as thorough as possible.  i
> appreciate any and all help not just solving this problem, but also
> understanding what's happening.  Thank you, much!
>
> bill
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>

Hi,

is the following what you want?

\version "2.18.0"

\score {
  <<
\new PianoStaff
  <<
  \new Staff = "upper" { c'''1\arpeggio  }
  \new Staff = "lower" { c'' 1\arpeggio  }
  >>
  \new Staff = "feet" { c'1\arpeggio }
  >>
  \layout {
\context {
  \Score
  %% Is not the default for Score -> IR
  \consists "Span_arpeggio_engraver"
  connectArpeggios = ##t
}
  }
}

HTH,
  Harm

P.S.
Please post a compilable example next time.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Lilypond-book and Default Staff Size

[James]

On 09/06/14 14:50, Br. Samuel Springuel wrote:
I'm creating a document with Lilypond book and want all the musical 
systems in the document to be the same size, but also want to be able 
to tune the size to match the document font size settings (I have to 
produce the document in both a "normal" version and a "large type" 
version).  So far, I've been placing a "staffsize=#" option on each 
snippet, but as the number of snippets is proliferating, this is 
getting cumbersome.  Is there a way to globally set the staff size for 
all lilypond snippets in a document?

http://lilypond.org/doc/v2.19/Documentation/usage/music-fragment-options

?

James

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: SystemStartBracket/Brace

[b...@wolfcomposer.com]

Hi, Thomas--


>  is the following what you want?
> 
>  \version "2.18.0"
> 
>  \score {
><<
>  \new PianoStaff
><<
>\new Staff = "upper" { c'''1\arpeggio  }
>\new Staff = "lower" { c'' 1\arpeggio  }
>\new Staff = "feet" { c'1\arpeggio }
>\layout {
>  \context {
>\Score
>%% Is not the default for Score -> IR
>\consists "Span_arpeggio_engraver"
>connectArpeggios = ##t
>  }
>}
>  }
> 



Yes it is!  Thank you, very much!  Regarding the comment in your code, i regret
that i did not read slowly or deeply enough in the IR and stand gratefully
corrected.  My apologies, also.  i should have replaced my variables with actual
notes.

Thank you, again!
bill___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Changing default font size

[tisimst]

Yeah! Didn't you hear?... next week?... Oh bother.

Just kidding.

Sorry. Confession: I don't really have ANY idea when 2.20 will be released.
I did hear some talk about it, which is why I intentionally used the word
"relatively". 

In any case, I do think this feature should be included in the next release.

-Abraham



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Changing-default-font-size-tp163069p163129.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: SystemStartBracket/Brace

[David Kastrup]

"b...@wolfcomposer.com"  writes:

> Hello, All--
>
> To start, i'm using LilyPond 2.18.2.  To keep this short, here is how i've set
> up my score:
>
> \score {
>
>   \new GrandStaff
> <<
> \set GrandStaff.connectArpeggios = ##t
>
>\new PianoStaff
>\set PianoStaff.connectArpeggios = ##t
>  <<
> \new Staff = "upper" \upper
> \new Staff = "lower" \lower
>  >>
>
>\new Staff = "feet" \feet
>
> >>
>
> }
>
> Many will recognize this as a modification of the "organ template" in
> section 3.4.3 of the Learning Manual.  i put the entire system in a
> GrandStaff because i found it the only way to connect an arpeggio
> across all three staves.

Huh?

upper = c''4\arpeggio
lower = c'4\arpeggio
feet = { \clef bass c4\arpeggio }

\score {
  \new Score \with { \consists Span_arpeggio_engraver
 connectArpeggios = ##t }
  {
<<
  \new PianoStaff
  <<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>
  
  \new Staff = "feet" \feet
>>
  }
}

> GrandStaff.SystemStartBrace.collapse-height = #10, the SystemStartBrace never
> changes size, still spanning over all three staves.
>
> The last option has led to some behaviour that i just don't understand.  i can
> set the collapse-height number to as large as 21, and the brace remains.  If i
> set the number to 22, the brace disappears.

More accurately, it collapses.

> Given that the total number of staff lines is 15, i don't see how that
> is conistent with this statement: % Must be lower than the actual
> number of staff lines.

How about "must be lower than the actual total height measured in staff
lines"?

> The quote came from the section of the Snippets manual on how to
> display a bracket with only one staff in a system.  Can i assume that
> the collapse-height property only works with one staff in a system, as
> per the snippet?

No.

> One more thing.  i nested all brackets and braces, defining the "feet" staff 
> as
> a single staff in a system (as per the snippet mentioned above), attempting to
> get everything to print.  Only the brace for the GrandStaff and the bracket 
> for
> the "feet" staff printed.  The brace for the PianoStaff did not print.  In 
> fact,
> in my setup, it never prints--ever.  i even changed PianoStaff to StaffGroup,
> specifying a bracket instead of a brace, and still the bracket wouldn't print.
>  It appears to be ignored in the nesting procedure.

If you set it after the staff is created, it is too late.  So try using
\new PianoStaff \with { ... }
for setting such properties.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

How to separate these voices??

[steve]

  Howdy!

 How do I get the bass quarter notes to separate from
 the middle 8ths? They are fused as 8ths, and

\override NoteColumn.force-hshift = #1

 shifts both the middle and bass voices?


\version "2.18.0"

 voiceone = \relative c' {
<<
{ e2. | }
  \\
{ gis,8[ b] gis[ b] gis[ b] | }
>>
 }

 voicetwo = \relative c {
< e, e' >4 dis' cis |
 }


guitar = << \voiceone \\ \voicetwo >>


 thanx - steve



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: SystemStartBracket/Brace

[David Kastrup]

Please *never* take the mailing list off the cc without announcement.
If people notice this after the fact, it means that they have to search
in their archives for the message and resend a copy to the mailing
list.  In this case, I resent the wrong message again.

It's a lot of hassle for the person involved, and it also means that you
think you, but not the mailing list, is entitled to further responses.

"b...@wolfcomposer.com"  writes:

> Thank you for your help and solution.  Thomas Morley's was a little
> different, and each worked perfectly.  This alone is one of my
> favorite features of Lilypond.  i also see some errors i committed in
> frustration and stand gratefully corrected on all accounts.  i still
> have a few comments and one remaining question:
>
>> The last option has led to some behaviour that i just don't understand.  i
>> canset the collapse-height number to as large as 21, and the brace remains.
>>  If i
>>  set the number to 22, the brace disappears.
>> 
>>> More accurately, it collapses.
>
> Understood!
>
>
>> Given that the total number of staff lines is 15, i don't see how that
>>  is conistent with this statement: % Must be lower than the actual
>>  number of staff lines.
>> 
>>> How about "must be lower than the actual total height measured in staff
>>> lines"?
>
>
>> The quote came from the section of the Snippets manual on how to
>>  display a bracket with only one staff in a system.  Can i assume that
>>  the collapse-height property only works with one staff in a system, as
>>  per the snippet?
>> 
>>> No.
>
> OK, and that's good to know--on both previous comments.  Still, why should the
> size of the brace have remained the same no what number i used from 0 to 21?

It either collapses (which means it disappears) or not.  If it doesn't
collapse, it spans all of the enclosing staves.

collapse-height is the most singularly uselessly defined property
I encountered so far.  It's main use is to avoid braces when one of two
grouped voices is removed because of the remove-first property, but its
definition causes, for example, bass tablature clefs (4 strings) and
guitar tablature clefs (6 strings) to look differently.

The unit should likely be "staves" for some reasonable definition of
"staff" rather than "height in xxx units".

But as long as that is its definition...

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to separate these voices??

[David Kastrup]

st...@linuxsuite.org writes:

>   Howdy!
>
>  How do I get the bass quarter notes to separate from
>  the middle 8ths? They are fused as 8ths, and
>
> \override NoteColumn.force-hshift = #1
>
>  shifts both the middle and bass voices?
>
>
> \version "2.18.0"
>
>  voiceone = \relative c' {
> <<
> { e2. | }
>   \\
> { gis,8[ b] gis[ b] gis[ b] | }
> >>
>  }
>
>  voicetwo = \relative c {
> < e, e' >4 dis' cis |
>  }
>
>
> guitar = << \voiceone \\ \voicetwo >>

This program produces no output.  Please include working minimal
examples demonstrating your problem with queries like that.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to separate these voices??

[Shane Brandes]

Try putting everything in the same voice with this sort of construct
{<<{}\\{}\\{}>>}

regards,
Shane

On Mon, Jun 9, 2014 at 11:55 AM,   wrote:
>
>   Howdy!
>
>  How do I get the bass quarter notes to separate from
>  the middle 8ths? They are fused as 8ths, and
>
> \override NoteColumn.force-hshift = #1
>
>  shifts both the middle and bass voices?
>
>
> \version "2.18.0"
>
>  voiceone = \relative c' {
> <<
> { e2. | }
>   \\
> { gis,8[ b] gis[ b] gis[ b] | }
> >>
>  }
>
>  voicetwo = \relative c {
> < e, e' >4 dis' cis |
>  }
>
>
> guitar = << \voiceone \\ \voicetwo >>
>
>
>  thanx - steve
>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Lilypond-book and Default Staff Size

[Br. Samuel Springuel]

Those options (specifically staffsize) are what I'm using right now, but 
they have to be set for each Lilypond command separately.  I'm wondering 
if there is a way to set them once and have said value apply to the 
whole document (which contains multiple Lilypond commands).


✝
Br. Samuel, OSB
(R. Padraic Springuel)

PAX ☧ ΧΡΙΣΤΟΣ

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to separate these voices??

[steve]

>
> This program produces no output.  Please include working minimal
> examples demonstrating your problem with queries like that.
>

 Ooops sorry.


\version "2.18.0"

 voiceone = \relative c' {
<<
{ e2. | }
  \\
{ gis,8[ b] gis[ b] gis[ b] | }
>>
 }

 voicetwo = \relative c {
< e, e' >4 dis' cis |
 }

 guitar = << { \voiceone } \\ { \voicetwo } >>

global = {
  \time 3/4
  \key e \major
  \clef "G_8"
}


\score {
\new Staff  { << \global \guitar >> }

\layout { }
}

 -steve


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to separate these voices??

[steve]

> Try putting everything in the same voice with this sort of construct
> {<<{}\\{}\\{}>>}
>

Doesn't change anything...

-steve


> regards,
> Shane
>
> On Mon, Jun 9, 2014 at 11:55 AM,   wrote:
>>
>>   Howdy!
>>
>>  How do I get the bass quarter notes to separate from
>>  the middle 8ths? They are fused as 8ths, and
>>
>> \override NoteColumn.force-hshift = #1
>>
>>  shifts both the middle and bass voices?
>>
>>
>> \version "2.18.0"
>>
>>  voiceone = \relative c' {
>> <<
>> { e2. | }
>>   \\
>> { gis,8[ b] gis[ b] gis[ b] | }
>> >>
>>  }
>>
>>  voicetwo = \relative c {
>> < e, e' >4 dis' cis |
>>  }
>>
>>
>> guitar = << \voiceone \\ \voicetwo >>
>>
>>
>>  thanx - steve
>>
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to separate these voices??

[Shane Brandes]

make sure you delete the unneeded voice from the score declaration.
 guitar = << { \voiceone }>>

On Mon, Jun 9, 2014 at 1:21 PM,   wrote:
>> Try putting everything in the same voice with this sort of construct
>> {<<{}\\{}\\{}>>}
>>
>
> Doesn't change anything...
>
> -steve
>
>
>> regards,
>> Shane
>>
>> On Mon, Jun 9, 2014 at 11:55 AM,   wrote:
>>>
>>>   Howdy!
>>>
>>>  How do I get the bass quarter notes to separate from
>>>  the middle 8ths? They are fused as 8ths, and
>>>
>>> \override NoteColumn.force-hshift = #1
>>>
>>>  shifts both the middle and bass voices?
>>>
>>>
>>> \version "2.18.0"
>>>
>>>  voiceone = \relative c' {
>>> <<
>>> { e2. | }
>>>   \\
>>> { gis,8[ b] gis[ b] gis[ b] | }
>>> >>
>>>  }
>>>
>>>  voicetwo = \relative c {
>>> < e, e' >4 dis' cis |
>>>  }
>>>
>>>
>>> guitar = << \voiceone \\ \voicetwo >>
>>>
>>>
>>>  thanx - steve
>>>
>>>
>>>
>>> ___
>>> lilypond-user mailing list
>>> lilypond-user@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to separate these voices??

[David Kastrup]

st...@linuxsuite.org writes:

>  Ooops sorry.
>
>
> \version "2.18.0"
>
>  voiceone = \relative c' {
> <<
> { e2. | }
>   \\
> { gis,8[ b] gis[ b] gis[ b] | }
> >>
>  }
>
>  voicetwo = \relative c {
> < e, e' >4 dis' cis |
>  }
>
>  guitar = << { \voiceone } \\ { \voicetwo } >>
>
> global = {
>   \time 3/4
>   \key e \major
>   \clef "G_8"
> }
>
>
> \score {
>   \new Staff  { << \global \guitar >> }
>
>   \layout { }
> }

Nesting several \\ at different levels does not work.  This is one case
where you are better off using explicit voices anyway since you can then
finetune the \voiceXxx things using for shifting voices apart in the
case of collision.  That gives you

\version "2.18.0"

 voiceone = \relative c' <<
   \new Voice {
 \voiceOne
 e2. | }
   \new Voice {
 \voiceThree
 gis,8[ b] gis[ b] gis[ b] | }
>>

voicetwo = \relative c
\new Voice {
  \voiceTwo
< e, e' >4 dis' cis |
}

guitar = << \voiceone \voicetwo >>

global = {
  \time 3/4
  \key e \major
  \clef "G_8"
}


\score {
  \new Staff  { << \global \guitar >> }
  
  \layout { }
}

I'm not overly convinced in how it is typeset, but then I don't have a
better suggestion after juggling with different presets.



-- 
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to separate these voices??

[Thomas Morley]

2014-06-09 19:41 GMT+02:00 David Kastrup :
> st...@linuxsuite.org writes:
>
>>  Ooops sorry.
>>
>>
>> \version "2.18.0"
>>
>>  voiceone = \relative c' {
>> <<
>> { e2. | }
>>   \\
>> { gis,8[ b] gis[ b] gis[ b] | }
>> >>
>>  }
>>
>>  voicetwo = \relative c {
>> < e, e' >4 dis' cis |
>>  }
>>
>>  guitar = << { \voiceone } \\ { \voicetwo } >>
>>
>> global = {
>>   \time 3/4
>>   \key e \major
>>   \clef "G_8"
>> }
>>
>>
>> \score {
>>   \new Staff  { << \global \guitar >> }
>>
>>   \layout { }
>> }
>
> Nesting several \\ at different levels does not work.  This is one case
> where you are better off using explicit voices anyway since you can then
> finetune the \voiceXxx things using for shifting voices apart in the
> case of collision.  That gives you
>
>
>
> I'm not overly convinced in how it is typeset, but then I don't have a
> better suggestion after juggling with different presets.
>
>
>
>
> --
> David Kastrup


Here my code as well.
Second example gives same output as David's
Third example shows strange behaviour of the Dot. IMHO, it should flip
back to the NoteHead. There's enough space.
A bug?

\version "2.18.0"

global = {
  \time 3/4
  \key e \major
  \clef "G_8"
}

\new Staff
  <<
  \global
  \new Voice \relative c' { \voiceOne e2. }
  \new Voice
\relative c' {
  \voiceFour
  \override NoteColumn.force-hshift = #1.1
  gis8[ b] gis[ b] gis[ b]
}
  \new Voice \relative c' { \voiceTwo < e,, e' >4 dis' cis }
  >>

\new Staff
  <<
  \global
  \new Voice \relative c' { \voiceOne e2. }
  \new Voice \relative c' { \voiceThree  gis8[ b] gis[ b] gis[ b] }
  \new Voice \relative c' { \voiceTwo < e,, e' >4 dis' cis }
  >>

\new Staff
  <<
  \mark "bug with Dots?"
  \global
  \new Voice \relative c' { \voiceOne e2. }
  \new Voice
\relative c' {
  \voiceThree
  \once \override NoteColumn.force-hshift = #1.5
  gis8[ b] gis[ b] gis[ b]
}
  \new Voice \relative c' { \voiceTwo < e,, e' >4 dis' cis }
  >>

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to separate these voices??

[tisimst]

Steve,

Ok, here's what I got your snippet to do:


 

I'm not sure how my solution plays into the rest of the piece you are
working on, but this works pretty well for me:

guitar = \relative c' { 
  << 
  { e2. }   % voiceOne
  \\ 
  {}   % voiceTwo
  \\
  { 4 dis' cis }  % voiceThree
  \\
  { gis'8[ b] gis[ b] gis[ b] }  % voiceFour
  >> 
} 

global = { 
  \time 3/4 
  \key e \major 
  \clef "G_8" 
} 

\score { 
  \new Staff  { 
\global 
\guitar
  } 
  \layout {} 
}

which results in this:


 

Personally, I don't quite like how far that pushed out the e-chord in
voiceThree because of the collision with the stem and the dot in voiceOne,
so we can force the e-chord to be a little closer to look like the 2nd and
3rd quarter notes, if you prefer, by adding an override before the e-chord:

guitar = \relative c' { 
  << 
  { e2. }   % voiceOne
  \\ 
  {}   % voiceTwo
  \\
  { /*\once \override NoteColumn.force-hshift = #0.3*/ 4 dis' cis } 
% voiceThree
  \\
  { gis'8[ b] gis[ b] gis[ b] }  % voiceFour
  >> 
}

which looks like this:


 

I can't say that this would be the perfect solution, but I think adding the
override makes the timing more obvious for the performer. Hope that helps!

-Abraham



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/How-to-separate-these-voices-tp163131p163143.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Notes engraved in weird order

[tisimst]

Mark,

Not sure if it's an artifact of using an older version, but using the
current 2.18.2 gives me consistent ordering regardless of the number of
times:

Drawing systems...
Notes: (-10 9 -12 11 -3 -5 -7 2 4 0 7 5) 
Notes: (-10 9 -12 11 -3 -5 -7 2 4 0 7 5)

This doesn't mean that it's the _right_ order, but at least it's consistent.

-Abraham



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Notes-engraved-in-weird-order-tp163091p163144.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Notes engraved in weird order

[David Kastrup]

tisimst  writes:

> Mark,
>
> Not sure if it's an artifact of using an older version, but using the
> current 2.18.2 gives me consistent ordering regardless of the number of
> times:
>
> Drawing systems...
> Notes: (-10 9 -12 11 -3 -5 -7 2 4 0 7 5) 
> Notes: (-10 9 -12 11 -3 -5 -7 2 4 0 7 5)
>
> This doesn't mean that it's the _right_ order, but at least it's consistent.

I've changed a few sorting routines that figured out duplicates by first
sorting according to memory address and then comparing and removing
adjacent elements, keeping the resulting order.

Since memory allocation is basically unpredictable, I made sure at some
cost that instead the _original_ order was retained.  That way the
results may still be arbitrary but at least consistent.

I suspect that some of these changes will be responsible for your
observations.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to separate these voices??

[steve]

 Thanks for the hints. I've looked at them and have come up with the
following which looks a lot like the original. F. Tarrega's transcription of
Beethoven minuet ( start of the trio ). Not sure if its the best solution
though...

http://imslp.org/wiki/6_Minuets,_WoO_10_%28Beethoven,_Ludwig_van%29

\version "2.18.0"

 voiceone = \relative c' {
   <<
   \new Voice { \voiceOne e2. | }
   \new Voice { \voiceThree \stemDown \override NoteColumn.force-hshift =
#1.1
gis, 8[ b] gis[ b] gis[ b] | }
   >>
 }

 voicetwo = \relative c {
   < e, e' >4 dis' cis |
 }

 guitar = << { \voiceone } \\ { \voicetwo } >>

global = {
  \time 3/4
  \key e \major
  \clef "G_8"
}

 \score {
\new Staff  { << \global \guitar >> }
\layout { }
 }


  thanx - steve


> 2014-06-09 19:41 GMT+02:00 David Kastrup :
>> st...@linuxsuite.org writes:
>>
>>>  Ooops sorry.
>>>
>>>
>>> \version "2.18.0"
>>>
>>>  voiceone = \relative c' {
>>> <<
>>> { e2. | }
>>>   \\
>>> { gis,8[ b] gis[ b] gis[ b] | }
>>> >>
>>>  }
>>>
>>>  voicetwo = \relative c {
>>> < e, e' >4 dis' cis |
>>>  }
>>>
>>>  guitar = << { \voiceone } \\ { \voicetwo } >>
>>>
>>> global = {
>>>   \time 3/4
>>>   \key e \major
>>>   \clef "G_8"
>>> }
>>>
>>>
>>> \score {
>>>   \new Staff  { << \global \guitar >> }
>>>
>>>   \layout { }
>>> }
>>
>> Nesting several \\ at different levels does not work.  This is one case
>> where you are better off using explicit voices anyway since you can then
>> finetune the \voiceXxx things using for shifting voices apart in the
>> case of collision.  That gives you
>>
>>
>>
>> I'm not overly convinced in how it is typeset, but then I don't have a
>> better suggestion after juggling with different presets.
>>
>>
>>
>>
>> --
>> David Kastrup
>
>
> Here my code as well.
> Second example gives same output as David's
> Third example shows strange behaviour of the Dot. IMHO, it should flip
> back to the NoteHead. There's enough space.
> A bug?
>
> \version "2.18.0"
>
> global = {
>   \time 3/4
>   \key e \major
>   \clef "G_8"
> }
>
> \new Staff
>   <<
>   \global
>   \new Voice \relative c' { \voiceOne e2. }
>   \new Voice
> \relative c' {
>   \voiceFour
>   \override NoteColumn.force-hshift = #1.1
>   gis8[ b] gis[ b] gis[ b]
> }
>   \new Voice \relative c' { \voiceTwo < e,, e' >4 dis' cis }
>   >>
>
> \new Staff
>   <<
>   \global
>   \new Voice \relative c' { \voiceOne e2. }
>   \new Voice \relative c' { \voiceThree  gis8[ b] gis[ b] gis[ b] }
>   \new Voice \relative c' { \voiceTwo < e,, e' >4 dis' cis }
>   >>
>
> \new Staff
>   <<
>   \mark "bug with Dots?"
>   \global
>   \new Voice \relative c' { \voiceOne e2. }
>   \new Voice
> \relative c' {
>   \voiceThree
>   \once \override NoteColumn.force-hshift = #1.5
>   gis8[ b] gis[ b] gis[ b]
> }
>   \new Voice \relative c' { \voiceTwo < e,, e' >4 dis' cis }
>   >>
>
> Cheers,
>   Harm
>



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: triangle noteheads

[Nick Didkovsky]

Dear Lilypond users,

A brief followup question regarding this technique of assigning noteheads.

I am using the notehead glyph technique to set noteheads, but have run 
into trouble trying to change noteheads within a chord.
Continuing with the cowbell example code that Fredrik originally sent me 
below, the following  does not set the notehead of  'g' in this chord to 
a triangle...

< c  e \cowbell  g >
...all three notes show regular noteheads.

If someone can illuminate how to set noteheads within a chord, I'd 
appreciate it!


Best regards,
Nick Didkovsky

On 5/15/14 6:55 PM, Fredrik Wallberg wrote:

Hi Nick,

you'll find more noteheads here: 
http://www.lilypond.org/doc/v2.19/Documentation/notation/the-feta-font#shape_002dnote-notehead-glyphs.


This snippet by Victor Adan shows how to use them in a score: 
http://lsr.di.unimi.it/LSR/Snippet?id=475.


An example:

cowbell = {
\once \override NoteHead.stencil = #ly:text-interface::print
\once \override NoteHead.text = #(markup #:musicglyph 
"noteheads.d2doThin")

}

{
\cowbell
c''4
}

/ Fredrik



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

ANN: Frescobaldi 2.0.16 released

[Wilbert Berendsen]

Hi all,

Frescobaldi 2.0.16 has been released. Frescobaldi is a text editor 
dedicated to entering LilyPond music.


Download:
http://www.frescobaldi.org/download

Main new features:
  - preference to automatically strip trailing whitespace on save 
(issue #274)
  - in Tools -> Rhythm: new command to remove duration scalings that 
contain a fraction value (the action was already available for some 
time, but it wasn't in the menu)
  - new option to copy only the styled HTML contents to the clipboard 
wrapped in a pre tag, not a full HTML document


Improvements:
  - jumps in the Document Outline also allow navigating back
  - autocompile does only happen when a document has toplevel markup or 
music

  - LilyPond instance can be selected in convert-ly dialog (wish #311)
  - Score Wizard: In the midi section the \tempo x=y syntax is now used 
when LilyPond version >= 2.16 is used (issue #337)

  - Score Wizard: new brass instruments contributed by Ryan Michael McClure
  - some missing commands and functions were added to highlighting and
autocompletion
  - the Document Fonts snippet doesn't require setting the staffize anymore
  - View -> Folding -> Fold all now folds all subregions as well, making
gradual unfolding easier (wish #394)

Main bugfixes:
  - fix sticky document setting lost on reload (issue #409)
  - fix html export and copy not using the correct color scheme
  - fix AttributeError in handle_lyricmode while typing \lyricmode
  - fix LilyPond version chooser not defaulting to the default LilyPond 
version

  - fix indenter aligning on comment
  - fix AttributeError: QStackedWidget object has no attribute 
cursorForPosition

on doubleclick in the text, reported by an Apple user
  - fix AttributeError: 'ScoreWizard' object has no attribute 
'showInsertDialog'

reported by an Apple user

Full changes:
https://github.com/wbsoft/frescobaldi/blob/master/ChangeLog

Enjoy!

--
Wilbert Berendsen
http://www.wilbertberendsen.nl/


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: SystemStartBracket/Brace

[b...@wolfcomposer.com]

>  Please *never* take the mailing list off the cc without announcement.
>  If people notice this after the fact, it means that they have to search
>  in their archives for the message and resend a copy to the mailing
>  list.  In this case, I resent the wrong message again.
> 
>  It's a lot of hassle for the person involved, and it also means that you
>  think you, but not the mailing list, is entitled to further responses.
> 


i see my mistake.  Thanks for pointing it out.  From here on out, i'll always
use the "Reply All" button.  i had never intended to remove the group from the
cc.



> 
>  It either collapses (which means it disappears) or not.  If it doesn't
>  collapse, it spans all of the enclosing staves.
> 
>  collapse-height is the most singularly uselessly defined property
>  I encountered so far.  It's main use is to avoid braces when one of two
>  grouped voices is removed because of the remove-first property, but its
>  definition causes, for example, bass tablature clefs (4 strings) and
>  guitar tablature clefs (6 strings) to look differently.
> 
>  The unit should likely be "staves" for some reasonable definition of
>  "staff" rather than "height in xxx units".
> 
>  But as long as that is its definition...
> 


NOW i understand.  Thank you, again.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

One of these things just isn't the same

[Daniel Rosen]

\version "2.19.7"

{ f4-> fis-> fes-> f!-> }

Why is the accent on the final note (the one with the natural sign before it) 
so much farther away from its parent NoteHead than the others? Is this a known 
issue?

DR


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: triangle noteheads

[Thomas Morley]

2014-06-09 21:01 GMT+02:00 Nick Didkovsky :
> Dear Lilypond users,
>
> A brief followup question regarding this technique of assigning noteheads.
>
> I am using the notehead glyph technique to set noteheads, but have run into
> trouble trying to change noteheads within a chord.
> Continuing with the cowbell example code that Fredrik originally sent me
> below, the following  does not set the notehead of  'g' in this chord to a
> triangle...
> < c  e \cowbell  g >
> ...all three notes show regular noteheads.
>
> If someone can illuminate how to set noteheads within a chord, I'd
> appreciate it!
>
> Best regards,
> Nick Didkovsky
>
>
> On 5/15/14 6:55 PM, Fredrik Wallberg wrote:
>>
>> Hi Nick,
>>
>> you'll find more noteheads here:
>> http://www.lilypond.org/doc/v2.19/Documentation/notation/the-feta-font#shape_002dnote-notehead-glyphs.
>>
>> This snippet by Victor Adan shows how to use them in a score:
>> http://lsr.di.unimi.it/LSR/Snippet?id=475.
>>
>> An example:
>>
>> cowbell = {
>> \once \override NoteHead.stencil = #ly:text-interface::print
>> \once \override NoteHead.text = #(markup #:musicglyph
>> "noteheads.d2doThin")
>> }
>>
>> {
>> \cowbell
>> c''4
>> }
>>
>> / Fredrik


Basically you need a tweak not an override to affect single NoteHeads
in a chord.

Though why not have all in one?

\version "2.18.0"

#(define (new-head type)
  (lambda (grob)
(let* ((duration (ly:grob-property grob 'duration-log))
   (head (format #f "noteheads.d~a~a" duration type))
   (stil (ly:font-get-glyph
   (ly:grob-default-font grob)
   head)))
  (if (ly:stencil-empty? stil)
  (begin
(ly:warning "Unknown NoteHead: ~a, ignoring." head)
(ly:note-head::print grob))
  stil

myHead =
#(define-music-function (parser location music)(ly:music?)
  (if (music-is-of-type? music 'event-chord)
  #{
\override NoteHead.stencil = #(new-head "doThin")
#music
  #}
  #{
\tweak NoteHead.stencil #(new-head "doThin")
#music
  #}))


\relative c' {

  \myHead
  c2

  \myHead
  4

  <
   c
   \myHead
   e
   \myHead
   \tweak duration-log #1
   g
  >4
}


HTH,
  Harm

Though, Harm's Lilypedia is closed now for every request without
version and tiny, compilable example-code.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: SystemStartBracket/Brace

[Matthew Collett]

On 10/06/2014, at 4:28 am, David Kastrup  wrote:

> Please *never* take the mailing list off the cc without announcement.

Please *never* blame ordinary list users for the idiosyncratic behaviour of the 
lilypond-user mailing list.  

This is the only list I have ever been on that does not reply to the list by 
default.  So as has been pointed out on a number of previous occasions, it is 
_not_ a matter of someone deliberately 'tak[ing] the mailing list off the cc', 
but rather one of accidentally forgetting to add it (or for new users, being 
unaware of the need to do so).

Best wishes,
Matthew


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: SystemStartBracket/Brace

[James Harkins]

Matthew Collett  ihug.co.nz> writes:

> 
> On 10/06/2014, at 4:28 am, David Kastrup  gnu.org> wrote:
> 
> > Please *never* take the mailing list off the cc without announcement.
> 
> Please *never* blame ordinary list users for the idiosyncratic behaviour of 
the lilypond-user mailing
> list.  
> 
> This is the only list I have ever been on that does not reply to the list by 
default.  So as has been pointed out on
> a number of previous occasions, it is _not_ a matter of someone deliberately 
'tak[ing] the mailing list
> off the cc', but rather one of accidentally forgetting to add it (or for new 
users, being unaware of the need
> to do so).

Here we go again...

Apparently, this list's behavior is correct according official standards, and 
every other list in the world does it wrong merely for the sake of user 
convenience. List members who don't like it are reminded that humans should 
now adapt to the needs of technology, instead of the other way around.

#FlameSuitOn

hjh


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Pagination

[Charles Berger]

Bonjour Jacques,

 

je voulais simplifier, en ne mettant qu'une partie de l'oeuvre.

Voici la 1ere partie de l'ensemble; je me suis arrêté des que j'ai aperçu
l'erreur.

 

\version "2.19.7"

\language "italiano"

 

\header {

  dedication = "."

  title = "."

  subtitle = "."

  subsubtitle = "."

  instrument = "."

  composer = "."

  arranger = "."

  poet = "."

  meter = "."

  piece = "."

  opus = "."

  copyright = "."

  tagline = "."

}

 

\layout {

  short-indent = 12\mm

  \context {

\Voice

\consists "Melody_engraver"

\override Stem #'neutral-direction = #'()

  }

}

 

global = {

  \key fad \phrygian

  \time 4/4

  \tempo 4=100

}

 

% Première voix !

tenorOne = \relative do'

{

  \global

  \override NoteHead.color = #cyan

  % En avant la musique !

  re,2\f fad4 la

  re2( re8) re re mi

  fad2. re8 re

  re2 re4 dod

  re16. mi16 fad4 r4. re8. re8 %??? Probleme

  re4 re16. re16 re4 dod

  mi16.( fad16) sol2 r

%??? Problème j'ai réécrit cette récurence et la çà bloque

  r4 \times 2/3 mi8\( fad sol\) sol4 r4

  r8 \times 3/3 mi8\( fad sol\) sol4 \times 3/3 mi16\( mi mi\)

  fad4 \times 3/3 mi8\( mi mi\) re4 mi

  dod4. dod8 re4 re

  re2 si

  re1

%??? Problème

%??? Problème

  r4 \times 2/3 mi8\( fad sol\) sol4 r4

  r8 \times 3/3 mi8\( fad sol\) sol4 \times 3/3 mi16\( mi mi\)

  fad4 \times 3/3 mi8\( mi mi\) re4 mi

  dod4. dod8 re4 re

  re2 si

  re1

%??? Problème

%??? Problème

  r4 \times 2/3 mi8\( fad sol\) sol4 r4

  r8 \times 3/3 mi8\( fad sol\) sol4 \times 3/3 mi16\( mi mi\)

  fad4 \times 3/3 mi8\( mi mi\) re4 mi

  dod4. dod8 re4 re

  re2 si

  re1

%??? Problème

  

 

}

 

% Seconde voix !

tenorTwo = \relative do'

{

  \global

\override NoteHead.color = #blue

  % En avant la musique !

  re,2\f fad4 la

  re2( re8) re re dod

  re2. re8 re

  re4( sol) fad mi

  fad16 mi re2 r4 re16. re16

  re2 sol16. sol16 fad4 mi

  fad16.( mi16) re4 r \times 2/3 fad16\( mi re\)

  

}

 

% Troisième voix !

bassOne = \relative do''

{

  \global

  \override NoteHead.color = #green

  \clef treble

  % En avant la musique ! 

  re2\f fad4 la

  re2( mi8) mi dod la

  la2. fad8 fad

  fad4( si) la sol

  la16 sol fad2 r4 fad16. fad16

  fad2 si16. si16 sol4 fad

  si16.( sol16) fad4 r2

  

  

}

 

% Quatième voix !

bassTwo = \relative do''

{

  \global

  \override NoteHead.color = #red

  \clef treble

  % En avant la musique !

  re2\f fad4 la

  re2( mi8) mi mi la,

  re,2. re8 re

  re2 re4 r

 

}

 

tenorOneVerseOne = \lyricmode

{

  \set stanza = "1."

  % Ajouter ici des paroles.  

}

 

tenorTwoVerseOne = \lyricmode

{

  \set stanza = "1."

  % Ajouter ici des paroles.

}

 

bassOneVerseOne = \lyricmode

{

  \set stanza = "1."

  % Ajouter ici des paroles.

}

 

bassTwoVerseOne = \lyricmode

{

  \set stanza = "1."

  % Ajouter ici des paroles.

}

 

 

tenorOneVerseTwo = \lyricmode

{

  \set stanza = "2."

  % Ajouter ici des paroles.  

}

 

tenorTwoVerseTwo = \lyricmode {

  \set stanza = "2."

  % Ajouter ici des paroles.

}

 

bassOneVerseTwo = \lyricmode

{

  \set stanza = "2."

  % Ajouter ici des paroles. 

}

 

bassTwoVerseTwo = \lyricmode

{

  \set stanza = "2."

  % Ajouter ici des paroles.

}

 

 

rehearsalMidi = #

(define-music-function

 (parser location name midiInstrument lyrics) (string? string? ly:music?)

 #{

   \unfoldRepeats

   <<

 \new Staff = "tenor1" \new Voice = "tenor1" { \tenorOne }

 \new Staff = "tenor2" \new Voice = "tenor2" { \tenorTwo }

 \new Staff = "bass1" \new Voice = "bass1" { \bassOne }

 \new Staff = "bass2" \new Voice = "bass2" { \bassTwo }

 

 \context Staff = $name {

   \set Score.midiMinimumVolume = #0.5

   \set Score.midiMaximumVolume = #0.5

   \set Score.tempoWholesPerMinute = #(ly:make-moment 60 4)

   \set Staff.midiMinimumVolume = #0.8

   \set Staff.midiMaximumVolume = #1.0

   \set Staff.midiInstrument = $midiInstrument

 }

 \new Lyrics \with

{

   alignBelowContext = $name

}

 \lyricsto $name $lyrics

   >>

 

 #})

 

\score

{

  \new ChoirStaff

<<

\new Staff \with {

  midiInstrument = "choir aahs"

  instrumentName = "Ténor1"

  shortInstrumentName = "Ténor1"

} { \clef "treble_8" \tenorOne }

\addlyrics { \tenorOneVerseOne }

\addlyrics { \tenorOneVerseTwo }

 

\new Staff \with {

  midiInstrument = "choir aahs"

  instrumentName = "Ténor2"

  shortInstrumentName = " Ténor2"

} { \clef "treble_8" \tenorTwo }

\addlyrics { \tenorTwoVerseOne }

\addlyrics { \tenorTwoVerseTwo }

 

\new Staff \with {

  midiInstrument = "choir aahs"

  instrumentName = "Basse1"

  shortInstrumentName = "Basse1"

} { \clef bass \bassOne }

\addlyrics { \bassOneVerseOne }

\addlyrics { \bassOneVerseTwo }

 

\

Re: Pagination

[Charles Berger]

Sorry for my english

Thank's for your answer

I try \tuplet instead of \times and it's ok

Thank you

Charles Berger



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Pagination-tp163061p163154.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Pagination

[Xavier Scheuer]

On 10 June 2014 07:15, Charles Berger  wrote:
>
> Sorry for my english
>
> Thank's for your answer
>
> I try \tuplet instead of \times and it's ok
>
> Thank you
>
> Charles Berger

FYI there is a French-speaking LilyPond user mailing list:
lilypond-user...@gnu.org (notice the "-fr"), where you can ask
questions in French.
Infos : https://lists.gnu.org/mailman/listinfo/lilypond-user-fr
Archives : http://lilypond-french-users.1298960.n2.nabble.com/

Cheers,
Xavier

-- 
Xavier Scheuer 
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user