Re: Tempo marking doesn't avoid cross-staff slur
>> This issue belongs into the group of the many cross-staff problems. >> AFAICS, we don't have this particular case covered, so please file >> an issue in the LilyPond tracker. > > For reference, it's : https://gitlab.com/lilypond/lilypond/-/issues/6688 Thanks! Werner
Re: Tempo marking doesn't avoid cross-staff slur
On Thu, Jan 11, 2024 at 4:40 AM Werner LEMBERG wrote: > > > I found a weird behavior -- I don't know if it's worthy of an issue > > or not, but here it is: > > > > The tempo marking will not avoid a slur that goes from staff to > > staff. Here is a snippet that shows the problem, and I've attached > > an image of it: [...] > > This issue belongs into the group of the many cross-staff problems. > AFAICS, we don't have this particular case covered, so please file an > issue in the LilyPond tracker. > For reference, it's : https://gitlab.com/lilypond/lilypond/-/issues/6688 -- Knute Snortum
Re: Tempo marking doesn't avoid cross-staff slur
> I found a weird behavior -- I don't know if it's worthy of an issue > or not, but here it is: > > The tempo marking will not avoid a slur that goes from staff to > staff. Here is a snippet that shows the problem, and I've attached > an image of it: [...] This issue belongs into the group of the many cross-staff problems. AFAICS, we don't have this particular case covered, so please file an issue in the LilyPond tracker. Werner
Tempo marking doesn't avoid cross-staff slur
I found a weird behavior -- I don't know if it's worthy of an issue or not, but here it is: The tempo marking will not avoid a slur that goes from staff to staff. Here is a snippet that shows the problem, and I've attached an image of it: \version "2.25.12" one = \relative { \tempo "Allegro maestoso" c'''2( e | \change Staff = "lower" c,1) | } two = \relative { s1 | s1 | } << \new Staff = "upper" \one \new Staff = "lower" \two >> -- Knute Snortum