musescore / musescore/MuseScore

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

Open
#16,712 14 comments 0 reactions 4 assignees View on GitHub

@RomanPudashkin is already working on this.

Since Mar 9, 2023.

MuseSounds P2 playback
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

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

https://user-images.githubusercontent.com/126709343/223775569-33a9af91-d137-4e5a-8cd5-21ec1eb1d80e.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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.