Re: print change of clef after barline

2014-06-01 Thread Damian leGassick

On 31 May 2014, at 22:12, Thomas Morley wrote:

 2014-05-31 20:05 GMT+02:00 Damian leGassick damianlegass...@mac.com:
 thanks Harm
 
 I found a way...though I don't understand how or why the vector works for 
 break-align-orders
 
 Damian
 
 Did you look into
 IR 3.1.22 BreakAlignment -break-align-orders ?
 
 Or NR A.17 Layout properties -break-align-orders
 
 
 Please specify whats not clear there and how to improve the description.
 
 Cheers,
  Harm

what is not clear is this bit:

The format is a vector of length 3, where each element is one order for 
end-of-line, middle of line, and start-of-line, respectively. 

the override in this:

\version 2.18.0

musicRH = {
\override Staff.Clef.full-size-change = ##t
\set Staff.printKeyCancellation = ##f
\override Score.BreakAlignment #'break-align-orders =
  #(make-vector 3 '(
   span-bar
   breathing-sign
   staff-bar
   clef
   key-cancellation
   key-signature
   time-signature))
 
 \key fis \major 
 s1 \bar ||  
 \set Staff.forceClef = ##t \key es \major s \bar || 
 \set Staff.forceClef = ##t \key a \major
 }
\layout { ragged-right = ##f }

\score {
  \new PianoStaff 
   
 \new Staff {\musicRH} 
 \new Staff {\musicRH} 
   
}

has only one order, suggesting that it acts on end-of-line only, but it also 
affects middle of line and also changes the spacing at start of line

I couldn't work out form the docs how to do the override just for middle of 
line (which is what I want), or how to do a vector with a different orders for 
end/middle/start respectively

thanks

Damian

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


Re: print change of clef after barline

2014-06-01 Thread David Kastrup
Damian leGassick damianlegass...@mac.com writes:

 On 31 May 2014, at 22:12, Thomas Morley wrote:

 Did you look into
 IR 3.1.22 BreakAlignment -break-align-orders ?
 
 Or NR A.17 Layout properties -break-align-orders

 what is not clear is this bit:

 The format is a vector of length 3, where each element is one order
 for end-of-line, middle of line, and start-of-line, respectively.

 \override Score.BreakAlignment #'break-align-orders =
   #(make-vector 3 '(
span-bar
breathing-sign
staff-bar
clef
key-cancellation
key-signature
time-signature))

 has only one order,

No.

 -- Scheme Procedure: make-vector len [fill]
 -- C Function: scm_make_vector (len, fill)
 Return a newly allocated vector of LEN elements.  If a second
 argument is given, then each position is initialized to FILL.
 Otherwise the initial contents of each position is unspecified.

 suggesting that it acts on end-of-line only, but it also affects
 middle of line and also changes the spacing at start of line

 I couldn't work out form the docs how to do the override just for
 middle of line (which is what I want), or how to do a vector with a
 different orders for end/middle/start respectively

By specifying three different vectors instead of creating one vector
with three equal elements.

-- 
David Kastrup

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


Re: print change of clef after barline

2014-06-01 Thread Thomas Morley
2014-06-01 10:23 GMT+02:00 David Kastrup d...@gnu.org:
 Damian leGassick damianlegass...@mac.com writes:

 On 31 May 2014, at 22:12, Thomas Morley wrote:

 Did you look into
 IR 3.1.22 BreakAlignment -break-align-orders ?

 Or NR A.17 Layout properties -break-align-orders

 what is not clear is this bit:

 The format is a vector of length 3, where each element is one order
 for end-of-line, middle of line, and start-of-line, respectively.

 \override Score.BreakAlignment #'break-align-orders =
   #(make-vector 3 '(
span-bar
breathing-sign
staff-bar
clef
key-cancellation
key-signature
time-signature))

 has only one order,

 No.

  -- Scheme Procedure: make-vector len [fill]
  -- C Function: scm_make_vector (len, fill)
  Return a newly allocated vector of LEN elements.  If a second
  argument is given, then each position is initialized to FILL.
  Otherwise the initial contents of each position is unspecified.

 suggesting that it acts on end-of-line only, but it also affects
 middle of line and also changes the spacing at start of line

 I couldn't work out form the docs how to do the override just for
 middle of line (which is what I want), or how to do a vector with a
 different orders for end/middle/start respectively

 By specifying three different vectors instead of creating one vector
 with three equal elements.

 --
 David Kastrup

@Damian

David explained it already, though, here a bit more demonstrative:

Look at:

guile (use-modules (ice-9 pretty-print))
guile (pretty-print (make-vector 3 '(
   span-bar
   breathing-sign
   staff-bar
   clef
   key-cancellation
   key-signature
   time-signature)))

It returns:

#((span-bar
breathing-sign
staff-bar
clef
key-cancellation
key-signature
time-signature)
  (span-bar
breathing-sign
staff-bar
clef
key-cancellation
key-signature
time-signature)
  (span-bar
breathing-sign
staff-bar
clef
key-cancellation
key-signature
time-signature))

Now it should be clear why this affects end-of-line, middle of line
and start-of-line in the same manner.
To get different settings you can't use (make-vector 3 '( ... )), but
you have to specify each entry in the vector differently.

@David
If an experienced user like Damian stumbles across it, it might be
worth clearifying it in NR/IR.
What do you think?

