musescore / musescore/MuseScore

Tremolo playback is incorrect in MuseSounds strings

Open
#31,273 2 comments 0 reactions 2 assignees View on GitHub

@zacjansheski is already working on this.

Since Dec 2, 2025.

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

Description

Issue type

General playback bug

Description with steps to reproduce
  1. Open the attached file (incorrect sting tremolo.mscz)
  2. Select one of the staves (for example, Violins)
  3. The single note (B only) through-stem tremolos play correctly regardless of tempo.
  4. When there is a chord (in this case G and B) the through-stem tremolo starts alternative between pitches.
  5. As the tempo slows down the alternative effect becomes very noticeable.
  6. The Violas, Violoncellos, and Contrabass have the same behavior.
Image

Related question:
Does MS support selection of measured vs. unmeasured tremolos? If yes, what is default? If above playback is measured, it still should not alternate between pitches.

Tested on latest MuseScore 4.6.3 and recent nightly build also shows problem (4.6.4.253300408)
Using MuseSounds Strings (section), MuseSampler version is 0.103.2.861

I didn't see this specific issue logged in the open issues.

Supporting files, videos and screenshots

Incorect string tremolo.zip

In which versions of MuseScore Studio is this issue present?

OS: Windows 11 Version 25H2 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.6.4-253300408, revision: github-musescore-musescore-7e32f16

Regression

I was unable to check

Operating system

Edition Windows 11 Home Version 25H2 Installed on ‎10/‎26/‎2025 OS build 26200.7171 Experience Windows Feature Experience Pack 1000.26100.265.0

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

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.