Hello Valentin, > Le 19 mai 2020 à 10:02, Valentin Villenave <[email protected]> a écrit : > > On 5/19/20, Jacques Menu <[email protected]> wrote: >> In the attached example, the \voiceOne and \voiceTwo commands used for the >> first score lead to the eigth rests in measure 2 to appear too high. > > Well, it’s merely printed the way the source code’s requesting it. > \voiceOne rests are consistently placed at the top of the staff. > >> Is there a way to use some equivalent of \voiceOne and \voiceTwo >> measure-wise in such a case, using it only in measures that have more than >> one voice playing? > > I *think* your best bet would be to take a look at the > #Merge_rests_engravers (in scm/scheme-engravers.scm), which should be > able to handle that sort of case (I just checked; it currently > doesn’t). You could then \consist it into all your Staff contexts by > default.
I’ll have a look at the Merge_rests_engravers, thanks. > By the way, why is xml2ly \tempo markup so convoluted when you could have > simply > > \tempo "" 4 = 110 > > (plus, it would remove the need for \markup \note, whose syntax has > recently changed.) This dates back to four years ago, when I started working on xml2ly... Thanks for pointing this enhancement out! JM
