musescore / musescore/MuseScore

Viola Section comes in too late on some quick notes

Open
#20,441 0 comments 0 reactions 1 assignee View on GitHub

@matthewreadbass is already working on this.

Since Dec 13, 2023.

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

Description

Issue type

Muse Sounds bug

Bug description

The violas in Muse Sounds are playing an incorrect rhythm when presented with 32nd notes, but only in the case of one particular score. The problem appears at measure 42 in the attached score. The problem persists after exiting and re-entering MS4.

Steps to reproduce

Create the following rhythm with the viola section:
image

Screenshots/Screen recordings

First, the violas coming in around a quarter of a beat late:

https://github.com/musescore/MuseScore/assets/73259774/65b3f980-8a5d-463c-aa37-314d85609aef

Here, the violas are replaced with the timpani to demonstrate the correct rhythm:

https://github.com/musescore/MuseScore/assets/73259774/98478963-3143-414c-aa88-44f954201228

And here, the violas actually perform the correct rhythm if it is a fresh score and not the one I attached:

https://github.com/musescore/MuseScore/assets/73259774/0882699a-3679-404f-ae28-70e224739cc2

MuseScore Version

MuseScore version (64-bit): 4.1.1-232071203, revision: github-musescore-musescore-e4d1ddf

Regression

I don't know

Operating system

Windows 11

Additional context

The project file

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.