Hi Kieren,
the issue is not fixed (yet), but I found a hint. The EE uses the
context-properties currentBarNumber and measurePosition to collect
current mods from the tree. Somehow these values are laid back inside
the EE code so they report the preceding moment when the Timing is moved
away from the Score context.
I have to build a MWE to expose the bug and to solve it.
Jan-Peter
Am 16.08.2017 um 15:55 schrieb Kieren MacMillan:
Hi David,
I'll try it in my "real-world" score and report back.
Here is a screenshot of a portion of my current engraving:
As you can see, the second staff is [correctly] displaying address@hidden, and
the third staff is [correctly] displaying address@hidden/4.
*HOWEVER*: the edition-engraver tweak required to color the notes in
the PianoStaff had to be set at address@hidden/8 [!!] in order to correctly
start at the moment which is obviously address@hidden/4. I feel certain this is
a flaw in the edition-engraver, and not with your
Current_moment_engraver code — I'm hoping your Current_moment_engraver
code [found two messages earlier in this thread] might help Jan-Peter
fix the edition-engraver (ASAP!) so that it correctly targets moments
in polymetric scores.
Many thanks,
Kieren.
________________________________
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info <http://www.kierenmacmillan.info>
‣ email: address@hidden <mailto:address@hidden>
_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user