Cyclic dependency error with change staff and trillSpan

2024-03-22 Thread Knute Snortum
Hi again,

I am getting a cyclic dependency error with code that uses change staff and
trillSpan.  Here is as minimal an example as I could create:

%%%
\version "2.24.3"
\language "english"

staffUp   = \change Staff = "upper"
staffDown = \change Staff = "lower"

rightHand = \relative {
  c''4\noBeam \staffDown \voiceOne \afterGrace g,4\startTrillSpan {
fs16\stopTrillSpan g } \staffUp \oneVoice c'2
}

\score {
  \new PianoStaff <<
\new Staff = "upper" \rightHand
\new Staff = "lower" { \clef bass s1 }
  >>
}
%%%

This produces two errors of the same type:

programming error: cyclic dependency: calculation-in-progress encountered
for VerticalAxisGroup.adjacent-pure-heights

continuing, cross fingers


>From what I can see, the PDF output is fine. The MWE needs notes before and
after the afterGrace, plus the trillSpan for the error to show. Any ideas
on how to fix this?

--
Knute Snortum


Re: change staff-staff-spacing in a single score?

2023-11-07 Thread Jean Abou Samra
Le mardi 07 novembre 2023 à 16:48 -0500, David Zelinsky a écrit :
> Though I am curious whether this was just an accident of implementation
> and would be easy to change, or if there is a more structural reason.


It is purely a bug. I've just
found https://gitlab.com/lilypond/lilypond/-/issues/1885 . I'm quite sure there
were more recent discussions, but maybe not on the bug tracker.




signature.asc
Description: This is a digitally signed message part


Re: change staff-staff-spacing in a single score?

2023-11-07 Thread David Zelinsky
Jean Abou Samra  writes:

> Le mardi 07 novembre 2023 à 00:55 -0500, David Zelinsky a écrit :
>> Is there a way to change the spacing between staves (single-staff
>> systems) in one score, in a document with multiple scores, without
>> introducing a page break?
>
> Unfortunately, the answer is currently no.

Thanks, Jean.  Good to at least have confirmation.

Though I am curious whether this was just an accident of implementation
and would be easy to change, or if there is a more structural reason.


Paul Hodges  writes:

> Assuming your sections are all (or nearly all) less than half a page,
> you could halve the paper requirement by typesetting onto landscape A5
> (or whatever is half the size of your output paper) and print from
> Acrobat (or whatever) two-up on each page.
>

Thanks, Paul.  That's a good idea.

-David



Re: change staff-staff-spacing in a single score?

2023-11-07 Thread Paul Hodges
Assuming your sections are all (or nearly all) less than half a page, you could 
halve the paper requirement by typesetting onto landscape A5 (or whatever is 
half the size of your output paper) and print from Acrobat (or whatever) two-up 
on each page.

Paul


 From:   David Zelinsky  
 To:
 Sent:   07/11/2023 5:55 
 Subject:   change staff-staff-spacing in a single score? 

Is there a way to change the spacing between staves (single-staff 
systems) in one score, in a document with multiple scores, without 
introducing a page break?  The only way I've found in the manual to 
change the spacing of systems (as opposed to staves within a system) is 
in a \paper block, and the lowest level that can occur is in a 
\bookpart, which introduces a page break which I don't want.  I could 
use NonMusicalPaperColumn.line-break-system-details, but that seems to 
only apply to one line, so I would need to set it separately for each 
line in the score, which is a nuisance. 
 
To explain better what I need, I am re-engraving some short sections 
from an orchestra part, to faithfully match the lines in the original 
but with some particular rhythmic changes that the conductor wants.  I 
will print these out and cut and paste them over the original (using 
removable/restickable adhesive), so I want everything to match the 
original as closely as possible.  The sections range from 1 to 5 lines 
each. 
 
Currently I am using a separate \score for each short section, which 
seems to make it easier to maintain control over the line breaks.  But 
I'm trying to fit as many on of these short scores on page as I 
reasonably can, to save trees.  I've set the staff size and 
staff-staff-spacing globally to match the average in the original pretty 
well, but of course the spacing varies some from page to page, so some 
of the sections need adjustment.  I could introduce a new \bookpart and 
\paper block for those sections, but I'd rather not have those extra 
page breaks. 
 
Is there a better way to do this? 
 
-David 
 


Re: change staff-staff-spacing in a single score?

2023-11-07 Thread Jean Abou Samra
Le mardi 07 novembre 2023 à 00:55 -0500, David Zelinsky a écrit :
> Is there a way to change the spacing between staves (single-staff
> systems) in one score, in a document with multiple scores, without
> introducing a page break?

Unfortunately, the answer is currently no.

Best,
Jean



signature.asc
Description: This is a digitally signed message part


change staff-staff-spacing in a single score?

2023-11-06 Thread David Zelinsky
Is there a way to change the spacing between staves (single-staff
systems) in one score, in a document with multiple scores, without
introducing a page break?  The only way I've found in the manual to
change the spacing of systems (as opposed to staves within a system) is
in a \paper block, and the lowest level that can occur is in a
\bookpart, which introduces a page break which I don't want.  I could
use NonMusicalPaperColumn.line-break-system-details, but that seems to
only apply to one line, so I would need to set it separately for each
line in the score, which is a nuisance.

To explain better what I need, I am re-engraving some short sections
from an orchestra part, to faithfully match the lines in the original
but with some particular rhythmic changes that the conductor wants.  I
will print these out and cut and paste them over the original (using
removable/restickable adhesive), so I want everything to match the
original as closely as possible.  The sections range from 1 to 5 lines
each.

Currently I am using a separate \score for each short section, which
seems to make it easier to maintain control over the line breaks.  But
I'm trying to fit as many on of these short scores on page as I
reasonably can, to save trees.  I've set the staff size and
staff-staff-spacing globally to match the average in the original pretty
well, but of course the spacing varies some from page to page, so some
of the sections need adjustment.  I could introduce a new \bookpart and
\paper block for those sections, but I'd rather not have those extra
page breaks.

Is there a better way to do this?

-David



Re: Programming error with change staff

2023-02-17 Thread Knute Snortum
On Fri, Feb 17, 2023 at 1:04 AM Thomas Morley 
wrote:

>
> Add
> \override Script.avoid-slur = #'inside
>
> Cheers,
>   Harm
>

That works great, thanks!


--
Knute Snortum


Re: Programming error with change staff

2023-02-17 Thread Thomas Morley
Am Do., 16. Feb. 2023 um 19:09 Uhr schrieb Knute Snortum :
>
> I have run into a situation where LilyPond produces a programming error.  It 
> involves changing staff, voice one, accent fingering and avoid-slur.  It's 
> best to just look at the MWE:
>
> \version "2.25.1"
>
> staffUp = \change Staff = "upper"
> staffDown = \change Staff = "lower"
>
> rightHand = {
>   \new Voice {
> \voiceOne \staffDown g16->-1( \staffUp c' c' \staffDown g)
>   }
> }
>
> leftHand = { \new Voice { \clef bass s4 } }
>
> \score {
>   \new PianoStaff \with { \override Fingering.avoid-slur = #'inside } <<
> \new Staff = "upper" \rightHand
> \new Staff = "lower" \leftHand
>   >>
> }
>
> There may be a way to get this smaller, but I couldn't find it.  Is there a 
> way around this bug as it is affecting my current project?
>
> --
> Knute Snortum

Add
\override Script.avoid-slur = #'inside

Cheers,
  Harm



RE: Programming error with change staff

2023-02-16 Thread Mark Stephen Mrotek
Knute,

 

Running your MWE under 2.22.2 it complies without a hitch.

 

Mark

 

From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org 
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Knute 
Snortum
Sent: Thursday, February 16, 2023 10:09 AM
To: lilypond-user@gnu.org
Subject: Programming error with change staff

 

I have run into a situation where LilyPond produces a programming error.  It 
involves changing staff, voice one, accent fingering and avoid-slur.  It's best 
to just look at the MWE:

 

\version "2.25.1"

staffUp = \change Staff = "upper"
staffDown = \change Staff = "lower"

rightHand = { 
  \new Voice { 
\voiceOne \staffDown g16->-1( \staffUp c' c' \staffDown g)
  }
}

leftHand = { \new Voice { \clef bass s4 } }

\score {
  \new PianoStaff \with { \override Fingering.avoid-slur = #'inside } <<
\new Staff = "upper" \rightHand
\new Staff = "lower" \leftHand
  >>
}

There may be a way to get this smaller, but I couldn't find it.  Is there a way 
around this bug as it is affecting my current project?

--
Knute Snortum



Programming error with change staff

2023-02-16 Thread Knute Snortum
I have run into a situation where LilyPond produces a programming error.
It involves changing staff, voice one, accent fingering and avoid-slur.
It's best to just look at the MWE:

\version "2.25.1"

staffUp = \change Staff = "upper"
staffDown = \change Staff = "lower"

rightHand = {
  \new Voice {
\voiceOne \staffDown g16->-1( \staffUp c' c' \staffDown g)
  }
}

leftHand = { \new Voice { \clef bass s4 } }

\score {
  \new PianoStaff \with { \override Fingering.avoid-slur = #'inside } <<
\new Staff = "upper" \rightHand
\new Staff = "lower" \leftHand
  >>
}

There may be a way to get this smaller, but I couldn't find it.  Is there a
way around this bug as it is affecting my current project?

--
Knute Snortum


RE: change Staff =

2022-08-29 Thread Mark Stephen Mrotek
Ming,

 

Bar 4 in both are identical. What is “wrong” in the second score?

What is wrong with bar 6? There is only one example.

What adjustment do you want to the beam in bar 5?

 

Mark

 

 

From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] 
On Behalf Of ming tsang
Sent: Monday, August 29, 2022 3:51 PM
To: lilypond-user 
Subject: Fwd: change Staff =

 

Sorry forgot to include the .ly file.

 

-- Forwarded message -
From: ming tsang mailto:ming.tsan...@gmail.com> >
Date: Mon, Aug 29, 2022 at 4:18 PM
Subject: change Staff =
To: lilypond-user mailto:lilypond-user@gnu.org> >

 

Dear lilyponders,

When I run my full score I got the following warning message.



warning: cannot find context to change to: Staff = right

 

Then I copy few measure ( just the piano staff), there is no warning message, 
but (see below) bar #4 bar #6 are wrong.




How to adjust the beam on bar #5?

ming (lyndon) tsang

 




 

-- 

ming (lyndon) tsang



Re: Learning how to use "\change Staff"; don't get it yet, obviously

2022-08-22 Thread Valentin Petzel
Hi Jean,

could have sworn there was some issue with contexts being alive using 
\RemoveEmptyStaves, but I fail to reproduce this ... But then, it doesn’t 
really make sense, as page breaking is done after als context magic is 
applied. I probably just messed up, that’s something I’m quite proficient at.

Best,
Valentin

Am Montag, 22. August 2022, 17:21:35 CEST schrieb Jean Abou Samra:
> > Le 22 août 2022 à 17:12, Valentin Petzel  a écrit :
> > 
> > Hi Ken,
> > 
> > you have two different scores, one that produces a score and one that
> > produces midi (is there any specific reason not to use one score with
> > both \layout { } and \midi { }?).
> > 
> > The first one works fine, the seconds creates problems. Basically what’s
> > happening is that you never actually names any staves "RH" or "LH", so
> > Lilypond cannot chance context. Change the \new Staff lines to \new Staff
> > =
> > "..." and it will work. Caveat: Changing contexts might fail if these
> > context to be changing into is not alive at that time, e.g. due to a line
> > break.
> Hi Valentin,
> 
> A minor question: the statement above is something I don’t understand, what
> do line breaks have to do with contexts being alive?
> 
> Thanks,
> 
> Jean
> 
> > This means that when doing such things you need to make sure that the
> > context you want to change into is alive, for example by filling the
> > staves with
> > 
> > <<
> > \rh
> > #(skip-of-length lh)
> > 
> > 
> > or even
> > 
> > <<
> > \rh
> > #(skip-of-length rh)
> > #(skip-of-length lh)
> > 
> > 
> > Cheers,
> > Valentin
> > 
> > Am Samstag, 30. Juli 2022, 23:48:59 CEST schrieb Kenneth Wolcott:
> >> Hi;
> >> 
> >>  I'm learning how to engrave music that changes from one staff to
> >>  another.
> >>  
> >>  I, obviously, do not understand yet how to do this, even after
> >> 
> >> reading the pertinent section in the Notation Reference.
> >> 
> >>  My attempt to engrave the first three bars of the harp score of Swan
> >> 
> >> Lake fails with the following:
> >> 
> >> Swan_Lake.ly:40:3: warning: cannot find context to change to: Staff = RH
> >> 
> >>  \change Staff = "RH"
> >> 
> >> Swan_Lake.ly:22:3: warning: cannot find context to change to: Staff = LH
> >> 
> >>  \change Staff = "LH" <> s4| % m01
> >>  
> >>  I have attached a screenshot of the first three bars of the harp
> >> 
> >> score of Swan Lake, my LIlypond source code and the result of my
> >> engraving attempt.
> >> 
> >>  I don't think that there's anything wrong with Lilypond, and there's
> >> 
> >> nothing wrong with the documentation, but this Lilypond user is a bit
> >> dense.
> >> 
> >>  If I can just get the first bar engraving correctly, I think I can
> >> 
> >> make it the rest of the way :-)
> >> 
> >> Thanks,
> >> Ken Wolcott



signature.asc
Description: This is a digitally signed message part.


Re: Learning how to use "\change Staff"; don't get it yet, obviously

2022-08-22 Thread Jean Abou Samra


> Le 22 août 2022 à 17:12, Valentin Petzel  a écrit :
> 
> Hi Ken,
> 
> you have two different scores, one that produces a score and one that 
> produces 
> midi (is there any specific reason not to use one score with both \layout { } 
> and \midi { }?).
> 
> The first one works fine, the seconds creates problems. Basically what’s 
> happening is that you never actually names any staves "RH" or "LH", so 
> Lilypond cannot chance context. Change the \new Staff lines to \new Staff = 
> "..." and it will work. Caveat: Changing contexts might fail if these context 
> to be changing into is not alive at that time, e.g. due to a line break.


Hi Valentin,

A minor question: the statement above is something I don’t understand, what do 
line breaks have to do with contexts being alive?

Thanks,

Jean




> 
> This means that when doing such things you need to make sure that the context 
> you want to change into is alive, for example by filling the staves with
> 
> << 
> \rh
> #(skip-of-length lh)
>>> 
> 
> or even
> 
> << 
> \rh
> #(skip-of-length rh)
> #(skip-of-length lh)
>>> 
> 
> Cheers,
> Valentin
> 
> 
> 
> Am Samstag, 30. Juli 2022, 23:48:59 CEST schrieb Kenneth Wolcott:
>> Hi;
>> 
>>  I'm learning how to engrave music that changes from one staff to another.
>> 
>>  I, obviously, do not understand yet how to do this, even after
>> reading the pertinent section in the Notation Reference.
>> 
>>  My attempt to engrave the first three bars of the harp score of Swan
>> Lake fails with the following:
>> 
>> Swan_Lake.ly:40:3: warning: cannot find context to change to: Staff = RH
>> 
>>  \change Staff = "RH"
>> Swan_Lake.ly:22:3: warning: cannot find context to change to: Staff = LH
>> 
>>  \change Staff = "LH" <> s4| % m01
>> 
>>  I have attached a screenshot of the first three bars of the harp
>> score of Swan Lake, my LIlypond source code and the result of my
>> engraving attempt.
>> 
>>  I don't think that there's anything wrong with Lilypond, and there's
>> nothing wrong with the documentation, but this Lilypond user is a bit
>> dense.
>> 
>>  If I can just get the first bar engraving correctly, I think I can
>> make it the rest of the way :-)
>> 
>> Thanks,
>> Ken Wolcott
> 


signature.asc
Description: Binary data


Re: Learning how to use "\change Staff"; don't get it yet, obviously

2022-08-22 Thread Valentin Petzel
Hi Ken,

you have two different scores, one that produces a score and one that produces 
midi (is there any specific reason not to use one score with both \layout { } 
and \midi { }?).

The first one works fine, the seconds creates problems. Basically what’s 
happening is that you never actually names any staves "RH" or "LH", so 
Lilypond cannot chance context. Change the \new Staff lines to \new Staff = 
"..." and it will work. Caveat: Changing contexts might fail if these context 
to be changing into is not alive at that time, e.g. due to a line break.

This means that when doing such things you need to make sure that the context 
you want to change into is alive, for example by filling the staves with

<< 
 \rh
 #(skip-of-length lh)
>>

or even

<< 
 \rh
 #(skip-of-length rh)
 #(skip-of-length lh)
>>

Cheers,
Valentin



Am Samstag, 30. Juli 2022, 23:48:59 CEST schrieb Kenneth Wolcott:
> Hi;
> 
>   I'm learning how to engrave music that changes from one staff to another.
> 
>   I, obviously, do not understand yet how to do this, even after
> reading the pertinent section in the Notation Reference.
> 
>   My attempt to engrave the first three bars of the harp score of Swan
> Lake fails with the following:
> 
> Swan_Lake.ly:40:3: warning: cannot find context to change to: Staff = RH
> 
>   \change Staff = "RH"
> Swan_Lake.ly:22:3: warning: cannot find context to change to: Staff = LH
> 
>   \change Staff = "LH" <> s4| % m01
> 
>   I have attached a screenshot of the first three bars of the harp
> score of Swan Lake, my LIlypond source code and the result of my
> engraving attempt.
> 
>   I don't think that there's anything wrong with Lilypond, and there's
> nothing wrong with the documentation, but this Lilypond user is a bit
> dense.
> 
>   If I can just get the first bar engraving correctly, I think I can
> make it the rest of the way :-)
> 
> Thanks,
> Ken Wolcott