Cheers,
  Harm

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


Re: print change of clef after barline

2014-06-01 Thread James

On 01/06/14 10:29, Thomas Morley wrote:

2014-06-01 10:23 GMT+02:00 David Kastrup d...@gnu.org:

Damian leGassick damianlegass...@mac.com writes:


On 31 May 2014, at 22:12, Thomas Morley wrote:

Did you look into
IR 3.1.22 BreakAlignment -break-align-orders ?

Or NR A.17 Layout properties -break-align-orders

what is not clear is this bit:

The format is a vector of length 3, where each element is one order
for end-of-line, middle of line, and start-of-line, respectively.
 \override Score.BreakAlignment #'break-align-orders =
   #(make-vector 3 '(
span-bar
breathing-sign
staff-bar
clef
key-cancellation
key-signature
time-signature))

has only one order,

No.

  -- Scheme Procedure: make-vector len [fill]
  -- C Function: scm_make_vector (len, fill)
  Return a newly allocated vector of LEN elements.  If a second
  argument is given, then each position is initialized to FILL.
  Otherwise the initial contents of each position is unspecified.


suggesting that it acts on end-of-line only, but it also affects
middle of line and also changes the spacing at start of line

I couldn't work out form the docs how to do the override just for
middle of line (which is what I want), or how to do a vector with a
different orders for end/middle/start respectively

By specifying three different vectors instead of creating one vector
with three equal elements.

--
David Kastrup

@Damian

David explained it already, though, here a bit more demonstrative:

Look at:

guile (use-modules (ice-9 pretty-print))
guile (pretty-print (make-vector 3 '(
span-bar
breathing-sign
staff-bar
clef
key-cancellation
key-signature
time-signature)))

It returns:

#((span-bar
 breathing-sign
 staff-bar
 clef
 key-cancellation
 key-signature
 time-signature)
   (span-bar
 breathing-sign
 staff-bar
 clef
 key-cancellation
 key-signature
 time-signature)
   (span-bar
 breathing-sign
 staff-bar
 clef
 key-cancellation
 key-signature
 time-signature))

Now it should be clear why this affects end-of-line, middle of line
and start-of-line in the same manner.
To get different settings you can't use (make-vector 3 '( ... )), but
you have to specify each entry in the vector differently.

@David
If an experienced user like Damian stumbles across it, it might be
worth clearifying it in NR/IR.
What do you think?

Yes, even I could follow that.

We could use this example and one that shows how to write it for 
specifying different vectors. I assume from reading this it would be


((make-vector 1 '( ... )),
(make-vector 2 '( ... )),
(make-vector 3 '( ... )),)

Or something - but then again, I am not the target audience for the IR :)

James


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


Re: print change of clef after barline

2014-06-01 Thread Thomas Morley
2014-06-01 11:32 GMT+02:00 James pkx1...@gmail.com:
 On 01/06/14 10:29, Thomas Morley wrote:

 2014-06-01 10:23 GMT+02:00 David Kastrup d...@gnu.org:

 Damian leGassick damianlegass...@mac.com writes:

 On 31 May 2014, at 22:12, Thomas Morley wrote:

 Did you look into
 IR 3.1.22 BreakAlignment -break-align-orders ?

 Or NR A.17 Layout properties -break-align-orders

 what is not clear is this bit:

 The format is a vector of length 3, where each element is one order
 for end-of-line, middle of line, and start-of-line, respectively.
  \override Score.BreakAlignment #'break-align-orders =
#(make-vector 3 '(
 span-bar
 breathing-sign
 staff-bar
 clef
 key-cancellation
 key-signature
 time-signature))

 has only one order,

 No.

   -- Scheme Procedure: make-vector len [fill]
   -- C Function: scm_make_vector (len, fill)
   Return a newly allocated vector of LEN elements.  If a second
   argument is given, then each position is initialized to FILL.
   Otherwise the initial contents of each position is unspecified.

 suggesting that it acts on end-of-line only, but it also affects
 middle of line and also changes the spacing at start of line

 I couldn't work out form the docs how to do the override just for
 middle of line (which is what I want), or how to do a vector with a
 different orders for end/middle/start respectively

 By specifying three different vectors instead of creating one vector
 with three equal elements.

 --
 David Kastrup

 @Damian

 David explained it already, though, here a bit more demonstrative:

 Look at:

 guile (use-modules (ice-9 pretty-print))
 guile (pretty-print (make-vector 3 '(
 span-bar
 breathing-sign
 staff-bar
 clef
 key-cancellation
 key-signature
 time-signature)))

 It returns:

 #((span-bar
  breathing-sign
  staff-bar
  clef
  key-cancellation
  key-signature
  time-signature)
(span-bar
  breathing-sign
  staff-bar
  clef
  key-cancellation
  key-signature
  time-signature)
