Alexander, Well, to Carl's comment, I am not actually putting a full-measure rest in a partial measure. The last full-measure rest (R2.) completely fills bar 151, which is in 3/4 time. While the error message doesn't tell us what exactly causes the bar-check error, it SHOULD be caused by the following 1/4-note partial measure that precedes m. 152 (in the new 4/4 time section), NOT the dotted 1/2-note in the previous time signature.
In other words, if I were to truncate the input file after the dotted 1/2-note in m. 151, but before the partial measure, and truncate the MultiMeasure template voice at the same spot, I would expect the part to print properly with no error. Which of course leads me to ask, "does Lilypond, once it sees the 1/4-note pickup to the new section, go back and consider the dotted 1/2 note that came before + this 1/4-note as 1 full measure in the new time signature? If so, then Carl's comment would explain the error. Whatever the case, I agree with you that we now have a good sense for the issue here and the error can be ignored. Thanks for the reply! Randy Alexander Kobel wrote: > > me - stanford wrote: >> Alexender, >> >> *Here's some more feedback for you *(whenever you get around to looking >> at this code again). I've attached all the relevant files: >> >> %============================================================= >> >> I'm not sure if you remember the barcheck issue I was getting? It >> looked like this: > >> * Bach_Singet_dem_Herrn_source_music.ly:85:23: warning: barcheck failed >> at: -1/4 * >> * ** \mark \default * >> * R2.*15 ** ** % N = 137 * > > Hi, Randy, > > it seems like this was kinda solved without me having a look at it at > all. In a recent message on lilypond-user (the "Partials and upbeats" > thread), Carl Sorensen says: >> But for the current status of bar-checks, putting a full-measure rest in >> a >> partial measure should always produce the barcheck warning, IMO. > > So it looks like the problem is not inherent to my code, though of > course the method used there is quite ugly and hack-ish, and it breaks > if you try to use anything but MultiMeasureRests in the BarNumberStaff > without manual tweaking of the global counter variables. > But in essence: One should not bother to care about the warnings as long > as it works. > > > Cheers, > Alexander > > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user > > -- View this message in context: http://old.nabble.com/Re%3A-your-MultiMeasureRest-utility-tp27867655p27885461.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
