[MU4 Issue] Sesquisharp and Sesquiflat accidentals fail to play back properly

[DaffodilAura]

Describe the bug Accidentals which require modification by over 100 cents don't work right

To Reproduce Steps to reproduce the behavior:

1. Create MuseScore file using Sesquisharp and Sesquiflat accidentals in MuseScore 3
2. Save score
3. Import Score to MuseScore 4
4. Try to play back your score
5. Listen as sesquisharp and sesquiflat accidentals fail to play back properly

Expected behavior Sesquisharps should behave like sharp symbols automatically in that they assume a raising of the note by a guaranteed 100 cents, and even respect key signatures, then, you should be able to add the remaining 50 or so cents by manual tuning. Sesquiflats should behave like flat symbols automatically in that they assume a lowering of the note by a guaranteed 100 cents, and also respect key signatures, then, you should be able to subtract the remaining 50 or so cents by manual tuning. Import from MuseScore 3 and earlier systems should see sequisharp and sesquiflat tuning readjusted to take advantage of the aforementioned new tuning mechanics for sesquisharp and sesquiflat accidentals.

Screenshots Will be supplied as needed later in the comments

Platform information

• OS: Windows 11

Additional context Even MuseScore 3 has long had problems in terms of the playback of sesquisharp and sesquiflat accidentals as they don't automatically add or subtract the 100 cents or respect key signatures.

[Jojo-Schmitz]

None of those 'exotic' accidentals do playback properly in MuseScore, only flat, sharp, double flat and double sharp (and natural). The infrastructure is in place for many of them, in that their (default) cent offset is know, see https://github.com/musescore/MuseScore/blob/3df592be2765246eed5aef58b0041e49f7e14578/src/engraving/libmscore/accidental.cpp#L54-L227 but no code is in place to use that.

So this is not a MU4 issue at all, but a general MuseScore issue, See also https://musescore.org/en/node/281507

[DaffodilAura]

Okay, @Jojo-Schmitz, I just read the comments in that link you posted, but the problem with using the workarounds mentioned is that the manual tuning no longer allows modifications by over 100 cents in MuseScore 4, and worse, figuring out which microtonal accidental to use in a given key signature is fraught with difficulty and glitched playback. I should know, since I've been using the available work arounds with MuseScore 3 for years. This is why I think now is the time to start utilizing some of the infrastructure that you've pointed out.

[Jojo-Schmitz]

I'd love to see that.

[DaffodilAura]

Upon closer examination yesterday, it turns out that this issue of microtonality not working in MuseScore 4 mainly affects MuseSounds, but MS Basic can indeed modify notes by up to 999 cents in either direction. That said, the issues with workarounds in MuseScore 3 are still very much real, and, from what I gather, continue to plague MuseScore 4.