musescore / musescore/MuseScore

Contemporary music notation palette

Open
#34,929 8 comments 2 reactions 1 assignee View on GitHub

@davidstephengrant is already working on this.

Since Sep 18, 2026.

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

Description

Your idea

As a composer and educator, I have a vested interest in the future of MuseScore, as probably over 90% of my students are now using it. While it has some incredibly advanced aspects (microtonal accidentals), there are some basic contemporary music notation areas that are still lacking or underdone. With a 'contemporary notation' palette, MuseScore could lead the way in this area.

While there are many things that could be added here, I have considered only the most common, important notations that would be needed and that have previously been requested. Some of these can already be achieved or 'hacked', but having them here would streamline their use.

I used the following criteria when coming up with a potential list:

  1. Notation should still be in common usage, and should be present in important, published scores by leading composers
  2. Notation should be 'feasible'/practical — I can imagine how it might be implemented, and the parameters necessary for completing it
  3. Notation should either not already be present in MuseScore, or is present, but requires a bit of adjustment in order to achieve what I'm interested in

Here are my suggested symbols:

  1. Aleatoric box, with option for extender line with arrow (line can be straight/curvy, arrow can be a vertical line)
  2. Time bracket, with editable text
  3. Duration indication, with editable duration
  4. Technique transition arrow (already exists, but needs fiddling/adjustment)
  5. Note-to-noise transition arrow (after Saariaho)
  6. Bow pressure triangle (after Saariaho)
  7. Sinewave vibrato/gliss diagram
  8. Variable sinewave vibrato/gliss diagram
  9. Squarewave smorzato diagram
  10. Play between bridge and tailpiece (after Penderecki)
  11. Play on tailpiece (after Penderecki)
  12. Play on bridge (after Penderecki)
  13. Play between bridge and tailpiece (after Penderecki)
  14. Irregular non-rhythmic tremolo (after Penderecki)
  15. Cluster block (after Penderecki)
  16. Cluster chord
  17. Notehead extender line (somewhat possible with note-attached lines; this just simplifies creation)
  18. Woodwind fingering diagrams
CONCEPT ART (Palette):
Image
SCORE EXAMPLES
  1. Aleatoric boxes (work by Georg Friedrich Haas)
Image
  1. Time bracket (work by Saariaho)
Image
  1. Duration indication (from Behind Bars)
Image
  1. Technique transition arrow (work by Kaija Saariaho)
Image
  1. Note-to-noise transition arrow (work by Saariaho)
Image
  1. Bow pressure triangle (work by Saariaho)
Image
  1. Sinewave vibrato/gliss diagram (work by Penderecki)
Image
  1. Variable sinewave vibrato/gliss diagram (work by Rebecca Saunders)
Image
  1. Squarewave smorzato diagram (work by Ferneyhough)
Image
  1. Play on tailpiece (work by Penderecki)
  2. Play on bridge (work by Penderecki)
Image
  1. Play between bridge and tailpiece (work by Penderecki)
Image
  1. Irregular non-rhythmic tremolo (after Penderecki)
Image
  1. Notehead extender line (score by Helmut Lachenmann)
Image
  1. Cluster block (after Penderecki)
Image
  1. Tone cluster chord (score by Henry Cowell)
Image
  1. Woodwind fingering diagrams (work by Saariaho)
Image
Problem to be solved

A number of these are fairly standard notation these days, and would be amazing be included in future version of MuseScore.

Prior art

Dorico has a number of these features available.

Additional context

Each of these probably represent a significant amount of coding. They could be gradually introduced in successive versions.

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

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.