Font support for SMuFL symbols to create visual swing markings

Open
#21,590 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating MuseScore's default music symbol font and the rendering path for text-based swing markings. Use the listed SMuFL individual-note and beamed-group symbols as the scope; done means common swing eighth- and sixteenth-note markings, with or without joined beams and tuplets, display correctly.

Written by the indexing model from the issue text.

Description

feature request
Your idea

SMuFL has a "Beamed groups of notes (U+E1F0–U+E20F)" block with symbols specifically designed for metric modulation and swing markings (See "Implementation notes" in the aforementioned SMuFL page and this "How to" page from MuseScore forum).

Currently, MuseScore's default music symbol font does not support these symbols, and thus swing markings created with them cannot be displayed correctly and appropriately.
image

I would like these symbols to be added so the common visual swing markings can be easily created in MuseScore.

Problem to be solved

Help create common visual swing markings.

Prior art

No response

Additional context

Minimum symbol set required to create the common swing markings (swing 8th notes and swing 16th notes with or without a joined beam):

Individual notes (U+E1D0–U+E1EF) Block

  • U+E1D7 (and U+1D160), note8thUp
  • U+E1D9 (and U+1D161), note16thUp

Beamed groups of notes (U+E1F0–U+E20F) Block

  • U+E1F1, textBlackNoteLongStem
  • U+E1F8, textCont8thBeamLongStem
  • U+E1F3, textBlackNoteFrac8thLongStem
  • U+E1F5, textBlackNoteFrac16thLongStem
  • U+E1F8, textCont8thBeamLongStem
  • U+E1FA, textCont16thBeamLongStem
  • U+E201, textTupletBracketStartLongStem
  • U+E202, textTuplet3LongStem
  • U+E203, textTupletBracketEndLongStem

Note: The tuplet bracket symbols should come after the note symbols.

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.