(span-bar
  breathing-sign
  staff-bar
  clef
  key-cancellation
  key-signature
  time-signature))

 Now it should be clear why this affects end-of-line, middle of line
 and start-of-line in the same manner.
 To get different settings you can't use (make-vector 3 '( ... )), but
 you have to specify each entry in the vector differently.

 @David
 If an experienced user like Damian stumbles across it, it might be
 worth clearifying it in NR/IR.
 What do you think?

 Yes, even I could follow that.

 We could use this example and one that shows how to write it for specifying
 different vectors. I assume from reading this it would be

 ((make-vector 1 '( ... )),
 (make-vector 2 '( ... )),
 (make-vector 3 '( ... )),)


Not exactly.

Here some crazy settings for time-signature:

#(
   ;; end of line: time-signature right before key-signature
   (span-bar
breathing-sign
staff-bar
clef
key-cancellation
time-signature
key-signature)
   ;; middle of line: time-signature right before staff-bar
  (span-bar
breathing-sign
time-signature
staff-bar
clef
key-cancellation
key-signature)
   ;; start of line: time-signature right before clef
  (span-bar
breathing-sign
staff-bar
time-signature
clef
key-cancellation
key-signature))

Though, applying this would return warnings:
  No spacing entry from TimeSignature to `clef'
  No spacing entry from TimeSignature to `key-signature'
which can be resolved with additional overrides for TimeSignature.space-alist


Here a compilable snippet:

\version 2.19.6

{
  \override Score.BreakAlignment #'break-align-orders =
##(
   ;; end of line: time-signature right before key-signature
   (span-bar
breathing-sign
staff-bar
clef
key-cancellation
time-signature
key-signature)
   ;; middle of line: time-signature before staff-bar
  (span-bar
breathing-sign
time-signature
staff-bar
clef
key-cancellation
key-signature)
   ;; start of line: time-signature before clef
  (span-bar
breathing-sign
staff-bar
time-signature
clef
key-cancellation
key-signature))
  \override Score.TimeSignature.space-alist.clef = #'(extra-space . 1)
  \override Score.TimeSignature.space-alist.key-signature = #'(extra-space . 1)

  \key c \minor
  \time 2/2
  c''1
  \key cis \minor
  \time 4/4
  d''
  \break
  \key c \minor
  \time 8/8
  e''
}


Cheers,
  Harm

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


Re: print change of clef after barline

2014-06-01 Thread David Kastrup
Thomas Morley thomasmorle...@gmail.com writes:

make-vector

 @David
 If an experienced user like Damian stumbles across it, it might be
 worth clearifying it in NR/IR.
 What do you think?

I don't think that we can reasonably explain stuff like make-vector in
our manuals.

The best we can do is to avoid it in elementary examples.  That may mean
spelling three identical lists out, or using
(let ((breaklst ...)) (vector breaklst breaklst breaklst))

It's probably most straightforward to spell the lists out three times.
That leaves the user with a tedious but reliable and easy to understand
recipe.

-- 
David Kastrup

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


Re: print change of clef after barline

2014-06-01 Thread Thomas Morley
2014-06-01 12:09 GMT+02:00 David Kastrup d...@gnu.org:
 Thomas Morley thomasmorle...@gmail.com writes:

 make-vector

 @David
 If an experienced user like Damian stumbles across it, it might be
 worth clearifying it in NR/IR.
 What do you think?

 I don't think that we can reasonably explain stuff like make-vector in
 our manuals.

 The best we can do is to avoid it in elementary examples.  That may mean
 spelling three identical lists out, or using
 (let ((breaklst ...)) (vector breaklst breaklst breaklst))

 It's probably most straightforward to spell the lists out three times.
 That leaves the user with a tedious but reliable and easy to understand
 recipe.

 --
 David Kastrup

Agreed.
I'll go for a patch.

Cheers,
  Harm

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


chord name

2014-06-01 Thread MING TSANG
lilyponders:
I am transcribe a score hardcopy and I encounter lily does not generate as the 
score hardcopy.
questions:
(1)  are they the same?
(2)  how can I make it show as the score hardcopy?
(3)  Is there a sample chord name sample?

Below is a sample code:
\version 2.19.7
\language english
chordz = \chordmode {
bf2:2      % score hardcopy show Bf2 : lily code as bf2:2 -generate as Bfsus2  
?are they the same?
f2:sus    % score hardcopy show Fsus :  lily code as f2:sus -generate as F  
?are they the same?
f2           % score hardcopy show F2 : lily code as f2 -generate as F  ?are 
they the same? 
ef:min7  % score hardcopy show EfM7 : lily code as ef:min7 -generate as Efm7  
?are they the same? 
}
\score {


\new ChordNames \chordz

\new Staff { \chordz }


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


Re: chord name

2014-06-01 Thread James

On 01/06/14 11:34, MING TSANG wrote:

lilyponders:
I am transcribe a score hardcopy and I encounter lily does not 
generate as the score hardcopy.

questions:
(1)  are they the same?
(2)  how can I make it show as the score hardcopy?
(3)  Is there a sample chord name sample?

Below is a sample code:
\version 2.19.7
\language english
chordz = \chordmode {
bf2:2  % score hardcopy show Bf2 : lily code as bf2:2 -generate 
as Bfsus2 ?are they the same?
f2:sus% score hardcopy show Fsus :  lily code as f2:sus -generate 
as F ?are they the same?
f2 % score hardcopy show F2 : lily code as f2 -generate as F 
?are they the same?
ef:min7  % score hardcopy show EfM7 : lily code as ef:min7 -generate 
as Efm7 ?are they the same?

}
\score {

\new ChordNames \chordz
\new Staff { \chordz }

\layout { }
}



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

Ming,

I cannot answer the specific comparative examples, but the Appendix

http://lilypond.org/doc/v2.18/Documentation/notation-big-page#common-chord-modifiers

does show much more than it ever did in the 2.18 docs.

Does this new information here help or not?

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


Re: print change of clef after barline

2014-06-01 Thread Thomas Morley
2014-06-01 12:19 GMT+02:00 Thomas Morley thomasmorle...@gmail.com:
 2014-06-01 12:09 GMT+02:00 David Kastrup d...@gnu.org:
 Thomas Morley thomasmorle...@gmail.com writes:

 make-vector

 @David
 If an experienced user like Damian stumbles across it, it might be
 worth clearifying it in NR/IR.
 What do you think?

 I don't think that we can reasonably explain stuff like make-vector in
 our manuals.

 The best we can do is to avoid it in elementary examples.  That may mean
 spelling three identical lists out, or using
 (let ((breaklst ...)) (vector breaklst breaklst breaklst))

 It's probably most straightforward to spell the lists out three times.
 That leaves the user with a tedious but reliable and easy to understand
 recipe.

 --
 David Kastrup

 Agreed.
 I'll go for a patch.

 Cheers,
   Harm


Well, I have a problem:

I assume the entries in
IR 3.1.22 BreakAlignment -break-align-orders
Or NR A.17 Layout properties -break-align-orders
are generated from define-grob-properties.scm
Correct?

We have already:
http://www.lilypond.org/doc/v2.19/Documentation/snippets/pitches#pitches-separating-key-cancellations-from-key-signature-changes

Therefore I think refering to that snippet would be sufficient.
Is it feasible to reference it from inside define-grob-properties.scm
If yes, how to do it?

Cheers,
  Harm

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


Re: chord name

2014-06-01 Thread MING TSANG
James:
Thank you for the link.  I will study it and let you know.
Emmanuel,
Ming


On Sunday, June 1, 2014 6:54:47 AM, James pkx1...@gmail.com wrote:
 


On 01/06/14 11:34, MING TSANG wrote:

lilyponders:
I am transcribe a score hardcopy and I encounter lily does not generate as the 
score hardcopy.
questions:
(1)  are they the same?
(2)  how can I make it show as the score hardcopy?
(3)  Is there a sample chord name sample?


Below is a sample code:
\version 2.19.7
\language english
chordz = \chordmode {
bf2:2      % score hardcopy show Bf2 : lily code as bf2:2 -generate as Bfsus2 
?are they the same?
f2:sus    % score hardcopy show Fsus :  lily code as f2:sus -generate as F 
?are they the same?
f2           % score hardcopy show F2 : lily code as f2 -generate as F ?are 
they the same? 
ef:min7  % score hardcopy show EfM7 : lily code as ef:min7 -generate as Efm7 
?are they the same? 
}
\score {


\new ChordNames \chordz

\new Staff { \chordz }


\layout { }
}





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

I cannot answer the specific comparative examples, but the Appendix

http://lilypond.org/doc/v2.18/Documentation/notation-big-page#common-chord-modifiers

does show much more than it ever did in the 2.18 docs.

Does this new information here help or not?

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


bar numbers above StaffGroups

2014-06-01 Thread Orm Finnendahl
Hi,

 I'm trying to print bar numbers not only at the top of the score, but
also above selected groups, (like brass, percussion, strings, etc.).

The code below does the trick, but the bar numbers are both printed in
columns above the topmost staff. Is there a canonical way to get them
printed directly above the StaffGroup?

I know there is a workaround by inserting an empty staff as topmost
staff of the group with Staff_symbol_engraver and such removed,
BarNumberEngraver enabled for that staff, keeping it alive and
reducing its height to 0. But I guess that wouldn't work very well if
notes on the topmost visible staff of that StaffGroup are sticking out
at the top: All bar numbers of the StaffGroup in that line then would
get printed way above the staff.

--
Orm

\version 2.19.5

music = { \relative c' { \repeat unfold 16 { c4 d e f } } }

\score {
  
\new Staff { \music }
\new Staff { \music }
\new StaffGroup = mygroup \with {
  \consists Bar_number_engraver
}
{

\new Staff { \music }
\new Staff { \music }

  }
  

  \layout{
\context { 
  \Score
  \override BarNumber.break-visibility = ##(#t #t #t)
}
  }
}



Using \consists Bar_number_engraver doesn't seem to do anything if
defined in a StaffGroup, but works for staffs. This is disadvantegous
as the barnumbers above the topmost staff in a group disappear if the
staff gets removed with \removeEmptyStaves.

Below are some snippets to show what I'm talking about. Is there a way
to make this work for a Staffgroup?

--
Orm

This doesn't show any barnumbers above the strings:

\

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


Re: Problems with DC al Fine template

2014-06-01 Thread Knute Snortum
In my previous example, just change _\dc to ^\dc and you have it.


Knute Snortum
(via Gmail)


On Sun, Jun 1, 2014 at 5:52 AM, Yann yann@free.fr wrote:

  Ok, I was too quick to post, now I remember the reason for these
  \consists and \remove statements. I have chords in my template, and I
  wanted the Fine and DC marks to be printed just above the staff
  (that is, between the chords and the staff). About this, where would
  you put the marks ? Between chords and staff, or above chords ?
 
  But I discovered it can be achieved by keeping the lines related to
  Mark_engraver. the \removeStaff_collecting_engraver seems to be
  the one m
  On Sat, May 24, 2014 at 10:14 AM, Yann yann@free.fr wrote:
 essing with the measure number position.
 
  so my (reduced) working example is as follows :
  \version 2.18.0
 
  \paper { #(set-paper-size a4) }
 
  accords = \chordmode {
c1 c2 f g c f g g1 c c2 c |
  }
 
  melody = \relative c' {
c'4 c c b |
c8 b a g f g a f |
b a g f e f g e |
a g f e d e f fis |
g2 g |
c4 c c d |
e8 f e d c2\once \override Score.RehearsalMark.self-alignment-X =
  #RIGHT \mark \markup { \tiny \italic D.C. al Fine } |
  }
 
  % Staves
  basePart = 
\new ChordNames { \accords }
\new Staff \with {
  \consists Mark_engraver
} 
  \new Voice = melody { \repeat volta 2 { \melody } }

  
 
  \book {
\score {
  \basePart
  \layout {
\context {
  \Score
  \remove Mark_engraver
}
  }
}
  }
 
 
  Yann
 2014-05-25 15:08 GMT+02:00 Knute Snortum ksnor...@gmail.com:
  Personally, I'd put the DC below the staff in this situation:
 
  \version 2.18.0
 
  accords = \chordmode {
c1 c2 f g c f g g1 c c2 c |
  }
 
  alignRight = \once \override Score.RehearsalMark.self-alignment-X =
 #RIGHT
  dc = \markup { \tiny \italic D.C. al Fine }
 
  melody = \relative c' {
c'4 c c b |
c8 b a g f g a f |
b a g f e f g e |
a g f e d e f fis |
g2 g |
c4 c c d |
e8 f e d \alignRight c2 _\dc |
  }
 
  basePart = 
\new ChordNames { \accords }
\new Staff 
  \new Voice = melody { \repeat volta 2 { \melody } }

 
 
  \score {
\basePart
\layout {
}
  }
 
  Knute Snortum
  (via Gmail)

 Thank you very much for your answer. But, in a case where there are
 lyrics as well below the staves, won't it get confusing if the DC mark
 is also below the staff ?

 Yann

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


Re: bar numbers above StaffGroups

2014-06-01 Thread Thomas Morley
2014-06-01 14:23 GMT+02:00 Orm Finnendahl orm.finnend...@hfmdk-frankfurt.de:
 Hi,

  I'm trying to print bar numbers not only at the top of the score, but
 also above selected groups, (like brass, percussion, strings, etc.).

 The code below does the trick, but the bar numbers are both printed in
 columns above the topmost staff. Is there a canonical way to get them
 printed directly above the StaffGroup?

 I know there is a workaround by inserting an empty staff as topmost
 staff of the group with Staff_symbol_engraver and such removed,
 BarNumberEngraver enabled for that staff, keeping it alive and
 reducing its height to 0. But I guess that wouldn't work very well if
 notes on the topmost visible staff of that StaffGroup are sticking out
 at the top: All bar numbers of the StaffGroup in that line then would
 get printed way above the staff.

 --
 Orm

 \version 2.19.5

 music = { \relative c' { \repeat unfold 16 { c4 d e f } } }

 \score {
   
 \new Staff { \music }
 \new Staff { \music }
 \new StaffGroup = mygroup \with {
   \consists Bar_number_engraver
 }
 {
 
 \new Staff { \music }
 \new Staff { \music }
 
   }
   

   \layout{
 \context {
   \Score
   \override BarNumber.break-visibility = ##(#t #t #t)
 }
   }
 }



 Using \consists Bar_number_engraver doesn't seem to do anything if
 defined in a StaffGroup, but works for staffs. This is disadvantegous
 as the barnumbers above the topmost staff in a group disappear if the
 staff gets removed with \removeEmptyStaves.

 Below are some snippets to show what I'm talking about. Is there a way
 to make this work for a Staffgroup?

 --
 Orm



A first idea:

\version 2.19.5

my-with =
\with {
  \override BarNumber.break-visibility = ##(#t #t #f)
  \consists Bar_number_engraver
  \consists Staff_collecting_engraver
  \override BarNumber.after-line-breaking = ##f
}

mI = \relative c' { \repeat unfold 16 { c4 d e f } }
mII = \relative c' { \repeat unfold 16 s1 }

\score {
  
\new Staff { \transpose c cis \mI }
\new Staff { \transpose c d \mI }
\new StaffGroup = mygroup \my-with
{

\new Staff { \transpose c ees \mI }
\new Staff { \transpose c e \mI }

  }
  

  \layout{
\context {
  \Score
  \override BarNumber.break-visibility = ##(#t #t #t)
}
\context {
  \Staff
  \RemoveEmptyStaves
  \override VerticalAxisGroup.remove-first = ##t
}
  }
}


Though, playing around with \mI and \mII you'll notice the BArNumbers
are not removed but overlay each other, while empty staves are
removed.


Cheers,
  Harm

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


Re: bar numbers above StaffGroups

2014-06-01 Thread David Kastrup
Orm Finnendahl orm.finnend...@hfmdk-frankfurt.de writes:

 Hi,

  I'm trying to print bar numbers not only at the top of the score, but
 also above selected groups, (like brass, percussion, strings, etc.).

 The code below does the trick, but the bar numbers are both printed in
 columns above the topmost staff. Is there a canonical way to get them
 printed directly above the StaffGroup?

 I know there is a workaround by inserting an empty staff as topmost
 staff of the group with Staff_symbol_engraver and such removed,
 BarNumberEngraver enabled for that staff, keeping it alive and
 reducing its height to 0. But I guess that wouldn't work very well if
 notes on the topmost visible staff of that StaffGroup are sticking out
 at the top: All bar numbers of the StaffGroup in that line then would
 get printed way above the staff.

 --
 Orm

 \version 2.19.5

 music = { \relative c' { \repeat unfold 16 { c4 d e f } } }

 \score {
   
 \new Staff { \music }
 \new Staff { \music }
 \new StaffGroup = mygroup \with {
   \consists Bar_number_engraver
 }
 {
 
 \new Staff { \music }
 \new Staff { \music }
 
   }
   

   \layout{
 \context { 
   \Score
   \override BarNumber.break-visibility = ##(#t #t #t)
 }
   }
 }




 Using \consists Bar_number_engraver doesn't seem to do anything if
 defined in a StaffGroup, but works for staffs. This is disadvantegous
 as the barnumbers above the topmost staff in a group disappear if the
 staff gets removed with \removeEmptyStaves.


2.2.8 Bar_number_engraver
-

A bar number is created whenever ‘measurePosition’ is zero and when
there is a bar line (i.e., when ‘whichBar’ is set).  It is put on top of
all staves, and appears only at the left side of the staff.  The staves
are taken from ‘stavesFound’, which is maintained by *note
Staff_collecting_engraver::.


2.2.112 Staff_collecting_engraver
-

Maintain the ‘stavesFound’ variable.

   Properties (read)

 ‘stavesFound’ (list of grobs)
  A list of all staff-symbols found.
   Properties (write)

 ‘stavesFound’ (list of grobs)
  A list of all staff-symbols found.

   ‘Staff_collecting_engraver’ is part of the following context(s):
*note DrumStaff::, *note GregorianTranscriptionStaff::, *note
KievanStaff::, *note MensuralStaff::, *note PetrucciStaff::, *note
Score::, *note Staff::, *note TabStaff:: and *note VaticanaStaff::.

-- 
David Kastrup

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


\bar partially broken for just me or everyone?

2014-06-01 Thread Tim McNamara
Since updating to 2.18.2 and using JazzLILY I notice that when I compile scores 
with \bar “|:” or \bar “:|” the repeat signs are not printed.  The opening 
repeat is omitted and the closing repeat is omitted and the end barline is also 
missing (if the repeat happens at the end of a line, anyway).  \bar “|.” works, 
however.  

Is this something peculiar to my situation or is this happening for others, too?



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


Re: \bar partially broken for just me or everyone?

2014-06-01 Thread Malte Meyn
Oh, and of course, convert-ly knows this, so you can use it to update 
old source files.


On 01.06.2014 18:59, Malte Meyn wrote:

It’s not a bug, it’s a feature (see documentation; Changes for 2.18 and
Notation Reference). \bar .|: and \bar :|. should do what you want.

On 01.06.2014 18:40, Tim McNamara wrote:

Since updating to 2.18.2 and using JazzLILY I notice that when I
compile scores with \bar “|:” or \bar “:|” the repeat signs are not
printed.  The opening repeat is omitted and the closing repeat is
omitted and the end barline is also missing (if the repeat happens at
the end of a line, anyway).  \bar “|.” works, however.

Is this something peculiar to my situation or is this happening for
others, too?



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



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


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


Phrasing Slur with Arrow

2014-06-01 Thread Kate Sekula
Hello all!  Is there a way to have a phrasing slur with an arrow? I was hoping 
for something like:  \override PhrasingSlur.bound-details.right.arrow = ##t, 
but that's no good.  Thanks!

~Kate


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


Re: Phrasing Slur with Arrow

2014-06-01 Thread Malte Meyn

Hello,

this was discussed just a few weeks ago at the German LilyPond forum:
http://www.lilypondforum.de/index.php?topic=1744.msg9669#msg9669
This post contains an (as far as I know) ready-to-use solution. Maybe 
Harm, who also subscribed to this list, will answer questions to this ;)


Malte

On 01.06.2014 20:31, Kate Sekula wrote:

Hello all!  Is there a way to have a phrasing slur with an arrow? I was hoping
for something like:  \override PhrasingSlur.bound-details.right.arrow = ##t,
but that's no good.  Thanks!

~Kate


___
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: \bar partially broken for just me or everyone?

2014-06-01 Thread Tim McNamara

On Jun 1, 2014, at 11:59 AM, Malte Meyn lilyp...@maltemeyn.de wrote:

 It’s not a bug, it’s a feature (see documentation; Changes for 2.18 and 
 Notation Reference). \bar .|: and \bar :|. should do what you want.

Huh!  Thanks, it took me a couple minutes to see the logic to that change.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: print change of clef after barline

2014-06-01 Thread Damian leGassick

On 1 Jun 2014, at 12:26, David Kastrup wrote:

 Thomas Morley thomasmorle...@gmail.com writes:
 
 2014-06-01 12:19 GMT+02:00 Thomas Morley thomasmorle...@gmail.com:
 2014-06-01 12:09 GMT+02:00 David Kastrup d...@gnu.org:
 Thomas Morley thomasmorle...@gmail.com writes:
 
 make-vector
 
 @David
 If an experienced user like Damian stumbles across it, it might be
 worth clearifying it in NR/IR.
 What do you think?
 
 I don't think that we can reasonably explain stuff like make-vector in
 our manuals.
 
 The best we can do is to avoid it in elementary examples.  That may mean
 spelling three identical lists out, or using
 (let ((breaklst ...)) (vector breaklst breaklst breaklst))
 
 It's probably most straightforward to spell the lists out three times.
 That leaves the user with a tedious but reliable and easy to understand
 recipe.
 
 --
 David Kastrup
 
 Agreed.
 I'll go for a patch.
 
 Cheers,
  Harm
 
 
 Well, I have a problem:
 
 I assume the entries in
 IR 3.1.22 BreakAlignment -break-align-orders
 Or NR A.17 Layout properties -break-align-orders
 are generated from define-grob-properties.scm
 Correct?
 
 Values from define-grobs.scm.
 
 We have already:
 http://www.lilypond.org/doc/v2.19/Documentation/snippets/pitches#pitches-separating-key-cancellations-from-key-signature-changes
 
 Therefore I think refering to that snippet would be sufficient.
 Is it feasible to reference it from inside define-grob-properties.scm
 If yes, how to do it?
 
 Judging from other manual entries, by putting the following at the end
 of the documentation string:
 
 @snippets
 
 @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
 {separating-key-cancellations-from-key-signature-changes.ly}
 
 -- 
 David Kastrup
 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user

hi all

yes, a link to that snippet would have enabled me to hack it out; searching the 
LSR it was not apparent that that snippet held all the answers

for 'normal but adventurous' users I wouldn't worry about examples in the 
manual being 'tedious but reliable' - I use a lot of the internals tweaks every 
day without really understanding how they work - the one's i've got to grips 
with quickest are the ones with the fullest examples.

thanks for all the help - I really appreciate it 

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


A book on how music notation should look

2014-06-01 Thread Richard Shann
Someone just pointed me to this source of opinion on music notation:

https://archive.org/details/EssentialDictionaryOfMusicNotation

I don't think I've seen it mentioned on this list before, so thought
folk might be interested. I just used it to educate myself on the
subject of melisma for which I was roundly condemned a while back.

Richard



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


Re: Getting LilyPond code with included files into LyX

2014-06-01 Thread Damian leGassick

On 26 May 2014, at 07:54, Ben Beeson wrote:

 Hi all,
 
 I decided that I wanted to compile a tune book using LyX. I have collected up 
 several tunes that I want in the tune book and these tunes are all engraved 
 with LilyPond.  Now I need to figure out how to get these tunes into a LyX 
 file so I can compile the tune book. 
 
 I have figured out how to get some music notes such as a scale into a LyX 
 document using the LilyPond module. Now I need to   figure out how to 
 make that work when your LilyPond code needs an included file such as 
 bagpipe.ly to render the music correctly.  So far I am not having much luck 
 with including bagpipe.ly and the LyX documentation has not helped much in 
 that regard.  I am missing something that will tell LyX to send the 
 instructions for the include files to LilyPond when it builds the file.  I am 
 hoping there is a simple fix for this, but I have not found it yet.  If 
 anyone knows how to get the LyX LilyPond module to include bagpipe.ly  or 
 some other path/to/some/file.ly   when building a document with LilyPond to 
 work, I would appreciate a short note to help explain that.
 
 Cheers and thanks in advance,
 
 Ben 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user

It works for me - though there's a catch...

On Mac OS 10.6.8 with LyX 2.0.5 I can get the included files to work *only* if 
they are located in

/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/ly/ 
(right-click on the Lilypond app and 'show package contents')

e.g. a source file that has: 

\include bagpipe.ly 

compiles for me in LyX if there is a file:

/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/ly/bagpipe.ly

/include path/to/some/file.ly does not work in LyX even if the file compiles 
as normal with 'regular' Lilypond

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


Re: Please how to use the Scheme debugger?

2014-06-01 Thread mark damerell
My apologies to D. Kastrup for having replied in the wrong way.

It seems that Lilypond ( lilypond-2.18.2-1.linux-x86.sh  installed
with default options )  comes with its own private copy of Guile
(1.8.7). Unfortunately this means that installing another version
of Guile does not change anything.  Please is there any way to
break the link between Lilypond and this version of Guile?

At present, the only way I can get a working debugger is by reverting
to Lilypond 2.14 .
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: print change of clef after barline

2014-06-01 Thread Thomas Morley
2014-06-01 13:26 GMT+02:00 David Kastrup d...@gnu.org:
 Thomas Morley thomasmorle...@gmail.com writes:

 2014-06-01 12:19 GMT+02:00 Thomas Morley thomasmorle...@gmail.com:
 2014-06-01 12:09 GMT+02:00 David Kastrup d...@gnu.org:
 Thomas Morley thomasmorle...@gmail.com writes:

 make-vector

 @David
 If an experienced user like Damian stumbles across it, it might be
 worth clearifying it in NR/IR.
 What do you think?

 I don't think that we can reasonably explain stuff like make-vector in
 our manuals.

 The best we can do is to avoid it in elementary examples.  That may mean
 spelling three identical lists out, or using
 (let ((breaklst ...)) (vector breaklst breaklst breaklst))

 It's probably most straightforward to spell the lists out three times.
 That leaves the user with a tedious but reliable and easy to understand
 recipe.

 --
 David Kastrup

 Agreed.
 I'll go for a patch.

 Cheers,
   Harm


 Well, I have a problem:

 I assume the entries in
 IR 3.1.22 BreakAlignment -break-align-orders
 Or NR A.17 Layout properties -break-align-orders
 are generated from define-grob-properties.scm
 Correct?

 Values from define-grobs.scm.

 We have already:
 http://www.lilypond.org/doc/v2.19/Documentation/snippets/pitches#pitches-separating-key-cancellations-from-key-signature-changes

 Therefore I think refering to that snippet would be sufficient.
 Is it feasible to reference it from inside define-grob-properties.scm
 If yes, how to do it?

 Judging from other manual entries, by putting the following at the end
 of the documentation string:

 @snippets

 @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
 {separating-key-cancellations-from-key-signature-changes.ly}

 --
 David Kastrup

https://codereview.appspot.com/96650050/

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


slur and tie in a chord

2014-06-01 Thread MING TSANG
lilyponders:
I have trouble make the following code working:
I like to see ef, tie to Ef,  Ef tie to Ef, Af slur to G.  The ties are ok but 
slur does not display.
 
\version 2.19.7
\language english
{
\key ef\major
\clef bass
ef,~ ef~ af(2. |ef, ef g)2.
}

Emmanuel,
Ming___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: bug triplet line collides with fingering

2014-06-01 Thread MarcM
I thought this bug had been reported but apparently not. I just recompiled
the same file with LilyPond_2.19.7 and the triplet line still collides with
either the fingering or with the slur.

\version 2.19.7
\language english
{
 \relative d' {
\tuplet 3/2 {d'4\flageolet a8-4(}  \tuplet 3/2{f d a)} 
 }
}
  
I tried several options and neither look nice. any way to reduce the width
of the bracket may be?









--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/bug-triplet-line-collides-with-fingering-tp57290p162993.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


small notehead in a chord

2014-06-01 Thread MING TSANG
lilyponders:
For the following code, how can I make notehead Ef, Ef, in the chords  smaller?

\version 2.19.7
\language english
{
\key ef\major
\time 3/4 
\clef bass
ef, ef af2. |ef, ef g2.
}
Emmanuel,
Ming.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Separate pedal staff shifts notes in music staves

2014-06-01 Thread Helge Kruse
To reproduce the behaviour you just have to extend on staff. e.g. the 
first stuff:


  \new Staff \relative c''{
\time 6/4

  { c2.( d2) d4 | c2.( d2) d4 | }
  \\
  { g,2. a | g2. a |}

c1. c c c c c c c
  }

Regards
Helge

Am 02.06.2014 04:27, schrieb Javier Ruiz-Alma:

I have Pedal markings on a separate 'dynamics staff within a PianoStaff


I need to place a sustainOff between 5th and 6th beats (on 6/4 time).
If I place the sustainOff on the 5th beat, the 6 quarter notes in the bass are 
kept at equal distances, however, if I place the sustainOff after the 5th beat, 
the note column of the 6th beat is shifted left.

I'm attaching images of the typesetting:

PedalStaff1.png (equal beat spacing when sustainOff placed on 5th beat):
s1\sustainOn s4 s4\sustainOff

PedalStaff2.png (compressed 6th beat when sustainOff placed after 5th beat):
{s1\sustainOn s8. s16\sustainOff s4}, or {s1\sustainOn s8 s8\sustainOff s4}

I tried to replicate with a tiny example, but I can't replicate this shifting 
behavior :

\version 2.18.2
\new PianoStaff

\new Staff \relative c''{
\time 6/4
{ c2.( d2) d4 | c2.( d2) d4 | } \\
{ g,2. a | g2. a |}



}
\new Staff \relative c'{
\clef bass
c4( ees f,ees'g f)
c4( ees f,ees'g f)
}
\new Dynamics {
\time 6/4
s1\sustainOn s4 s4\sustainOff
s1\sustainOn s8. s16\sustainOff s4
}




The issue does occur in bar78 in the following score:
https://gist.github.com/dominicus/8085e4d3e8692ca64d27


Any ideas as to why a separate pedal staff may influence the note columns in 
other staves?


Javier Ruiz-Alma




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





smime.p7s
Description: S/MIME Kryptografische Unterschrift
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: (was: print change of clef after barline) scm vectors in frescobaldi

2014-06-01 Thread Wilbert Berendsen
Op Sun, 01 Jun 2014 22:56:15 +0200
Simon Albrecht simon.albre...@mail.de schreef:

 Looking at this code, I notice that Frescobaldi doesn’t seem to 
 recognise Scheme vectors. It would be nice (if also rarely important)
 to have them correctly highlighted.
 
 Best, Simon

Fixed!
Thanks,
Wilbert


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


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


Re: bug triplet line collides with fingering

2014-06-01 Thread James
ccing bug list

On 02/06/14 02:37, MarcM wrote:
 I thought this bug had been reported but apparently not. I just recompiled
 the same file with LilyPond_2.19.7 and the triplet line still collides with
 either the fingering or with the slur.

 \version 2.19.7
 \language english
 {
  \relative d' {
 \tuplet 3/2 {d'4\flageolet a8-4(}  \tuplet 3/2{f d a)} 
  }
 }
   
 I tried several options and neither look nice. any way to reduce the width
 of the bracket may be?









 --
 View this message in context: 
 http://lilypond.1069038.n5.nabble.com/bug-triplet-line-collides-with-fingering-tp57290p162993.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


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