Lightningbolt / Broken Arpeggio style

Open
#29,514 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No source files or tests are named. Start by locating the existing arpeggio styles and the Master palette's "Combining string noise for stem" symbol; done means the new style plays the requested two-notes-up, one-note-down pattern and is displayed as a lightningbolt.

Written by the indexing model from the issue text.

Description

Your idea

Please add a new arpeggio style which plays notes alternatingly like in the image below (2 notes up, 1 note down), and is notated like a lightningbolt.

Image
Problem to be solved

Adding this type of arpeggio would be a massive boon for anyone writing for carillon, as this arpeggio is both common and very idiomatic in carillon music. Its absence makes writing for the instrument very difficult.

Due to carillon players playing with their whole hands instead of their fingers, it's a lot easier to play an arpeggio by alternating their hands and following this pattern, than to play an arpeggio 'normally'; as you would with any other instrument.

Prior art

No response

Additional context

The master palette contains a symbol "Combining string noise for stem" which looks a bit similar, but this is a relatively small symbol. While it's possible to upscale it, doing so to make it have the proper height also makes it way too wide, and it's impossible to customize the proportions, not to mention what a pain it is to notate it this way.

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

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.

More from musescore/MuseScore

All issues in musescore/MuseScore

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.