[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Conflicting RehearsalMarks
From: |
David Kastrup |
Subject: |
Re: Conflicting RehearsalMarks |
Date: |
Mon, 23 May 2022 14:59:08 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Thomas Morley <thomasmorley65@gmail.com> writes:
> Hi,
>
> consider the code below
>
> \layout {
> \context {
> \StaffGroup
> \consists "Mark_engraver"
> \consists "Staff_collecting_engraver"
> }
> \context {
> \Score
> \remove "Mark_engraver"
> \remove "Staff_collecting_engraver"
> }
> }
>
> <<
> \new StaffGroup << \new Staff { \mark "foo" R1 } \new Staff { R1 } >>
> \new StaffGroup << \new Staff { \mark "bar" R1 } \new Staff { R1 } >>
> \new StaffGroup << \new Staff { \mark "buzz" R1 } \new Staff { R1 } >>
>>>
>
> working fine with 2.22., i.e. no warnings and three different
> RehearsalMarks are printed.
> With 2.23.9 I get warnings about conficting events (imho, there are no
> conficts, the Mark_engraver is moved!) and only the first one, "foo"
> is printed at every StaffGroup.
>
> How to fix?
There is likely a relation to the Mark_tracking_translator, and the
respective convert-ly rule decides that this cannot be resolved
automatically and bombs out with
python/convertrules.py: stderr_write(_("If independent mark sequences
are desired, use multiple Mark_tracking_translators."))
which is a bit disappointing for functionality that is rather commonly
used. I see no documentation apart from the Changes entry that would
address this change in interface. I think fixing at least the
documentation situation would be critical before a stable release.
--
David Kastrup