musescore / musescore/MuseScore

Incorrect playback with through-stem tremolo chords | Musestrings

Open
#23,217 13 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

playback
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 playback behavior of through-stem tremolos with chords is incorrect with Musesound strings. Ideally, the desired result for chords with a through-stem tremolo is to play both notes with tremolo samples. Such is not the case right now with Musesound strings. The current result sounds like sustain samples playing tremolo-between-notes.
Screenshot 2024-06-13 000725

Steps to reproduce
  1. Open a new score with any of the string section (Violin (solo/section), Viola (solo/section), etc....)
  2. Ensure the sound assignment is Musesounds.
  3. Input chords.
  4. Place through-stem tremolo markings on the chords.
  5. Press play.
  6. Observe the result. It should be the chord played with tremolo samples. However, such is not the case with the current Musesounds.
Screenshots/Screen recordings

Here is the OBS studio recording documenting the playback behavior.

https://github.com/musescore/MuseScore/assets/171134512/8d7bd6d7-5fdc-44b4-802a-c98e2739d1c3

Here is the score to complete the documentation requirements. Though this issue is not on a score-by-score basis, I thought it best to include it in this report.

https://drive.google.com/file/d/1KhC1Tf60_xld9BfjA_KTt5btPLX2N6TJ/view?usp=sharing

MuseScore Version

Musescore Studio 4.3.1

Regression

No.

Operating system

Windows 11

Additional context

Works normally in Musescore Basic (ie the notes machine-gun together, not in an alternating fashion as one would expect with between-note tremolo). Behavior is only observed with all of Musestrings.

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.