Re: 2.22: unexpected bar numbering when using * lengths and skipBars
"Silas S. Brown" <[email protected]>
| Newsgroups | gmane.comp.gnu.lilypond.bugs |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Nov 21, 2022 at 12:54:45PM +0000, Mark Knoop wrote: > Hi Silas, > Remember that in LilyPond, durations carry over from the previous event > if not explicitly specified. This includes the duration of multimeasure > rests. You have already found the solution - this is the expected > behaviour. Thanks. In that case, can I request that any attempt to add a note while "*" is in the duration should cause an error, or at the very least a warning? I was playing in an orchestra, and I used Lilypond to redo my part to make it easier to read. I missed out a "2" after an "R2*4" by mistake. There was no visual indication that anything was wrong, apart from the bar numbers, which I didn't realise I had to check, until I found in rehearsal that the numbers being used by the conductor did not match with my part. Since I can't think of any situation where you really would want a minim to last 4 bars (but still look like one minim), I wonder if at the very least this should cause a warning similar to the "barcheck failed" warnings. Thanks. -- Silas S. Brown http://ssb22.user.srcf.net _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond