|
From: | Urs Liska |
Subject: | Re: Behavior of non-flag side with strictBeatBeaming |
Date: | Thu, 14 Jan 2016 09:00:34 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 |
Am 13.01.2016 um 20:07 schrieb Pierre
Perol-Schneider:
The more I think of it, the more I find the current behaviour inconsistent. Actually LilyPond forces a subdivision when it performs strictBeatBeaming, not giving the user the choice. Of course the divided rendering is the easiest to read, but that's usually true for subdivideBeams = ##t. Take the attached example "undivided". Of course the second line is easier to read and therefore preferable, but still the first line is possible - and even the default behaviour. So I suggest the following:
The attached image beaming-options.png illustrates these three
options. Urs |
undivided.png
Description: PNG image
beaming-options.png
Description: PNG image
[Prev in Thread] | Current Thread | [Next in Thread] |