Autobeaming overrides
I'm putting the finishing touches to the Rhythm section of the Notation Reference and would like some help. The usual override for modifying the automatic beaming rhythm specifies the ending beat of the beam: #(override-auto-beam-setting '(end * * 6 8) 4 8) It is also possible to specify the starting beat of the beam, but I cannot see when it is necessary to do this. Are there any situations when the starting beat -must- be specified, or is this just an alternative? Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Autobeaming overrides
I don't have an answer to your question but I do have a request regarding this section of the manual. In section 1.2.4 Beams/Setting automatic beam behavior, there is the statement: Note that the default auto-beaming rules are specified in ‘scm/auto-beam.scm’, so you can revert rules that you did not explicitly create. I've long felt that this wording should be more explicit. Maybe something like: Note that the default auto-beaming rules are specified in ‘scm/auto-beam.scm’. When constructing auto-beaming rules of your own it is necessary to specifically revert any default rule that is contrary to your new rule. Maybe you've got a better phrasing for it. -David Trevor Daniels wrote: I'm putting the finishing touches to the Rhythm section of the Notation Reference and would like some help. The usual override for modifying the automatic beaming rhythm specifies the ending beat of the beam: #(override-auto-beam-setting '(end * * 6 8) 4 8) It is also possible to specify the starting beat of the beam, but I cannot see when it is necessary to do this. Are there any situations when the starting beat -must- be specified, or is this just an alternative? Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Autobeaming overrides
Thanks David I think the words you quote are from the 2.10 docs. The wording in the 2.11 docs will be: "If any unexpected beam behavior occurs, check the default automatic beam settings in ‘scm/auto-beam.scm’ for possible interference, because the beam endings defined there will still apply in addition to your own. Any unwanted or conflicting default endings must be reverted for your time signature(s). "Existing auto-beam rules are removed by using" [here follows an example] Hope that's better. Trevor - Original Message - From: "David Bobroff" <[EMAIL PROTECTED]> To: "Trevor Daniels" <[EMAIL PROTECTED]> Cc: "Lilypond-User List" ; "Lily-Devel List" <[EMAIL PROTECTED]> Sent: Sunday, October 19, 2008 10:16 AM Subject: Re: Autobeaming overrides I don't have an answer to your question but I do have a request regarding this section of the manual. In section 1.2.4 Beams/Setting automatic beam behavior, there is the statement: Note that the default auto-beaming rules are specified in ‘scm/auto-beam.scm’, so you can revert rules that you did not explicitly create. I've long felt that this wording should be more explicit. Maybe something like: Note that the default auto-beaming rules are specified in ‘scm/auto-beam.scm’. When constructing auto-beaming rules of your own it is necessary to specifically revert any default rule that is contrary to your new rule. Maybe you've got a better phrasing for it. -David Trevor Daniels wrote: I'm putting the finishing touches to the Rhythm section of the Notation Reference and would like some help. The usual override for modifying the automatic beaming rhythm specifies the ending beat of the beam: #(override-auto-beam-setting '(end * * 6 8) 4 8) It is also possible to specify the starting beat of the beam, but I cannot see when it is necessary to do this. Are there any situations when the starting beat -must- be specified, or is this just an alternative? Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Autobeaming overrides
David Bobroff Sunday, October 19, 2008 11:35 AM Actually I was looking at the 2.11 docs. I even tried refreshing and it was still the same. Perhaps that's due to viewing the online docs at lilypond.org rather than from the latest source. Yes, that's the reason. The docs at http://kainhofer.com/~lilypond/Documentation/user/lilypond are more recent, and contain better wording, but the precise words I mentioned I added in response to your mail and are still in my local git repository. Trevor In any event I applaud the new wording and I thank you for your attention to that detail. -David Trevor Daniels wrote: Thanks David I think the words you quote are from the 2.10 docs. The wording in the 2.11 docs will be: "If any unexpected beam behavior occurs, check the default automatic beam settings in ‘scm/auto-beam.scm’ for possible interference, because the beam endings defined there will still apply in addition to your own. Any unwanted or conflicting default endings must be reverted for your time signature(s). "Existing auto-beam rules are removed by using" [here follows an example] Hope that's better. Trevor - Original Message - From: "David Bobroff" <[EMAIL PROTECTED]> To: "Trevor Daniels" <[EMAIL PROTECTED]> Cc: "Lilypond-User List" ; "Lily-Devel List" <[EMAIL PROTECTED]> Sent: Sunday, October 19, 2008 10:16 AM Subject: Re: Autobeaming overrides I don't have an answer to your question but I do have a request regarding this section of the manual. In section 1.2.4 Beams/Setting automatic beam behavior, there is the statement: Note that the default auto-beaming rules are specified in ‘scm/auto-beam.scm’, so you can revert rules that you did not explicitly create. I've long felt that this wording should be more explicit. Maybe something like: Note that the default auto-beaming rules are specified in ‘scm/auto-beam.scm’. When constructing auto-beaming rules of your own it is necessary to specifically revert any default rule that is contrary to your new rule. Maybe you've got a better phrasing for it. -David Trevor Daniels wrote: I'm putting the finishing touches to the Rhythm section of the Notation Reference and would like some help. The usual override for modifying the automatic beaming rhythm specifies the ending beat of the beam: #(override-auto-beam-setting '(end * * 6 8) 4 8) It is also possible to specify the starting beat of the beam, but I cannot see when it is necessary to do this. Are there any situations when the starting beat -must- be specified, or is this just an alternative? Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Autobeaming overrides
Actually I was looking at the 2.11 docs. I even tried refreshing and it was still the same. Perhaps that's due to viewing the online docs at lilypond.org rather than from the latest source. In any event I applaud the new wording and I thank you for your attention to that detail. -David Trevor Daniels wrote: Thanks David I think the words you quote are from the 2.10 docs. The wording in the 2.11 docs will be: "If any unexpected beam behavior occurs, check the default automatic beam settings in ‘scm/auto-beam.scm’ for possible interference, because the beam endings defined there will still apply in addition to your own. Any unwanted or conflicting default endings must be reverted for your time signature(s). "Existing auto-beam rules are removed by using" [here follows an example] Hope that's better. Trevor - Original Message - From: "David Bobroff" <[EMAIL PROTECTED]> To: "Trevor Daniels" <[EMAIL PROTECTED]> Cc: "Lilypond-User List" ; "Lily-Devel List" <[EMAIL PROTECTED]> Sent: Sunday, October 19, 2008 10:16 AM Subject: Re: Autobeaming overrides I don't have an answer to your question but I do have a request regarding this section of the manual. In section 1.2.4 Beams/Setting automatic beam behavior, there is the statement: Note that the default auto-beaming rules are specified in ‘scm/auto-beam.scm’, so you can revert rules that you did not explicitly create. I've long felt that this wording should be more explicit. Maybe something like: Note that the default auto-beaming rules are specified in ‘scm/auto-beam.scm’. When constructing auto-beaming rules of your own it is necessary to specifically revert any default rule that is contrary to your new rule. Maybe you've got a better phrasing for it. -David Trevor Daniels wrote: I'm putting the finishing touches to the Rhythm section of the Notation Reference and would like some help. The usual override for modifying the automatic beaming rhythm specifies the ending beat of the beam: #(override-auto-beam-setting '(end * * 6 8) 4 8) It is also possible to specify the starting beat of the beam, but I cannot see when it is necessary to do this. Are there any situations when the starting beat -must- be specified, or is this just an alternative? Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: elegant compound time signatures
It is common to only write out what is necessary to avoid confusion, which then varies with context. For example, an Ispaychi (Испайчи) decomposes as 3+2+3+2+3, but in my score its is written as 8 + 5 16 16 probably to distinguish not from an Eleno Mome that may be written in 13 16 Or at least in the 1970s - the latter from seem to not be used, replaced by a 7 8 So the former could be written in 13 16 too, regardless of the Eleno Mome meter. The scores of the region that I have, aimed for performance, do not use "+", but just sums it up. The "+" appears in musicological texts and schools. There are different ways to subbeam, too, depending if one wants the subaccents be indicated. This rachenitsa snip is typeset as (2+2)+(2+1), which is not wrong, but (2+2)+3 would be more normal - I could not get Lilypond to make the 2+1 into a 3. <> This gankino horo snip is typeset as (2+2)+(2+1)+(2+2), again not wrong, but scores use the styles 4+3+4 or (2+2)+3+(2+2). (Hitting the same 2+1 problem.) <> Hans On 19 Oct 2008, at 05:48, Graham Percival wrote: I'm reasonably happy with my solution to compound times. I'm still wondering about the printing -- should I leave it as 3 + 3 + 2 8 8 8 or change it to something like 8 (3+3+2) 8 Anyway, that's a relatively minor issue. The attached file prints compound time signatures and sets up automatic beaming. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
LSR search broken
Seb The LSR search mechanism seems to be broken at the moment, in that many (all?) of the preview titles and text returned following a search are one out from the real results of the search. For example, a search for "slash" returns three previews, the title and text of which have nothing to do with slashes, although the images are correct. The links are correct, as clicking on them brings up the real results of the search. For example, the first of the returned previews has the title "Free Meter - increasing the barnumber whereever you want" (which is snippet 333), but clicking on it brings up "Rhythmic slashes" (snippet 332). In other words, the link attached to the preview title and the image is correct, but the preview title and text are for the snippet with an index number one greater. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR search broken
Greetings Seba, while we're at it, the ERW LSR interface has been down again several times during the past two weeks (I can't remember exactly the days, but it never lasts more than a couple of hours). When I wanted to enter new snippets, I received the following message: "no output from lilypond"; then the snippet list in the interface became empty, and I couldn't do anything more. We also have some problems with snippets that are more than 1 system long: only the first system is visible, and the \break command has no effect: http://lsr.dsi.unimi.it/LSR/Item?id=521 Thanks! Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR search broken
2008/10/19 Valentin Villenave <[EMAIL PROTECTED]>: > We also have some problems with snippets that are more than 1 system > long: only the first system is visible, and the \break command has no > effect: > http://lsr.dsi.unimi.it/LSR/Item?id=521 This should be fixed now, though I can't verify since preview comes up blank. 'breakable is version specific to 2.11; the equivalent property for beams in 2.10 is allowBeamBreak. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Staff switch
Thanks - this saved my day :-) stefan Jonathan Kulp schrieb: I think you just had one small typo. By changing "staff" to "Staff" in the following line it works for me: \change Staff = RHStaff b c d e Jon Stefan Slapeta wrote: Hi all, please could anybody give me a hint why staff switches are not working with me?? Find attached a short sample of my approach, as I understand from the documentation. Thanks very much! Stefan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR search broken
On Oct 19, 2008, at 5:24 PM, Trevor Daniels wrote: Seb The LSR search mechanism seems to be broken at the moment, in that many (all?) of the preview titles and text returned following a search are one out from the real results of the search. For example, a search for "slash" returns three previews, the title and text of which have nothing to do with slashes, although the images are correct. The links are correct, as clicking on them brings up the real results of the search. For example, the first of the returned previews has the title "Free Meter - increasing the barnumber whereever you want" (which is snippet 333), but clicking on it brings up "Rhythmic slashes" (snippet 332). In other words, the link attached to the preview title and the image is correct, but the preview title and text are for the snippet with an index number one greater. Yep. That would be fixed overnight by the index rebuild process, but I did it automatically. There was a discrepancy between LSR's internal view of the database and the database itself. I must admit I have no clue as to how this could happen. I'm investigating. Ciao, seba ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR search broken
Neil Puttock Sunday, October 19, 2008 5:19 PM 2008/10/19 Valentin Villenave <[EMAIL PROTECTED]>: We also have some problems with snippets that are more than 1 system long: only the first system is visible, and the \break command has no effect: http://lsr.dsi.unimi.it/LSR/Item?id=521 This should be fixed now, though I can't verify since preview comes up blank. 'breakable is version specific to 2.11; the equivalent property for beams in 2.10 is allowBeamBreak. Ah, right. I've been with 2.11 so long I'd forgotten that (and so had the previous submitter). It now seems to break correctly, but the second system doesn't display :( As I need the snippet for the 2.11 docs do I need to put the 2.11 version in input/new, or will it get updated automatically during a 2.11 build? Trevor Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR search broken
2008/10/19 Trevor Daniels <[EMAIL PROTECTED]>: > As I need the snippet for the 2.11 docs do I need to put the > 2.11 version in input/new, or will it get updated automatically during > a 2.11 build? Makelsr.py will update it automatically, though we'll have to remove the property from the description. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Combine staves
Hi all, is it possible to combine two staves temporarily in the score? The reason behind it is that two voices have identical notes in this section, and I would like to print them in one single staff (stem up and down). It would be nice if this also reflects to the instrument names... Thanks! Stefan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR search broken
Neil Puttock Sunday, October 19, 2008 6:06 PM Subject: Re: LSR search broken 2008/10/19 Trevor Daniels <[EMAIL PROTECTED]>: As I need the snippet for the 2.11 docs do I need to put the 2.11 version in input/new, or will it get updated automatically during a 2.11 build? Makelsr.py will update it automatically, though we'll have to remove the property from the description. OK. Done. It also now displays two systems correctly. Thanks Seba!? Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine staves
Well, it's easy enough to put two voices on the same staff and make their stems go in opposite directions. See the docs where they discuss single-staff polyphony (Learning Manual section 2.3.5 for version 2.11.62 or later), and depending on how you do the single-staff polyphony, you may need \voiceOne, \voiceTwo, and so forth. If you leave the second staff empty in spots where the first staff has both voices (by empty I mean having skips or full-measure rests), then I *think* it is hidden by default. HTH, Jon Stefan Slapeta wrote: Hi all, is it possible to combine two staves temporarily in the score? The reason behind it is that two voices have identical notes in this section, and I would like to print them in one single staff (stem up and down). It would be nice if this also reflects to the instrument names... Thanks! Stefan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midi2ly
On Sat, Oct 18, 2008 at 08:00:25PM -0700, Graham Percival wrote: > On Sun, Oct 19, 2008 at 03:27:28AM +0200, Martin Tarenskeen wrote: > > > > Last question: driekwart-midi.ly shows \version "2.7.18" while I'm > > testing lilypond 2.11.62. Has the program not been maintained/updated > > for a long time ? > > Yes, it has not been maintained in a long time. > > > Shouldn't someone do that, > > Thanks for volunteering. I look forward to your patches. I have just begun to learn Lilypond and don't know anything about Python. Maybe I should do some stying on this subject. But at this moment I'm not the right person to fix and improve midi2ly. Someone else maybe can fix the -o and the time signature bugs I reported in my previous posting ? -- Martin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine staves
This could be nice occasion to use the \chage Staff = "..." command, which is explained in the section of keyboard music (where it is indidpensible), but it can be used on any named staves in your score. You can also change the instrument name manually at this point. Note that you will need to make sure that the change happens at a line break so the score makes sense. I guess you could wait to the end when you know where the line breaks are. Does anyone know of a more elegant solution? Andrew On Sun, Oct 19, 2008 at 2:32 PM, Jonathan Kulp <[EMAIL PROTECTED]> wrote: > Well, it's easy enough to put two voices on the same staff and make their > stems go in opposite directions. See the docs where they discuss > single-staff polyphony (Learning Manual section 2.3.5 for version 2.11.62 or > later), and depending on how you do the single-staff polyphony, you may need > \voiceOne, \voiceTwo, and so forth. > > If you leave the second staff empty in spots where the first staff has both > voices (by empty I mean having skips or full-measure rests), then I *think* > it is hidden by default. > > HTH, > > Jon > > Stefan Slapeta wrote: >> >> Hi all, >> >> is it possible to combine two staves temporarily in the score? The reason >> behind it is that two voices have identical notes in this section, and I >> would like to print them in one single staff (stem up and down). It would be >> nice if this also reflects to the instrument names... >> >> Thanks! >> >> Stefan >> >> >> >> ___ >> lilypond-user mailing list >> lilypond-user@gnu.org >> http://lists.gnu.org/mailman/listinfo/lilypond-user >> > > -- > Jonathan Kulp > http://www.jonathankulp.com > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine staves
Andrew Hawryluk wrote: This could be nice occasion to use the \change Staff = "..." command, which is explained in the section of keyboard music (where it is indidpensible), but it can be used on any named staves in your score. You can also change the instrument name manually at this point. Note that you will need to make sure that the change happens at a line break so the score makes sense. I guess you could wait to the end when you know where the line breaks are. Does anyone know of a more elegant solution? Well, you can always manually insert a \break where you want the line break ;-) Andrew On Sun, Oct 19, 2008 at 2:32 PM, Jonathan Kulp <[EMAIL PROTECTED]> wrote: If you leave the second staff empty in spots where the first staff has both voices (by empty I mean having skips or full-measure rests), then I *think* it is hidden by default. No it's not! Read about \RemoveEmptyStaffContext in http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Modifying-single-staves#Hiding-staves (Why "*think*", when you easily can test it in one minute if you have LilyPond available?) /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine staves
I created a short example doing this with the staff-change command and
it gets the lower voice into the upper staff just fine, with the
noteheads merged and the stems going opposite directions, but the
vacated staff doesn't disappear like I think Stefan wanted. Is this the
sort of thing you envisioned, Andrew?
\version "2.11.62"
csu = \change Staff = up
up = \relative c'' {
\repeat unfold 3 { c4 d e d | }
\break
\voiceOne c4 d e d
}
down = \relative c' {
\repeat unfold 2 { c4 d e d |}
c8 d e f g f g a16 b |
\csu \voiceTwo c4 d e d
}
\score {
\new StaffGroup <<
\new Staff = "up" <<
\up
>>
\new Staff = "down" <<
\down
>>
>>
\layout {}
\midi {}
}
Andrew Hawryluk wrote:
This could be nice occasion to use the \chage Staff = "..." command,
which is explained in the section of keyboard music (where it is
indidpensible), but it can be used on any named staves in your score.
You can also change the instrument name manually at this point.
Note that you will need to make sure that the change happens at a line
break so the score makes sense. I guess you could wait to the end when
you know where the line breaks are. Does anyone know of a more elegant
solution?
Andrew
On Sun, Oct 19, 2008 at 2:32 PM, Jonathan Kulp <[EMAIL PROTECTED]> wrote:
Well, it's easy enough to put two voices on the same staff and make their
stems go in opposite directions. See the docs where they discuss
single-staff polyphony (Learning Manual section 2.3.5 for version 2.11.62 or
later), and depending on how you do the single-staff polyphony, you may need
\voiceOne, \voiceTwo, and so forth.
If you leave the second staff empty in spots where the first staff has both
voices (by empty I mean having skips or full-measure rests), then I *think*
it is hidden by default.
HTH,
Jon
Stefan Slapeta wrote:
Hi all,
is it possible to combine two staves temporarily in the score? The reason
behind it is that two voices have identical notes in this section, and I
would like to print them in one single staff (stem up and down). It would be
nice if this also reflects to the instrument names...
Thanks!
Stefan
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine staves
Yes. Replace "\layout {}" with "\layout { \context{
\RemoveEmptyStaffContext}}" and the empty staff disappears. You can
also place the \break in the "csu" command to make it easier to use.
Maybe you could even add a \tag so this only takes effect in the full
score and the individual instrumental parts are unaffected by the
staff switch or the forced line breaks.
Andrew
\version "2.11.62"
csu = {\change Staff = up \break}
up = \relative c'' {
\repeat unfold 3 { c4 d e d | }
\voiceOne c4 d e d
}
down = \relative c' {
\repeat unfold 2 { c4 d e d |}
c8 d e f g f g a16 b |
\csu \voiceTwo c4 d e d
}
\score {
\new StaffGroup <<
\new Staff = "up" <<
\up
>>
\new Staff = "down" <<
\down
>>
>>
\layout { \context{ \RemoveEmptyStaffContext}}
\midi {}
}
On Sun, Oct 19, 2008 at 5:34 PM, Jonathan Kulp <[EMAIL PROTECTED]> wrote:
> I created a short example doing this with the staff-change command and it
> gets the lower voice into the upper staff just fine, with the noteheads
> merged and the stems going opposite directions, but the vacated staff
> doesn't disappear like I think Stefan wanted. Is this the sort of thing you
> envisioned, Andrew?
>
>
> \version "2.11.62"
>
> csu = \change Staff = up
>
> up = \relative c'' {
> \repeat unfold 3 { c4 d e d | }
> \break
> \voiceOne c4 d e d
> }
>
> down = \relative c' {
> \repeat unfold 2 { c4 d e d |}
> c8 d e f g f g a16 b |
> \csu \voiceTwo c4 d e d
> }
>
> \score {
> \new StaffGroup <<
>\new Staff = "up" <<
> \up
>>>
>\new Staff = "down" <<
> \down
>>>
> >>
> \layout {}
> \midi {}
> }
>
>
> Andrew Hawryluk wrote:
>>
>> This could be nice occasion to use the \chage Staff = "..." command,
>> which is explained in the section of keyboard music (where it is
>> indidpensible), but it can be used on any named staves in your score.
>> You can also change the instrument name manually at this point.
>>
>> Note that you will need to make sure that the change happens at a line
>> break so the score makes sense. I guess you could wait to the end when
>> you know where the line breaks are. Does anyone know of a more elegant
>> solution?
>>
>> Andrew
>>
>> On Sun, Oct 19, 2008 at 2:32 PM, Jonathan Kulp <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> Well, it's easy enough to put two voices on the same staff and make their
>>> stems go in opposite directions. See the docs where they discuss
>>> single-staff polyphony (Learning Manual section 2.3.5 for version 2.11.62
>>> or
>>> later), and depending on how you do the single-staff polyphony, you may
>>> need
>>> \voiceOne, \voiceTwo, and so forth.
>>>
>>> If you leave the second staff empty in spots where the first staff has
>>> both
>>> voices (by empty I mean having skips or full-measure rests), then I
>>> *think*
>>> it is hidden by default.
>>>
>>> HTH,
>>>
>>> Jon
>>>
>>> Stefan Slapeta wrote:
Hi all,
is it possible to combine two staves temporarily in the score? The
reason
behind it is that two voices have identical notes in this section, and I
would like to print them in one single staff (stem up and down). It
would be
nice if this also reflects to the instrument names...
Thanks!
Stefan
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
>>> --
>>> Jonathan Kulp
>>> http://www.jonathankulp.com
>>>
>>>
>>> ___
>>> lilypond-user mailing list
>>> lilypond-user@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/lilypond-user
>>>
>>
>
> --
> Jonathan Kulp
> http://www.jonathankulp.com
>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine staves
That works very well, Andrew. I'll have to investigate the \tag command
a bit more. It might be useful in my orchestral piece. Best,
Jon
Andrew Hawryluk wrote:
Yes. Replace "\layout {}" with "\layout { \context{
\RemoveEmptyStaffContext}}" and the empty staff disappears. You can
also place the \break in the "csu" command to make it easier to use.
Maybe you could even add a \tag so this only takes effect in the full
score and the individual instrumental parts are unaffected by the
staff switch or the forced line breaks.
Andrew
\version "2.11.62"
csu = {\change Staff = up \break}
up = \relative c'' {
\repeat unfold 3 { c4 d e d | }
\voiceOne c4 d e d
}
down = \relative c' {
\repeat unfold 2 { c4 d e d |}
c8 d e f g f g a16 b |
\csu \voiceTwo c4 d e d
}
\score {
\new StaffGroup <<
\new Staff = "up" <<
\up
>>
\new Staff = "down" <<
\down
>>
>>
\layout { \context{ \RemoveEmptyStaffContext}}
\midi {}
}
On Sun, Oct 19, 2008 at 5:34 PM, Jonathan Kulp <[EMAIL PROTECTED]> wrote:
I created a short example doing this with the staff-change command and it
gets the lower voice into the upper staff just fine, with the noteheads
merged and the stems going opposite directions, but the vacated staff
doesn't disappear like I think Stefan wanted. Is this the sort of thing you
envisioned, Andrew?
\version "2.11.62"
csu = \change Staff = up
up = \relative c'' {
\repeat unfold 3 { c4 d e d | }
\break
\voiceOne c4 d e d
}
down = \relative c' {
\repeat unfold 2 { c4 d e d |}
c8 d e f g f g a16 b |
\csu \voiceTwo c4 d e d
}
\score {
\new StaffGroup <<
\new Staff = "up" <<
\up
>>
\new Staff = "down" <<
\down
>>
>>
\layout {}
\midi {}
}
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: elegant compound time signatures
On Sun, Oct 19, 2008 at 04:36:48PM +0200, Hans Aberg wrote:
> This gankino horo snip is typeset as (2+2)+(2+1)+(2+2), again not wrong,
> but scores use the styles 4+3+4 or (2+2)+3+(2+2). (Hitting the same 2+1
> problem.)
What, like this? I think this is the second bar of the gankino
horo snippet. Here's two ways of doing it, depending on how picky
you want to be.
Cheers,
- Graham
\version "2.11.62"
\relative c'' {
\time 11/16
\set Timing.beatGrouping = #'(4 3 4)
c16 b a g
g f a
g8 f16 e
\set subdivideBeams = ##t
\set beatLength = #(ly:make-moment 1 8)
c'16[ b a g]
\unset subdivideBeams
\unset beatLength
g f a
g8 f16 e
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
