Thank you, Mats. The snippet compiles now, so we can go ahead with the
switch to 2.12.
It's probably a good idea to do as you suggest, though, and move the NR
example to a LSR snippet that will be included in NR. I'll look into
that in the next few days. Right now I have a different project that's
rather pressing.
Valentin, the tarball is ready and will be coming in a private email.
Best,
Jon
Mats Bengtsson wrote:
The first of the two examples can be replaced by the following, but
there's already a similar example available in the NR 1.2.3 "Polymetric
notation", below "*/Staves with different time signatures, unequal bar
lengths"/*, so I don't really see any point in keeping the example
below. Well, at second thought I modified the LSR example to show how to
deal with a StaffGroup to get the bracket but not the spanning bar
lines, but then it's better to either include that aspect in the example
in the NR or to move the example from the NR into an LSR snippet that's
included as a snippet in the NR.
\version "2.11.62"
\header {
texidoc = "
This snippets demonstrates how to handle staff grouping and
synchronizing when typesetting polymetric ensemble music.
"
doctitle = "Polymetric section: synchronizing different groups of staves"
}
%LSR contributed by John Mandereau, Reinhold Kainhofer on an idea by
Werner Lemberg.
\score {
\new StaffGroup <<
\new Staff { c'1 c' c'4 }
\new Staff { \clef bass d4 e f g a1 a4 }
\new Staff \relative c' { \time 3/4 f8 e f g a4 g2.~ g4 f8 e f4 }
\new Staff \relative c'' { a2 d, e c c4 }
>>
\layout {
\context {
\Score
\remove Default_bar_line_engraver
\remove Timing_translator
}
\context {
\StaffGroup
\remove Span_bar_engraver
}
\context {
\Staff
% the order of engravers matters here: e.g. if Timing_translator
% comes after Default_bar_line_engraver, barlines are messed up.
\consists Timing_translator
\consists Default_bar_line_engraver
}
}
}
/Mats
Jonathan Kulp wrote:
Jonathan Kulp wrote:
Cool! I'm going to run them one more time to be sure, then I'll send
you the tarball privately, Valentin.
Jon
One snippet won't compile (attached). If someone wants to have a go
at it that'd be great. Otherwise I can get to it a bit later today.
Jon
------------------------------------------------------------------------
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Jonathan Kulp
http://www.jonathankulp.com
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
