On Jan 15, 2021, at 12:17, Werner LEMBERG wrote:
>
>> The "Unmetered music" section in the manual already discusses issues
>> with bar numbers, accidentals, and autobeaming. It might be helpful
>> to mention the workaround of using \partial 1024 s1024 to force a
>> new measure at the end of a ca
On Jan 15, 2021, at 18:58, Thomas Morley wrote:
>
> (3) if the cadenza has inner bar-lines, we should provide a simple
> method to increase BarNumbers. Not sure, if we could implement this as
> an automtism…
I had a similar thought, but for a method to force a measure break, with other
things (
Am Fr., 15. Jan. 2021 um 02:36 Uhr schrieb Dan Eble :
>
> On Jan 14, 2021, at 19:13, Dan Eble wrote:
> >
> > On Jan 14, 2021, at 18:33, Dan Eble wrote:
> >>
> >> Alas, all is not well with earlier versions. Consider the confusing bar
> >> numbers in the following elaboration of your example. H
>>> Add issue #3640 to this discussion. Accidentals, bar numbers, and
>>> (now) multi-measure rests are all impacted by the fact that \bar
>>> "|" does not create a new measure.
>>
>> Maybe the whole thing is primarily a documentation issue that could
>> be fixed with prominent warnings at appro
Dan Eble writes:
> On Jan 15, 2021, at 06:53, David Kastrup wrote:
>>
>> Werner LEMBERG writes:
>>
Add issue #3640 to this discussion. Accidentals, bar numbers, and
(now) multi-measure rests are all impacted by the fact that \bar "|"
does not create a new measure.
>>>
>>> May
On Jan 15, 2021, at 06:53, David Kastrup wrote:
>
> Werner LEMBERG writes:
>
>>> Add issue #3640 to this discussion. Accidentals, bar numbers, and
>>> (now) multi-measure rests are all impacted by the fact that \bar "|"
>>> does not create a new measure.
>>
>> Maybe the whole thing is primari
> On Jan 15, 2021, at 04:53, Werner LEMBERG wrote:
>
>
>> Add issue #3640 to this discussion. Accidentals, bar numbers, and
>> (now) multi-measure rests are all impacted by the fact that \bar "|"
>> does not create a new measure.
>
> Maybe the whole thing is primarily a documentation issue
Werner LEMBERG writes:
>> Add issue #3640 to this discussion. Accidentals, bar numbers, and
>> (now) multi-measure rests are all impacted by the fact that \bar "|"
>> does not create a new measure.
>
> Maybe the whole thing is primarily a documentation issue that could be
> fixed with prominent
> Add issue #3640 to this discussion. Accidentals, bar numbers, and
> (now) multi-measure rests are all impacted by the fact that \bar "|"
> does not create a new measure.
Maybe the whole thing is primarily a documentation issue that could be
fixed with prominent warnings at appropriate places?
On Jan 14, 2021, at 19:13, Dan Eble wrote:
>
> On Jan 14, 2021, at 18:33, Dan Eble wrote:
>>
>> Alas, all is not well with earlier versions. Consider the confusing bar
>> numbers in the following elaboration of your example. How would you resolve
>> it?
>
> My thoughts:
>
> Measure 1 is c
On Jan 14, 2021, at 18:33, Dan Eble wrote:
>
> Alas, all is not well with earlier versions. Consider the confusing bar
> numbers in the following elaboration of your example. How would you resolve
> it?
My thoughts:
Measure 1 is complete, so the first "2" is not incorrect, though it might n
On Jan 14, 2021, at 11:38, Thomas Morley wrote:
>
> Hi,
>
> this code
> {
> \cadenzaOn
> b2
> \bar "|"
> \cadenzaOff
> R1
> }
> returns bad output with current master.
> 2.22.0 is ok.
Alas, all is not well with earlier versions. Consider the confusing bar
numbers in the following elabora
On Jan 14, 2021, at 11:38, Thomas Morley wrote:
>
> Hi,
>
> this code
> {
> \cadenzaOn
> b2
> \bar "|"
> \cadenzaOff
> R1
> }
> returns bad output with current master.
> 2.22.0 is ok.
Harm,
Thanks for the report. I'll try to investigate within the next day.
Regards,
—
Dan
Hi,
this code
{
\cadenzaOn
b2
\bar "|"
\cadenzaOff
R1
}
returns bad output with current master.
2.22.0 is ok.
Images attached.
First bad commit:
commit b65af84b861a9036c19b02f5de5be250d5fe0fa1
Author: Dan Eble
Date: Sat Dec 12 11:15:07 2020 -0500
Timing_translator: set measureSt
14 matches
Mail list logo
