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

[tick97115115]

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

[zacjansheski]

It seems to me that the root of the issue is that glissandi can take extra metronomic time depending on how large the interval is

https://github.com/musescore/MuseScore/assets/69917893/47a1c516-f189-4397-a17d-796325b13e20

[zacjansheski]

Other notes are dropped from playback to compensate

https://github.com/musescore/MuseScore/assets/69917893/1c28fe87-823f-4460-942f-b10ff49fc967

[zacjansheski]

Issue does not persist when using Muse Sounds

[bkunda]

Another important one to address!

At least it seems Muse Sounds handles this fairly well (I even half wonder whether some notes are cleverly dropped to allow the next beat to sound on time, or whether the gliss is simply played super quickly). At any rate, the first fix for this would probably be to align soundfont/VST with how Muse Sounds sounds.