musescore / musescore/MuseScore

Add a pair of quavers = triplet crotchet quaver metronome mark to the tempo palette

Open
#28,075 2 comments 0 reactions 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

For the metronome mark often seen after the word swing shown graphically as:
opening parenthesis pair of quavers = a crotchet & quaver under a triplet bracket, closing parentheses
to be added to the tempo palette

Problem to be solved

It seems this can only be achieved currently by various graphic methods and special characters that do not read with a screen reader. This would allow an accessible way for blind users to add this metronome mark. But also as it is a common metronome marking that is difficult for anyone to achieve without advanced work arounds it would be generally useful. It would also give a starting point that can easily be added and edited for other triplet markings.

Prior art

No response

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

No files or tests are named in the issue. Start by locating the tempo palette implementation and existing triplet or swing metronome marks, then trace how palette items are inserted and exposed to screen readers. Done means the requested mark can be added from the palette and remains accessible without graphic workarounds.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
accessibility, 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.