duh, I am A Idiot, sorry. That needed some extra code to work. Here's a
more comprehensive version:

\version "2.19.28"
\time 2/4
VITympanoMusic = \new Voice \relative c {
  \clef bass
  \partial 8
  r8 |
  R2*54^\markup { \center-align TACET }
  R2.*29^\markup { \center-align TACET }
}

VIsystembreaks = \new Voice {
   \partial 8 s8 | s2*32 | \break
   s4 s8
   \tempo \markup {\sans \medium \fontsize #4 "Adagio" } s8 |
   s2*21 \bar "||" \break
   \time 3/4
   s2.*29 \once \override Score.RehearsalMark.break-visibility =
#begin-of-line-invisible
   \mark \markup { \musicglyph #"scripts.ufermata" } \bar "||" \pageBreak
%% End Credo, Bar 83

   }

and then inside a \score block:
\VITympanoMusic \VIsystembreaks

I resolved the issue with the barcheck: there was a mismatch between the
number of rests given by systembreaks and that in TympanoMusic, but I got
confused because it said the barcheck failed *before* the measure with the
"R2*54" code.

Anyway, the matter is resolved for the barcheck, but I still have a
problem: how do I show an entire set of movements as tacet in the part, but
still have the tympani (with whole-measure rests) show up on the first line
of each movement? I can't use the "R2*X" formula because there's a \time
change in the middle. Is there a code to give that sets an instrument as
tacet for an entire, say, \book block?

Sorry about the sub-working example.

A

On Thu, Oct 8, 2015 at 6:05 PM, Jacques Menu <[email protected]> wrote:

> \markup{\huge\bold TACET}
>
> solves you second question.
>
>
> > Le 8 oct. 2015 à 18:04, Jacques Menu <[email protected]> a écrit :
> >
> > Hello A,
> >
> > \version "2.19.28"
> >
> > VITympanoMusic = \new Voice \relative c {
> >  \clef bass
> >  \partial 8
> >  r8 |
> >  R2*54^\markup { \center-align TACET }
> >  R2.*29^\markup { \center-align TACET }
> > }
> >
> > {
> > \VITympanoMusic
> > }
> >
> > This has 29 times three quater notes, so if you use the default 4/4,
> then you get:
> >
> >       warning: barcheck failed at: 3/4
> >
> > But has DK says, we don’t know how you use this...
> >
> > JM
> >
> >
> >> Le 8 oct. 2015 à 16:12, David Kastrup <[email protected]> a écrit :
> >>
> >> "N. Andrew Walsh" <[email protected]> writes:
> >>
> >>> Hi List,
> >>>
> >>> I'm working on a collection of masses, which I've broken up into a
> tree of
> >>> files: each mass is in its own directory, with separate files for each
> >>> movement and a master file listing all the \includes. There are also
> now
> >>> separate files for each movement's \score block, so I can have
> different
> >>> layout options per movement (this also seems necessary if I want each
> >>> \music block to be contained in a differently-named variable to call up
> >>> later when making the parts).
> >>>
> >>> Here's my issue: in the last mass, the tympani part is tacet. I want
> the
> >>> Tympani to show up in the score in the first system only; but in the
> part,
> >>> I would like to have the \header block for that mass over a \markup
> >>> declaring TACET in big block letters (potentially over a compressed
> >>> rest-bar). I can do this for simple movements, but now I have one with
> a)
> >>> an 8th-note pickup, and b) a meter change in the middle. If I have the
> >>> following in the Tympani variable:
> >>>
> >>> VITympanoMusic = \new Voice \relative c {
> >>> \clef bass
> >>> \partial 8 r8 | R2*54^\markup { \center-align TACET }
> >>> R2.*29^\markup { \center-align TACET }
> >>> }
> >>>
> >>> Lily throws a barcheck failure (but looks fine in the score). Is there
> a
> >>> better way to do this? am I doing something wrong here, or is this a
> bug
> >>> with Lily herself?
> >>
> >> I don't see any meter change.  I don't see a minimal example one could
> >> compile.  I don't even see a version number.
> >>
> >> How do you suppose anybody is going to analyze your problem without
> >> knowledge about the actual corresponding LilyPond file and the actual
> >> corresponding LilyPond binary?
> >>
> >> --
> >> David Kastrup
> >>
> >> _______________________________________________
> >> lilypond-user mailing list
> >> [email protected]
> >> https://lists.gnu.org/mailman/listinfo/lilypond-user
> >
>
>
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to