Re: Converting a large project from 2.18 to 2.19: what to expect?

2017-04-04 Thread Malte Meyn 


Am 05.04.2017 um 08:17 schrieb Shevek:
> 1) How stable is 2.19 for end users on a demanding project? It seems like
> forever since 2.18, so I'm sort of surprised there hasn't been 2.20 already.
> Is there some major problem I should be worried about in 2.19?

See
https://sourceforge.net/p/testlilyissues/issues/search/?q=%28_type%3ACritical+OR+labels%3ARegression%29+AND+%28status%3ANew+OR+status%3AAccepted+OR+status%3AStarted%29
for a list of critical bugs/regressions. It would be nice to have a 2.20
soon but these have to be solved before a release.

I would recommend to simply try 2.19 (install 2.19, make a copy of your
project, run convert-ly and lilypond on this copy), I have never had
problems with 2.19 that weren’t there in 2.18. (Of course that doesn’t
mean that there cannot be any problems but it seems like problems are
very rare for many use cases.)

> 2) What should I expect to break under 2.19? Music output changes to look
> out for as I proofread? Things that might make snippets or Scheme behave
> differently or not be backwards compatible?

Output changes: MIDI articulation, MultiMeasureRest spacing, whiteout style.

Input changes: the omission of “parser” and “location” arguments in
music functions, \partial at volta repeats and time signature changes.

These are only some examples. For details and other changes see
http://lilypond.org/doc/v2.19/Documentation/changes/

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

Converting a large project from 2.18 to 2.19: what to expect?

2017-04-04 Thread Shevek 
Hi,

I'm currently in the process of composing a symphony in Lilypond 2.18.2.
There are a few graphical bugs that are making me consider converting the
project to the current 2.19 (parentheses/accidental collision, tempo mark
spacing with uniform-stretching), but I'm hesitant to jump immediately
because I have like 20k+ lines of code, some of which was already updated
from 2.16, and also libraries of custom snippets.

So my questions:

1) How stable is 2.19 for end users on a demanding project? It seems like
forever since 2.18, so I'm sort of surprised there hasn't been 2.20 already.
Is there some major problem I should be worried about in 2.19?

2) What should I expect to break under 2.19? Music output changes to look
out for as I proofread? Things that might make snippets or Scheme behave
differently or not be backwards compatible?

3) Are there any notable regressions in terms of graphical output? My music
already looks pretty great overall in 2.18.2, so I don't want to go through
the trouble of upgrading to fix graphical bugs if I'll just be trading them
for different graphical bugs. From experience so far, it seems my project is
expansive enough that there's a good chance I'll run into any given
graphical bug, unless it's specific to early music notation or something.

Thanks so much for your help. I realize this is a pretty broad question.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Converting-a-large-project-from-2-18-to-2-19-what-to-expect-tp201938.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: Double Bar with Grace Notes Problem -- Problem Solved

2017-04-04 Thread Bill Kone 
Phil

 

You were exactly right.

 

I should have added spacer grace notes to each part.

 

Now each part prints correctly while the score is also correct.

 

Thanks for helping out on a problem that I had given up on.

 

Bill

 

From: Phil Holmes [mailto:m...@philholmes.net] 
Sent: Tuesday, April 4, 2017 4:37 AM
To: Bill Kone ; lilypond-user@gnu.org
Subject: Re: Double Bar with Grace Notes Problem

 

If you read
http://lilypond.org/doc/v2.18/Documentation/notation/special-rhythmic-concer
ns#grace-notes - specifically Known issues and warnings, you'll see that you
need to have equal length grace notes or rests in all parts.  This can be
done with spacer rests.  The second bar of clarinet 2 should be:

 

\grace s8 d''8 r8 \grace s8 d''8 r8 r4 |


--
Phil Holmes

 

 

- Original Message - 

From: Bill Kone   

To: lilypond-user@gnu.org   

Sent: Tuesday, April 04, 2017 6:36 AM

Subject: Double Bar with Grace Notes Problem

 

I have a lot of concert/marching band music some of which is old hand
written manuscript. From time-to-time  I try to transcribe the hand-written
manuscript to a much more readable  product.

Generally I do each instrument then combine them into a score.

 

The problem is, in this case as shown in the sample below and attached
image, that a double bar before the grace notes, on the clarinet 1 and 2
seems to cause a separate bar line, which also increments the measure
counter, but only on the score.

 

Below is an extraction as a two staff script (the same as when each
independent part is combined into a score). Each part needs to have the same
bar markings so I can't just leave the double bar out on a couple of parts.

 

