MS Basic Glissandi can take extra metronomic time depending on how large the interval is. Other notes might not play to compensate.

Issue type

General playback bug

Bug description

When glissando across a measure, the first note in the next measure dosen't make any sound, but if you start straight from the next measure thess notes sounds properly.

Steps to reproduce

project_sample.zip

Screenshots/Screen recordings

I found that this issue occurs on a strict occasion.

Play starts from measure 2 to measure 3, the chord in the red mark won't make a sound.
But starting straight from measure 3 this chord sounded proper.

I tried to write another similar measure, but it sounds proper.

Then I tried to adjust these two measures, when I removed the wavy glissando mark between these two measures, the chord sounded well.

These three examples in screenshots were included in the project file I uploaded in the "Steps to reproduce" section.

MuseScore Version

MuseScore version (64-bit): 4.1.1-232071203, revision: github-musescore-musescore-e4d1ddf

Regression

I don't know

Operating system

Windows11

Additional context

No response