musescore / musescore/MuseScore

Make the default tuning (in note playback properties) the natural (0)

Open
#25,618 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

My idea is for the natural and unedited tuning of the playback of a note to be of the natural,

for example, if the note would be with a sharp, it would 100 cents higher (a half step, 100), while if the note would be with a flat, it would be 100 cents lower, therefore displaying it based on the center, which is the natural.

brief explanation

natural = 0 cents, flat = -100 cents, sharp = (+, not displayed) 100.

when faced with microtonal accidentals (like a quartertone) then it would be displayed based on its specific tuning,
for example, a half sharp, in cents it is 50 cents higher than the natural (0) therefore it will be displayed as 50, instead of the default 0 as of right now.

some microtonal accidentals are used for cosmetic purposes (which they often edit with their own personal tunings) and/or have different meaning depending on subjective definition, therefore this could remove confusion from those who professionally compose microtonal music

Problem to be solved

The addition of this feature can simplify confusion when faced with specific microtonal accidentals, like 1/7th tones, specific signs which have no completely agreed on definition, or specific accidentals with meanings that can only be rarely found,
if this addition will be included, it can erase that confusion while also confirming what tuning the accidentals will refer to.

Prior art

No response

Additional context

image

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, tests, or entry points are named. Start by locating the note playback properties and the code that maps accidentals to tuning values, then inspect how the current default of 0 is shown. Done means natural notes remain at 0 while standard and microtonal accidentals display their corresponding cent offsets.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.