In this case I just took the double bars out completely from all the parts
but I am still wondering if it is my ignorance or what seems to me to be a
bug. 

 

In the attached script, by commenting out the double bar in the clarinet2
staff the problem goes away on the conductor's score but of course now the
clarinet2 part has a missing double bar.

 

I tried creating a variable defined as:  dblbar= { \bar "||" } then on the
conductor score defined it as: dlbar = {} for all but the top line of the
conductor's score in this case the flute. I believe it might work but made
management more difficult for something that I figured I was doing wrong.

 

Any thoughts?

 

See also attached image

 

\version "2.18.2"

 

\score{

  \new GrandStaff <<



\new Staff = "Clarinet1" 

{

  \set Staff.instrumentName = #"Clar1"

  \time 3/4

  g''8 r8 g8 r8 r4 |

  \bar "||" 

  \grace {g'16 ( b'16} d''8 )

  r8\grace {g'16 ( b'16} d''8 ) r8 r4 |

}





\new Staff = "clarinet2" 

{

  \set Staff.instrumentName = \markup { Clar2 }

  \time 3/4

  g''8 r8 g8 r8 r4 |

  

  % -- If I comment out this bar formats OK

  \bar "||" 

  % --

  

  d''8 r8 d''8 r8 r4 |

}

  >>

  \layout{}

}


  _  


___
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: Set a property in before-line-breaking

2017-04-04 Thread Andrew Bernard 
Hi Urs,

I am fascinated by your recent deep questions about lilypond internals
programming. Can you tell us about the project you are working on? It seems
very grand.

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

Re: Is there a better way of assigning an instrument name to Voice?

2017-04-04 Thread Mike Dean 
>From caagr98:
<<
  \new Staff = "mel" \with { instrumentName = "Melody" } \melody
  \new PianoStaff \with { instrumentName = "Piano" } <<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>
>>
Cobbling items from Item 1.6 in the Notation manual [0.02458] and Piano
template (simple) [0.11905]

Mike Dean

On Tue, Apr 4, 2017 at 1:46 PM, Mike Dean  wrote:

