musescore / musescore/MuseScore

Subscores

Open
#25,968 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

Many score will use the same pattern over and over again in different parts of a song. Maybe the verse drum beat is the exact same verse 1 and it is in verse 2. It would be great to be able to create some sort of score subsections.

Problem to be solved

A subscores would be a score that is saved into a score itself and then you can place this subscores into the main score itself like a note or rest.

For example a simple drum subscore could be (X-X-X-X---X-X-X). And you can place this subscore into the main score like this (X-X-X-X---X-X-X|X---X---|X-X-X-X---X-X-X). In the previous example the subscore was placed in bar one and three and the subscore is like a note. You can edit the subscore in another tab.

Subscores should be saved in the score file and not as a seperate file that is imported/linked to the score file.

Prior art

Kinda like how MPD LDraw files work for those who use LDraw. LDraw has something called submodels which are small models inside of a model and these submodels can be placed inside the model like a brick one or multiple times.

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

https://github.com/orgs/musescore/discussions/32168

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

Begin with issue #25968 and the linked discussion #32168; no implementation files or tests are identified. Before coding, establish the intended score model, editing behavior, and file-storage requirements, with completion defined as reusable subscores integrated into a main score.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.