Am 27.08.2015 um 15:50 schrieb Joel Ebel:
On Thu, Aug 27, 2015 at 2:53 AM, David Kastrup <d...@gnu.org> wrote:
Oh wow. This one is seriously annoying. If you take out all
\stopStaff, it is apparent that the TabStaff is alive through the whole
piece. This is also the case when replacing \new Line with \new
StaffGroup. This is something like the "the first new context in a
group is kept alive" rule. If you replace
\new TabStaff ...
with
<< \new DevNull {} \new TabStaff ... >>
the problem goes away even without \stopStaff. But that's seriously
messed up.
--
David Kastrup
That's abstract, but the result is much better. The one remaining
issue is that if the switch to RhythmicStaff occurs on a line break,
TAB is still printed on the first subsequent line. I can live with it,
but is it possible to prevent that?
Technically, the TAB is a clef.
\omit TabStaff.Clef before the first note in the RhythmicStaff does the
trick.
Yours, Simon
Simple example below. TAB is on
line 2, but not line 3.
\version "2.19.25"
\new Line {
<<
\new Devnull {}
\new TabStaff { \relative c { c1 } }
>>
\break
\new RhythmicStaff { 1 \break 1 }
}
\layout {
\context {
\name "Line"
\type "Engraver_group"
\consists "Axis_group_engraver"
\accepts TabStaff
\accepts RhythmicStaff
}
\context {
\Score
\accepts "Line"
}
}
_______________________________________________
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
