lilypond-user
[Top][All Lists]
Advanced

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

Re: use of 1/2 staff divisio maior in gregorian chant.


From: Keith N. McKenna
Subject: Re: use of 1/2 staff divisio maior in gregorian chant.
Date: Wed, 05 Dec 2012 13:08:08 -0500
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0

David Kastrup wrote:
"Keith N. McKenna" <address@hidden> writes:

Keith N. McKenna wrote:
Greetings All;

In many some of the Gregorian Chant's I have access to they show the
divisio Maior as starting slightly above the third line of the staff and
continuing to just below the second line of the staff instead of a full
"bar line" like the Divisio Maxima only less bold. Is it possible to get
this configuration using lilypond 2.16?

Regards
Keith

After beating my head against the walls on this for a few  few days
with some very helpful suggestion off list from Jeffrey Trevino, thank
you very much Jeff, I stumbled on a very simple way to do it. While
searching through the documentation I discovered a link to the version
2.17.1 docs that Showed the divisio maior to be the half staff mark
that I prefer. Installed version 2.17.1 and ran a quick test and in
works like a charm.

It won't persist as it has been "fixed" in 2.17.7, and since the code is
"clever", all bets are off just what will be entailed to reliably change
it to the way you prefer.

Cf. <URL:https://codereview.appspot.com/6778050#msg11>.

This is really to bad. Changing it back to the former makes it very difficult to differentiate it from the divisioMaxima. The intended audience I have is one that is unfamiliar with chant to begin with so even such an seemingly insignificant thing can make its introduction much more difficult.

There is a difference between how a line is performed when it includes a divisioMaior or a divisioMaxima, The 2 signs should be clearly different to convey that to the performer.

Given that the fix is in for 2.17.7 and up, is there any over rides that could be applied to make it closer to what it is in 2.17.1.

Regards
Keith




reply via email to

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