Ties across key changes with accidentals are incorrect

• Jun 15, 2021 - 05:15
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
needs info
Regression
No
Workaround
Yes
Project

Steps to reproduce:

  1. Create piece with key change from G to Ab.
  2. Input the note C tied across the key change.
  3. Use the arrow keys to move this down a semitone.

Expected result:
The note displays as Cb (correct for final key) across both parts of the tie.

Actual result:
The note displays as B before the key change and as C after it

Basically, the two parts of the tie aren't properly linked, so they both display correctly for the key they belong to, regardless of whether that makes them appear differently to their counterpart.

Workaround: enter the accidental manually from the palettes.


Comments

Workaround No Yes

FWIW, it's quite deliberate that we allow enharmonic ties, they are often a desirable thing in cases like this. So I'd actually be fine with the default behavior of up/down across key changes to treat the notes separately, then if you want a homogenous spelling, you simply add it normally. ALl of the combinations - B to Cb, B to B, Cb to Cb - should be possible to create. But of course, we do need to get the accidentals right!

In reply to by Marc Sabatella

That's really interesting, I didn't know that enharmonic ties were a thing that existed. Imo it makes it quite confusing to read, and is something I'd probably want to avoid in my notation, but if it isn't musically incorrect then I guess this is all good. My only question is whether it would make more sense to have enharmonic ties need to be added manually, and try to keep the notes of ties on the same note: I can imagine this behaviour being quite confusing for users who weren't intending to create an enharmonic tie.

Status active needs info

Enharmonic ties are used if the harmony changes while the note is still sound. Like if you have a Fm chord followed by an E7 chord, and so you might tie the Ab in the Fm to the G# in the E. That case of course you'd expect to need to create manually, and you can, by entering the two notes first then adding the tie.

But the most common situation for these enharmonic ties is probably exactly what you are describing - a key change, with the note being spelled one way in one key but differently in the other key. So from a sharp key to a flat key, it would be normal to show the change in spelling across the key signature. Thus I think it actually should be the default in this case - it really is the most correct way to notate this. Assuming, of course, we don't leave out any necessary accidentals!

However, for me, this does work correctly. Your original description says you are seeing only a C for the second note, and that would be wrong. But when I try it, I see Cb, exactly as I expect. If you are seeing a C, that would be a bug indeed. Can you attach your score so we can investigate?