musescore / musescore/MuseScore

Muse Piano accents are inconsistent

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

@matthewreadbass is already working on this.

Since May 25, 2024.

MuseSounds P1
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

When using Muse Sounds, the various methods of specifying emphasis (accent/marcato articulations, sf/fz/sfz dynamic markings etc.) cause inconsistent results.

Steps to reproduce
  1. Create a new solo piano score using Muse Sounds
  2. Add a whole bunch of notes (ideally over 30) at the same pitch
  3. Add various accents/marcato articulations, dynamic "emphasis" type markings to various notes
  4. Duplicate the whole passage and add a regular f dynamic to the second copy.
  5. Play it back and and observe that some accents are very subtle (even a "marcato" hat), and others make no difference at all or even make the sound quieter! (e.g. fz when the underlying dynamic is f)

My general expectation:

  • Regular "accent" articulation mark could be something between the current level of emphasis and what you get with sfz when the underlying dynamic is mf. Regular marcato articulation mark (^) should be pretty much what you get using sfz (again when the underlying dynamic is mf).
  • Probably no need for any difference between fz/sf/sfz (debatable obviously), at least at mf underlying dynamic. Arguably sf should always mean "at least forte for just this note, but obviously louder than unmarked notes".
  • At an f underlying dynamic, fz (or the ^ marcato mark) should give something a bit less than the current sffz).
Screenshots/Screen recordings

https://musescore.com/user/7209246/scores/17311960/s/6liQrz

image

MuseScore Version

4.3

Regression

I don't know

Operating system

Windows 11

Additional context

No response

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.