Bug: gradual tempo mark disappears when crossing instrument change

When a gradual tempo (like a rit…) is extended across an instrument change, it will vanish from the score… I was lucky to have caught that before a rehearsal…

I attached a sample project: if you move or extend the ritardando one grid value to the right, it will disappear.

Important: this bug only happens if “layout options – players – transition point for instrument change” is set to “before first note in new instrument”. – I was wrong on that, see edit

Is there a way to have the tempo marking show, other than changing that layout option?
disappearing-tempo-with-instrument-change.dorico (1.4 MB)

EDIT: just noticed that won’t help much, if you switch the setting for the instrument change transition point to “after last note in old instrument”, then the transition point will be placed after the first bar in the picture, and you won’t be able to have a ritardando cross that point…

The bug doesn’t appear in version 5. I’m hoping for a fix as soon as possible; it’s quite concerning, especially for projects developed on the earlier version.

1 Like

As @mati indicated, this is a regression in Dorico 6, which will hopefully be fixed in a future update. In the meantime, if you change the settings in Layout Options > Staves and Systems > System-attached Items as shown below, …

… then gradual tempos can be extended into bars 2 and 11 without disappearing:

4 Likes

Thanks for this - we’ll take a look.

4 Likes

Thank you for your replies! @johnkprice I owe you one :folded_hands: – this option helps me get my tempo marks to reappear!

Just to give notice: I found two further issues when using this workaround:

  1. the ritardando doesn’t “dock” and vertically auto align when overlapping with the “a tempo” (while it does work in the first system where there is no instrument change
  2. collision with instrument change label is not avoided (which I didn’t notice at first because the standard distance engraving option for the instrument label was set so high already in my sample project)

(these of course I can fix manually in the meantime, just giving notice)

for future reference: this was fixed in version 6.0.2

Thank you so much! This was an annoying issue, and it got fixed in a short time!