Re: Edition Engraver -- Bar 1

2018-04-07 Thread Craig Dabelstein
Here is an example of the problem. The EE overide is working in measure 3
but not measure 1.

Craig


On 8 April 2018 at 05:43, arnepe  wrote:

> good evening all,
> (and hoping this post is related to the topic ...)
>
> I've just set up a small test-file case:
> if a Score starts with a \partial, the mod applied to 1 0/4 is mirrored on
> the upbeat as well (see  MWE-bar1.ly
> ).
>
> Otherwise mods in Bar 1 on the first beat work fine for me...
>
> cheers
> Arne
>
>
>
> --
> 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
>



-- 
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
*http://maximesmusic.com *


ee problem.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Edition Engraver -- Bar 1

2018-04-07 Thread arnepe
good evening all, 
(and hoping this post is related to the topic ...)

I've just set up a small test-file case:
if a Score starts with a \partial, the mod applied to 1 0/4 is mirrored on
the upbeat as well (see  MWE-bar1.ly
).

Otherwise mods in Bar 1 on the first beat work fine for me...

cheers
Arne



--
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: Edition Engraver -- Bar 1

2018-04-07 Thread Stefano Troncaro
Hi Craig,

Could you post a snippet of your code? I also had this problem before when
Voices were being created automatically because of the way the code was
structured. Maybe it's the same issue.

2018-04-07 4:08 GMT-03:00 Jan-Peter Voigt :

> Hi Craig,
>
> I'll investigate that on Monday. I thought I fixed this issue a while ago,
> but if you are facing it now there still needs to be something to be done.
>
> Jan-Peter
>
> Am 7. April 2018 08:22:52 MESZ schrieb Craig Dabelstein <
> craig.dabelst...@gmail.com>:
>>
>> Hi all,
>>
>> Is there something strange about trying to reference the first beat of
>> the first bar of a piece of music. My mods are all working except the one
>> on the first beat of bar 1.
>>
>> \editionMod global 1 0/4 gossec.simphonie.clarinetII.Voice etc...
>>
>> Any ideas?
>>
>> Craig
>>
>>
>> --
>> *Craig Dabelstein*
>> Maxime's Music
>> craig.dabelst...@gmail.com
>> *http://maximesmusic.com *
>>
>
> --
> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
>
> ___
> 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: double bar number

2018-04-07 Thread bb
Thank you! That does the job! I tried something else but had no success.
Now I know one first has to

    \remove "Bar_number_engraver"

in the \Score, than add the new one.

I rdeduced the lines, obviously the code is still working? Great! Thanks!

\version "2.18.2"

chordsone = \chordmode { c1:7  f1:7 c1:7 }
one =
  \relative c {
    \override Score.BarNumber.break-visibility = #all-visible
    \clef "bass_8"
    c,4 g' c, ges' | f c' f, des |c g' c, as' |
  }


harmonies = \chordmode { b2.:min fis2:min7 | }
\layout {
  \context {
    \Score
    \remove "Bar_number_engraver"
  }
  \context {
    \Staff
    \consists "Bar_number_engraver"
    \override BarNumber.break-visibility = #all-visible
  }
}

\score {
  <<
    \new ChordNames { \chordsone }
    \new Staff { \one }
  >>
}



Am 07.04.2018 um 15:25 schrieb Andrew Bernard:
> That prints the numbers high - I think the OP wants to avoid that.
>
> Have a look at this from the list, a possible answer.
>
> https://lists.gnu.org/archive/html/lilypond-user/2017-06/msg00382.html
>
> Andrew
>
>
>
> On 7 April 2018 at 23:22, Knute Snortum  > wrote:
>
> Try this:
>
> \version "2.19.80"
> chordsone = \chordmode { c1:7  f1:7 c1:7 }
> one = 
>   \relative c {
>     \override Score.BarNumber.break-visibility = #all-visible
>     \clef "bass_8"
>     c,4 g' c, ges' | f c' f, des |c g' c, as' |
>   }
>
> \score  {
>   <<
>     \new ChordNames { \chordsone }
>     \new Staff
>     \one
>   >>
> }
>
>
>
> ___
> 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: double bar number

2018-04-07 Thread bb
Thak you! But this is not the solution. I want the bar numbers just
above the note lines, separated from the chord names. Jazz players
complain the bar numbers neighboring the chord names as in Jazz
harmonies there sometimes are strange names of complicated chords.

Regards


