Re: Getting beam subdivision working

[David Kastrup]

David Kastrup <dak@gnu.org> writes:

> Dan Eble <dan@lyric.works> writes:
>
>> On Jun 16, 2023, at 19:13, Jason Yip <sripedia_getpgrp@slmail.me> 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 means minSubdivideInterval and
> maxSubdivideInterval must be an integral power of 2 (including
> negative).
>
>>> between those two values, the beam can be subdivided by that
>>> interval. minSubdivideInterval can be 0 for no minimum limit,
>>> maxSubdivideInterval can be infinity for no maximum limit.
>>
>> Setting the representation aside, is the following another way of
>> describing what you have in mind?
>>
>> * These properties are independently optional.
>> * The allowed values are integer powers of two (including negative powers).
>
> 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 only use the duration-log info while I consider it conceivable
that in the context of tuplets, ultimately also the factor may get used.

-- 
David Kastrup