musescore / musescore/MuseScore

Decouple Transposition of Linked Staves from Source Staves

Open
#16,589 4 comments 8 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

When creating a linked stave, its transposition property is linked to the transposition of the original stave. I.e., if I use the Stave Properties Dialog to set some transposition on the original staff, it will carry over to the linked stave as well.

It would be nice to be able to set individual transpositions per linked staff.

Problem to be solved

Common use case: As a jazz musician, I often work with lead sheets. Lead Sheets contain only one voice that is used by all instrumentalists. To generate parts for transposing instruments, I can either

  • Create a new transposing instrument, Copy-paste the whole voice, hide the original one and export a PDF
  • Transpose the whole score using Tools > Transpose and export a PDF
  • ...or set the transposition of the part in the Stave Properties Dialog and export a PDF

Either way, this process is a little tedious and error-prone. More importantly, it needs to be completed each time a change is made in the original score.

If the transpositions of linked staves could be set individually, I could just add linked staves, set their transpositions accordingly, and changes from the original staff would carry over automatically.

Another use case that is probably a little more obscure: To help practice a song, I sometimes generate transposed copies in all 12 keys. The same process as above applies.

Prior art

N.A.

Additional context

N.A.

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 reviewing the Stave Properties Dialog behavior described in the issue and tracing how linked staves inherit transposition. Done means each linked stave can have its own transposition while changes from the source stave continue to carry over automatically.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.