Am 07.04.2018 um 15:22 schrieb Knute Snortum:
>
> \version "2.19.80"
> chordsone = \chordmode { c1:7  f1:7 c1:7 }
> one = 
>   \relative c {
>     \override Score.BarNumber.break-visibility = #all-visible
>     \clef "bass_8"
>     c,4 g' c, ges' | f c' f, des |c g' c, as' |
>   }
>
> \score  {
>   <<
>     \new ChordNames { \chordsone }
>     \new Staff
>     \one
>   >>
> }


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


Re: double bar number

2018-04-07 Thread Andrew Bernard
That prints the numbers high - I think the OP wants to avoid that.

Have a look at this from the list, a possible answer.

https://lists.gnu.org/archive/html/lilypond-user/2017-06/msg00382.html

Andrew



On 7 April 2018 at 23:22, Knute Snortum  wrote:

> Try this:
>
> \version "2.19.80"
> chordsone = \chordmode { c1:7  f1:7 c1:7 }
> one =
>   \relative c {
> \override Score.BarNumber.break-visibility = #all-visible
> \clef "bass_8"
> c,4 g' c, ges' | f c' f, des |c g' c, as' |
>   }
>
> \score  {
>   <<
> \new ChordNames { \chordsone }
> \new Staff
> \one
>   >>
> }
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: double bar number

2018-04-07 Thread Knute Snortum
Try this:

\version "2.19.80"
chordsone = \chordmode { c1:7  f1:7 c1:7 }
one =
  \relative c {
\override Score.BarNumber.break-visibility = #all-visible
\clef "bass_8"
c,4 g' c, ges' | f c' f, des |c g' c, as' |
  }

\score  {
  <<
\new ChordNames { \chordsone }
\new Staff
\one
  >>
}



---
Knute Snortum
(via Gmail)

On Sat, Apr 7, 2018 at 4:25 AM, bb  wrote:

> I want bar numbers for every bar and a low bar number position to avoid
> interference with the chord names. My first attempt shows two bar
> numbers one over the other. I do not want the second, the upper bar
> number. I cannot find a solution. Thanks for help.
>
> \version "2.19.80"
> chordsone = \chordmode { c1:7  f1:7 c1:7 }
> one = {
> \relative c {
> \override Score.BarNumber.break-visibility = #all-visible
> \clef "bass_8"
>   c,4 g' c, ges' | f c' f, des |c g' c, as' |
> }}
> \score  {
>   <<
> \new ChordNames { \chordsone }
> \new Staff
> \one
>  >>
> }
>   \layout {\context {
> \Staff
> \consists "Bar_number_engraver"
>   }}
>
>
> ___
> 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: Cross-staff chords question

2018-04-07 Thread Jacques Menu Muzhic
Thanks, Simon!

JM

> Le 7 avr. 2018 à 15:03, Simon Albrecht  a écrit :
> 
> On 07.04.2018 11:39, Jacques Menu Muzhic wrote:
>> When a hand doesn’t play, is it best for the keyboard player to read rests 
>> or should skips be used instead?
> 
> Definitely rests. Using skips is the convention if that hand only switched to 
> the other staff.
> There may be exceptions depending on context.
> 
> Best, Simon


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


Re: Cross-staff chords question

2018-04-07 Thread Simon Albrecht

On 07.04.2018 11:39, Jacques Menu Muzhic wrote:

When a hand doesn’t play, is it best for the keyboard player to read rests or 
should skips be used instead?


Definitely rests. Using skips is the convention if that hand only 
switched to the other staff.

There may be exceptions depending on context.

Best, Simon

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


double bar number

2018-04-07 Thread bb
I want bar numbers for every bar and a low bar number position to avoid
interference with the chord names. My first attempt shows two bar
numbers one over the other. I do not want the second, the upper bar
number. I cannot find a solution. Thanks for help.

\version "2.19.80"
chordsone = \chordmode { c1:7  f1:7 c1:7 }
one = {
\relative c {
\override Score.BarNumber.break-visibility = #all-visible
\clef "bass_8"
  c,4 g' c, ges' | f c' f, des |c g' c, as' |
}}
\score  {
  <<
    \new ChordNames { \chordsone }   
    \new Staff
    \one
 >>
}
  \layout {\context {
    \Staff
    \consists "Bar_number_engraver"
  }}


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


Re: Cross-staff chords question

2018-04-07 Thread Jacques Menu Muzhic
Hello Andrew,

When a hand doesn’t play, is it best for the keyboard player to read rests or 
should skips be used instead?

JM

