musescore / musescore/MuseScore

"Concert Pitch" is an ambiguous term and above that it's also symbolized in an misleading way

Open
#16,746 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

Please consider this request more as a feedback.
I don't think it's gonna be open very long.
Still I'll try to be as clear and short as possible.

I believe:

  1. "Concert Pitch" should better be called "Sounding Pitch".
  2. Neither for "Concert Pitch" nor for "Sounding Pitch" should the symbol be a tuning fork.
Problem to be solved

Allow me to explain why I think so:

  1. "Concert Pitch" is an ambiguous term which is also used for tuning. See:

image

In Germany for example "Concert Pitch" is only associated with tuning and
I myself still can't remember whether "Concert Pitch" actually means "written" or "sounding" pitch,
since the term does not contain this information.

image
2. The tuning fork symbol makes it seem as though
the term "Concert Pitch" would have to do with its second meaning: the frequency of the master-tuning,
which in the giving case it has not.

Prior art

No response

Additional context

Final thoughts:

"Sounding Pitch" would be a clear term
which contains the actual meaning inside its name.

Because of that it would need no symbol to explain itself
so that both problems could be solved at once.

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 names no files, tests, or entry points. Start by locating the UI entry for “Concert Pitch” and its associated tuning-fork symbol, then confirm the proposed terminology and icon changes in the relevant music-notation interface; done means the label and symbol no longer convey the ambiguous meaning described.

Written by the indexing model from the issue text.

Assessment

Domain
design
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 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.