Re: add articulation support to multi measure rests (issue 562710043 by lilypond@maltemeyn.de)

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: add articulation support to multi measure rests (issue 562710043 by lilypond@maltemeyn.de)

David Kastrup
Multimeasure rests can be split into multiple rests and across lines.
That's what makes then a Spanner rather than an Item and is the main
cause of this complication.  How are you dealing with such a split?  A
fermata only makes sense on the last such rest, most text markups make
sense only on the first such rest.


https://codereview.appspot.com/562710043/diff/572630043/input/regression/multi-measure-rest-text.ly
File input/regression/multi-measure-rest-text.ly (right):

https://codereview.appspot.com/562710043/diff/572630043/input/regression/multi-measure-rest-text.ly#newcode19
input/regression/multi-measure-rest-text.ly:19: R2._\fermata _"Ad lib"
I don't think the order of \fermata and "Ad lib" is to be determined by
LilyPond: this is a single item.

https://codereview.appspot.com/562710043/

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: add articulation support to multi measure rests (issue 562710043 by lilypond@maltemeyn.de)

Dan Eble
On Apr 27, 2019, at 04:54, [hidden email] wrote:
>
> Multimeasure rests can be split into multiple rests and across lines.
> That's what makes then a Spanner rather than an Item and is the main
> cause of this complication.  How are you dealing with such a split?  A
> fermata only makes sense on the last such rest, most text markups make
> sense only on the first such rest.

See Malte’s answer when I raised the same concern:
http://lists.gnu.org/archive/html/lilypond-devel/2019-04/msg00087.html <http://lists.gnu.org/archive/html/lilypond-devel/2019-04/msg00087.html>

It’s a bit long to quote, but his major premise is that \fermata on a compressed multimeasure rest is ambiguous to the point of being useless.

Dan

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: add articulation support to multi measure rests (issue 562710043 by lilypond@maltemeyn.de)

David Kastrup
Dan Eble <[hidden email]> writes:

> On Apr 27, 2019, at 04:54, [hidden email] wrote:
>>
>> Multimeasure rests can be split into multiple rests and across lines.
>> That's what makes then a Spanner rather than an Item and is the main
>> cause of this complication.  How are you dealing with such a split?  A
>> fermata only makes sense on the last such rest, most text markups make
>> sense only on the first such rest.
>
> See Malte’s answer when I raised the same concern:
> http://lists.gnu.org/archive/html/lilypond-devel/2019-04/msg00087.html
> <http://lists.gnu.org/archive/html/lilypond-devel/2019-04/msg00087.html>
>
> It’s a bit long to quote, but his major premise is that \fermata on a
> compressed multimeasure rest is ambiguous to the point of being
> useless.

But we are talking about a \fermata on an _uncompressed_ multimeasure
rest here.  If the compression leaves just a single rest, placing the
fermata does not pose a conundrum to typesetting (it may pose one to the
musician but that's entirely the composer's choice and fault).

--
David Kastrup

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: add articulation support to multi measure rests (issue 562710043 by lilypond@maltemeyn.de)

Dan Eble
On Apr 27, 2019, at 07:31, David Kastrup <[hidden email]> wrote:
>
> But we are talking about a \fermata on an _uncompressed_ multimeasure
> rest here.  If the compression leaves just a single rest, placing the
> fermata does not pose a conundrum to typesetting (it may pose one to the
> musician but that's entirely the composer's choice and fault).

I agree, though I won’t suggest that the issue should block acceptance of this patch, since \fermataMarkup had the same problem.  Treating it as a known issue would be nice.

Dan


_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel