musescore / musescore/MuseScore

Per-instrument Styles in Single .mss File

Open
#30,431 0 comments 0 reactions 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

For each saved style, the file should contain the "master style" for the score and default part style, and list the adjustments needed for individual instruments. For example, the XML tag for "Tuba" would only contain the definitions for tuba-specific adjustments, which override the primary style defined above.

This would make it easier to blanket-adjust styles for an entire project without overriding instrument-specific needs.

Problem to be solved

With current system, I can either load one style file and manually adjust each instrument's style (move measure numbers to bottom for piccolo, adjust system spacing for tuba, etc) OR I can save/load a style file for each instrument, which leads to desynchronization between these files when I adjust a font/weight.

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

No source file or test is named. Begin by locating the .mss serialization and the XML handling for instrument-specific style tags, then compare how master, default-part, and instrument adjustments are saved and loaded. Done means one style file can preserve shared defaults while retaining instrument-specific overrides without desynchronization.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.