musescore / musescore/MuseScore

Changing dynamic during arpeggiation

Open
#22,377 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

I propose to expand the notation options (currently available in Musescore) of dynamic notation to include arpeggiation.
It would be great if the user could place the hairpins vertically right in front of the arpeggio sign, thereby indicating how the loudness should change during the playback of the arpeggiated chord.
Снимок экрана (228)

Problem to be solved

This will allow the reader/performer to clearly understand exactly how the arpeggiated chord should be played. And it will be easier for the user to compose such a musical notation, instead of entering a bunch of notes before the beat and indicating the dynamics. I suggest a simpler and more understandable version of the notation.

Prior art

No response

Additional context

It should be understood that the change in dynamics during arpeggiation occurs taking into account the fact that the chord is played before the beat (and the last note falls on the beat), which has not yet been fixed in Musescore, as I outlined in issue #22342.

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.

Research direction

No implementation files or tests are identified. Start by reviewing the existing dynamic and arpeggio behavior, then read issue #22342 for the timing constraint; done means supporting vertically placed hairpins that convey dynamics during arpeggiation in notation and playback.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.