> Le 7 avr. 2018 à 11:11, Andrew Bernard  a écrit :
> 
> Hi JM,
> 
> Speaking as a keyboard player myself, it's not just a matter of presenting 
> the notes. Usually in contexts like this it can be an indication of which 
> hand takes what, with the upper staff being the RH and the lower the LH. 
> There's no hard and fast rule about that, (and some players don't even seem 
> to know this) but it may help you decide how to engrave this.
> 
> Andrew
> 
> ___
> 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: Cross-staff chords question

2018-04-07 Thread Jacques Menu Muzhic
Hello Rutger, Malte and Andrew,

I overlooked \crossStaff and didn’t get the Span_stem_engraver should be used, 
sorry for that and for not removing the extraneous music in my last post.

Thanks for your help, and a nice day!

JM

> Le 7 avr. 2018 à 11:11, Andrew Bernard  a écrit :
> 
> Hi JM,
> 
> Speaking as a keyboard player myself, it's not just a matter of presenting 
> the notes. Usually in contexts like this it can be an indication of which 
> hand takes what, with the upper staff being the RH and the lower the LH. 
> There's no hard and fast rule about that, (and some players don't even seem 
> to know this) but it may help you decide how to engrave this.
> 
> Andrew
> 
> ___
> 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: Cross-staff chords question

2018-04-07 Thread Andrew Bernard
Hi JM,

Speaking as a keyboard player myself, it's not just a matter of presenting
the notes. Usually in contexts like this it can be an indication of which
hand takes what, with the upper staff being the RH and the lower the LH.
There's no hard and fast rule about that, (and some players don't even seem
to know this) but it may help you decide how to engrave this.

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


Re: Cross-staff chords question

2018-04-07 Thread Malte Meyn



Am 07.04.2018 um 10:51 schrieb Menu Jacques:
I’m no pianist though: is this OK for a keyboard player, or is Finale’s 
output: […] better, and if so, how can I obtain the cross-staves stems this way?


What is better depends on whether it should be played with one hand or 
two. Please always give a minimal code example, not this way too much 
generated code.


\version "2.19.81"

\new PianoStaff \with {
  \consists #Span_stem_engraver
} <<
  \new Staff = "top" \relative {
s1
s4 \crossStaff { \stemDown \autoBeamOff c'8  }
  }
  \new Staff = "bot" \relative {
\clef bass
a8 \change Staff = "top" e' \change Staff = "bot" a, \change Staff 
= "top" e'

c' e, \change Staff = "bot" a, \change Staff = "top" b'
\stemDown
\change Staff = "bot"  \change Staff = "top"  
\change Staff = "bot"  g'

  }
>>

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


Re: Cross-staff chords question

2018-04-07 Thread Rutger Hofman
Did you (following the manual 
http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-keyboards#cross_002dstaff-stems 
):


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

to enable cross-staff stems?

And did you (following the manual) specify \crossStaff { .. } for the 
chords you want cross-staff? Be aware, you (probably) need to disable 
auto-beaming and specify stem direction explicitly for those.


I applied these, the resulting .ly and .pdf are attached. It shows 
cross-staff chords.


Rutger

On 04/07/2018 10:51 AM, Menu Jacques wrote:

Hello folks,

It seems that the last two chords should be split in two, with each one 
placed in the desired staff.


This leads to the following, see the second score block below:


I’m no pianist though: is this OK for a keyboard player, or is Finale’s 
output:


better, and if so, how can I obtain the cross-staves stems this way?

Thanks for your help!

JM


%

\version "2.19.58"
% automatically converted by musicxml2ly from 
43d-MultiStaff-StaffChange.xml_inter.xml



\header {
   texidoc =
   "Staff changes in a piano staff.
           The voice from the second staff has some notes/chords on the 
first
           staff. The final two chords have some notes on the first, 
some on

           the second staff."
}

\layout {
   \context {
     \Score
     skipBars = ##t
     autoBeaming = ##f
   }
}

PartPOneVoiceOne =  \relative c' {
   \clef "treble" \key c \major \time 4/4
   s1 | % 2
   R1 \bar "|."
}

