Guitar tuning doesn't change "Usable pitch range"

Open
#30,621 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
desktop

Research direction

Start by reproducing the issue through a classical guitar score, the Guitar palette's String tuning, and Staff/Part properties. Trace how Dropped D affects the usable pitch range and how the D2 note is validated. Done means the open low D is accepted automatically, with the behavior clarified for amateur and professional ranges.

Written by the indexing model from the issue text.

Description

P4 UX/interaction
Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. Create a new (classical) guitar score from template under Solo > Guitar.
  2. Add a String tuning from the Guitar palette and set it to Dropped D tuning.
  3. Enter a low D note (absolute pitch D2), which is the open low D string.

Current behaviour: the note is red since it is outside the usable pitch range. To change this, one needs to right click on the staff to go to Staff/Part properties and change the "Usable pitch range" to D2 (I'm not sure whether for amateur or professional range, maybe both).

Expected behaviour: this is done automatically.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/ecbcd298-a229-4841-8626-b19737d652bc

In which versions of MuseScore Studio is this issue present?

4.6.2

Regression

I was unable to check

Operating system

Arch x86_64

Additional context

Why does this option "usable pitch range" even exist, for guitar at that? And why the distinction between "amateur" and "professional"? I understand that this was also available under MuseScore 3, but I'd suggest to remove this option a future versions, maybe MuseScore Studio 5.

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

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.

More from musescore/MuseScore

All issues in musescore/MuseScore

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.