Re: 2.22: unexpected bar numbering when using * lengths and skipBars

Le 23/11/2022 à 18:00, Mats Bengtsson a écrit : On 2022-11-22 19:30, Silas S. Brown wrote: Hm.  Josquin des Prez is sort of borderline here... Hi, yes that has notes going across barlines.  But wouldn't that cause "barcheck failed" warnings anyway, even

Re: 2.22: unexpected bar numbering when using * lengths and skipBars

On 2022-11-22 19:30, Silas S. Brown wrote: Hm. Josquin des Prez is sort of borderline here... Hi, yes that has notes going across barlines. But wouldn't that cause "barcheck failed" warnings anyway, even apart from the notes using a multiplier? (e.g. the

Re: 2.22: unexpected bar numbering when using * lengths and skipBars

"Silas S. Brown" writes: >> Hm. Josquin des Prez is sort of borderline here... >> > > Hi, yes that has notes going across barlines. But wouldn't that > cause "barcheck failed" warnings anyway, even apart from the > notes using a multiplier? Why would you

Re: 2.22: unexpected bar numbering when using * lengths and skipBars

> Hm. Josquin des Prez is sort of borderline here... > Hi, yes that has notes going across barlines. But wouldn't that cause "barcheck failed" warnings anyway, even apart from the notes using a multiplier? (e.g. the dotted minim already goes across a

Re: 2.22: unexpected bar numbering when using * lengths and skipBars

"Silas S. Brown" writes: >> > 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? >> >> That would turn into a real nuisance for "simile" triplets entered as >> durations with *2/3

Re: 2.22: unexpected bar numbering when using * lengths and skipBars

> > 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? > > That would turn into a real nuisance for "simile" triplets entered as > durations with *2/3 multiplier. OK, then we'd have to

Re: 2.22: unexpected bar numbering when using * lengths and skipBars

On 11/21/22 05:36, Silas S. Brown wrote: % In 2/4 time, I want to write 4 bars rest % followed by 2 minims (half-notes). % The bar numbering comes out differently: \version "2.22.2" \relative c' { \set Score.skipBars = ##t \time 2/4 R2*4 c ^"This is bar 5" \break d ^"I think this should be bar

Re: 2.22: unexpected bar numbering when using * lengths and skipBars

"Silas S. Brown" writes: > On Mon, Nov 21, 2022 at 12:54:45PM +, 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

Re: 2.22: unexpected bar numbering when using * lengths and skipBars

On Mon, Nov 21, 2022 at 12:54:45PM +, 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 >

Re: 2.22: unexpected bar numbering when using * lengths and skipBars

Hi Silas, At 12:36 on 21 Nov 2022, Silas S. Brown wrote: > % In 2/4 time, I want to write 4 bars rest > % followed by 2 minims (half-notes). > % The bar numbering comes out differently: > \version "2.22.2" > \relative c' { > \set Score.skipBars = ##t > \time 2/4 R2*4 c ^"This is bar 5" \break >