musescore / musescore/MuseScore

accidentals above note (for editorial corrections or musica ficta)

Open
#33,678 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

It would be nice to have an option in the Properties panel to put particular accidentals above the note. (This would only apply to selected accidentals, not all accidentals.)

Occasional accidentals above the notes are a common convention in modern editions of early music, for example, when notating accidentals that were omitted from the score but are implied (musica ficta). I've also seen it in new editions of e.g. baroque music when an editor indicates an accidental that was not explicitly written in the score, perhaps due to a printing error, but is probably implied.

See also #19177.

Problem to be solved

This can be done manually right now by clicking and dragging an accidental, but it's hard to get the placement completely consistent (especially across other edits).

Prior art

For example, see this Renaissance piece by Arcadelt, which was typeset using Lilypond:

Image
Additional context

No response

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.

Research direction

The issue points to the Properties panel and the existing manual accidental-dragging behavior; start by tracing those entry points and review related issue #19177. Done means a selected accidental can be placed above its note through an option, with placement remaining consistent after other edits.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.