Font support for SMuFL symbols to create visual swing markings
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
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.
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
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.
More from musescore/MuseScore
-
engraving P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
community P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
regression nightly UX/interaction
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in musescore/MuseScore
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·