Re: Staff Grouping

[Phil Holmes]

"Dave Higgins" <address@hidden> wrote in message 
news:address@hidden
> Phil Holmes <mail <at> philholmes.net> writes:
>
> > "Dave Higgins" <lilypond <at> dkds.us> wrote in message
> > news:loom.20140514T190802-260 <at> post.gmane.org...
> > >> I'm not top-posting
> > >
> > > \version "2.18.2"
> > >
> > > \score { <<
> > >        \new Staff { \relative c' { << { c1 } \new Staff { g' } >> 
> > > \break
> > > c,1 \break | << { c } \new Staff { g' } >> \break | c, } }
> > >        \new Staff { \relative c' { << { b1 } \new Staff { f' } >> 
> > > \break
> > > b,
> > > \break | << { b } \new Staff { f' } >> \break | b, } }
> > >>> }
> > > \layout {}
> > >
> > > I'm having trouble understanding why staff grouping isn't working.  If 
> > > I
> > > start with 2 parts that start with divisi staffs, that section is 
> > > correct.
> > > When I go to a new divisi staff later on, the staffs are intermingled.
> > > I'm
> > > not sure if this is the expected behavior, but I've not been able to
> > > overcome it (except through changing the parts).  Obviously, if one 
> > > part
> > > is
> > > compiled, the layout is correct.
> >
> > Did you see my reply of May 12th?
>
> Yes.

Then perhaps you could have replied?

> I'm not trying to hide staffs.  If you're saying the solution is to
> have however many multiple staffs that may only occur for a few measures
> entered into a part of multiple hundreds of single staff notes, that's not
> really a solution.

Well, an option _is_ to hide staves that you don't need.  It's quite simple. 
Try this:

\layout {
\context {
\Staff \RemoveEmptyStaves
\override VerticalAxisGroup.remove-first = ##t
}
}
<<
\new Staff { \repeat unfold 20 R1 c'1 \repeat unfold 19 R1 }
\new Staff { \repeat unfold 40 c'1 }
> >


> If you compiled the above example and noticed that what I typed in is
> basically this:
> \version "2.18.2"
> \score { << \new Staff { relative c' { <c g'>1 c <c g'> c } }
> \new Staff { relative c' { <b f'>1 b <b f'> b } } >> }
>
> but what comes out is this:
> \version "2.18.2"
> \score { << \new Staff { relative c' { <c g'> c <c b> c } }
> \new Staff { relative c' { <b g'> b <f' g> b, } } >> }
>
> The notes are correct, the layout is wrong.
>
> There's something wrong in the way that staffs are grouped if multiple
> staffs are called later in a part.
>
> If you take the breaks out of the example above, the second new staff is
> dangling below the staffs.  Which says that "\new Staff" isn't a singular
> (atomic) call.  Maybe it's a problem with layout?  Perhaps \new Staff 
> should
> have some function where you name it, e.g. "\new Staff = part1staff1" and
> "\new Staff = part1staff2" which would which would group them correctly.
>
> I don't report to the bug list without reason (read big annoyance).

I actually don't understand what you expect LilyPond to be doing here, but 
the issue of temporarily starting and stopping staves is covered quite well 
in the Notation Reference in the section on Ossia Staves.  Have you tried 
adapting code from there?

--
Phil Holmes
Bug Squad