musescore / musescore/MuseScore

Edit string data does not change usable pitch range properly

Open
#34,314 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community P3 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)

Description with steps to reproduce
  1. Open staff/part properties window
  2. Edit string data (example, standard to drop tuning on guitars)

The usable pitch range boxes seem to reflect the new tuning, but revert to the previous setting when the window is closed. Notes written for drop tuning still appear red as out of range.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/4f0bb59b-c037-45ae-8335-e08d1b8f4290

In which versions of MuseScore Studio is this issue present?

4.7.3

Regression

I was unable to check

Operating system

macOS 26.5.2

Additional context

No response

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

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

Start by reproducing the issue in the staff/part properties window using a guitar's standard tuning changed to drop tuning. Trace how edited string data updates the usable pitch range and survives closing the window; done when the setting persists and notes appropriate for the new tuning are no longer shown as out of range.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.