musescore / musescore/MuseScore

Allow automatically exploding chords into parts

Open
#28,127 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

When creating parts, in addition to the existing controls for voice visibility, I would like to have an option to automatically explode chords into the parts. For example, 2-note chords in voice 1 in the original staff would be split into voice 1 and voice 2 from the parts' perspective, without altering the original staff.

Problem to be solved

In many orchestral scores, two wind or brass instruments may be written on the same staff, but notated as chords rather than separate voices, like in this example:

Image

Currently, if we have this notation on the score, the only way to create appropriate parts for Flutes 1 and 2 is to create a second staff which is hidden in the main score and contains the same music but split into voice 1 and voice 2. Then we can create parts from this hidden staff and use the voice visibility flags to select the respective parts.

Although this is a usable workaround (with the explode/implode tools to help set up the hidden staff), it is laborious and also does not automatically synchronize changes between the score and parts, which is a major downside.

Additionally, it would be nice to handle "a 2" (or 3, 4, etc) passages in the score by automatically duplicating the material to both/all parts. That might be a separate option.

Having these tools would creatly improve the usability of MuseScore for creating full sets of parts for orchestral scores.

Prior art

No response

Additional context

No response

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

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 existing parts and voice-visibility controls alongside the explode/implode tools. Define how chord notes should map to voices without changing the original staff, and determine how optional “a 2” or “a 3” duplication should behave; done means generated parts stay synchronized with score changes.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.