|
From: | Peter Bjuhr |
Subject: | Re: Implementation of \tuplet allow both incorrect and correct musical expressions |
Date: | Thu, 26 Mar 2015 23:15:07 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 |
On 2015-03-26 21:47, Simon Albrecht
wrote:
Thanks for sharing the full snippet! You have learned LilyPond quickly! And it's now easier to see what you are aiming for. The first bar is an upbeat (partial) so the timing isn't exact anyway. But the last bar with the septuplet is too crowded in my reading. I'd definitively prefer 32ths here instead of 16ths. But when you write that the 16ths are more elegant it suggests to me that you're aiming for a notation with more rhythmical freedom like grace notes or a cadenza. (You also use excessive brackets to enclose these tuplets that to me invoke the feeling of something (rhythmically) exceptional.) Interesting that you perceive it that way. Certainly, it looks less ‘impressive’. :-) Personally, I’d probably prefer following the Nearness Rule here. But, you see, for that reason it’s good that Lily gives us the freedom to choose ourselves. I totally agree! Lily should be a flexible tool and give the full freedom that it is up to the composer/engraver to master. Best Peter |
[Prev in Thread] | Current Thread | [Next in Thread] |