musescore / musescore/MuseScore

Removing Instrument Name in Staff/Part Properties changes clef from Bass to Treble

Open
#24,274 2 comments 0 reactions 1 assignee View on GitHub

@cbjeukendrup is already working on this.

Since Oct 29, 2025.

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

Removing Instrument Name in Staff/Part Properties changes clef from Bass to Treble

I have a piano duet score with the second instrument only showing the bass part.
image

I need to hide the instrument name (the whole score if for piano only, so it's redundant).

  1. Right click the second instrument.
  2. Select the Staff/Part Properties pop-up dialog
  3. Clear the Long and / or Short Instrument Name
  4. Click Apply
    Observe:
  • the instrument clef changes from bass to treble and moves down one octave.
    image

Note: if you do the same clearing of instrument name in the Instruments panel, there is no issue.
image

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/7499a89e-19ef-4157-b519-938a09988165

What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.2-241630831, revision: github-musescore-musescore-22b46f2

Regression

No

Operating system

Windows 11

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.