lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by addres


From: Dan Eble
Subject: Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by address@hidden)
Date: Thu, 28 Dec 2017 11:55:46 -0500

On Dec 28, 2017, at 05:49, address@hidden wrote:
> 
> Thank you for that hint. Indeed there is an unwanted interaction. The
> following prints two maxima rests instead of one maxima + one longa +
> one breve + one semibreve. I’ll have to work on this.
> 
> {
>  \override MultiMeasureRest.expand-limit = 15
>  \override MultiMeasureRest.round-up-to-longer-rest = ##t
>  \time 3/1
>  R\breve.*15
> }
> 
> https://codereview.appspot.com/333340043/

I don’t consider myself qualified to answer your questions about use cases, but 
_if_ it is appropriate to ignore round-up-to-longer-rest for church rests, it 
looks easy to achieve that by moving the following term out of 
calc_closest_duration_log() into its caller calc_measure_duration_log().

        to_boolean (me->get_property ("round-up-to-longer-rest”)

That would leave calc_closest_duration_log() doing exactly what it is told in 
terms of rounding.

Regards,
— 
Dan




reply via email to

[Prev in Thread] Current Thread [Next in Thread]