> Somewhere in the LSR is a snippet to shrink the size of the melody line
>
> Mike Dean
>
> On Tue, Apr 4, 2017 at 1:39 PM, Mike Dean  wrote:
>
>> After trial by errors and caagr98's (thanks much!!!) help:
>>
>> <<
>> \new Staff = "mel" { \melody }
>> <<  \set Staff.instrumentName = "Melody" >>
>>  \new PianoStaff <<
>> \set PianoStaff.instrumentName = #"Piano  "
>> \new Staff = "upper" \upper
>> \new Staff = "lower" \lower
>>   >>
>> >>
>>
>> (
>>
>> Mike Dean
>>
>> On Tue, Apr 4, 2017 at 12:56 PM, Mike Dean  wrote:
>>
>>> < < \new Voice = "mel" { \melody }
>>>* \set Voice.instrumentName = #"Melody"*
>>>  \new PianoStaff <<
>>> \set PianoStaff.instrumentName = #"Piano  "
>>> \new Staff = "upper" \upper
>>> \new Staff = "lower" \lower
>>>   >>
>>> >>
>>> Mike Dean
>>>
>>
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is there a better way of assigning an instrument name to Voice?

2017-04-04 Thread caagr98 

<<
  \new Staff = "mel" \with { instrumentName = "Melody" } \melody
  \new PianoStaff \with { instrumentName = "Piano" } <<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>
>>

That *should* work.

You forgot to reply-list again.

On 04/04/17 19:47, Mike Dean wrote:

Still had struggles getting the output correct with "\with"

Mike Dean

On Tue, Apr 4, 2017 at 1:41 PM, mailto:caag...@gmail.com>> wrote:

Still not using \with?

On 04/04/17 19:39, Mike Dean wrote:

After trial by errors and caagr98's (thanks much!!!) help:

<<
\new Staff = "mel" { \melody }
<<  \set Staff.instrumentName = "Melody" >>
 \new PianoStaff <<
\set PianoStaff.instrumentName = #"Piano  "
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>



(

Mike Dean

On Tue, Apr 4, 2017 at 12:56 PM, Mike Dean mailto:dean...@aquinas.edu>
>> wrote:

< < \new Voice = "mel" { \melody }
   *\set Voice.instrumentName = #"Melody"*
 \new PianoStaff <<
\set PianoStaff.instrumentName = #"Piano  "
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>
>>
Mike Dean




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



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





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

Re: Is there a better way of assigning an instrument name to Voice?

2017-04-04 Thread Mike Dean 
Somewhere in the LSR is a snippet to shrink the size of the melody line

Mike Dean

On Tue, Apr 4, 2017 at 1:39 PM, Mike Dean  wrote:

> After trial by errors and caagr98's (thanks much!!!) help:
>
> <<
> \new Staff = "mel" { \melody }
> <<  \set Staff.instrumentName = "Melody" >>
>  \new PianoStaff <<
> \set PianoStaff.instrumentName = #"Piano  "
> \new Staff = "upper" \upper
> \new Staff = "lower" \lower
>   >>
> >>
>
> (
>
> Mike Dean
>
> On Tue, Apr 4, 2017 at 12:56 PM, Mike Dean  wrote:
>
>> < < \new Voice = "mel" { \melody }
>>* \set Voice.instrumentName = #"Melody"*
>>  \new PianoStaff <<
>> \set PianoStaff.instrumentName = #"Piano  "
>> \new Staff = "upper" \upper
>> \new Staff = "lower" \lower
>>   >>
>> >>
>> Mike Dean
>>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is there a better way of assigning an instrument name to Voice?

2017-04-04 Thread caagr98 

Still not using \with?

On 04/04/17 19:39, Mike Dean wrote:

After trial by errors and caagr98's (thanks much!!!) help:

<<
\new Staff = "mel" { \melody }
<<  \set Staff.instrumentName = "Melody" >>
 \new PianoStaff <<
\set PianoStaff.instrumentName = #"Piano  "
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>




(

Mike Dean

On Tue, Apr 4, 2017 at 12:56 PM, Mike Dean mailto:dean...@aquinas.edu>> wrote:

< < \new Voice = "mel" { \melody }
   *\set Voice.instrumentName = #"Melody"*
 \new PianoStaff <<
\set PianoStaff.instrumentName = #"Piano  "
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>
>>
Mike Dean




___
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: Is there a better way of assigning an instrument name to Voice?

2017-04-04 Thread Mike Dean 
After trial by errors and caagr98's (thanks much!!!) help:

<<
\new Staff = "mel" { \melody }
<<  \set Staff.instrumentName = "Melody" >>
 \new PianoStaff <<
\set PianoStaff.instrumentName = #"Piano  "
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>
>>

(

Mike Dean

On Tue, Apr 4, 2017 at 12:56 PM, Mike Dean  wrote:

> < < \new Voice = "mel" { \melody }
>* \set Voice.instrumentName = #"Melody"*
>  \new PianoStaff <<
> \set PianoStaff.instrumentName = #"Piano  "
> \new Staff = "upper" \upper
> \new Staff = "lower" \lower
>   >>
> >>
> Mike Dean
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is there a better way of assigning an instrument name to Voice?

2017-04-04 Thread caagr98 
Yeah, I don't think Voice supports instrumentName; my bad. I'd recommend 
replacing the \new Voice with a \new Staff. Aside from working properly 
with certain \with properties, I personally think it makes more sense. 
It's certainly more consistent with the piano staff, at least.


I would also recommend using \new for creating new contexts, and only 
use \context for referring to existing ones. You can use \with 
{instrumentName} on the PianoStaff as well, by the way.


Oh, and please reply to the list as well. In Thunderbird, it's [Reply 
List] instead of [Reply]; it's probably something similar in other clients.


On 04/04/17 19:27, Mike Dean wrote:

Stumbled across it:

<<
\context Staff = "mel" { \melody }
<<
  \set Staff.instrumentName = "Melody" >>
 \context PianoStaff <<
\set PianoStaff.instrumentName = #"Piano  "
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>





Mike Dean

On Tue, Apr 4, 2017 at 1:22 PM, Mike Dean mailto:dean...@aquinas.edu>> wrote:


On Tue, Apr 4, 2017 at 1:00 PM, mailto:caag...@gmail.com>> wrote:

\with { instrumentName = "Melody" }


Thanks..
However, I did not succeed in getting the name to print:

Inline image 1

I was looking at the Staff headword snippet [0.02458] for an idea,
but I am not understanding it correctly...Would I need to put things
in a \context Staff command:

<<
\context Staff = "melody" <<
  \set Staff.instrumentName = "Melody" >>
 \context PianoStaff <<
\set PianoStaff.instrumentName = #"Piano  "
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>


Mike Dean




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

Re: Is there a better way of assigning an instrument name to Voice?

2017-04-04 Thread caagr98 

You can use a \with block:

\new Voice = "mel" \with { instrumentName = "Melody" } { \melody }

On 04/04/17 18:56, Mike Dean wrote:

< < \new Voice = "mel" { \melody }
   *\set Voice.instrumentName = #"Melody"*
 \new PianoStaff <<
\set PianoStaff.instrumentName = #"Piano  "
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>



Mike Dean


___
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

Is there a better way of assigning an instrument name to Voice?

2017-04-04 Thread Mike Dean 
< < \new Voice = "mel" { \melody }
   * \set Voice.instrumentName = #"Melody"*
 \new PianoStaff <<
\set PianoStaff.instrumentName = #"Piano  "
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>
>>
Mike Dean
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: German User Forum down

2017-04-04 Thread Johannes Roeßler 
Hi, Joei from the German Forum here - I second Malte and would also support If 
I can help there.
@Malte have you or somebody else contacted the admin? Any news?

cheers, Joei

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

Re: Set a property in before-line-breaking

2017-04-04 Thread Urs Liska 


Am 04.04.2017 um 13:48 schrieb Urs Liska:
> Hi,
>
> one more time a question about the order of operations.
>
> In the following MWE I use ly:grob-set-property! in the
> before-line-breaking callback to set the X-offset property of the
> NoteHead's parent NoteColumn.
>
> This has the expected effect and visually offsets the note column
> accordingly, but when I read out the property with ly:grob-property in
> the after-line-breaking callback (the stencil callback that I actually
> use behaves the same) it returns '(), i.e. "unset".
>
>
> \version "2.19.54"
>
> {
>   \override NoteHead.before-line-breaking =
>   #(lambda (nh)
>  (let ((nc (ly:grob-parent nh Y)))
>(ly:grob-set-property! nc 'X-offset 4)))
>   \override NoteHead.after-line-breaking =
>   #(lambda (nh)
>  (let ((nc (ly:grob-parent nh Y)))
>(ly:message "offset : ~a" (ly:grob-property nc 'X-offset
>   c'1
> }
>  
> I'm somewhat confused that at the later point in time the property
> seemingly isn't present although it obviously does what I expect it to do.
>
> The background is: I need to offset the note column to make space for an
> object left to it. As I can't do that automatically I want to write out
> a message telling the user to what value he has to set the x offset.
> This setting of the x offset happens during before-line-breaking, they
> can't use \override in the input files. With the behaviour as I see it I
> can only say "please add N to your current X-offset" (instead of "set
> X-offset to M").
>
> Any explanations or suggestions?
>
> TIA
> Urs
>

Just for the record: I've found a workaround by saving the offset in the
before-line-breaking function, so I can add that value later to report
the correct data. But it's still confusing ...

Urs

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

What is the hook to execute *after* everything else?

2017-04-04 Thread Urs Liska 
Hi all,

once more something about the order of operations (someone should
finally write a book about this topic ...):

I'm collecting information in a Scheme alist, which is populated in the
stencil callback function.

When everything else has been processed I'd like to print a report from
this alist on the console (or in a file), but I don't know how I can
trigger such a function. I thought I'd write an engraver and use the
(finalize) clause, but obviously this is still too early (the alist is
empty at that point).

Could someone please point me in the right direction?

Thanks
Urs


-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Re: Access Score.NoteColumn from a given note column

2017-04-04 Thread Urs Liska 
Hi David,


Am 03.04.2017 um 15:04 schrieb David Nalesnik:
> On Mon, Apr 3, 2017 at 6:59 AM, Urs Liska  wrote:
>>
>> Am 03.04.2017 um 13:57 schrieb Urs Liska:
>>> Is there a way to either affect the Grob in the Score context (probably
>>> not) or to retrieve a list/array of all NoteColumns that happen at the
>>> same time in other contexts?
> The associated paper column will contain grobs from other contexts:
>
> \new PianoStaff <<
>   \new Staff
>   \relative {
> \override Score.NoteHead.before-line-breaking =
> #(lambda (nh)
>(let*
> ((col (ly:item-get-column nh))
>  (elts (ly:grob-array->list (ly:grob-object col 'elements)))
>  (ncs (filter (lambda (elt) (grob::has-interface elt
> 'note-column-interface)) elts))
>  (nc (ly:grob-parent nh Y))
>  (id (ly:grob-property nh 'id))
>  (mod (assoc-ref mods id)))
> (if mod
> (for-each (lambda (n)
> (ly:grob-set-property! n 'X-offset mod))
>   ncs))
> ))
> c'1 ~ \tweak #'id "one" c2 e
>   }
>   \new Staff
>   \relative {
> R1
> c'2 c
>   }
> HTH,
> David

Thanks, this is exactly what I needed. I'm slowly getting my head around
navigating this information (as is extensively documented in the list
archives ;-) ), but obviously I stopped short of trying out *this*
combination.

Urs

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Set a property in before-line-breaking

2017-04-04 Thread Urs Liska 
Hi,

one more time a question about the order of operations.

In the following MWE I use ly:grob-set-property! in the
before-line-breaking callback to set the X-offset property of the
NoteHead's parent NoteColumn.

This has the expected effect and visually offsets the note column
accordingly, but when I read out the property with ly:grob-property in
the after-line-breaking callback (the stencil callback that I actually
use behaves the same) it returns '(), i.e. "unset".


\version "2.19.54"

{
  \override NoteHead.before-line-breaking =
  #(lambda (nh)
 (let ((nc (ly:grob-parent nh Y)))
   (ly:grob-set-property! nc 'X-offset 4)))
  \override NoteHead.after-line-breaking =
  #(lambda (nh)
 (let ((nc (ly:grob-parent nh Y)))
   (ly:message "offset : ~a" (ly:grob-property nc 'X-offset
  c'1
}
 
I'm somewhat confused that at the later point in time the property
seemingly isn't present although it obviously does what I expect it to do.

The background is: I need to offset the note column to make space for an
object left to it. As I can't do that automatically I want to write out
a message telling the user to what value he has to set the x offset.
This setting of the x offset happens during before-line-breaking, they
can't use \override in the input files. With the behaviour as I see it I
can only say "please add N to your current X-offset" (instead of "set
X-offset to M").

Any explanations or suggestions?

TIA
Urs

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Re: Double Bar with Grace Notes Problem

2017-04-04 Thread Phil Holmes 
If you read 
http://lilypond.org/doc/v2.18/Documentation/notation/special-rhythmic-concerns#grace-notes
 - specifically Known issues and warnings, you'll see that you need to have 
equal length grace notes or rests in all parts.  This can be done with spacer 
rests.  The second bar of clarinet 2 should be:

\grace s8 d''8 r8 \grace s8 d''8 r8 r4 |



--
Phil Holmes


  - Original Message - 
  From: Bill Kone 
  To: lilypond-user@gnu.org 
  Sent: Tuesday, April 04, 2017 6:36 AM
  Subject: Double Bar with Grace Notes Problem


  I have a lot of concert/marching band music some of which is old hand written 
manuscript. From time-to-time  I try to transcribe the hand-written manuscript 
to a much more readable  product.

  Generally I do each instrument then combine them into a score.

   

  The problem is, in this case as shown in the sample below and attached image, 
that a double bar before the grace notes, on the clarinet 1 and 2  seems to 
cause a separate bar line, which also increments the measure counter, but only 
on the score.

   

  Below is an extraction as a two staff script (the same as when each 
independent part is combined into a score). Each part needs to have the same 
bar markings so I can't just leave the double bar out on a couple of parts.

   

  In this case I just took the double bars out completely from all the parts 
but I am still wondering if it is my ignorance or what seems to me to be a bug. 

   

  In the attached script, by commenting out the double bar in the clarinet2 
staff the problem goes away on the conductor's score but of course now the 
clarinet2 part has a missing double bar.

   

  I tried creating a variable defined as:  dblbar= { \bar "||" } then on the 
conductor score defined it as: dlbar = {} for all but the top line of the 
conductor's score in this case the flute. I believe it might work but made 
management more difficult for something that I figured I was doing wrong.


  Any thoughts?

   

  See also attached image

   

  \version "2.18.2"

   

  \score{

\new GrandStaff <<

  

  \new Staff = "Clarinet1" 

  {

\set Staff.instrumentName = #"Clar1"

\time 3/4

g''8 r8 g8 r8 r4 |

\bar "||" 

\grace {g'16 ( b'16} d''8 )

r8\grace {g'16 ( b'16} d''8 ) r8 r4 |

  }

  

  

  \new Staff = "clarinet2" 

  {

\set Staff.instrumentName = \markup { Clar2 }

\time 3/4

g''8 r8 g8 r8 r4 |



% -- If I comment out this bar formats OK

\bar "||" 

% --



d''8 r8 d''8 r8 r4 |

  }

>>

\layout{}

  }



--


  ___
  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