The glissando abnormally affects the playback of the adjacent staff of the instrument [MS Basic only]

Issue type

General playback bug

Description with steps to reproduce

Make sure you have two staffs in one instrument. I will demonstrate how the bug works on violins.

1. -Write down a whole note on one of the staffs, two half notes on the other and a portamento glissando between them.
   -Click Play.

https://github.com/user-attachments/assets/c75a10e2-e3cd-44c5-a15a-7e4dfd3517a8

You will hear that the whole note is lowered in parallel with the glissando, although it is without a glissando. As soon as the glissando on the upper note carrier is completed, the whole note returns to its original pitch. It's very strange. The whole note should not be lowered in parallel, because there is no glissando in it.
2. Everything is the same, just change the glissando style to chromatic. Look at what comes out of it:

https://github.com/user-attachments/assets/cd194b5d-df55-493d-bdd6-77297789c196

As soon as the chromatic glissando reaches the second half note, the whole note stops sounding.
3. Last. Try to notate a portamento glissando on two staffs, only in different directions. Listen to how it goes:

https://github.com/user-attachments/assets/969e5063-e02a-4d35-a279-1319fb0eb42d

Supporting files, videos and screenshots

4.4.3-242971445, revision: github-musescore-musescore-eb6b367

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

4.5.0-243380315, revision: github-musescore-musescore-20ecf84

Regression

No

Operating system

Windows 11

Additional context

No response

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