musescore / musescore/MuseScore
Triangular noteheads as the highest/lowest possible pitch. Notation
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
I propose to implement such notation in Musescore, taking into account the correct vertical alignment of such notes (depending on the free space and the placement of previous notes).
Problem to be solved
This will allow users (instead of taking up a bunch of vertical space and using octave lines) to specify the highest or lowest pitch as a note.
Recently, I had the need to write a glissando from the note cluster (I will create an issue about it separately) to the highest note. I managed to get the desired look (but not the sound) with difficulty, for this I had to manually align the stems, hide the noteheads, add specially designed symbols from the palette, etc. It's very painstaking and tedious. To avoid this, I just propose to implement it.
Additional context
Basically, such notes are used only to indicate the final pitch of the glissando. I will note only some basic details:
- The stems of such notes should not be centered on the edge (as with ordinary notes), but in the center of the musical notehead;
- The vertical arrangement of such notes (above the staff - for the highest pitch and below - for the lowest) should depend on how high or low the previous note was located on the staff / ledger lines;
- The guide says that to indicate the whole note, you need to use two halves connected by a tie. I suggest that we reconsider this designation option and take into account that in the SMuFL there are special noteheads designed for both minim and semibreve notehead-values.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.