PartPOneVoiceTwo =  \relative a {
   \clef "bass" \key c \major \time 4/4 | % 1
   a8 [
   \change Staff="1"
   e'8
   \change Staff="2"
   a,8
   \change Staff="1"
   e'8 ] c'8 [ e,8
   \change Staff="2"
   a,8 b'8 ] 8 [
   \change Staff="1"
   8
   \change Staff="2"
   8
   \change Staff="2"
   8 ]
   \change Staff="2"
   r2 \bar "|."
}


% The score definition
\score {
   <<
     \new PianoStaff
     <<
       \context Staff = "1" <<
         \context Voice = "PartPOneVoiceOne" {  \PartPOneVoiceOne }
       >>

       \context Staff = "2" <<
         \context Voice = "PartPOneVoiceTwo" {  \PartPOneVoiceTwo }
       >>
     >>
   >>

   \layout {}
   % To create MIDI output, uncomment the following line:
   %  \midi {\tempo 4 = 100 }
}


PartPOneVoiceOneBIS =  \relative c' {
   \clef "treble" \key c \major \time 4/4

   % \override Stem.cross-staff = ##t
   %  \override Stem.length = #19 % this is in half-spaces,
   % so it makes stems 9.5 staffspaces long
   %  \override Stem.Y-offset = #-6 % stems are normally lengthened
   % upwards, so here we must lower the stem by the amount
   % equal to the lengthening - in this case (19 - 7) / 2
   % (7 is default stem length)

   %  \override NoteColumn.ignore-collision = ##t

   R1 | % 2
   r4
   %\once \override Stem.direction = #LEFT
   c8
   8
   r2
   \bar "|."
}

PartPOneVoiceTwoBIS =  \relative a {
   \clef "bass" \key c \major \time 4/4 | % 1

   a8 [
   \change Staff="1"
   e'8
   \change Staff="2"
   a,8
   \change Staff="1"
   e'8 ] c'8 [ e,8
   \change Staff="2"
   a,8 b'8 ] 8 [
   \change Staff="1"
   8
   \change Staff="2"
   8
   \change Staff="2"
   g'8 ]
   \change Staff="2"
   r2 \bar "|."
}


% The score definition
\score {
   <<
     \new PianoStaff
     <<
       \context Staff = "1" <<
         \context Voice = "PartPOneVoiceOne" {  \PartPOneVoiceOneBIS }
       >>

       \context Staff = "2" <<
         \context Voice = "PartPOneVoiceTwo" {  \PartPOneVoiceTwoBIS }
       >>
     >>
   >>

   \layout {}
   % To create MIDI output, uncomment the following line:
   %  \midi {\tempo 4 = 100 }
}

%

Le 6 avr. 2018 à 23:11, Menu Jacques > a écrit :


Hello folks,

Under section « Cross-staff chords - beaming problems workaround » in 
the LP Snippets, one can find a way to obtain chords spanning two 
staves without any « <...> » chord in fact:





I’d like to keep the standard chord notation to obtain:


and currently only get (see last two chords):



Tried to add a staff change after the first g’ inside the last chord 
(in red below), but that is not syntactically correct.


Is there a way in recent LP versions to make that approach work? That 
would be much more direct that the snippet mentioned above.


Thanks for your help!

JM


%%

\version "2.19.58"
% automatically converted by musicxml2ly from 
43d-MultiStaff-StaffChange.xml_inter.xml



\header {
    texidoc =
    "Staff changes in a piano staff.
          The voice from the second staff has some notes/chords on the 
first
          staff. The final two chords have some notes on the first, 
some on

          the second staff."
    }

\layout {
    \context { \Score
        skipBars = ##t
        autoBeaming = ##f
        }
    }
PartPOneVoiceOne =  \relative c' {
    \clef "treble" \key c \major \time 4/4 s1 | % 2
    R1 \bar "|."
    }


Re: Edition Engraver -- Bar 1

2018-04-07 Thread Jan-Peter Voigt
Hi Craig,

I'll investigate that on Monday. I thought I fixed this issue a while ago, but 
if you are facing it now there still needs to be something to be done.

Jan-Peter 

Am 7. April 2018 08:22:52 MESZ schrieb Craig Dabelstein 
:
>Hi all,
>
>Is there something strange about trying to reference the first beat of
>the
>first bar of a piece of music. My mods are all working except the one
>on
>the first beat of bar 1.
>
>\editionMod global 1 0/4 gossec.simphonie.clarinetII.Voice etc...
>
>Any ideas?
>
>Craig
>
>
>-- 
>*Craig Dabelstein*
>Maxime's Music
>craig.dabelst...@gmail.com
>*http://maximesmusic.com *

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Edition Engraver -- Bar 1

2018-04-07 Thread Craig Dabelstein
Hi all,

Is there something strange about trying to reference the first beat of the
first bar of a piece of music. My mods are all working except the one on
the first beat of bar 1.

\editionMod global 1 0/4 gossec.simphonie.clarinetII.Voice etc...

Any ideas?

Craig


-- 
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
*http://maximesmusic.com *
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user