On Jun 17, 2023, at 09:27, David Kastrup wrote:
>
>>
>> That sounds like it would make more sense to specify those values in the
>> form of a "duration log", like the first argument to a ly:make-duration
>> call.
>
> Or just use a duration in the first place. First iterations would
> likely
David Kastrup writes:
> Dan Eble writes:
>
>> On Jun 16, 2023, at 19:13, Jason Yip wrote:
>>>
>>> minSubdivideInterval and maxSubdivideInterval. They are both
>>> Rationals. Their numerator and denominator must be a power of 2. For
>>> each power of 2 (including negative powers of 2 of
Dan Eble writes:
> On Jun 16, 2023, at 19:13, Jason Yip wrote:
>>
>> minSubdivideInterval and maxSubdivideInterval. They are both
>> Rationals. Their numerator and denominator must be a power of 2. For
>> each power of 2 (including negative powers of 2 of course)
That's redundant. It just
On Jun 16, 2023, at 19:13, Jason Yip wrote:
>
> minSubdivideInterval and maxSubdivideInterval. They are both Rationals. Their
> numerator and denominator must be a power of 2. For each power of 2
> (including negative powers of 2 of course) between those two values, the beam
> can be
On Fri, 2023-06-16 at 19:46 +0200, Jean Abou Samra wrote:
> Le vendredi 16 juin 2023 à 18:11 +0200, Jonas Hahnfeld a écrit :
> > I think I'd still lean towards doing the release as planned because (a)
> > the issue is already there with the current 2.25.5 and (b) it's also
> > not clear that a fix