musescore / musescore/MuseScore

Musestring sound flags lack articulation playback

Open
#23,219 2 comments 0 reactions 2 assignees View on GitHub

@bkunda is already working on this.

Since Jun 14, 2024.

MuseSounds needs info
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

Musestrings sound flags that are not set to Ord. do not respond to articulations (staccato, accent, etc.). This is also observed to ignore tremolo markings, resulting in a machine gun of sustain samples.

Steps to reproduce
  1. Open the score attachment: https://drive.google.com/file/d/1Stcjgwe10vyrbIU1f9Pw1Z7vE5w_aBZq/view?usp=sharing
  2. Highlight any of the Musestrings in isolation
  3. Press play
  4. Observe the results. Articulations seem to be ignored by the other Musestring soundflags unless they are set to Ord.
Screenshots/Screen recordings

No response

MuseScore Version

Musescore Studio 4.3.1

Regression

No.

Operating system

Windows 11

Additional context

Since tremolo markings of non-Ord sound flags result in machine guns of sustain samples, I interpret that this issue may be a result of the lack of dedicated samples rather than a playback trigger error. However, I report this behavior as a bug rather than a feature request to have samples of staccato, accent, tremolo, and trills for non-Ord sound flags in case my interpretation is incorrect.

This extends to text articulations (pizzicato) since I do not notice any difference in playback when I add accents to a pizzicato note. Tremolo fortunately does respond to accents (both the text and marking version).

The behavior mentioned above (for both sound flags and regular staff text that trigger playback) is not a regression as they have been observed since. Since this is a Musesound-specific behavior, I would like to confirm that MS Basic behaves normally in its own MS Basic way.

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.