musescore / musescore/MuseScore

Need to prevent notes being entered below the tuning range of the staff

Open
#20,989 6 comments 1 reaction 2 assignees View on GitHub

@DmitryArefiev is already working on this.

Since Jan 27, 2024.

needs review UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

Using the guitar 8vb staff as an example. It is possible to enter notes accidentally below the tuning rage of the stave (i.e. below E) because the note input algorithm does not always choose the correct octave. This often happens when the previously-added note is low on the bass string. In this case it is clear that any subsequent note should be added at the higher octave so that it above the lower tuning limit of the guitar. Unfortunately this does not always happen and the note is added at the lower octave.

Suggestion: Institute a further check in note-input mode to ensure that the note is added at the appropriate octave, where there is ambiguity: i.e. above the minimum tuning range of the guitar.

No doubt this can also be applied to other instrunents.

MuseScore Version

MuseScore version (64-bit): 4.2.0-233521125, revision: github-musescore-musescore-eb8d33c

Regression

No.

Operating system

OS: Linux Mint 20.1, Arch.: x86_64,

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.