(Similar to 25831) Staccato notes incorrectly sustained possibly indefinitely in playback on instruments with multiple staves with certain tempos

[onnogli]

Issue type

General playback bug

Description with steps to reproduce

NOTE: I saw 25831 but they're discussing a slightly different situation, as they describe it needing dynamics, not needing an instrument with multiple staves, and such.

1. Make a new score with a piano.
2. On one staff, put repeated notes of uniform length (I chose to go with all quarters) with the staccato marking for a few bars.
3. On the other staff, put repeated eighth-notes (or something quicker than the other line).
4. Add a tempo marking at the start with a glitched tempo (I tried a few, q = 93, 111, 112 seem to be bugged at least)
5. (Optional) Change the sound to something that's easier to hear the difference between sustain and staccato such as a violin or voice.
6. Hit play (should hear some of the quarter notes be long instead of short)

Supporting files, videos and screenshots

Staccato Sustain.zip

What is the latest version of MuseScore Studio where this issue is present?

4.5.0

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Windows 10

Additional context

• Not an issue on Muse Sounds
• Doesn't matter which stave of the instrument it's on
• Dynamics don't change anything
• As long as the quarter note that would be sustained has eighth notes at the same time, it would sustain (doesn't matter what the surroundings are)
• Seems to happen when the quicker line has notes that are powers of 2 times as short
  • 4/8 (quarter over eighth) is bugged
  • 4/16 is bugged
  • 4/(8th note triplets) is bugged
  • 2/(8th note triplets) is bugged
• Different tempos repeat the notes at different points
• Choosing different note lengths may change position of the sustained staccatos

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible