musescore / musescore/MuseScore

Allow different clefs in parts from score

Open
#20,352 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

I would like the option to be able to have a different initial clef in a part than the score.

Problem to be solved

I prefer to input mensural notation in each part before editing the whole texture in order to more easily proof my entry of each partbook. It would be best in this case to have the original clef (usually a C clef) in the part but have modern vocal clefs (treble and bass) in the score. In Musescore 4.2, one can exclude a clef change from score or parts but not the initial clef.

Prior art

In Lilypond, one can achieve this by leaving the clef out of the variable that contains pitches and then calling that variable with different clefs preceding it. One can also contain the clef setting in a tag and then call the desired tag in the layout of the score or part.

Additional context

My particular context could be worked around by using an extra measure at the beginning as padding and then excluding the C clef from the score. Eventually, though that measure would need to be deleted.

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 tracing how MuseScore handles the initial clef and the existing option to exclude clef changes from scores or parts. Review the issue's LilyPond comparison and the current score/part behavior before choosing an approach. Done means a part can use a different initial clef from the score without requiring a padding measure.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.