When pausing and pressing play, unwanted playback of previous chord symbols occurs (Muse Sounds only)

[zr-jl]

Issue type

General playback bug

Bug description

Hello,
When you start the playback on a beat of a bar where there is no chord present (I'm talking about chords introduced with cmd+K)
then MS4.0.2 systematically plays the last chord it finds written on the previous bars of the score.

This problem is stable and reproducible and this even if this chord is far away from the beginning of the score...

OS: macOS 12.6, Arch.: x86_64, MuseScore version (64-bit): 4.0.2-230601209, revision: github-musescore-musescore-48ac167

If.then.MS4.0.2.Play.always.the.previous.chord.mp4

Steps to reproduce

1. create a little new score
2. enter with cmd+K some chords (with empty bars in the middle)
3. play starting on a beat of an empty bar

Screenshots/Screen recordings

No response

MuseScore Version

MuseScore version (64-bit): 4.0.2-230601209, revision: github-musescore-musescore-48ac167

Regression

Unfortunately I can't answer this question. I have been using MuseScore for less than six months on my iMac. It is only recently (only with MS4.0.2) that I started to add chords on some scores of the choir I sing with. Most of the scores were a capella until then.

Operating system

OS: macOS 12.6, Arch.: x86_64,

Additional context

For information, I tested the thing by curiosity on another computer but this time a PC and with MS4.0.0 or 4.0.1 under Windows 10 the problem does not exist.

[zr-jl]

If ...then MS4.0.2 Play always the previous chord.mscz.zip

[Tantacrul]

Did you experience this in 4.0.1 or 4.0.0?

(this is what we mean by a regression)

[zr-jl]

Unfortunately I can't answer this question. I have been using MuseScore for less than six months on my iMac. It is only recently (only with MS4.0.2) that I started to add chords on some scores of the choir I sing with. Most of the scores were a capella until then.
For information, I tested the thing by curiosity on another computer but this time a PC and with MS4.0.0 or 4.0.1 under Windows 10 the problem does not exist.

[Tantacrul]

OK then. One of us will figure it out. Thanks!

[DmitryArefiev]

Did you experience this in 4.0.1 or 4.0.0?

(this is what we mean by a regression)

Investigated. This happens in 4.0.1/4.0.0 as well and only with MuseSounds

bandicam.2023-03-09.14-51-23-629.mp4

[Tantacrul]

Interesting. Thanks @DmitryArefiev! Perhaps it's a MuseSounds thing... but I wonder if it's not much more likely a MS4 thing. I've added the relevant people who can answer this.

[zr-jl]

Hello,
For your information, after testing I notice that
the problem persists identical
after the following updates performed this week:

OS: macOS 12.7, Arch: x86_64,
MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433
and
MuseHub V1.0.2

The temporary workaround by activating the "MuseScore Basic Playback setup profile" is still possible, but it's a disadvantage

. What's more, currently every time the other profile is activated (MuseScore Basic <> MuseSounds)
an unexpected session crash...

greeting from Switzerland!
Jean-Louis

[zr-jl]

For your information, after a quick test, the problem is still present with MuseScore 4.3.1

OS: macOS 12.7, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.1-241490902, revision: github-musescore-musescore-026c26b