musescore / musescore/MuseScore

Template for Piano 4 Hands

Open
#29,413 1 comment 4 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

Originally posted by vixyswillie in #29399, August 21, 2025
I am proposing the creation of a new template in Mu4 for "Piano 4 Hands," listed under the "Solo" category.

IMSLP.org currently contains over 4500 compositions and arrangements for two people playing on the same piano. This unique full score requires a braced pair of treble clef staves for the primary part (termed "Primo") and a braced pair of bass clef staves for the secondary part (termed "Secondo").

When the score is printed, the following conventions are typically observed:

  • Page 1 (unnumbered) is a title page that contains the name of the composition (including any Opus and Catalog Numbers), the composer, the arranger (if different from the composer) and the publication date.

  • Page 2 bears the name of the composition as the title, with "Secondo" as the subtitle. The composer's name and any Opus/Catalog Number appears immediately above the first staff on the right. The first pair of braced bass clef staves on the page is indented. This is the first page of music for the secondary part.

  • Page 3 is identical to page 2, with pairs of braced treble clef staves and "Primo" as the subtitle. This is the first page of music for the primary part.

  • Page 4 bears only "Secondo" as the subtitle. This is the second page of music for the secondary part.

  • Page 5 is identical to page 4, with "Primo" as the subtitle. This is the second page of music for the primary part.

  • Page numbering and subtitling continue as above to the end of the piece.

  • The number of measures on both player's pages must match, so that page turns align during performance.

I don't see a way to attach a PDF example of the above, but am happy to do so upon request if it would be helpful.

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

The issue requests a new Mu4 “Piano 4 Hands” template under the “Solo” category, but names no files, tests, or entry points. Start by locating the existing Mu4 template definitions and comparable Solo templates, then verify the Primo/Secondo layout, alternating subtitles, title page, and aligned measure counts against a representative score.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
design, desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.