musescore / musescore/MuseScore

[Tuning] Playable range should be extended to reflect string tunings

Open
#19,790 1 comment 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue type

Other type of issue

Bug description

Per the design spec, changing an instrument's range via the new alternate tunings widget should also extend the playable range of the instrument, such that notes don't appear in red when they are in fact now available.

Steps to reproduce
  1. Apply alternate tuning widget to a score containing a guitar instrument
  2. Lower 6th string to D
  3. Enter an open D on the 6th string
  4. The note D is coloured red, indicating it is beyond the playable range of the instrument
Expected behaviour

The "Professional" and "amateur" usable pitch ranges of the instrument in Stave/Part Properties should be updated to reflect any changes to the lowest (and highest) playable pitches in effect as a result of changes to that instrument's tuning. Pitches available as a result of string tuning changes should be reflected in both the "professional" and "amateur" usable pitch range settings.

Screenshots/Screen recordings
Screenshot 2023-10-20 at 1 42 56 pm
MuseScore Version

OS: macOS 13.1, Arch.: x86_64, MuseScore version (64-bit): 4.2.0-232930304, revision: github-musescore-musescore-c8d643a

Regression

No.

Operating system

macOS 13.1

Additional context

No response

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.