[Top][All Lists]

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

Re: Strange results from simultaneous RehearsalMarks

From: Thomas Morley
Subject: Re: Strange results from simultaneous RehearsalMarks
Date: Sun, 28 Jul 2019 11:32:19 +0200

Am Sa., 27. Juli 2019 um 18:29 Uhr schrieb Patrick Karl <address@hidden>:

I'm running LIlyPond 2.19.81 on a Mac desktop running OSX 10.11.6.

I'm confused about the warnings generated by the following snippet:

\version "2.19.81" \score {     \new GrandStaff <<         \new Staff  {             c'1\bar "|." \mark\markup { \musicglyph #"scripts.ufermata" } }         \new Staff \with { \consists "Mark_engraver" }  {             d'1 \override Staff.RehearsalMark #'direction = #DOWN \mark                 \markup { \musicglyph #"scripts.dfermata" } }     >> }

Compiling this snippet throws the following Warnings: [...]

It doesn't look like the second rehearsal mark was junked at all. In fact, the output looks just like I hoped.

Per default, Mark_engraver is in Score-context. You didn't remove it from there, thus LilyPond sees two simultaneous RehearsalMarks in Score and complains. All as it should be.
NB Simply adding the engraver to a Staff does not change the situation in Score.

Your code is based on a LSR-snippet, you may try some of the others dealing with simultaneous RehearsalMarks.
Or probably suppress the warning.


PNG image

PNG image

reply via email to

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