musescore / musescore/MuseScore

Tempo change while loading audio samples causes some instruments to retain old tempo

Open
#22,044 0 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Mar 24, 2024.

P3 playback regression MS3
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

If you open a score containing a lot of instruments and quickly change the tempo before all samples are fully loaded, some of the instruments will have the old tempo and some will have the new tempo.

Steps to reproduce
  1. Open a score containing many instruments.
  2. While the instruments are loading, change the tempo marking.
  3. Press play and hear the error: only some instruments have the new tempo
Screenshots/Screen recordings

No response

MuseScore Version

4.2.1

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

macOS 12.7.2

Additional context

The attached MuseScore file illustrates the issue quite well; just open it and quickly add a "1" to the tempo marking before the samples fully load, to make it 180 bpm. Hit play to hear the problem: all the notes should play in unison, but they don't.

Tempo Bug.mscz.zip

Note that the issue is probably more likely to occur with Muse Sounds, which takes longer to load than MS Basic (not sure about VST instruments). And it's entirely possible that this would hardly be an issue on super fast computers, where the samples load quicker. I am currently using a 2014 Mac mini.

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.