signature.asc
Description: This is a digitally signed message part.


Re: Trying to create a two-octave ascending C Major scale using the change Staff example in NR

2022-07-31 Thread Kenneth Wolcott
Maybe I got it now :-)

Thanks to all of you who put up with me 

Ken

On Sun, Jul 31, 2022 at 6:33 PM Kenneth Wolcott
 wrote:
>
> Ah! I created more than one bar of notes, therefore I have to have
> more than one bar of spacer notes. Doh!
>
> On Sun, Jul 31, 2022 at 5:35 PM Kenneth Wolcott
>  wrote:
> >
> > Hi;
> >
> >   Starting a new email thread regarding my difficulty in understanding
> > how to use the Lilypond \change Staff feature...
> >
> > I'm trying to create a two-octave ascending C Major scale using the
> > change Staff example in NR.
> >
> > https://lilypond.org/doc/v2.22/Documentation/notation-big-page.html#changing-staff-manually
> >
> > I'm losing the lower staff. What am I doing wrong?
> >
> > Please see my Lilypond source and the resulting pdf (attached).
> >
> > Thanks,
> > Ken Wolcott


four_octave_scale.ly
Description: Binary data


four_octave_scale.pdf
Description: Adobe PDF document


Re: Trying to create a two-octave ascending C Major scale using the change Staff example in NR

2022-07-31 Thread Kenneth Wolcott
Ah! I created more than one bar of notes, therefore I have to have
more than one bar of spacer notes. Doh!

On Sun, Jul 31, 2022 at 5:35 PM Kenneth Wolcott
 wrote:
>
> Hi;
>
>   Starting a new email thread regarding my difficulty in understanding
> how to use the Lilypond \change Staff feature...
>
> I'm trying to create a two-octave ascending C Major scale using the
> change Staff example in NR.
>
> https://lilypond.org/doc/v2.22/Documentation/notation-big-page.html#changing-staff-manually
>
> I'm losing the lower staff. What am I doing wrong?
>
> Please see my Lilypond source and the resulting pdf (attached).
>
> Thanks,
> Ken Wolcott



Trying to create a two-octave ascending C Major scale using the change Staff example in NR

2022-07-31 Thread Kenneth Wolcott
Hi;

  Starting a new email thread regarding my difficulty in understanding
how to use the Lilypond \change Staff feature...

I'm trying to create a two-octave ascending C Major scale using the
change Staff example in NR.

https://lilypond.org/doc/v2.22/Documentation/notation-big-page.html#changing-staff-manually

I'm losing the lower staff. What am I doing wrong?

Please see my Lilypond source and the resulting pdf (attached).

Thanks,
Ken Wolcott


two_octave_scale.ly
Description: Binary data


two_octave_scale.pdf
Description: Adobe PDF document


Re: Learning how to use "\change Staff"; don't get it yet, obviously

2022-07-31 Thread Kenneth Wolcott
Thank you, Mark.  I will start a new email thread on this topic
starting with a more basic \change Staff query.

On Sat, Jul 30, 2022 at 7:02 PM Mark Stephen Mrotek
 wrote:
>
> Kenneth,
>
> If you want, send your code to me and I shall try to achieve what you want 
> with an explanation.
>
> Mark
>
> -Original Message-
> From: Kenneth Wolcott [mailto:kennethwolc...@gmail.com]
> Sent: Saturday, July 30, 2022 6:45 PM
> To: Mark Stephen Mrotek 
> Cc: Lily Pond 
> Subject: Re: Learning how to use "\change Staff"; don't get it yet, obviously
>
> Hi Mark;
>
>   Thank you for the help.
>
>   I'm still having trouble wrapping my head around this.
>
>   I think that the problem (in general) with my being able to apply examples 
> from the documentation to my engraving attempts is that the example is not 
> large enough (not enough notes, too minimal) to require its own variable to 
> contain the notes, so that gets in the way of the Lilypond feature that I 
> want to use.
>
>   I will try removing the variables and just place the notes for the first 
> measure only to see if I can finally make this work, and generalize it later.
>
> Thanks,
> Ken
>
> On Sat, Jul 30, 2022 at 3:04 PM Mark Stephen Mrotek  
> wrote:
> >
> > Kenneth,
> >
> > Not dense at all.
> > Change staff works within a single voice. You split it between rh and lh. 
> > Might suggest you use "upper" and "lower" for staff designation if you use 
> > rh and lh as variable names.
> >
> > Assuming you start in "lower" with lh.
> > Then
> > \tuplet 3/2 { b,8(d b }
> >   \change Staff = "upper"   %% now continue with what you want in "upper"
> > { d'8 fs' b' } \tuplet 3/2 { d''8 b' fs' }
> >   \change Staff = "lower"   %% and so on.
> >
> > Note: that rh must contain spacers all the while so that the voice can move 
> > back and forth without collisions.
> >
> > Mark
> >
> > -Original Message-
> > From: lilypond-user
> > [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf
> > Of Kenneth Wolcott
> > Sent: Saturday, July 30, 2022 2:49 PM
> > To: Lily Pond 
> > Subject: Learning how to use "\change Staff"; don't get it yet,
> > obviously
> >
> > Hi;
> >
> >   I'm learning how to engrave music that changes from one staff to another.
> >
> >   I, obviously, do not understand yet how to do this, even after reading 
> > the pertinent section in the Notation Reference.
> >
> >   My attempt to engrave the first three bars of the harp score of Swan Lake 
> > fails with the following:
> >
> > Swan_Lake.ly:40:3: warning: cannot find context to change to: Staff =
> > RH
> >
> >   \change Staff = "RH"
> > Swan_Lake.ly:22:3: warning: cannot find context to change to: Staff =
> > LH
> >
> >   \change Staff = "LH" <> s4| % m01
> >
> >   I have attached a screenshot of the first three bars of the harp score of 
> > Swan Lake, my LIlypond source code and the result of my engraving attempt.
> >
> >   I don't think that there's anything wrong with Lilypond, and there's 
> > nothing wrong with the documentation, but this Lilypond user is a bit dense.
> >
> >   If I can just get the first bar engraving correctly, I think I can
> > make it the rest of the way :-)
> >
> > Thanks,
> > Ken Wolcott
> >
>



RE: Learning how to use "\change Staff"; don't get it yet, obviously

2022-07-30 Thread Mark Stephen Mrotek
Kenneth,

If you want, send your code to me and I shall try to achieve what you want with 
an explanation.

Mark

-Original Message-
From: Kenneth Wolcott [mailto:kennethwolc...@gmail.com] 
Sent: Saturday, July 30, 2022 6:45 PM
To: Mark Stephen Mrotek 
Cc: Lily Pond 
Subject: Re: Learning how to use "\change Staff"; don't get it yet, obviously

Hi Mark;

  Thank you for the help.

  I'm still having trouble wrapping my head around this.

  I think that the problem (in general) with my being able to apply examples 
from the documentation to my engraving attempts is that the example is not 
large enough (not enough notes, too minimal) to require its own variable to 
contain the notes, so that gets in the way of the Lilypond feature that I want 
to use.

  I will try removing the variables and just place the notes for the first 
measure only to see if I can finally make this work, and generalize it later.

Thanks,
Ken

On Sat, Jul 30, 2022 at 3:04 PM Mark Stephen Mrotek  
wrote:
>
> Kenneth,
>
> Not dense at all.
> Change staff works within a single voice. You split it between rh and lh. 
> Might suggest you use "upper" and "lower" for staff designation if you use rh 
> and lh as variable names.
>
> Assuming you start in "lower" with lh.
> Then
> \tuplet 3/2 { b,8(d b }
>   \change Staff = "upper"   %% now continue with what you want in "upper"
> { d'8 fs' b' } \tuplet 3/2 { d''8 b' fs' }
>   \change Staff = "lower"   %% and so on.
>
> Note: that rh must contain spacers all the while so that the voice can move 
> back and forth without collisions.
>
> Mark
>
> -Original Message-
> From: lilypond-user 
> [mailto:lilypond-user-bounces+carsonmark=ca.rr....@gnu.org] On Behalf 
> Of Kenneth Wolcott
> Sent: Saturday, July 30, 2022 2:49 PM
> To: Lily Pond 
> Subject: Learning how to use "\change Staff"; don't get it yet, 
> obviously
>
> Hi;
>
>   I'm learning how to engrave music that changes from one staff to another.
>
>   I, obviously, do not understand yet how to do this, even after reading the 
> pertinent section in the Notation Reference.
>
>   My attempt to engrave the first three bars of the harp score of Swan Lake 
> fails with the following:
>
> Swan_Lake.ly:40:3: warning: cannot find context to change to: Staff = 
> RH
>
>   \change Staff = "RH"
> Swan_Lake.ly:22:3: warning: cannot find context to change to: Staff = 
> LH
>
>   \change Staff = "LH" <> s4| % m01
>
>   I have attached a screenshot of the first three bars of the harp score of 
> Swan Lake, my LIlypond source code and the result of my engraving attempt.
>
>   I don't think that there's anything wrong with Lilypond, and there's 
> nothing wrong with the documentation, but this Lilypond user is a bit dense.
>
>   If I can just get the first bar engraving correctly, I think I can 
> make it the rest of the way :-)
>
> Thanks,
> Ken Wolcott
>




Re: Learning how to use "\change Staff"; don't get it yet, obviously

2022-07-30 Thread Kenneth Wolcott
Hi Mark;

  Thank you for the help.

  I'm still having trouble wrapping my head around this.

  I think that the problem (in general) with my being able to apply
examples from the documentation to my engraving attempts is that the
example is not large enough (not enough notes, too minimal) to require
its own variable to contain the notes, so that gets in the way of the
Lilypond feature that I want to use.

  I will try removing the variables and just place the notes for the
first measure only to see if I can finally make this work, and
generalize it later.

Thanks,
Ken

On Sat, Jul 30, 2022 at 3:04 PM Mark Stephen Mrotek
 wrote:
>
> Kenneth,
>
> Not dense at all.
> Change staff works within a single voice. You split it between rh and lh. 
> Might suggest you use "upper" and "lower" for staff designation if you use rh 
> and lh as variable names.
>
> Assuming you start in "lower" with lh.
> Then
> \tuplet 3/2 { b,8(d b }
>   \change Staff = "upper"   %% now continue with what you want in "upper"
> { d'8 fs' b' } \tuplet 3/2 { d''8 b' fs' }
>   \change Staff = "lower"   %% and so on.
>
> Note: that rh must contain spacers all the while so that the voice can move 
> back and forth without collisions.
>
> Mark
>
> -Original Message-
> From: lilypond-user 
> [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of 
> Kenneth Wolcott
> Sent: Saturday, July 30, 2022 2:49 PM
> To: Lily Pond 
> Subject: Learning how to use "\change Staff"; don't get it yet, obviously
>
> Hi;
>
>   I'm learning how to engrave music that changes from one staff to another.
>
>   I, obviously, do not understand yet how to do this, even after reading the 
> pertinent section in the Notation Reference.
>
>   My attempt to engrave the first three bars of the harp score of Swan Lake 
> fails with the following:
>
> Swan_Lake.ly:40:3: warning: cannot find context to change to: Staff = RH
>
>   \change Staff = "RH"
> Swan_Lake.ly:22:3: warning: cannot find context to change to: Staff = LH
>
>   \change Staff = "LH" <> s4| % m01
>
>   I have attached a screenshot of the first three bars of the harp score of 
> Swan Lake, my LIlypond source code and the result of my engraving attempt.
>
>   I don't think that there's anything wrong with Lilypond, and there's 
> nothing wrong with the documentation, but this Lilypond user is a bit dense.
>
>   If I can just get the first bar engraving correctly, I think I can make it 
> the rest of the way :-)
>
> Thanks,
> Ken Wolcott
>



RE: Learning how to use "\change Staff"; don't get it yet, obviously

2022-07-30 Thread Mark Stephen Mrotek
Kenneth,

Not dense at all.
Change staff works within a single voice. You split it between rh and lh. Might 
suggest you use "upper" and "lower" for staff designation if you use rh and lh 
as variable names.

Assuming you start in "lower" with lh.
Then 
\tuplet 3/2 { b,8(d b }
  \change Staff = "upper"   %% now continue with what you want in "upper"
{ d'8 fs' b' } \tuplet 3/2 { d''8 b' fs' }
  \change Staff = "lower"   %% and so on.

Note: that rh must contain spacers all the while so that the voice can move 
back and forth without collisions.

Mark

-Original Message-
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] 
On Behalf Of Kenneth Wolcott
Sent: Saturday, July 30, 2022 2:49 PM
To: Lily Pond 
Subject: Learning how to use "\change Staff"; don't get it yet, obviously

Hi;

  I'm learning how to engrave music that changes from one staff to another.

  I, obviously, do not understand yet how to do this, even after reading the 
pertinent section in the Notation Reference.

  My attempt to engrave the first three bars of the harp score of Swan Lake 
fails with the following:

Swan_Lake.ly:40:3: warning: cannot find context to change to: Staff = RH

  \change Staff = "RH"
Swan_Lake.ly:22:3: warning: cannot find context to change to: Staff = LH

  \change Staff = "LH" <> s4| % m01

  I have attached a screenshot of the first three bars of the harp score of 
Swan Lake, my LIlypond source code and the result of my engraving attempt.

  I don't think that there's anything wrong with Lilypond, and there's nothing 
wrong with the documentation, but this Lilypond user is a bit dense.

  If I can just get the first bar engraving correctly, I think I can make it 
the rest of the way :-)

Thanks,
Ken Wolcott




Re: Change staff and cross staff

2020-11-07 Thread Knute Snortum
Yes, that does it.  Thanks!

--
Knute Snortum


On Sat, Nov 7, 2020 at 2:38 PM damianlegassick  wrote:
>
> urgh
>
> and you'll have to add
>
> \once \override Dots.stencil = ##f
>
> just before the gis8.
>
> Damian
>
> On 7 November 2020 at 22:33, damianlegassick  wrote:
>
> fiddly one this
>
> \version "2.21.7"
>
> \layout {
> \context {
> \PianoStaff
> \consists #Span_stem_engraver
> }
> }
>
> rhmusic = {
> \time 3/4
> \key e \major
> \change Staff = "lower"
> \stemUp
> 8[ r16
> \change Staff = "upper"
> e'16]
>
> }
>
> lhmusic = {
> \key e \major
> \clef "bass"
> <<
> {
> \once \omit Stem
> \once \omit Beam
> \slurDown
> gis8.( \crossStaff {b16)}
> }
> \\
> {
> e,4
> }
> >>
> }
>
> \new PianoStaff {
> <<
> \new Staff = "upper" {\rhmusic}
> \new Staff = "lower"{\lhmusic}
> >>
>
> }
>
> On 7 November 2020 at 22:04, Knute Snortum  wrote:
>
> Oh, this is so close! The snippet provided doesn't have the slur from
> the lower g sharp to the b in it, so I tried adding it. The b is in
> the lower hand so I tried slurring to the e and then use \shape to fix
> it, but it produces a programming error. Here's the modified
> snippet...
>
> %%% Start
> \version "2.21.7"
>
> \layout { \context { \PianoStaff \consists #Span_stem_engraver } }
>
> rhmusic = {
> \time 3/4 \key e \major
> \change Staff = "lower"
> \stemUp 8[( r16 % added start paren
> \change Staff = "upper" e'16]) % added end paren
> }
>
> lhmusic = {
> \key e \major
> \clef "bass"
> << { s8. \crossStaff {b16} } \\ { e,4 } >>
> }
>
> \new PianoStaff
> <<
> \new Staff = "upper" {\rhmusic}
> \new Staff = "lower"{\lhmusic}
>
>
> %%% End
>
> ...and here's the output I get:
>
> Starting lilypond 2.21.80 [Untitled (2)]...
> Processing `/tmp/frescobaldi-l36z197r/tmplwcszgtc/document.ly'
> Parsing...
> Interpreting music...
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...lilypond:
> /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.22/flower/include/interval.hh:256:
> T Interval_t::center() const [with T = double]: Assertion
> `!is_empty ()' failed.
> Exited with return code 6.
>
> --
> Knute Snortum
>
> On Sat, Nov 7, 2020 at 1:32 PM Knute Snortum  wrote:
>
>
> That looks good! Thanks!
>
>
> --
>
> Knute Snortum
>
>
>
> On Sat, Nov 7, 2020 at 11:09 AM damianlegassick  
> wrote:
>
> >
>
> > Try this for starters
>
> >
>
> > \version "2.21.7"
>
> >
>
> > \layout { \context { \PianoStaff \consists #Span_stem_engraver } }
>
> >
>
> > rhmusic = {
>
> > time 3/4 \key e \major
>
> > \change Staff = "lower"
>
> > \stemUp 8[ r16
>
> > \change Staff = "upper" e'16]
>
> > }
>
> >
>
> > lhmusic = {
>
> > \key e \major
>
> > \clef "bass"
>
> > << { s8. \crossStaff {b16} } \\ { e,4 } >>
>
> > }
>
> >
>
> > \new PianoStaff {
>
> > <<
>
> > \new Staff = "upper" {\rhmusic}
>
> > \new Staff = "lower"{\lhmusic}
>
> > >>
>
> > }
>
> >
>
> > On 7 November 2020 at 19:04, Knute Snortum  wrote:
>
> >
>
> > Here's a better MWE with my try using voices in the left hand:
>
> >
>
> > %%% Start
>
> > \version "2.20.0"
>
> > \language "english"
>
> >
>
> > staffUp = \change Staff = "upper"
>
> > staffDown = \change Staff = "lower"
>
> >
>
> > rh = \relative c' {
>
> > s8. \crossStaff e16
>
> > }
>
> >
>
> > lh = \relative c' {
>
> > \clef bass
>
> > << { 8[ r16 b] } \\ { e,,4 } >>
>
> > }
>
> >
>
> > \score {
>
> > \new PianoStaff <<
>
> > \new Staff = "upper" { \rh }
>
> > \new Staff = "lower" { \lh }
>
> > >>
>
> > \layout {
>
> > \context {
>
> > \PianoStaff
>
> > \consists #Span_stem_engraver
>
> > }
>
> > }
>
> > }
>
> > %%% End
>
> >
>
> > --
>
> > Knute Snortum
>
> >
>
> > On Sat, Nov 7, 2020 at 10:48 AM Knute Snortum  wrote:
>
> >
>
> >
>
> > I have a tricky measure in the Chopin Mazurka I'm working on. The
>
> >
>
> > notes need to be on the lower staff (from the right hand) and the last
>
> >
>
> > chord is cross staff. I'd like to be able to do something like
>
> >
>
> > this...
>
> >
>
> >
>
> > %%% Start
>
> >
>
> > \version "2.20.0"
>
> >
>
> >
>
> > staffUp = \change Staff = "upper"
>
> >
>
> > staffDown = \change Staff = "lower"
>
> >
>
> >
>
> > \relative c, {
>
> >
>
> > \staffDown 8[ r16 
>
> >
>
> > }
>
> >
>
> > %%% End
>
> >
>
> >
>
> > ..but of course that doesn't work. I tried something with two voices
>
> >
>
> > in the left hand, but ran into problems. I've attached a screenshot
>
> >
>
> > of the measure.
>
> >
>
> >
>
> > --
>
> >
>
> > Knute Snortum
>
> >
>
> >



Re: Change staff and cross staff

2020-11-07 Thread Lukas-Fabian Moser

Hi Knute,

Am 07.11.20 um 20:02 schrieb Knute Snortum:

Here's a better MWE with my try using voices in the left hand:

%%% Start
\version "2.20.0"
\language "english"

staffUp   = \change Staff = "upper"
staffDown = \change Staff = "lower"

rh = \relative c' {
   s8. \crossStaff e16
}

lh = \relative c' {
   \clef bass
   << { 8[ r16 b] } \\ { e,,4 } >>
}

\score {
   \new PianoStaff <<
 \new Staff = "upper" { \rh }
 \new Staff = "lower" { \lh }
   >>
   \layout {
 \context {
   \PianoStaff
   \consists #Span_stem_engraver
 }
   }
}
%%% End


My take, of course not so terribly different from Damian's solution:

\version "2.21.1"

\layout {
  \context {
    \PianoStaff
    \consists Span_stem_engraver
  }
}

rhmusic = {
  \time 3/4
  \key e \major
  <<
    {
  \change Staff = "lower"
  \voiceOne
  b8[ r16
  % Uncomment for alternative solution:
  % 8[ r16
  \change Staff = "upper"
  \crossStaff e'16]
    }
    \new Voice
    {
  \change Staff = "lower"
  % Uncomment for alternative solution:
  % \once\omit Stem
  \voiceOne gis4*3/4_( \crossStaff b16)
    }
  >>
  4 ->
}

lhmusic = {
  \key e \major
  \clef "bass"
  \once \voiceTwo e,4 4 q->
}

\new PianoStaff
<<
  \new Staff = "upper" { \rhmusic }
  \new Staff = "lower"{ \lhmusic }
>>

I admit it's a bit longer, but I'd prefer to keep the magic inside the 
\rhmusic variable.


The alternative solution might be cleaner: It's a matter of either
- faking an actual chord by letting a crotchet's stem melt into a 
quaver's stem, or

- (alternative solution) doubling a notehead.

Lukas




Re: Change staff and cross staff

2020-11-07 Thread damianlegassick

urgh


and you'll have to add


\once \override Dots.stencil = ##f


just before the gis8.


Damian

On 7 November 2020 at 22:33, damianlegassick  wrote:


fiddly one this


\version "2.21.7"

\layout {
\context {
\PianoStaff
\consists #Span_stem_engraver
}
}

rhmusic = {
\time 3/4
\key e \major
\change Staff = "lower"
\stemUp
8[ r16
\change Staff = "upper"
e'16]

}

lhmusic = {
\key e \major
\clef "bass"
<<
{
\once \omit Stem
\once \omit Beam
\slurDown
gis8.( \crossStaff {b16)}
}
\\
{
e,4
}



}

\new PianoStaff {
<<
\new Staff = "upper" {\rhmusic}
\new Staff = "lower"{\lhmusic}




}

On 7 November 2020 at 22:04, Knute Snortum  wrote:


Oh, this is so close! The snippet provided doesn't have the slur from
the lower g sharp to the b in it, so I tried adding it. The b is in
the lower hand so I tried slurring to the e and then use \shape to fix
it, but it produces a programming error. Here's the modified
snippet...

%%% Start
\version "2.21.7"

\layout { \context { \PianoStaff \consists #Span_stem_engraver } }

rhmusic = {
\time 3/4 \key e \major
\change Staff = "lower"
\stemUp 8[( r16 % added start paren
\change Staff = "upper" e'16]) % added end paren
}

lhmusic = {
\key e \major
\clef "bass"
<< { s8. \crossStaff {b16} } \\ { e,4 } >>
}

\new PianoStaff
<<
\new Staff = "upper" {\rhmusic}
\new Staff = "lower"{\lhmusic}



%%% End

...and here's the output I get:

Starting lilypond 2.21.80 [Untitled (2)]...
Processing `/tmp/frescobaldi-l36z197r/tmplwcszgtc/document.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...lilypond:
/home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.22/flower/include/interval.hh:256:
T Interval_t::center() const [with T = double]: Assertion
`!is_empty ()' failed.
Exited with return code 6.

--
Knute Snortum

On Sat, Nov 7, 2020 at 1:32 PM Knute Snortum  wrote:



That looks good! Thanks!


--
Knute Snortum




On Sat, Nov 7, 2020 at 11:09 AM damianlegassick  wrote:


Try this for starters

\version "2.21.7"

\layout { \context { \PianoStaff \consists #Span_stem_engraver } }

rhmusic = {
time 3/4 \key e \major
\change Staff = "lower"
\stemUp 8[ r16
\change Staff = "upper" e'16]
}

lhmusic = {
\key e \major
\clef "bass"
<< { s8. \crossStaff {b16} } \\ { e,4 } >>
}

\new PianoStaff {
<<
\new Staff = "upper" {\rhmusic}
\new Staff = "lower"{\lhmusic}
>>
}

On 7 November 2020 at 19:04, Knute Snortum  wrote:

Here's a better MWE with my try using voices in the left hand:

%%% Start
\version "2.20.0"
\language "english"

staffUp = \change Staff = "upper"
staffDown = \change Staff = "lower"

rh = \relative c' {
s8. \crossStaff e16
}

lh = \relative c' {
\clef bass
<< { 8[ r16 b] } \\ { e,,4 } >>
}

\score {
\new PianoStaff <<
\new Staff = "upper" { \rh }
\new Staff = "lower" { \lh }
>>
\layout {
\context {
\PianoStaff
\consists #Span_stem_engraver
}
}
}
%%% End

--
Knute Snortum

On Sat, Nov 7, 2020 at 10:48 AM Knute Snortum  wrote:


I have a tricky measure in the Chopin Mazurka I'm working on. The

notes need to be on the lower staff (from the right hand) and the last

chord is cross staff. I'd like to be able to do something like

this...


%%% Start

\version "2.20.0"


staffUp = \change Staff = "upper"

staffDown = \change Staff = "lower"


\relative c, {

\staffDown 8[ r16 

}

%%% End


..but of course that doesn't work. I tried something with two voices

in the left hand, but ran into problems. I've attached a screenshot

of the measure.


--

Knute Snortum



Re: Change staff and cross staff

2020-11-07 Thread damianlegassick

fiddly one this


\version "2.21.7"

\layout {
\context {
\PianoStaff
\consists #Span_stem_engraver
}
}

rhmusic = {
\time 3/4
\key e \major
\change Staff = "lower"
\stemUp
8[ r16
\change Staff = "upper"
e'16]

}

lhmusic = {
\key e \major
\clef "bass"
<<
{
\once \omit Stem
\once \omit Beam
\slurDown
gis8.( \crossStaff {b16)}
}
\\
{
e,4
}



}

\new PianoStaff {
<<
\new Staff = "upper" {\rhmusic}
\new Staff = "lower"{\lhmusic}




}

On 7 November 2020 at 22:04, Knute Snortum  wrote:


Oh, this is so close! The snippet provided doesn't have the slur from
the lower g sharp to the b in it, so I tried adding it. The b is in
the lower hand so I tried slurring to the e and then use \shape to fix
it, but it produces a programming error. Here's the modified
snippet...

%%% Start
\version "2.21.7"

\layout { \context { \PianoStaff \consists #Span_stem_engraver } }

rhmusic = {
\time 3/4 \key e \major
\change Staff = "lower"
\stemUp 8[( r16 % added start paren
\change Staff = "upper" e'16]) % added end paren
}

lhmusic = {
\key e \major
\clef "bass"
<< { s8. \crossStaff {b16} } \\ { e,4 } >>
}

\new PianoStaff
<<
\new Staff = "upper" {\rhmusic}
\new Staff = "lower"{\lhmusic}



%%% End

...and here's the output I get:

Starting lilypond 2.21.80 [Untitled (2)]...
Processing `/tmp/frescobaldi-l36z197r/tmplwcszgtc/document.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...lilypond:
/home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.22/flower/include/interval.hh:256:
T Interval_t::center() const [with T = double]: Assertion
`!is_empty ()' failed.
Exited with return code 6.

--
Knute Snortum

On Sat, Nov 7, 2020 at 1:32 PM Knute Snortum  wrote:



That looks good! Thanks!


--
Knute Snortum




On Sat, Nov 7, 2020 at 11:09 AM damianlegassick  wrote:


Try this for starters

\version "2.21.7"

\layout { \context { \PianoStaff \consists #Span_stem_engraver } }

rhmusic = {
time 3/4 \key e \major
\change Staff = "lower"
\stemUp 8[ r16
\change Staff = "upper" e'16]
}

lhmusic = {
\key e \major
\clef "bass"
<< { s8. \crossStaff {b16} } \\ { e,4 } >>
}

\new PianoStaff {
<<
\new Staff = "upper" {\rhmusic}
\new Staff = "lower"{\lhmusic}
>>
}

On 7 November 2020 at 19:04, Knute Snortum  wrote:

Here's a better MWE with my try using voices in the left hand:

%%% Start
\version "2.20.0"
\language "english"

staffUp = \change Staff = "upper"
staffDown = \change Staff = "lower"

rh = \relative c' {
s8. \crossStaff e16
}

lh = \relative c' {
\clef bass
<< { 8[ r16 b] } \\ { e,,4 } >>
}

\score {
\new PianoStaff <<
\new Staff = "upper" { \rh }
\new Staff = "lower" { \lh }
>>
\layout {
\context {
\PianoStaff
\consists #Span_stem_engraver
}
}
}
%%% End

--
Knute Snortum

On Sat, Nov 7, 2020 at 10:48 AM Knute Snortum  wrote:


I have a tricky measure in the Chopin Mazurka I'm working on. The

notes need to be on the lower staff (from the right hand) and the last

chord is cross staff. I'd like to be able to do something like

this...


%%% Start

\version "2.20.0"


staffUp = \change Staff = "upper"

staffDown = \change Staff = "lower"


\relative c, {

\staffDown 8[ r16 

}

%%% End


..but of course that doesn't work. I tried something with two voices

in the left hand, but ran into problems. I've attached a screenshot

of the measure.


--

Knute Snortum



Re: Change staff and cross staff

2020-11-07 Thread Knute Snortum
Oh, this is so close!  The snippet provided doesn't have the slur from
the lower g sharp to the b in it, so I tried adding it.  The b is in
the lower hand so I tried slurring to the e and then use \shape to fix
it, but it produces a programming error.  Here's the modified
snippet...

%%% Start
\version "2.21.7"

\layout { \context { \PianoStaff \consists #Span_stem_engraver } }

rhmusic = {
\time 3/4 \key e \major
\change Staff = "lower"
\stemUp 8[( r16 % added start paren
\change Staff = "upper" e'16]) % added end paren
}

lhmusic = {
\key e \major
\clef "bass"
<< { s8. \crossStaff {b16} } \\ { e,4 } >>
}

\new PianoStaff
<<
\new Staff = "upper" {\rhmusic}
\new Staff = "lower"{\lhmusic}
>>
%%% End

...and here's the output I get:

Starting lilypond 2.21.80 [Untitled (2)]...
Processing `/tmp/frescobaldi-l36z197r/tmplwcszgtc/document.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...lilypond:
/home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.22/flower/include/interval.hh:256:
T Interval_t::center() const [with T = double]: Assertion
`!is_empty ()' failed.
Exited with return code 6.

--
Knute Snortum

On Sat, Nov 7, 2020 at 1:32 PM Knute Snortum  wrote:
>
> That looks good!  Thanks!
>
> --
> Knute Snortum
>
>
> On Sat, Nov 7, 2020 at 11:09 AM damianlegassick  
> wrote:
> >
> > Try this for starters
> >
> > \version "2.21.7"
> >
> > \layout { \context { \PianoStaff \consists #Span_stem_engraver } }
> >
> > rhmusic = {
> > time 3/4 \key e \major
> > \change Staff = "lower"
> > \stemUp 8[ r16
> > \change Staff = "upper" e'16]
> > }
> >
> > lhmusic = {
> > \key e \major
> > \clef "bass"
> > << { s8. \crossStaff {b16} } \\ { e,4 } >>
> > }
> >
> > \new PianoStaff {
> > <<
> > \new Staff = "upper" {\rhmusic}
> > \new Staff = "lower"{\lhmusic}
> > >>
> > }
> >
> > On 7 November 2020 at 19:04, Knute Snortum  wrote:
> >
> > Here's a better MWE with my try using voices in the left hand:
> >
> > %%% Start
> > \version "2.20.0"
> > \language "english"
> >
> > staffUp = \change Staff = "upper"
> > staffDown = \change Staff = "lower"
> >
> > rh = \relative c' {
> > s8. \crossStaff e16
> > }
> >
> > lh = \relative c' {
> > \clef bass
> > << { 8[ r16 b] } \\ { e,,4 } >>
> > }
> >
> > \score {
> > \new PianoStaff <<
> > \new Staff = "upper" { \rh }
> > \new Staff = "lower" { \lh }
> > >>
> > \layout {
> > \context {
> > \PianoStaff
> > \consists #Span_stem_engraver
> > }
> > }
> > }
> > %%% End
> >
> > --
> > Knute Snortum
> >
> > On Sat, Nov 7, 2020 at 10:48 AM Knute Snortum  wrote:
> >
> >
> > I have a tricky measure in the Chopin Mazurka I'm working on. The
> >
> > notes need to be on the lower staff (from the right hand) and the last
> >
> > chord is cross staff. I'd like to be able to do something like
> >
> > this...
> >
> >
> > %%% Start
> >
> > \version "2.20.0"
> >
> >
> > staffUp = \change Staff = "upper"
> >
> > staffDown = \change Staff = "lower"
> >
> >
> > \relative c, {
> >
> > \staffDown 8[ r16 
> >
> > }
> >
> > %%% End
> >
> >
> > ..but of course that doesn't work. I tried something with two voices
> >
> > in the left hand, but ran into problems. I've attached a screenshot
> >
> > of the measure.
> >
> >
> > --
> >
> > Knute Snortum
> >
> >



Re: Change staff and cross staff

2020-11-07 Thread Knute Snortum
That looks good!  Thanks!

--
Knute Snortum


On Sat, Nov 7, 2020 at 11:09 AM damianlegassick  wrote:
>
> Try this for starters
>
> \version "2.21.7"
>
> \layout { \context { \PianoStaff \consists #Span_stem_engraver } }
>
> rhmusic = {
> time 3/4 \key e \major
> \change Staff = "lower"
> \stemUp 8[ r16
> \change Staff = "upper" e'16]
> }
>
> lhmusic = {
> \key e \major
> \clef "bass"
> << { s8. \crossStaff {b16} } \\ { e,4 } >>
> }
>
> \new PianoStaff {
> <<
> \new Staff = "upper" {\rhmusic}
> \new Staff = "lower"{\lhmusic}
> >>
> }
>
> On 7 November 2020 at 19:04, Knute Snortum  wrote:
>
> Here's a better MWE with my try using voices in the left hand:
>
> %%% Start
> \version "2.20.0"
> \language "english"
>
> staffUp = \change Staff = "upper"
> staffDown = \change Staff = "lower"
>
> rh = \relative c' {
> s8. \crossStaff e16
> }
>
> lh = \relative c' {
> \clef bass
> << { 8[ r16 b] } \\ { e,,4 } >>
> }
>
> \score {
> \new PianoStaff <<
> \new Staff = "upper" { \rh }
> \new Staff = "lower" { \lh }
> >>
> \layout {
> \context {
> \PianoStaff
> \consists #Span_stem_engraver
> }
> }
> }
> %%% End
>
> --
> Knute Snortum
>
> On Sat, Nov 7, 2020 at 10:48 AM Knute Snortum  wrote:
>
>
> I have a tricky measure in the Chopin Mazurka I'm working on. The
>
> notes need to be on the lower staff (from the right hand) and the last
>
> chord is cross staff. I'd like to be able to do something like
>
> this...
>
>
> %%% Start
>
> \version "2.20.0"
>
>
> staffUp = \change Staff = "upper"
>
> staffDown = \change Staff = "lower"
>
>
> \relative c, {
>
> \staffDown 8[ r16 
>
> }
>
> %%% End
>
>
> ..but of course that doesn't work. I tried something with two voices
>
> in the left hand, but ran into problems. I've attached a screenshot
>
> of the measure.
>
>
> --
>
> Knute Snortum
>
>



Re: Change staff and cross staff

2020-11-07 Thread damianlegassick

Try this for starters


\version "2.21.7"

\layout { \context { \PianoStaff \consists #Span_stem_engraver } }

rhmusic = {
time 3/4 \key e \major
\change Staff = "lower"
\stemUp 8[ r16
\change Staff = "upper" e'16]
}

lhmusic = {
\key e \major
\clef "bass"
<< { s8. \crossStaff {b16} } \\ { e,4 } >>
}

\new PianoStaff {
<<
\new Staff = "upper" {\rhmusic}
\new Staff = "lower"{\lhmusic}



}

On 7 November 2020 at 19:04, Knute Snortum  wrote:


Here's a better MWE with my try using voices in the left hand:

%%% Start
\version "2.20.0"
\language "english"

staffUp = \change Staff = "upper"
staffDown = \change Staff = "lower"

rh = \relative c' {
s8. \crossStaff e16
}

lh = \relative c' {
\clef bass
<< { 8[ r16 b] } \\ { e,,4 } >>
}

\score {
\new PianoStaff <<
\new Staff = "upper" { \rh }
\new Staff = "lower" { \lh }



\layout {
\context {
\PianoStaff
\consists #Span_stem_engraver
}
}
}
%%% End

--
Knute Snortum

On Sat, Nov 7, 2020 at 10:48 AM Knute Snortum  wrote:



I have a tricky measure in the Chopin Mazurka I'm working on. The
notes need to be on the lower staff (from the right hand) and the last
chord is cross staff. I'd like to be able to do something like
this...


%%% Start
\version "2.20.0"


staffUp = \change Staff = "upper"
staffDown = \change Staff = "lower"


\relative c, {
\staffDown 8[ r16 
}
%%% End


..but of course that doesn't work. I tried something with two voices
in the left hand, but ran into problems. I've attached a screenshot
of the measure.


--
Knute Snortum



Re: Change staff and cross staff

2020-11-07 Thread Knute Snortum
Here's a better MWE with my try using voices in the left hand:

%%% Start
\version "2.20.0"
\language "english"

staffUp   = \change Staff = "upper"
staffDown = \change Staff = "lower"

rh = \relative c' {
  s8. \crossStaff e16
}

lh = \relative c' {
  \clef bass
  << { 8[ r16 b] } \\ { e,,4 } >>
}

\score {
  \new PianoStaff <<
\new Staff = "upper" { \rh }
\new Staff = "lower" { \lh }
  >>
  \layout {
\context {
  \PianoStaff
  \consists #Span_stem_engraver
}
  }
}
%%% End

--
Knute Snortum

On Sat, Nov 7, 2020 at 10:48 AM Knute Snortum  wrote:
>
> I have a tricky measure in the Chopin Mazurka I'm working on.  The
> notes need to be on the lower staff (from the right hand) and the last
> chord is cross staff.  I'd like to be able to do something like
> this...
>
> %%% Start
> \version "2.20.0"
>
> staffUp   = \change Staff = "upper"
> staffDown = \change Staff = "lower"
>
> \relative c, {
>   \staffDown 8[ r16 
> }
> %%% End
>
> ..but of course that doesn't work.  I tried something with two voices
> in the left hand, but ran into problems.  I've attached a screenshot
> of the measure.
>
> --
> Knute Snortum



Change staff and cross staff

2020-11-07 Thread Knute Snortum
I have a tricky measure in the Chopin Mazurka I'm working on.  The
notes need to be on the lower staff (from the right hand) and the last
chord is cross staff.  I'd like to be able to do something like
this...

%%% Start
\version "2.20.0"

staffUp   = \change Staff = "upper"
staffDown = \change Staff = "lower"

\relative c, {
  \staffDown 8[ r16 
}
%%% End

..but of course that doesn't work.  I tried something with two voices
in the left hand, but ran into problems.  I've attached a screenshot
of the measure.

--
Knute Snortum


Re: Change staff and dynamics position

2020-09-30 Thread Aaron Hill

On 2020-09-30 1:09 pm, Philippe Auclair wrote:

Oups... Sorry, here are the pdf files.

In the following example, in the piano left staff music, \clef "bass"
is BEFORE \dynamicUp : the score goes completely wild ! (1st attached
pdf).
If \clef "bass" is AFTER \dynamicUp, the score is correct (2nd pdf).
Is there an explanation?


Looks like some unexpected interaction with implicit Voice creation.

Explicitly creating voices seems to help:


% . . .
  \new Staff = "PianoRight" \new Voice { \PianoRightMusic }
  \new Staff = "PianoLeft" \new Voice { \PianoLeftMusic }
% . . .



-- Aaron Hill



Re: Change staff and dynamics position

2020-09-30 Thread Philippe Auclair

Oups... Sorry, here are the pdf files.

In the following example, in the piano left staff music, \clef "bass" is 
BEFORE \dynamicUp : the score goes completely wild ! (1st attached pdf).

If \clef "bass" is AFTER \dynamicUp, the score is correct (2nd pdf).
Is there an explanation?

Philippe Auclair

% This is the beginning of the piano part of
% Jules Massenet, Chansons des bois d'Amaranthe N°5, Chantez !
% Graver: Philippe Auclair
% If \clef "bass" is set before \dynamicUp, piano left staff is wrong
% If \dynamicUp is set before \clef "bass", piano left staff becomes correct

\version "2.20.0"
\include "italiano.ly"

PianoRightMusic = \relative do {
\key sib \major
\time 2/4

\change Staff = "PianoLeft" \voiceOne fa8^.^^[
   \change Staff = "PianoRight" \oneVoice
   r16 ^^] 4 ~
8[ r16 ^^~] 4
}

PianoLeftMusic = \relative do {
\clef "bass"
\dynamicUp
\key sib \major
\time 2/4

\voiceTwo 8^.^^ \oneVoice r8 \clef treble 4^^ ~
8 r 4^^
}

\score {
\new PianoStaff {
  <<
  \new Staff = "PianoRight" { \PianoRightMusic }
  \new Staff = "PianoLeft" { \PianoLeftMusic }
  >>
}
}


change-staff-bug-1.pdf
Description: Adobe PDF document


change-staff-bug-2.pdf
Description: Adobe PDF document


Change staff and dynamics position

2020-09-30 Thread Philippe Auclair

Hi,

In the following example, in the piano left staff music, \clef "bass" is 
BEFORE \dynamicUp : the score goes completely wild ! (1st attached pdf).

If \clef "bass" is AFTER \dynamicUp, the score is correct (2nd pdf).
Is there an explanation?

Philippe Auclair

% This is the beginning of the piano part of
% Jules Massenet, Chansons des bois d'Amaranthe N°5, Chantez !
% Graver: Philippe Auclair
% If \clef "bass" is set before \dynamicUp, piano left staff is wrong
% If \dynamicUp is set before \clef "bass", piano left staff becomes correct

\version "2.20.0"
\include "italiano.ly"

PianoRightMusic = \relative do {
\key sib \major
\time 2/4

    \change Staff = "PianoLeft" \voiceOne fa8^.^^[
   \change Staff = "PianoRight" \oneVoice
   r16 ^^] 4 ~
8[ r16 ^^~] 4
}

PianoLeftMusic = \relative do {
\clef "bass"
\dynamicUp
\key sib \major
\time 2/4

\voiceTwo 8^.^^ \oneVoice r8 \clef treble 4^^ ~
8 r 4^^
}

\score {
\new PianoStaff {
  <<
  \new Staff = "PianoRight" { \PianoRightMusic }
  \new Staff = "PianoLeft" { \PianoLeftMusic }
  >>
}
}



collision between beam and lyrics when using \change Staff

2019-08-19 Thread mason
I am using `\change Staff` to manually switch between the staves of a
PianoStaff, as per.[1]

Above the piano staff is a voice part with lyrics. The beams of the
piano part collide with the lyrics of the voice part. If I do not use
`\change Staff` then the collision does not occur.

%%% begin MWE %%%
\version "2.21.0"

% collision between beam and lyrics
\score {
  <<
\new Staff \relative c' { c'4 c c }
\addlyrics { foo bar foo }
\new PianoStaff <<
  \new Staff = "up"
  \relative c' {
s2. |
  }
  \new Staff = "down"
  \relative c' {
\clef bass
    \time 3/4
c,,8  c' \change Staff = "up" c' c' c' c,
  }
>>
  >>
}

% no collision
\score {
  <<
\new Staff \relative c' { c'4 c c }
\addlyrics { foo bar foo }
\new PianoStaff <<
  \new Staff = "up"
  \relative c' {
\override Beam.direction = #UP
s4 c'8 c' c' c,
  }
  \new Staff = "down"
  \relative c' {
\clef bass
\time 3/4
c,,8  c' s2
  }
    >>
  >>
}
%%% end MWE %%%

How can I avoid collisions between beams and lyrics while using `\change
Staff`?

Thanks,

Mason

[1] 
http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-keyboards#changing-staff-manually


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


Re: Change staff clef immediately after time signature

2019-02-04 Thread Christopher R. Maden

On 2/4/19 10:18 AM, Aaron Hill wrote:

I overlooked \cueClefUnset so that's the better option.

For the grob, the Internals reference is your friend: CueEndClef


Thanks!  I really need to get more familiar with the internals 
reference.  One of these days in my copious free time.


David, thanks for the \grace suggestion — interestingly, when I tried 
it, the new clef overlapped the time signature, not the primary clefs, 
and I didn’t get the weird doubling in the right hand.


I’m still a little surprised that LilyPond doesn’t have a setting 
somewhere to explicitly place clefs regardless of propriety, similar to 
the way one can force an accidental.  Nonetheless, this is a great 
solution for now — thanks, Aaron and David (and everyone who has helped 
make this such an amazing piece of software).


~Chris
--
Chris Maden, text nerd
http://crism.maden.org/ >
Emperor Norton had the right idea.

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


Re: Change staff clef immediately after time signature

2019-02-04 Thread Aaron Hill

On 2019-02-04 6:47 am, Christopher R. Maden wrote:

On 2/4/19 6:03 AM, Aaron Hill wrote:
Note in this case I changed the CueClef font-size to match the reduced 
size of a non-cue clef when it appears within a line.


That looks great, thanks!  The \cueClefUnset bass clef still looks
tiny, and if I use \cueClef to switch back to bass, it shows up in
every line...  If I switch back with \cueClef bass, but then use
\cueClefUnset later, I get a redundant tiny bass clef, and if I use
\cueClef bass immediately followed by \cueClefUnset, the unset
supersedes the set, and I get a tiny clef.

I tried the naïve override: \override CueClefUnset.font-size = #-2 but
that has no apparent effect.  What’s the grob used to produce the clef
at an unset event?


I overlooked \cueClefUnset so that's the better option.

For the grob, the Internals reference is your friend: CueEndClef

-- Aaron Hill

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


Re: Change staff clef immediately after time signature

2019-02-04 Thread Christopher R. Maden

On 2/4/19 6:03 AM, Aaron Hill wrote:
Note in this case I changed the CueClef font-size to match the reduced 
size of a non-cue clef when it appears within a line.


That looks great, thanks!  The \cueClefUnset bass clef still looks tiny, 
and if I use \cueClef to switch back to bass, it shows up in every 
line...  If I switch back with \cueClef bass, but then use \cueClefUnset 
later, I get a redundant tiny bass clef, and if I use \cueClef bass 
immediately followed by \cueClefUnset, the unset supersedes the set, and 
I get a tiny clef.


I tried the naïve override: \override CueClefUnset.font-size = #-2 but 
that has no apparent effect.  What’s the grob used to produce the clef 
at an unset event?


~Chris
--
Chris Maden, text nerd
http://crism.maden.org/ >
Emperor Norton had the right idea.

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


Re: Change staff clef immediately after time signature

2019-02-04 Thread David Kastrup
"Christopher R. Maden"  writes:

> This is probably a FAQ, but I can’t find the right combination of
> search terms to tease it from the ether...
>
> I want a piano staff, with the left hand to start with bass clef, but
> then immediately switch to treble clef after the time signature.
>
> Mnon-WE is attached.  Probably this involves monkeying with the clef
> engraver, but I haven’t figured out how.

Here is an attempt that would still suffer from issue 34 but even if you
fix that, the spacing is insane.

\version "2.18.2"

\include "english.ly"

\new PianoStaff <<
  \new Staff {
\clef treble
\key d \major
\time 4/4
d''4 d'' d'' d''
  }
  \new Staff {
\clef bass
\key d \major
\time 4/4
\grace s4 \clef treble
d'4 d' d' d'
  }
>>


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


Re: Change staff clef immediately after time signature

2019-02-04 Thread Aaron Hill

On 2019-02-03 8:44 pm, Christopher R. Maden wrote:

On 2/3/19 9:43 PM, Aaron Hill wrote:

Does \cueClef help?


It does... though then when I \clef bass back again it’s ignored.  I
can use \cueClefUnset...

Thanks, this is a great workaround.  I suspect there is a better (more
properly LilyPondish) answer, but this is more than adequate for now.


Simply use \cueClef again when switching back to bass:


\version "2.19.82"

rh = \relative c'' { c2 a | b g }
lh = \relative a' { a4 f d b | g4 e c a }

% Using \clef only.
\new PianoStaff <<
  \new Staff << { \clef treble } \rh >>
  \new Staff << { \clef treble s1 \clef bass } \lh >>




% Using \clef and \cueClef together.
\new PianoStaff <<
  \new Staff << { \clef treble } \rh >>
  \new Staff \with { \override CueClef.font-size = #-2 }
<< { \clef bass \cueClef treble s1 \cueClef bass } \lh >>





Note in this case I changed the CueClef font-size to match the reduced 
size of a non-cue clef when it appears within a line.



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


Re: Change staff clef immediately after time signature

2019-02-03 Thread Andrew Bernard
HI Chris,

That makes sense. I also like to preserve the composer's own notation where
possible. And as said, it's not actually wrong! Good old Sousa!

Andrew


On Mon, 4 Feb 2019 at 16:43, Christopher R. Maden  wrote:

>
> I’m transcribing Sousa’s “A Typical Tune of Zanzibar,”[*] and I’m trying
> not to change the notation too much unnecessarily.
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Change staff clef immediately after time signature

2019-02-03 Thread Christopher R. Maden

On 2/4/19 12:36 AM, Andrew Bernard wrote:

This comes up reasonably often. May I ask why you don't simply start
the piece with the treble clef? If you immediately change to treble,
what is the point of having the bass clef at this point? It's a
musical decision up to you, but it always strikes me as a bit
unnecessary. Any player will know the lower staff is the left hand,
assuming this is normalish piano music, so there is no need for a
bass clef to remind them. What you want is not wrong. just clumsy,
and adds more visual noise to a score for the brain to deal with.


I’m transcribing Sousa’s “A Typical Tune of Zanzibar,”[*] and I’m trying 
not to change the notation too much unnecessarily.


I also think it kind of makes sense — the lower staff is almost entirely 
in the bass clef, and it makes sense to set that expectation right at 
the start, even if the first two bars are in treble clef.


~Chris

[*] http://levysheetmusic.mse.jhu.edu/collection/073/057 >
--
Chris Maden, text nerd
http://crism.maden.org/ >
Emperor Norton had the right idea.

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


Re: Change staff clef immediately after time signature

2019-02-03 Thread Andrew Bernard
Hi Christopher,

This comes up reasonably often. May I ask why you don't simply start the
piece with the treble clef? If you immediately change to treble, what is
the point of having the bass clef at this point? It's a musical decision up
to you, but it always strikes me as a bit unnecessary. Any player will know
the lower staff is the left hand, assuming this is normalish piano music,
so there is no need for a bass clef to remind them. What you want is not
wrong. just clumsy, and adds more visual noise to a score for the brain to
deal with.

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


Re: Change staff clef immediately after time signature

2019-02-03 Thread Christopher R. Maden

On 2/3/19 9:43 PM, Aaron Hill wrote:

Does \cueClef help?


It does... though then when I \clef bass back again it’s ignored.  I can 
use \cueClefUnset...


Thanks, this is a great workaround.  I suspect there is a better (more 
properly LilyPondish) answer, but this is more than adequate for now.


Thanks again,
Chris
--
Chris Maden, text nerd
http://crism.maden.org/ >
Emperor Norton had the right idea.

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


Re: Change staff clef immediately after time signature

2019-02-03 Thread Aaron Hill

On 2019-02-03 6:43 pm, Aaron Hill wrote:

On 2019-02-03 6:33 pm, Christopher R. Maden wrote:

This is probably a FAQ, but I can’t find the right combination of
search terms to tease it from the ether...

I want a piano staff, with the left hand to start with bass clef, but
then immediately switch to treble clef after the time signature.

Mnon-WE is attached.  Probably this involves monkeying with the clef
engraver, but I haven’t figured out how.


Does \cueClef help?


\version "2.19.82"

\new PianoStaff <<
  \new Staff { \clef treble b'2 2 }
  \new Staff { \clef bass \cueClef treble b'4 4 4 4 }
>>



And if you want to change the size:


\version "2.19.82"

\new PianoStaff <<
  \new Staff { \clef treble b'2 2 }
  \new Staff { \clef bass
\once \override Staff.CueClef.font-size = #0
\cueClef treble b'4 4 4 4
  }





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


Re: Change staff clef immediately after time signature

2019-02-03 Thread Aaron Hill

On 2019-02-03 6:33 pm, Christopher R. Maden wrote:

This is probably a FAQ, but I can’t find the right combination of
search terms to tease it from the ether...

I want a piano staff, with the left hand to start with bass clef, but
then immediately switch to treble clef after the time signature.

Mnon-WE is attached.  Probably this involves monkeying with the clef
engraver, but I haven’t figured out how.


Does \cueClef help?


\version "2.19.82"

\new PianoStaff <<
  \new Staff { \clef treble b'2 2 }
  \new Staff { \clef bass \cueClef treble b'4 4 4 4 }





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


Change staff clef immediately after time signature

2019-02-03 Thread Christopher R. Maden
This is probably a FAQ, but I can’t find the right combination of search 
terms to tease it from the ether...


I want a piano staff, with the left hand to start with bass clef, but 
then immediately switch to treble clef after the time signature.


Mnon-WE is attached.  Probably this involves monkeying with the clef 
engraver, but I haven’t figured out how.


Thanks in advance,
Chris
--
Chris Maden, text nerd
http://crism.maden.org/ >
Emperor Norton had the right idea.
\version "2.18.2"

\include "english.ly"

\new PianoStaff <<
  \new Staff {
\clef treble
\key d \major
\time 4/4
d''4 d'' d'' d''
  }
  \new Staff {
\clef bass
\key d \major
\time 4/4
\clef treble
d'4 d' d' d'
  }
>>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Different behavior of \partcombine + \change Staff in 2.19

2017-11-12 Thread Shevek
In order to cleanly manage wind parts sharing staves in an orchestral score,
I have been using a pattern like the following throughout my projects:

\paper {
  indent = 2.5\cm
  short-indent = 1.5\cm
}

global = {
  s1*4
  \break
  s1*4
  \break
  s1*4
}

bsnI = \relative {
  \tag #'score {
\partcombineApart
\oneVoice
\dynamicDown
  }
  R1 |
  \resetRelativeOctave c
  c4 d e f |
  g4 f e d |
  R1 |
  \tag #'score \partcombineUnisono
  \resetRelativeOctave c
  c4 d e f |
  g4 f e d |
}

bsnII = \relative {
  \tag #'score {
\change Staff = "Bsn2"
\oneVoice
  }
  \resetRelativeOctave c
  c4 d e f |
  g4 f e d |
  R1*2 |
  c4 d e f |
  g4 f e d |
}

\score {
  \new StaffGroup \with {
instrumentName = "Bassoon  "
shortInstrumentName = "Bsn.  "
  } <<
\new Staff = "Bsn1" \with {
  instrumentName = \markup\column { "1" "2" }
  shortInstrumentName = \markup\column { "1" "2" }
  \clef bass
} << \global \partcombine \bsnI \bsnII >>
\new Staff = "Bsn2" \with {
  instrumentName = "2"
  shortInstrumentName = "2"
  \clef bass
  \override VerticalAxisGroup.remove-empty = ##t
  \override VerticalAxisGroup.remove-first = ##t
} \global
  >>
  \layout {
\context {
  \StaffGroup
  \override InstrumentName.self-alignment-X = #0
}
\context {
  \Staff
  \override InstrumentName.self-alignment-X = #1
}
  }
}

If you compile this in 2.18, it works beautifully because after the
beginning, no further Staff changes are required — the partcombiner
automatically pulls the second part into the primary staff whenever it is
set to unisono, soloII, or chords mode. In 2.19, however, you'll see that
the unison passage displays on both staves, while still putting "a2" above
the primary staff. This changed behavior breaks a tremendous amount of my
code in a way that isn't easy to cleanly fix. Is this change intended? Is
there a way I can salvage the old behavior?

By the way, if you compile my example code above, you might notice "warning:
cannot find context to switch to," yet the actual output finds a context to
switch to just fine. Is there a way to get rid of this? I get hundreds of
these whenever I compile my projects, and it makes it hard to find genuine
errors.

Thanks.



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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


Re: change staff

2017-01-28 Thread Gianmaria Lari
Absolutely agree :) Consider my last code a scheme exercise...

On 28 January 2017 at 09:33, Helge Kruse <helge.kr...@gmx.net> wrote:

> Am 26.01.2017 um 10:51 schrieb Gianmaria Lari:
> > ... and this is one more way to do the change staff using a scheme
> function
> > that toggle between the two staff.
> >
> ...
> > Not sure it can be more useful than the other ones. Also have no idea if
> > this logic should be written differently. But it has been a nice scheme
> > exercise :)
>
> I think it's better to use two switch the staves up and down. If you use
> the same expression for both directions then you have to count the
> instances to see where you are. This makes the Lilypond source less
> readable. On the other side you would get a huge amount of warnings and
> a scrambled output if you miss one of your \cs or misspelled it.
>
> Regards,
> Helge
>
>
> ___
> 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: change staff

2017-01-28 Thread Helge Kruse
Am 26.01.2017 um 10:51 schrieb Gianmaria Lari:
> ... and this is one more way to do the change staff using a scheme function
> that toggle between the two staff.
> 
...
> Not sure it can be more useful than the other ones. Also have no idea if
> this logic should be written differently. But it has been a nice scheme
> exercise :)

I think it's better to use two switch the staves up and down. If you use
the same expression for both directions then you have to count the
instances to see where you are. This makes the Lilypond source less
readable. On the other side you would get a huge amount of warnings and
a scrambled output if you miss one of your \cs or misspelled it.

Regards,
Helge


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


Re: change staff

2017-01-26 Thread Gianmaria Lari
... and this is one more way to do the change staff using a scheme function
that toggle between the two staff.

\version "2.19.54"

#(define staffToggle #f)
cs= #(define-music-function (parser location) ;cs = Change Staff
   ()
   (begin
(set! staffToggle (not staffToggle))
(if staffToggle
    #{ \change Staff = "left" #}
    #{ \change Staff = "right" #})))


right = \fixed c' {
  \clef treble
  \time 2/4
  g8 \cs g \cs e \cs e \cs
}

left = \fixed c' {
  \clef treble
  s2
}

\score {
  \new PianoStaff
  <<
\new Staff = "right" \right
\new Staff = "left"  \left
  >>
  \layout { }
}


Not sure it can be more useful than the other ones. Also have no idea if
this logic should be written differently. But it has been a nice scheme
exercise :)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: change staff

2017-01-25 Thread Gianmaria Lari
Thank you, Malte and Noeck, it works perfectly.

I post here another solution, that is interesting because it doesn't use
scheme and more easy to understand.

\version "2.19.54"
csl = { \change Staff = "left" }
csr = { \change Staff = "right" }

right = \fixed c' {
  \clef treble
  \time 2/4
  g8-4 \csl g_4 \csr e-3 \csl e_3 \csr
  g8-4 \csl g_4 \csr e4-2
  \bar "|."
}

left = \fixed c' {
  \clef treble
  s2
  s4 c_2
}

\score {
  \new PianoStaff
  <<
\new Staff = "right" \right
\new Staff = "left"  \left
  >>
  \layout { }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: change staff

2017-01-25 Thread Noeck
Am 25.01.2017 um 14:38 schrieb SoundsFromSound:
> Do you know how to fix them?

Hi,

you need staves named "right" and "left" for this to work:


\version "2.19.50"

l =
#(define-music-function (music) (ly:music?)
   #{
 \change Staff = "left"
 #music
 \change Staff = "right"
   #})

right = \fixed c' {
  \clef treble
  \time 2/4
  g8-4 \l g_4 e-3 \l e_3
  g8-4 \l g_4 e4-2
  \bar "|."
}

% the new part:
\new PianoStaff <<
  \new Staff = right \right
  \new Staff = left { \clef bass s1 }
>>

HTH,
Joram

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


Re: change staff

2017-01-25 Thread SoundsFromSound
Malte Meyn-3 wrote
> Am 25.01.2017 um 11:55 schrieb Gianmaria Lari:
>> - Is there a simpler way to write this source code avoiding all these
>> change staff?
> 
> You could use a simple music function:
> 
> l =
> #(define-music-function (music) (ly:music?)
>#{
>  \change Staff = "left"
>  #music
>  \change Staff = "right"
>#})
> 
> right = \fixed c' {
>   \clef treble
>   \time 2/4
>   g8-4 \l g_4 e-3 \l e_3
>   g8-4 \l g_4 e4-2
>   \bar "|."
> }
> 
>> - Is it correct writing the left hand using s2 etc. etc.?
> 
> Yes it is.
> 
> 
> ___
> lilypond-user mailing list

> lilypond-user@

> https://lists.gnu.org/mailman/listinfo/lilypond-user

Hello,

When I copied your code into a new LilyPond file, I got some warnings at
every instance of the "l". 

Do you know how to fix them?
--

l = 
#(define-music-function (music) (ly:music?) 
   #{ 
 \change Staff = "left" 
 #music 
 \change Staff = "right" 
   #}) 

right = \fixed c' { 
  \clef treble 
  \time 2/4 
  g8-4 \l g_4 e-3 \l e_3 
  g8-4 \l g_4 e4-2 
  \bar "|." 
} 

*warning: cannot find context to switch to
warning: cannot find context to switch to
warning: cannot find context to switch to
warning: cannot find context to switch to*




-
composer | sound designer | asmr artist 
LilyPond Tutorials (for beginners) --> http://bit.ly/bcl-lilypond
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/change-staff-tp199525p199528.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: change staff

2017-01-25 Thread Malte Meyn


Am 25.01.2017 um 11:55 schrieb Gianmaria Lari:
> - Is there a simpler way to write this source code avoiding all these
> change staff?

You could use a simple music function:

l =
#(define-music-function (music) (ly:music?)
   #{
 \change Staff = "left"
     #music
     \change Staff = "right"
   #})

right = \fixed c' {
  \clef treble
  \time 2/4
  g8-4 \l g_4 e-3 \l e_3
  g8-4 \l g_4 e4-2
  \bar "|."
}

> - Is it correct writing the left hand using s2 etc. etc.?

Yes it is.


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


change staff

2017-01-25 Thread Gianmaria Lari
- Is there a simpler way to write this source code avoiding all these
change staff?
- Is it correct writing the left hand using s2 etc. etc.?

Thank you, g.

\version "2.19.54"
right = \fixed c' {
  \clef treble
  \time 2/4
  g8-4 \change Staff = "left" g_4 \change Staff = "right" e-3 \change Staff
= "left" e_3 \change Staff = "right"
  g8-4 \change Staff = "left" g_4 \change Staff = "right" e4-2
  \bar "|."
}

left = \fixed c' {
  \clef treble
  s2
  s4 c_2
}

\score {
  \new PianoStaff
  <<
\new Staff = "right" \right
\new Staff = "left"  \left
  >>
  \layout { }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Automatically change staff instrument name

2016-05-10 Thread David Wright
On Tue 10 May 2016 at 13:21:36 (+0200), Davide Liessi wrote:
> In the following code, the two short instrument names "A" and "B" of
> the second system are put one on top of the other (as I expected).
> I can solve the collision manually, e.g. with something similar to the
> three commented lines.
> 
> Is there a way to automatically change the short instrument names (or
> any other property) based on the visible staves?

I expect you need the schemers. Funnily enough, this works:

\new StaffGroup \with {
  shortInstrumentName = "A "
  \RemoveEmptyStaves
} <<
  \new Staff { c'1 \break R1 \break c'1 }
  \new Staff \with { shortInstrumentName = "(B)" } {
c'1 c'1 c'1
  }
>>

Cheers,
David.

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


Automatically change staff instrument name

2016-05-10 Thread Davide Liessi
Hi all.

In the following code, the two short instrument names "A" and "B" of
the second system are put one on top of the other (as I expected).
I can solve the collision manually, e.g. with something similar to the
three commented lines.

Is there a way to automatically change the short instrument names (or
any other property) based on the visible staves?

Thanks for any pointer.
Best wishes.
Davide


\version "2.19.35"
\new StaffGroup \with {
  shortInstrumentName = "A"
  \RemoveEmptyStaves
} <<
  \new Staff { c'1 \break R1 \break c'1 }
  \new Staff \with { shortInstrumentName = "B" } {
c'1
%\once \set StaffGroup.shortInstrumentName =
%\markup { \center-column { "A" "B" } }
%\once \set Staff.shortInstrumentName = ""
c'1 c'1
  }
>>

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


Re: Bad alignment with \change Staff and \ottava

2015-04-02 Thread Thomas Morley
2015-04-02 18:03 GMT+02:00 René Brandenburger r...@brandenburger.lu:
 Dear list,

 I'm typesetting a piano piece whith a staff change from the lower to the
 upper staff, the upper staff having an ottava bracket. This leads to the
 lower chord being slightly shifted to the right.
 Is there a workaround for this?

 Regards
 René Brandenburger

 Example code follows, output attached:

 \version 2.19.16

 right = \relative c'' {
   R1

If you comment \ottava #1 the following warning is printed:
warning: this Voice needs a \voiceXx or \shiftXx setting
  
   c' gis'1
No idea why it is omitted with \ottava #1

   \ottava #1
   g''! c1
   \ottava #0 |
 }

 left = \relative c' {
   \clef bass
   R1
   \change Staff = right

% Following the warning you should insert here:
\voiceTwo

   c' gis'1
   \change Staff = left  |

 }

 \score {
   \new PianoStaff 
 \new Staff = right{ \right }
 \new Staff = left {  \left }
   
   \layout { }
 }



HTH,
  Harm

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


Bad alignment with \change Staff and \ottava

2015-04-02 Thread René Brandenburger
Dear list,

I'm typesetting a piano piece whith a staff change from the lower to the
upper staff, the upper staff having an ottava bracket. This leads to the
lower chord being slightly shifted to the right.
Is there a workaround for this?

Regards
René Brandenburger

Example code follows, output attached:

\version 2.19.16

right = \relative c'' {
  R1
  \ottava #1
  g''! c1
  \ottava #0 |
}

left = \relative c' {
  \clef bass
  R1
  \change Staff = right
  c' gis'1
  \change Staff = left  |

}

\score {
  \new PianoStaff 
\new Staff = right{ \right }
\new Staff = left {  \left }
  
  \layout { }
}

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


Re: Bad alignment with \change Staff and \ottava

2015-04-02 Thread René Brandenburger
Thanks, tis does the trick

Am 02.04.2015 um 19:14 schrieb Thomas Morley:
 2015-04-02 18:03 GMT+02:00 René Brandenburger r...@brandenburger.lu:
 Dear list,

 I'm typesetting a piano piece whith a staff change from the lower to the
 upper staff, the upper staff having an ottava bracket. This leads to the
 lower chord being slightly shifted to the right.
 Is there a workaround for this?

 Regards
 René Brandenburger

 Example code follows, output attached:

 \version 2.19.16

 right = \relative c'' {
   R1
 If you comment \ottava #1 the following warning is printed:
 warning: this Voice needs a \voiceXx or \shiftXx setting
   
c' gis'1
 No idea why it is omitted with \ottava #1

   \ottava #1
   g''! c1
   \ottava #0 |
 }

 left = \relative c' {
   \clef bass
   R1
   \change Staff = right
 % Following the warning you should insert here:
 \voiceTwo

   c' gis'1
   \change Staff = left  |

 }

 \score {
   \new PianoStaff 
 \new Staff = right{ \right }
 \new Staff = left {  \left }
   
   \layout { }
 }


 HTH,
   Harm



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


Re: \change staff

2014-12-19 Thread tisimst
Try this. I know there are multiple ways for doing this (like changing 
beam-knee-length, or whatever), but it's a quick hack that works (sorry 
it's for 2.18.2, but I think you can convert it back):

%-- SNIP -

\version 2.18.2
\language english
right = { 
  \time 4/4 \key ef\major
  r4 af16 c' ef' af' bf ef'g8 ef' af c' ef' af' ef' |%m52
  bf ef' f' g'1 |%m53 
  s2. \bar|. %m54  
}

left = {
  \time 4/4 \key ef\major
  af,8 ef ~ ef4 g,4 f | 
  ef,16 bf, ef f 
  \once \override Beam.positions = #'(4.25 . 5.75)
  \stemUp g bf \change Staff = right \stemDown ef' f' 
  \stemNeutral g' bf' ef'' f'' g' bf' ef'' f'' g''4~\arpeggio | 
   {q2.} \new Voice { \change Staff =left r2 r4 }  \bar|. 
%m52-54
}

\score {
  \new PianoStaff \with {
instrumentName = Pno.
shortInstrumentName = Pno.
  } 
\new Staff = right \with {
  midiInstrument = acoustic grand
} \right
\new Staff = left \with {
  midiInstrument = acoustic grand
} { \clef bass \left }
  
  \layout { }
  \midi { }
}

%-- SNIP -

HTH,
Abraham

On Fri, Dec 19, 2014 at 7:18 AM, MING TSANG [via Lilypond] 
ml-node+s1069038n169515...@n5.nabble.com wrote:
 Dear ponders,
 
 I am having hard time to code lilypond to produce the original score:
 1.  \change staff did not produce the same as the original
 2.  how to code the last bar
 
 Thanks in advance.
 
 Immanuel,
 Ming.
 
 
 
 
 ___ 
 lilypond-user mailing list 
 [hidden email] 
 https://lists.gnu.org/mailman/listinfo/lilypond-user
 
  2014-12-18_222720_original.png (364K) Download Attachment
  2014-12-18_223006_lilycode.png (18K) Download Attachment
  test_change-staff.ly (1K) Download Attachment
 
 
 If you reply to this email, your message will be added to the 
 discussion below:
 http://lilypond.1069038.n5.nabble.com/change-staff-tp169515.html
 To start a new topic under User, email 
 ml-node+s1069038n...@n5.nabble.com 
 To unsubscribe from Lilypond, click here.
 NAML




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/change-staff-tp169515p169516.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: \change staff

2014-12-19 Thread MING TSANG
AbrahamThank you. It works on v2.19.15 as well.Immanuel,Ming 

 On Friday, December 19, 2014 11:01 AM, lilypond-user-requ...@gnu.org 
lilypond-user-requ...@gnu.org wrote:
   

 

  1. Re:\change staff (tisimst)
  
Message: 1
Date: Fri, 19 Dec 2014 07:33:36 -0700 (MST)
From: tisimst tisimst.lilyp...@gmail.com
To: lilypond-user@gnu.org
Subject: Re: \change staff
Message-ID: 1418999603.948...@smtp.gmail.com
Content-Type: text/plain; charset=us-ascii

Try this. I know there are multiple ways for doing this (like changing 
beam-knee-length, or whatever), but it's a quick hack that works (sorry 
it's for 2.18.2, but I think you can convert it back):

%-- SNIP -

\version 2.18.2
\language english
right = { 
  \time 4/4 \key ef\major
  r4 af16 c' ef' af' bf ef'g8 ef' af c' ef' af' ef' |%m52
  bf ef' f' g'1 |%m53 
  s2. \bar|. %m54          
}

left = {
  \time 4/4 \key ef\major
  af,8 ef ~ ef4 g,4 f | 
  ef,16 bf, ef f 
  \once \override Beam.positions = #'(4.25 . 5.75)
  \stemUp g bf \change Staff = right \stemDown ef' f' 
  \stemNeutral g' bf' ef'' f'' g' bf' ef'' f'' g''4~\arpeggio | 
   {q2.} \new Voice { \change Staff =left r2 r4 }  \bar|. 
%m52-54
}

\score {
  \new PianoStaff \with {
    instrumentName = Pno.
    shortInstrumentName = Pno.
  } 
    \new Staff = right \with {
      midiInstrument = acoustic grand
    } \right
    \new Staff = left \with {
      midiInstrument = acoustic grand
    } { \clef bass \left }
  
  \layout { }
  \midi { }
}

%-- SNIP -

HTH,
Abraham

On Fri, Dec 19, 2014 at 7:18 AM, MING TSANG [via Lilypond] 
ml-node+s1069038n169515...@n5.nabble.com wrote:
 Dear ponders,
 
 I am having hard time to code lilypond to produce the original score:
 1.  \change staff did not produce the same as the original
 2.  how to code the last bar
 
 Thanks in advance.
 
 Immanuel,
 Ming.
 
 
 
 
 ___ 
 lilypond-user mailing list 
 [hidden email] 
 https://lists.gnu.org/mailman/listinfo/lilypond-user
 
  2014-12-18_222720_original.png (364K) Download Attachment
  2014-12-18_223006_lilycode.png (18K) Download Attachment
  test_change-staff.ly (1K) Download Attachment
 
 
 If you reply to this email, your message will be added to the 
 discussion below:
 http://lilypond.1069038.n5.nabble.com/change-staff-tp169515.html
 To start a new topic under User, email 
 ml-node+s1069038n...@n5.nabble.com 
 To unsubscribe from Lilypond, click here.
 NAML





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


Re: change staff coding

2014-12-07 Thread Gilberto Agostinho
Hi,

Since you are naming your staves as right and left in the \score block,
then you must use \change Staff = right or \change Staff = left when
changing staves, instead of \change Staff = up. So on line 23 simply
exchange the word up for right (with the commas).

Best,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/change-staff-coding-tp169278p169280.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


possible bug: \change Staff and beam collision

2014-11-02 Thread Gilberto Agostinho
Hello all,

Please have a look on the following code:

\version 2.19.15

\new PianoStaff 
  \new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8 
\ottava #1 a'''
\ottava #0 a' 
a,
  }
  \new Staff = down {
\clef bass
s2 
  }


\new PianoStaff 
  \new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8 
\ottava #1 a'''
\ottava #0 a' 
\change Staff = down a,
  }
  \new Staff = down {
\clef bass
s2 
  }


Which produces:

http://lilypond.1069038.n5.nabble.com/file/n168324/11.png 

As you can see, without changing staff the ottava position is high enough
not to collide with the beam, but when changing staff the ottava position
gets lower (!) and collides with the beam. Anyone know any workaround for
this problem?

Best,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/possible-bug-change-Staff-and-beam-collision-tp168324.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: possible bug: \change Staff and beam collision

2014-11-02 Thread Mike Solomon

 On Nov 2, 2014, at 8:40 PM, Gilberto Agostinho gilbertohasn...@gmail.com 
 wrote:
 
 Hello all,
 
 Please have a look on the following code:
 
 \version 2.19.15
 
 \new PianoStaff 
  \new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8 
\ottava #1 a'''
\ottava #0 a' 
a,
  }
  \new Staff = down {
\clef bass
s2 
  }
 
 
 \new PianoStaff 
  \new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8 
\ottava #1 a'''
\ottava #0 a' 
\change Staff = down a,
  }
  \new Staff = down {
\clef bass
s2 
  }
 
 
 Which produces:
 
 http://lilypond.1069038.n5.nabble.com/file/n168324/11.png 
 
 As you can see, without changing staff the ottava position is high enough
 not to collide with the beam, but when changing staff the ottava position
 gets lower (!) and collides with the beam. Anyone know any workaround for
 this problem?
 
 Best,
 Gilberto
 

This is a persistent issue in LilyPond development - there was some work on it 
in course a couple years ago that has since been put on hold but I hope to pick 
it back up one day.

The gist of the problem (and others like it) is that, because the beam is cross 
staff, the layout engine does not know where it will be placed because it does 
not know how far apart vertically the notes are until final page spacing is 
done.  That means that all objects that depend on the beam for placement (such 
as the ottava) ignore it when being placed and, as a result, you get collisions.

I know that Keith has several cross-staff-related workarounds in his piano 
scores.  Sorry I can’t be of more help, but it is not an easy issue.

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


Re: possible bug: \change Staff and beam collision

2014-11-02 Thread Mike Solomon

 On Nov 2, 2014, at 8:40 PM, Gilberto Agostinho gilbertohasn...@gmail.com 
 wrote:
 
 Hello all,
 
 Please have a look on the following code:
 
 \version 2.19.15
 
 \new PianoStaff 
 \new Staff = up {
   \override Score.Beam.damping = 3
   \stemUp a'8 
   \ottava #1 a'''
   \ottava #0 a' 
   a,
 }
 \new Staff = down {
   \clef bass
   s2 
 }
 
 
 \new PianoStaff 
 \new Staff = up {
   \override Score.Beam.damping = 3
   \stemUp a'8 
   \ottava #1 a'''
   \ottava #0 a' 
   \change Staff = down a,
 }
 \new Staff = down {
   \clef bass
   s2 
 }
 
 
 Which produces:
 
 http://lilypond.1069038.n5.nabble.com/file/n168324/11.png 
 
 As you can see, without changing staff the ottava position is high enough
 not to collide with the beam, but when changing staff the ottava position
 gets lower (!) and collides with the beam. Anyone know any workaround for
 this problem?
 
 Best,
 Gilberto
 

This is a persistent issue in LilyPond development - there was some work on it 
in course a couple years ago that has since been put on hold but I hope to pick 
it back up one day.

The gist of the problem (and others like it) is that, because the beam is cross 
staff, the layout engine does not know where it will be placed because it does 
not know how far apart vertically the notes are until final page spacing is 
done.  That means that all objects that depend on the beam for placement (such 
as the ottava) ignore it when being placed and, as a result, you get collisions.

I know that Keith has several cross-staff-related workarounds in his piano 
scores.  Sorry I can’t be of more help, but it is not an easy issue.

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


Re: possible bug: \change Staff and beam collision

2014-11-02 Thread Mike Solomon

 On Nov 2, 2014, at 8:40 PM, Gilberto Agostinho gilbertohasn...@gmail.com 
 wrote:
 
 Hello all,
 
 Please have a look on the following code:
 
 \version 2.19.15
 
 \new PianoStaff 
 \new Staff = up {
  \override Score.Beam.damping = 3
  \stemUp a'8 
  \ottava #1 a'''
  \ottava #0 a' 
  a,
 }
 \new Staff = down {
  \clef bass
  s2 
 }
 
 
 \new PianoStaff 
 \new Staff = up {
  \override Score.Beam.damping = 3
  \stemUp a'8 
  \ottava #1 a'''
  \ottava #0 a' 
  \change Staff = down a,
 }
 \new Staff = down {
  \clef bass
  s2 
 }
 
 
 Which produces:
 
 http://lilypond.1069038.n5.nabble.com/file/n168324/11.png 
 
 As you can see, without changing staff the ottava position is high enough
 not to collide with the beam, but when changing staff the ottava position
 gets lower (!) and collides with the beam. Anyone know any workaround for
 this problem?
 
 Best,
 Gilberto
 

This is a persistent issue in LilyPond development - there was some work on it 
in course a couple years ago that has since been put on hold but I hope to pick 
it back up one day.

The gist of the problem (and others like it) is that, because the beam is cross 
staff, the layout engine does not know where it will be placed because it does 
not know how far apart vertically the notes are until final page spacing is 
done.  That means that all objects that depend on the beam for placement (such 
as the ottava) ignore it when being placed and, as a result, you get collisions.

I know that Keith has several cross-staff-related workarounds in his piano 
scores.  Sorry I can’t be of more help, but it is not an easy issue.

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


Re: possible bug: \change Staff and beam collision

2014-11-02 Thread Gilberto Agostinho
Hi Mike,

Thanks for your reply.


Mike Solomon wrote
 This is a persistent issue in LilyPond development - there was some work
 on it in course a couple years ago that has since been put on hold but I
 hope to pick it back up one day.

I totally understand it.


Mike Solomon wrote
 I know that Keith has several cross-staff-related workarounds in his piano
 scores.  Sorry I can’t be of more help, but it is not an easy issue.

Thanks anyway, I will see if I find some interesting snippet by Keith then.
My case is always complicated though, my main work is with algorithmically
generated music and so I always need to either automatize a solution or
completely forget about it and approach the problem of notation from a
different point of view (manual tweaking isn't an option for what I do). 

Best,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/possible-bug-change-Staff-and-beam-collision-tp168324p168329.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: possible bug: \change Staff and beam collision

2014-11-02 Thread Keith OHara
Gilberto Agostinho gilbertohasnofb at gmail.com writes:

 but when changing staff the ottava position
 gets lower (!) and collides with the beam. 

LilyPond allows you to beam to any other staff, so in general that
beam might have to go up and cross the ottava bracket, while the
bracket must stay with the staff.  This is not likely with ottava
brackets but cross-staff beams and their stems sometimes need to cross 
similar spanning structures.

The code is so far not sophisticated enough to look ahead to staff layout
when placing the ottava on its home staff, so assumes the cross-staff
beam might have to cross it.

Logically we should have a setting 
  \override Staff.OttavaBracket.cross-staff = 
#ly:side-position-interface::calc-cross-staf
to tell Lilypond she may move the OttavaBracket along with the beam 
but when I give LilyPond permission this way, she does not move the beam.

 My case is always complicated though, my main work is with algorithmically
 generated music and so I always need to either automatize a solution or
 completely forget about it and approach the problem of notation from a
 different point of view (manual tweaking isn't an option for what I do). 

I have no better suggestion.  The manual tweak is simple, though,
  \once\override Staff.OttavaBracket.staff-padding = #6

and Lilypond makes it easy to put overrides in a separate expression 
 { s1*54 \overrideThis}
   { s1*32 s2 \overrideThat}
 



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


Re: possible bug: \change Staff and beam collision

2014-11-02 Thread Gilberto Agostinho
Hi Keith,

Thanks for the detailed explanation, I think I understand the situation well
now.


Keith OHara wrote
 I have no better suggestion.  The manual tweak is simple, though,
   \once\override Staff.OttavaBracket.staff-padding = #6

Thanks anyway. Unfortunately my case of avoiding manual tweaks is not simple
laziness: I work with generative music, which means that I will give the
performers a computer program rather than a score, and I will let them
generate a new version of a work by themselves. This means that I have
absolutely no chances of ever tweaking that .ly file. 

Nevertheless, I am trying to play around with staff-padding but the results
are not very good. Sometimes the ottavas are way too high, sometimes the
collision problem appears again.

Thanks a lot for your reply, I really appreciate it.

Best,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/possible-bug-change-Staff-and-beam-collision-tp168324p168337.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


can a context change staff-affinity in a frenched score?

2014-09-28 Thread Kieren MacMillan
Hi all,

Given

  \new ChoirStaff 
\new Staff
\new Lyrics
\new Staff
  

Can the Lyrics have staff-affinity = #CENTER when both Staff contexts are 
alive, and staff-affinity = #UP or #DOWN when the lower or upper Staff, 
respectively, is frenched? I’m using the latest development build, if it makes 
any difference.

Thanks,
Kieren.
___

Kieren MacMillan, composer
www:  http://www.kierenmacmillan.info
email:  i...@kierenmacmillan.info


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


Re: \change staff question

2014-09-25 Thread Simon Albrecht

Hello Ming,

if you have a look into the documentation for \change (when in doubt, 
look it up in the command index), you’ll find that it does not require 
any braces following or indeed any argument. It looks like you try to 
enter the notes in parallel, which is illogical, since they are 
sequential: You write a single voice which flips over from one staff to 
another. So in your example, you write all the 64th notes in the order 
in which they sound, and after every four notes you write a \change 
command. This can become tedious if there are many changes, so you 
should make an abbreviation like

ri = \change Staff = right
or, in case it’s necessary,
ri = { \change Staff = right \voiceTwo } % and the like.

HTH, Simon

Am 25.09.2014 um 01:52 schrieb MING TSANG:

Hi, lilyponders:
I try to lilypond duplicate the score as shown on the screen copy of a 
score sheet.   The change Staff seems not changing from left to right.

I have sample file test_come-thou-fount.ly
when compile I have the following warning:

Starting lilypond-windows.exe 2.19.14 [test_come-thou-count.ly]...
Processing 
`C:/Users/Tsang/Dropbox/Lyndon/LiLy/come-thou-fount-of-every-blessing/test_come-thou-count.ly'

Parsing...
Interpreting music...
warning: Change_iterator::process (): Voice = `':
C:/Users/Tsang/Dropbox/Lyndon/LiLy/come-thou-fount-of-every-blessing/test_come-thou-count.ly:23:5 
https://ca-mg6.mail.yahoo.com/neo/0: warning: cannot change `staff' 
to `right': none of these in my family
\change staff = right {gs'64[ b'd''f''] b'[d''f''gs''] d''f''gs''b'' 
f''[gs''b''d'''] gs''b''d'''f''' b''[d'''f'''gs'''] b'''4)\fermata }

warning: Change_iterator::process (): Voice = `':
C:/Users/Tsang/Dropbox/Lyndon/LiLy/come-thou-fount-of-every-blessing/test_come-thou-count.ly:24:5 
https://ca-mg6.mail.yahoo.com/neo/1: warning: cannot change `staff' 
to `left': none of these in my family
\change staff = left {b64[ d'f'gs'] d'[f'gs'b'] f'[gs'b'd''] 
gs'[b'd''f''] b'[d''f''gs'']} %m65
C:/Users/Tsang/Dropbox/Lyndon/LiLy/come-thou-fount-of-every-blessing/test_come-thou-count.ly:26:14 
https://ca-mg6.mail.yahoo.com/neo/2: warning: barcheck failed at: 1/4

b,fs b2.
|%m66
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `test_come-thou-count.ps'...
Converting to `./test_come-thou-count.pdf'...
Success: compilation successfully completed
Completed successfully in 2.6.


I have play around the code and cannot make it do the same as the 
screen copy. Need help!

Immanuel,
Ming


___
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: \change staff question

2014-09-25 Thread Mark Stephen Mrotek
Ming,

 

In m66, and m67 you have an “unassigned” number, i.e. a “4.”

Your time signature is ¾, yet there are 4 beats written in the first measure
of the upper voice of the screen shot.

 

Mark

 

From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
MING TSANG
Sent: Wednesday, September 24, 2014 4:52 PM
To: lilypond-user@gnu.org
Subject: \change staff question

 

Hi, lilyponders:

I try to lilypond duplicate the score as shown on the screen copy of a score
sheet.   The change Staff seems not changing from left to right.

I have sample file test_come-thou-fount.ly

when compile I have the following warning:

 

Starting lilypond-windows.exe 2.19.14 [test_come-thou-count.ly]...

Processing
`C:/Users/Tsang/Dropbox/Lyndon/LiLy/come-thou-fount-of-every-blessing/test_c
ome-thou-count.ly'

Parsing...

Interpreting music...

warning: Change_iterator::process (): Voice = `': 

 https://ca-mg6.mail.yahoo.com/neo/0
C:/Users/Tsang/Dropbox/Lyndon/LiLy/come-thou-fount-of-every-blessing/test_co
me-thou-count.ly:23:5: warning: cannot change `staff' to `right': none of
these in my family

\change staff = right {gs'64[ b'd''f''] b'[d''f''gs''] d''f''gs''b''
f''[gs''b''d'''] gs''b''d'''f''' b''[d'''f'''gs'''] b'''4)\fermata }

warning: Change_iterator::process (): Voice = `': 

 https://ca-mg6.mail.yahoo.com/neo/1
C:/Users/Tsang/Dropbox/Lyndon/LiLy/come-thou-fount-of-every-blessing/test_co
me-thou-count.ly:24:5: warning: cannot change `staff' to `left': none of
these in my family

\change staff = left {b64[ d'f'gs'] d'[f'gs'b'] f'[gs'b'd''] gs'[b'd''f'']
b'[d''f''gs'']} %m65

 https://ca-mg6.mail.yahoo.com/neo/2
C:/Users/Tsang/Dropbox/Lyndon/LiLy/come-thou-fount-of-every-blessing/test_co
me-thou-count.ly:26:14: warning: barcheck failed at: 1/4

b,fs b2. 

|%m66

Preprocessing graphical objects...

Finding the ideal number of pages...

Fitting music on 1 page...

Drawing systems...

Layout output to `test_come-thou-count.ps'...

Converting to `./test_come-thou-count.pdf'...

Success: compilation successfully completed

Completed successfully in 2.6.

 

 

I have play around the code and cannot make it do the same as the screen
copy. Need help!

Immanuel,

Ming

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


Re: Stem spacing with change staff

2013-06-06 Thread Janek Warchoł
2013/6/6 Andrew Bernard andrew.bern...@gmail.com:
 Thanks, that works - but has the unfortunate side effect of spacing the rest
 of the score far too wide. Is there a way you can adjust proportional
 spacing for a single bar?

I think that \newSpacingSection can help you.
hth,
Janek

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


Re: Stem spacing with change staff

2013-06-06 Thread Eluze
Janek Warchoł-2 wrote
 2013/6/6 Andrew Bernard lt;

 andrew.bernard@

 gt;:
 Thanks, that works - but has the unfortunate side effect of spacing the
 rest
 of the score far too wide. Is there a way you can adjust proportional
 spacing for a single bar?
 
 I think that \newSpacingSection can help you.

I don't think you even need that:

resetting or unsetting the proportionalNotationDuration

\unset Score.proportionalNotationDuration

should just do it!

Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Stem-spacing-with-change-staff-tp146702p146764.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


Stem spacing with change staff

2013-06-05 Thread Andrew Bernard
Greetings List,

The following snippet shows an unexpected behaviour. If proportional
spacing is enabled, the stems become unevenly spaced, but only when using
\change Staff. With proportional spacing not enabled, there is no problem.

What is going on here? I am wanting proportional notation for the score,
and even stem spacing for bars like this. Any enlightenment most
appreciated.



\version 2.17.18

upper = \relative c'' {

  \time 1/8

  \stemUp

  \once \override TupletBracket.bracket-visibility = ##f
  \once \override TupletNumber.stencil = ##f
  \tuplet 10/1 {
c8[
\change Staff = bass d,,
\change Staff = treble e''
\change Staff = bass f,,
\change Staff = treble g''
\change Staff = bass a,,
\change Staff = treble b''
\change Staff = bass c,,
\change Staff = treble b''
\change Staff = bass a,,]
  }
}

lower = \relative c {
  \clef bass
  \time 1/8

  s8
}

\score {
  \new StaffGroup {

  \new Staff = treble { \upper }
  \new Staff = bass { \lower }

  }
  \layout {
\context {
  \Score
  \accidentalStyle Score.dodecaphonic
  proportionalNotationDuration = #(ly:make-moment 1/20)

}
  }
}




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


Re: Stem spacing with change staff

2013-06-05 Thread Eluze
Andrew Bernard wrote
 Greetings List,
 
 The following snippet shows an unexpected behaviour. If proportional
 spacing is enabled, the stems become unevenly spaced, but only when using
 \change Staff. With proportional spacing not enabled, there is no problem.
 
 What is going on here? I am wanting proportional notation for the score,
 and even stem spacing for bars like this. Any enlightenment most
 appreciated.

augment the value for the proportional duration:

proportionalNotationDuration = #(ly:make-moment 1/100)

Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Stem-spacing-with-change-staff-tp146702p146706.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: Stem spacing with change staff

2013-06-05 Thread Andrew Bernard
Thanks, that works - but has the unfortunate side effect of spacing the 
rest of the score far too wide. Is there a way you can adjust 
proportional spacing for a single bar?


Andrew

On 6/06/13 12:32 AM, Eluze wrote:

augment the value for the proportional duration:

proportionalNotationDuration = #(ly:make-moment 1/100)

Eluze



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


Re: change staff for component notes of chord

2013-01-25 Thread Xavier Scheuer
On 25 January 2013 08:17, Jeffrey Trevino jeffrey.trevi...@gmail.com wrote:
 hi there,

 I like the change staff interface for switching staffs and beaming across
 them. Is there a similar interface available for chords, which allows the
 user to specify that certain higher or lower notes should be drawn on a
 different staff? I would find this much easier to use than the cross-staff
 stem interface described in the keyboard writing section.

Not yet, but there is an open feature request about this.
http://code.google.com/p/lilypond/issues/detail?id=2270

Cheers,
Xavier

-- 
Xavier Scheuer x.sche...@gmail.com

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


Re: change staff for component notes of chord

2013-01-25 Thread Phil Holmes
- Original Message - 
From: Xavier Scheuer x.sche...@gmail.com

To: Jeffrey Trevino jeffrey.trevi...@gmail.com
Cc: lilypond-user lilypond-user@gnu.org
Sent: Friday, January 25, 2013 10:50 AM
Subject: Re: change staff for component notes of chord


On 25 January 2013 08:17, Jeffrey Trevino jeffrey.trevi...@gmail.com 
wrote:

hi there,

I like the change staff interface for switching staffs and beaming 
across

them. Is there a similar interface available for chords, which allows the
user to specify that certain higher or lower notes should be drawn on a
different staff? I would find this much easier to use than the 
cross-staff

stem interface described in the keyboard writing section.


Not yet, but there is an open feature request about this.
http://code.google.com/p/lilypond/issues/detail?id=2270

Cheers,
Xavier


Just checking that you're aware that cross-staff stems were improved in late 
2.15.  If you use 2.16 or 2.17 I think they work fairly well:


http://lilypond.org/doc/v2.17/Documentation/notation/common-notation-for-keyboards#cross_002dstaff-stems

--
Phil Holmes 



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


Re: change staff for component notes of chord

2013-01-25 Thread Jeffrey Trevino
Hi there,

Thanks for your responses. I'll make due with the current span stem
engraver, but I think that it would be easier to extend the functionality
of the \change Staff = staffName paradigm to do this more elegantly in
future versions.

cheers,
Jeff

On Fri, Jan 25, 2013 at 3:26 AM, Phil Holmes m...@philholmes.net wrote:

 - Original Message - From: Xavier Scheuer x.sche...@gmail.com
 To: Jeffrey Trevino jeffrey.trevi...@gmail.com
 Cc: lilypond-user lilypond-user@gnu.org
 Sent: Friday, January 25, 2013 10:50 AM
 Subject: Re: change staff for component notes of chord



  On 25 January 2013 08:17, Jeffrey Trevino jeffrey.trevi...@gmail.com
 wrote:

 hi there,

 I like the change staff interface for switching staffs and beaming
 across
 them. Is there a similar interface available for chords, which allows the
 user to specify that certain higher or lower notes should be drawn on a
 different staff? I would find this much easier to use than the
 cross-staff
 stem interface described in the keyboard writing section.


 Not yet, but there is an open feature request about this.
 http://code.google.com/p/**lilypond/issues/detail?id=2270http://code.google.com/p/lilypond/issues/detail?id=2270

 Cheers,
 Xavier


 Just checking that you're aware that cross-staff stems were improved in
 late 2.15.  If you use 2.16 or 2.17 I think they work fairly well:

 http://lilypond.org/doc/v2.17/**Documentation/notation/common-**
 notation-for-keyboards#cross_**002dstaff-stemshttp://lilypond.org/doc/v2.17/Documentation/notation/common-notation-for-keyboards#cross_002dstaff-stems

 --
 Phil Holmes

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


change staff for component notes of chord

2013-01-24 Thread Jeffrey Trevino
hi there,

I like the change staff interface for switching staffs and beaming across
them. Is there a similar interface available for chords, which allows the
user to specify that certain higher or lower notes should be drawn on a
different staff? I would find this much easier to use than the cross-staff
stem interface described in the keyboard writing section.

thank you,
Jeff

-- 
Jeff Treviño
PhD Candidate in Music Composition
@ the University of California, San Diego
Skype: jeffreytrevino
E-mail: jeffrey.trev...@gmail.com
Web: www.jeffreytrevino.com
Cell: (619)565-9611
9310H Redwood Dr.
La Jolla, CA 92037
USA
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


issues with change staff

2012-08-19 Thread cgodefro free

Hello,

I'm experimenting some issues with the change staff command. It seems 
that both staff are linked together.
the \stemUp is not taking into account and the \change Staff = up 
affect as well the down staff.


Does anyone can help me unlinked the both staff?

i did the test on both 2.14 and  2.15.95 and the result is the same.

thanks for your help.

Christophe
\version 2.15.43

\include italiano.ly

HanonID = \relative do {
\clef treble \time 2/4  \tempo Moderato| % 1
\stemUp \change Staff = down do16-1 mi-2 fa-3 sol-4 la-5 sol fa mi
	re-1 fa-2 sol la si la sol fa
	mi-1 sol-2 la si do si la sol 
	fa la si do re do si la
	sol si \change Staff = up do re mi re do si 
	la do re mi fa mi re do 
	si re mi fa sol fa mi re
	}
	
HanonIG = \relative do {
\clef bass \time 2/4 | % 1
\stemDown do,16_5 mi_4 fa_3 sol_2 la_1 sol fa mi
	re_5 fa_4 sol la si la sol fa
	mi_1 sol_2 la si do si la sol 
	fa la si do re do si la
	sol si do re mi re do si 
	la do re mi fa mi re do 
	si re mi fa sol fa mi re
	}
	
\score {
\new PianoStaff 
\new Staff  = up \HanonID 
\new Staff = down \HanonIG
 
	   \layout {}
 }___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: issues with change staff

2012-08-19 Thread james

On Aug 19, 2012, at 11:38 AM, cgodefro free wrote:

 Hello,
 
 I'm experimenting some issues with the change staff command. It seems that 
 both staff are linked together.
 the \stemUp is not taking into account and the \change Staff = up affect as 
 well the down staff.
 
 Does anyone can help me unlinked the both staff?
 
 i did the test on both 2.14 and  2.15.95 and the result is the same.
 
 thanks for your help.
 
 Christophe
Add an explicit \new Voice to each voice. As it is, lilypond's putting them in 
the same implicit voice context.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


\change Staff in Voice context

2012-06-28 Thread Neil Thornock
Hi all,
I'm wondering why, in the snippet below, the staff change does not
affect the mid voice throughout. It returns to the top staff in the
next measure.

Is there a way to have the staff change affect the entire voice throughout?

%%%

aa = \transpose c c' {
{ c'1 } \context Voice = mid { \change Staff = lo c4 d e f~ } 
{ d'1 } \context Voice = mid { f4 e d c } 
}

bb = { s1*2 }


   \new Staff = hi { \aa }
   \new Staff = lo { \bb }


-- 
Neil Thornock, D.M.
The recent premiere of ...and a bunch of other stuff:
http://www.youtube.com/watch?v=LQtvPet3k8c
Assistant Professor of Music
Composition/Theory
Brigham Young University

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


stem length and change staff

2012-06-12 Thread Tiresia GIUNO
Dear all,

in the attached files (.ly  .png) the alteration of the first b' in the
second bar produces an incorrect length of the stems and an incorrect
position of the beam.

This behavior does not appear in the third bar, where the third chord
is modified. Is there any reason for that?

To correct this situation, I'm overriding the beam's position with
\once \override Beam #'positions = #'(-4.5 . -5.5)

Any other suggestion?

Thanks a lot,
T

%{ changeStaffStem %}
% -*- indent-tabs: true; tab-width: 2;
\version 2.14.2
\include english.ly

uSt = { \change Staff = upStaff }
dSt = { \change Staff = downStaff }

upStaffMusic = {
	\relative c' {
		b' c d8 \dSt \stemUp c, e g
		\uSt \stemDown b' d e \dSt \stemUp d, fs a
		r2
	
		\uSt \stemDown bf' c d8 \dSt \stemUp c, e g \uSt
		\stemDown b' d e \dSt \stemUp d, fs a
		r2
		
		\uSt \stemDown bf' c d8 \dSt \stemUp c, e g \uSt
		\stemDown c' d e \dSt \stemUp d, fs a
		r2
	}
}

\new PianoStaff 
	\new Staff = upStaff \upStaffMusic
	\new Staff = downStaff { s1*3 }
attachment: changeStaffStem-example.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: stem length and change staff

2012-06-12 Thread -Eluze


Tiresia Giuno wrote:
 
 in the attached files (.ly  .png) the alteration of the first b' in the
 second bar produces an incorrect length of the stems and an incorrect
 position of the beam.
 

agreed, but version 2.15.40 looks much better!

Eluze

-- 
View this message in context: 
http://old.nabble.com/stem-length-and-change-staff-tp34002754p34002856.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.


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


Re: stem length and change staff

2012-06-12 Thread Tiresia GIUNO
On Tue, 12 Jun 2012 15:24:49 -0700 (PDT)
-Eluze elu...@gmail.com wrote:
 
 
 Tiresia Giuno wrote:
  
  in the attached files (.ly  .png) the alteration of the first b'
  in the second bar produces an incorrect length of the stems and an
  incorrect position of the beam.
  
 
 agreed, but version 2.15.40 looks much better!
 
 Eluze
 

Thank you for your suggestion!
T

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


\change Staff don't work fine

2011-09-13 Thread Mario Moles
Any idea? Thank's!
\version 2.15.10
csr = \change Staff = right
csl = \change Staff = left 
sn=\stemNeutral
su=\stemUp
sd=\stemDown
tn=\tieNeutral
suon = \sustainOn
suof = \sustainOff
tempoMark = {
  \once \override Score.RehearsalMark #'self-alignment-X = #LEFT
  \once \override Score.RehearsalMark #'break-align-symbols = #'(time-
signature key-signature)
  \once \override Staff.TimeSignature #'break-align-anchor-alignment = #LEFT
  \mark \markup \bold {
Allegro molto
}
}

global = {
  \tempoMark
  \key g \major
  \time 6/8
}
rightOne = \relative c' {
  \global
  % Qui segue la musica.
  \global
  \override Fingering #'avoid-slur = #'inside
  % Qui segue la musica.
  \csl c8\pp \csr g' c, \csl b \csr g' c,|
  \csl c \csr g' c, \csl g \csr g' c,|
  \csl c \csr g' c, \csl b \csr g' c,|
  \csl c \csr g' c, \csl g \csr g' c,|
  \csl c \csr g' c, \csl b \csr g' c,|
  \csl c \csr g' c, \csl g \csr g' c,|  
  \csl e \csr b' e, \csl d \csr b' e,|
  \csl e \csr b' e, \csl b \csr b' e,|
  \csl e \csr b' e, \csl d \csr b' e,|
  \csl e \csr b' e, \csl b \csr b' e,|
  \csl g \csr d' g, \csl fis \csr d' g,|
  \csl g \csr d' g, \csl d \csr d' g,|
  \csl g \csr d' g, \csl fis \csr d' g,|
  \csl c, \csr g' c, \csl b \csr g' c,|
  \csl c \csr g' c, \csl g \csr g' c,|
  \csl c \csr g' c, \csl b \csr g' c,|
  \csl c \csr g' c, \csl b \csr g' c,|
  \csl b \csr fis' b, \csl a \csr fis' b,|
  \csl b \csr fis' b, \csl a \csr fis' b,|
  \csl a \csr e' a, \csl g \csr e' a,|
  \csl a \csr e' a, \csl g \csr e' a,|
  \clef bass
  \repeat unfold 4
  {\csl \su g \csr \sd d' g, \csl \su fis \csr \sd d' g,|}
  \repeat unfold 2
  {\csl \su fis \csr \sd cis' fis, \csl \su e \csr \sd cis' fis,|}
  \repeat unfold 2
  {\csl \su e \csr \sd b' e, \csl \su d \csr \sd b' e,|}
  \repeat unfold 2
  {\csl \su d \csr \sd a' d, \csl \su c \csr \sd a' d,|}
  \repeat unfold 2
  {\csl \su c \csr \sd g' c, \csl \su a \csr \sd g' c,|}
  \csl \su g \csr \sd g' c, \csl \su fis, \csr \sd g' c,|
  \csl \su e,2.|
  \csr
  \repeat unfold 4 {r2.}|
  \time 2/4
  \repeat unfold 21{r2}|
  \clef treble
  \time 6/8
  e'''4 d8 c4 d8|
  
}

rightTwo = \relative c' {
  \global
  % Qui segue la musica.
  s2.*39|
  s2*21|
  g, b2.|  
}

leftOne = \relative c' {
  \global
  % Qui segue la musica.
  s2.*39|
%   s2*21|
  \csl
%   c,8 g' c b, g' c|
}

leftTwo = \relative c {
  \global
  % Qui segue la musica.
  c'4.\suon b|
  c g|
  c b|
  c g|
  c b|
  c g|
  e' d|
  e b|
  e d|
  e b|
  \clef treble
  g' fis|
  g d|
  g fis|
  \clef bass
  c b|
  c g|
  c b|
  c b|
  b a|
  b a|
  a g|
  a g|
  g fis|
  g fis|
  g fis|
  g fis|
  fis e|
  fis e|
  e d|
  e d|
  d c|
  d c|
  c b|
  c a|
  g fis|
  s2.|
  \repeat unfold 4 {r2.}|
  \repeat unfold 21{r2}|
  \clef bass
  c'4. b|  
}

\score {
  \new PianoStaff \with {
instrumentName = Pf.
  } 
\new Staff = right \with {
  midiInstrument = acoustic grand
}  \rightOne \\ \rightTwo 
\new Staff = left \with {
  midiInstrument = acoustic grand
} { \clef bass  \leftOne \\ \leftTwo  }
  
  \layout { }
  \midi {
\context {
  \Score
  tempoWholesPerMinute = #(ly:make-moment 100 4)
}
  }
}

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


Re: \change Staff don't work fine

2011-09-13 Thread Phil Holmes
There's too much music here to work out your problem.  Could you a) say what 
you believe is wrong, and b) cut the music down to a tiny example showing your 
problem.

--
Phil Holmes


  - Original Message - 
  From: Mario Moles 
  To: lilypond-user@gnu.org 
  Sent: Tuesday, September 13, 2011 4:07 PM
  Subject: \change Staff don't work fine


  Any idea? Thank's!

  \version 2.15.10

  csr = \change Staff = right

  csl = \change Staff = left 

  sn=\stemNeutral

  su=\stemUp

  sd=\stemDown

  tn=\tieNeutral

  suon = \sustainOn

  suof = \sustainOff

  tempoMark = {

  \once \override Score.RehearsalMark #'self-alignment-X = #LEFT

  \once \override Score.RehearsalMark #'break-align-symbols = #'(time-signature 
key-signature)

  \once \override Staff.TimeSignature #'break-align-anchor-alignment = #LEFT

  \mark \markup \bold {

  Allegro molto

  }

  }




  global = {

  \tempoMark

  \key g \major

  \time 6/8

  }

  rightOne = \relative c' {

  \global

  % Qui segue la musica.

  \global

  \override Fingering #'avoid-slur = #'inside

  % Qui segue la musica.

  \csl c8\pp \csr g' c, \csl b \csr g' c,|

  \csl c \csr g' c, \csl g \csr g' c,|

  \csl c \csr g' c, \csl b \csr g' c,|

  \csl c \csr g' c, \csl g \csr g' c,|

  \csl c \csr g' c, \csl b \csr g' c,|

  \csl c \csr g' c, \csl g \csr g' c,| 

  \csl e \csr b' e, \csl d \csr b' e,|

  \csl e \csr b' e, \csl b \csr b' e,|

  \csl e \csr b' e, \csl d \csr b' e,|

  \csl e \csr b' e, \csl b \csr b' e,|

  \csl g \csr d' g, \csl fis \csr d' g,|

  \csl g \csr d' g, \csl d \csr d' g,|

  \csl g \csr d' g, \csl fis \csr d' g,|

  \csl c, \csr g' c, \csl b \csr g' c,|

  \csl c \csr g' c, \csl g \csr g' c,|

  \csl c \csr g' c, \csl b \csr g' c,|

  \csl c \csr g' c, \csl b \csr g' c,|

  \csl b \csr fis' b, \csl a \csr fis' b,|

  \csl b \csr fis' b, \csl a \csr fis' b,|

  \csl a \csr e' a, \csl g \csr e' a,|

  \csl a \csr e' a, \csl g \csr e' a,|

  \clef bass

  \repeat unfold 4

  {\csl \su g \csr \sd d' g, \csl \su fis \csr \sd d' g,|}

  \repeat unfold 2

  {\csl \su fis \csr \sd cis' fis, \csl \su e \csr \sd cis' fis,|}

  \repeat unfold 2

  {\csl \su e \csr \sd b' e, \csl \su d \csr \sd b' e,|}

  \repeat unfold 2

  {\csl \su d \csr \sd a' d, \csl \su c \csr \sd a' d,|}

  \repeat unfold 2

  {\csl \su c \csr \sd g' c, \csl \su a \csr \sd g' c,|}

  \csl \su g \csr \sd g' c, \csl \su fis, \csr \sd g' c,|

  \csl \su e,2.|

  \csr

  \repeat unfold 4 {r2.}|

  \time 2/4

  \repeat unfold 21{r2}|

  \clef treble

  \time 6/8

  e'''4 d8 c4 d8|


  }




  rightTwo = \relative c' {

  \global

  % Qui segue la musica.

  s2.*39|

  s2*21|

  g, b2.| 

  }




  leftOne = \relative c' {

  \global

  % Qui segue la musica.

  s2.*39|

  % s2*21|

  \csl

  % c,8 g' c b, g' c| 

  }




  leftTwo = \relative c {

  \global

  % Qui segue la musica.

  c'4.\suon b|

  c g|

  c b|

  c g|

  c b|

  c g|

  e' d|

  e b|

  e d|

  e b|

  \clef treble

  g' fis|

  g d|

  g fis|

  \clef bass

  c b|

  c g|

  c b|

  c b|

  b a|

  b a|

  a g|

  a g|

  g fis|

  g fis|

  g fis|

  g fis|

  fis e|

  fis e|

  e d|

  e d|

  d c|

  d c|

  c b|

  c a|

  g fis|

  s2.|

  \repeat unfold 4 {r2.}|

  \repeat unfold 21{r2}|

  \clef bass

  c'4. b| 

  }




  \score {

  \new PianoStaff \with {

  instrumentName = Pf.

  } 

  \new Staff = right \with {

  midiInstrument = acoustic grand

  }  \rightOne \\ \rightTwo 

  \new Staff = left \with {

  midiInstrument = acoustic grand

  } { \clef bass  \leftOne \\ \leftTwo  }

  

  \layout { }

  \midi {

  \context {

  \Score

  tempoWholesPerMinute = #(ly:make-moment 100 4)

  }

  }

  }


  -- 

  oiram/bin/selom



--


  ___
  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: \change Staff don't work fine

2011-09-13 Thread Xavier Scheuer
On 13 September 2011 17:07, Mario Moles mario-mo...@libero.it wrote:

 Any idea? Thank's!

 [code]


That's because you use the   \\   construct, which implicitly
creates voices 1 and 2 in *both* staves.

Please use explicitly instantiated voices instead and it should work
fine.  See the modified  \score  block below.

I hope we would have less problem with this when issue #1316
http://code.google.com/p/lilypond/issues/detail?id=1316
will be fixed!

Cheers,
Xavier

 Modified  \score  block

\score {
  \new PianoStaff \with {
instrumentName = Pf.
  } 
\new Staff = right \with {
  midiInstrument = acoustic grand
} {
  
\new Voice = rightOne {
  \voiceOne
  \rightOne
}
\new Voice = rightTwo {
  \voiceTwo
  \rightTwo
}
  
}
\new Staff = left \with {
  midiInstrument = acoustic grand
} {
  \clef bass
  
\new Voice = leftOne {
  \voiceOne
  \leftOne
}
\new Voice = leftTwo {
  \voiceTwo
  \leftTwo
}
  
}
  
}

 End

-- 
Xavier Scheuer x.sche...@gmail.com

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


Re: \change Staff don't work fine

2011-09-13 Thread Mario Moles
In data martedì 13 settembre 2011 17:14:37, hai scritto:
 There's too much music here to work out your problem.  Could you a) say
 what you believe is wrong, and b) cut the music down to a tiny example
 showing your problem.
 
 --
 Phil Holmes
 
Right! I'm sorry!
In the bar 2, leftOne: 2° g is not in the correct stave!


\version 2.15.10
csr = \change Staff = right
csl = \change Staff = left 

global = {
  \key g \major
  \time 6/8
}
rightOne = \relative c' {
  \global
  % Qui segue la musica.
  \global
  % Qui segue la musica.
  \csl c,8 \csr g'' c, \csl c, \csr g'' c,|
  \csl c, \csr g'' c, 
 
}

rightTwo = \relative c' {
  \global
  % Qui segue la musica.
  
}

leftOne = \relative c' {
  \global
  % Qui segue la musica.
  s4. s4.|
  g g|
}

leftTwo = \relative c {
  \global
  % Qui segue la musica.
  c4. c|
  c c|
}

\score {
  \new PianoStaff \with {
instrumentName = Pf.
  } 
\new Staff = right \with {
  midiInstrument = acoustic grand
}  \rightOne \\ \rightTwo 
\new Staff = left \with {
  midiInstrument = acoustic grand
} { \clef bass  \leftOne \\ \leftTwo  }
  
  \layout { }
  \midi {
\context {
  \Score
  tempoWholesPerMinute = #(ly:make-moment 100 4)
}
  }
}

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


Re: \change Staff don't work fine

2011-09-13 Thread Mario Moles
In data martedì 13 settembre 2011 17:24:49, hai scritto:
 On 13 September 2011 17:07, Mario Moles mario-mo...@libero.it wrote:
  Any idea? Thank's!
  
  [code]
Ok! Great! Thank you!
 
 That's because you use the   \\   construct, which implicitly
 creates voices 1 and 2 in *both* staves.
 
 Please use explicitly instantiated voices instead and it should work
 fine.  See the modified  \score  block below.
 
 I hope we would have less problem with this when issue #1316
 http://code.google.com/p/lilypond/issues/detail?id=1316
 will be fixed!
 
 Cheers,
 Xavier
 
  Modified  \score  block
 
 \score {
   \new PianoStaff \with {
 instrumentName = Pf.
   } 
 \new Staff = right \with {
   midiInstrument = acoustic grand
 } {
   
 \new Voice = rightOne {
   \voiceOne
   \rightOne
 }
 \new Voice = rightTwo {
   \voiceTwo
   \rightTwo
 }
 
 }
 \new Staff = left \with {
   midiInstrument = acoustic grand
 } {
   \clef bass
   
 \new Voice = leftOne {
   \voiceOne
   \leftOne
 }
 \new Voice = leftTwo {
   \voiceTwo
   \leftTwo
 }
 
 }
 
 }
 
  End

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


Re: \change Staff and barchecks in LilyPondTool

2010-12-15 Thread Valentin Villenave
On Mon, Dec 13, 2010 at 11:26 PM, George_ georgexu...@gmail.com wrote:
 I seem to be having a problem with \change Staff screwing up my barchecks.

Thanks, I've added it to the LilyPondTool bug tracker:
https://sourceforge.net/tracker/?func=detailaid=3138066group_id=91119atid=596024

Cheers,
Valentin.

(P.S. -- Hi Bertalan! ;-)

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


Re: \change Staff and barchecks in LilyPondTool

2010-12-15 Thread George_

Cheers. I didn't know where to put this, but I thought here was best, seeing
as I seem to see many people here seem to work on LilypondTool as well.

Thanks

George


Valentin Villenave wrote:
 
 On Mon, Dec 13, 2010 at 11:26 PM, George_ georgexu...@gmail.com wrote:
 I seem to be having a problem with \change Staff screwing up my
 barchecks.
 
 Thanks, I've added it to the LilyPondTool bug tracker:
 https://sourceforge.net/tracker/?func=detailaid=3138066group_id=91119atid=596024
 
 Cheers,
 Valentin.
 
 (P.S. -- Hi Bertalan! ;-)
 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 http://lists.gnu.org/mailman/listinfo/lilypond-user
 
 

-- 
View this message in context: 
http://old.nabble.com/%5Cchange-Staff-and-barchecks-in-LilyPondTool-tp30449894p30466779.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.


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


Re: \change Staff and barchecks in LilyPondTool

2010-12-14 Thread Phil Holmes
- Original Message - 
From: George_ georgexu...@gmail.com

To: lilypond-user@gnu.org
Sent: Monday, December 13, 2010 10:26 PM
Subject: \change Staff and barchecks in LilyPondTool




I seem to be having a problem with \change Staff screwing up my barchecks.
For example:

e16 d c d e8 f
\change Staff = LH
gis, e r a |

for me produces a barcheck of 9/8.

bes8. a16 g f e d
\change Staff = LH
cis4 f8 \rest cis |

gives a barcheck of 17/16, and

\change Staff = LH
r8 a16 gis a8 b
\change Staff = RH
c c16 b c8 d |

gives a barcheck of 5/8 (??).

It seems to me that each \change Staff line is for some reason being taken
as just another note. There's no error message in the log warning about
barchecks being wrong, so I assume this is only something to do with a
LilyPondTool definition or something like that.
--



Could you post a tiny, complete example that shows this, please?

--
Phil Holmes



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


Re: \change Staff and barchecks in LilyPondTool

2010-12-14 Thread George_


Phil Holmes-2 wrote:
 
 - Original Message - 
 From: George_ georgexu...@gmail.com
 To: lilypond-user@gnu.org
 Sent: Monday, December 13, 2010 10:26 PM
 Subject: \change Staff and barchecks in LilyPondTool
 
 Could you post a tiny, complete example that shows this, please?
 
 --
 Phil Holmes
 
 
 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 http://lists.gnu.org/mailman/listinfo/lilypond-user
 
 


Sure:

\version 2.13.40

staffPiano = \new PianoStaff {
\time 4/4

\new Staff = RH 
\relative c' {
c16 d e f g a b c8 b16 a g f e d c |

bes'8. a16 g f e d
\change Staff = LH
cis4 d,8 \rest cis' |

\change Staff = RH
e16 d c d e8 f
\change Staff = LH
gis, e r 
\change Staff = RH
a' |

\change Staff = LH
r8 a,16 gis a8 b
c c16 b c8 b |

}

\new Staff = LH {
\clef F
s1 s1 s1 s1
}

}



\score {

\staffPiano


  \layout {
  }
}

The first bar is just a CM scale; it's not really relevant, but its barcheck
is correct: 1/1.

Bar 2: 17/16
Bar 3: 11/8
Bar 4: 9/8
-- 
View this message in context: 
http://old.nabble.com/%5Cchange-Staff-and-barchecks-in-LilyPondTool-tp30449894p30457014.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.


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


Re: \change Staff and barchecks in LilyPondTool

2010-12-14 Thread Carl Sorensen



On 12/14/10 10:38 AM, George_ georgexu...@gmail.com wrote:

 
 
 
 Phil Holmes-2 wrote:
 
 - Original Message -
 From: George_ georgexu...@gmail.com
 To: lilypond-user@gnu.org
 Sent: Monday, December 13, 2010 10:26 PM
 Subject: \change Staff and barchecks in LilyPondTool
 
 Could you post a tiny, complete example that shows this, please?
 
 --
 Phil Holmes
 
 
 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 http://lists.gnu.org/mailman/listinfo/lilypond-user
 
 
 
 
 Sure:
 
 \version 2.13.40
 
 staffPiano = \new PianoStaff {
 \time 4/4
 
 \new Staff = RH
 \relative c' {
 c16 d e f g a b c8 b16 a g f e d c |
  
 bes'8. a16 g f e d
 \change Staff = LH
 cis4 d,8 \rest cis' |
  
 \change Staff = RH
 e16 d c d e8 f
 \change Staff = LH
 gis, e r
 \change Staff = RH
 a' |
  
 \change Staff = LH
 r8 a,16 gis a8 b
 c c16 b c8 b |
 
 }

 \new Staff = LH {
 \clef F
 s1 s1 s1 s1
 }
 
 }
 
 
 
 \score {
 
 \staffPiano
 

   \layout {
   }
 }
 
 The first bar is just a CM scale; it's not really relevant, but its barcheck
 is correct: 1/1.
 
 Bar 2: 17/16
 Bar 3: 11/8
 Bar 4: 9/8
 --



Phil,

This is a LilyPOndTool bug, not a LilyPond bug.  The output is correct in
LilyPOnd, as the original post indicated.

Thanks,

Carl


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


\change Staff and barchecks in LilyPondTool

2010-12-13 Thread George_

I seem to be having a problem with \change Staff screwing up my barchecks.
For example:

e16 d c d e8 f
\change Staff = LH
gis, e r a |

for me produces a barcheck of 9/8.

bes8. a16 g f e d
\change Staff = LH
cis4 f8 \rest cis |

gives a barcheck of 17/16, and

\change Staff = LH
r8 a16 gis a8 b 
\change Staff = RH
c c16 b c8 d |

gives a barcheck of 5/8 (??).

It seems to me that each \change Staff line is for some reason being taken
as just another note. There's no error message in the log warning about
barchecks being wrong, so I assume this is only something to do with a
LilyPondTool definition or something like that.
-- 
View this message in context: 
http://old.nabble.com/%5Cchange-Staff-and-barchecks-in-LilyPondTool-tp30449894p30449894.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.


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


Re: temporarily change staff indentation

2010-07-25 Thread Philipp Zedler
Hi Branco,

 Maybe an easier way would be to make multiple \score (one per part)
 but if I'm not wrong this would lead to several midi files and to
 repeat for each part the settings of time, clef, key, not to mention
 staffgroup etc.
I do use the alternative you describe. To avoid typing things twice I
use variables which are introduced here:
http://lilypond.org/doc/v2.13/Documentation/notation/file-structure
and input files which are explained here:
http://lilypond.org/doc/v2.13/Documentation/notation/including-lilypond-files

Cheers
Philipp


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


  1   2   >