musescore / musescore/MuseScore

Ambitus showing bracketed noteheads separately

Open
#18,943 0 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

In vocal music, when a part has a particularly low or high notes, there's sometimes an optional alternative, which is shown as a bracketed notehead. Occasionally this is reversed, so the highest/lowest note is optional and becomes bracketed. When the highest or lowest note of a part is a bracketed notehead, the ambitus could also show it bracketed, and include the highest/lowest non-bracketed notehead as well to show the required and optional ranges of a part.

Problem to be solved

At present I can't indicate optional ranges at the start of a piece with an ambitus - all the optional high and low notes are shown as full noteheads in the ambitus which makes it look as though the required range is larger than it is.

Prior art

In Sibelius, I'd just use non-playing notes to work around this, meaning I could choose to bracket them myself, but this requires manual checking of the ranges. The ambitus in MuseScore is great as it calculates from the notes themselves, but I miss the control of being able to show optional ranges.

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.

Research direction

Start by locating the ambitus calculation and rendering entry points, then trace how bracketed noteheads are represented in the score. Define the required and optional high and low notes from the issue description, and verify that the ambitus distinguishes bracketed extremes while retaining the non-bracketed range.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.