musescore / musescore/MuseScore

Providing repetitive bar disclosures on subsequent systems

Open
#23,917 0 comments 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

My idea

I propose to implement a function that would force the program to automatically duplicate a repeating bar on subsequent systems. Example:
Снимок экрана (475)

We are talking about an instrumental part. It would be great if the repeat signs were present only in the instrumental part, and not in the full score as well. In the full score, it is important to reveal all the repetitions so that the conductor can better understand the musical texture itself. Therefore, it would be good to have settings like "convert to repeat characters only in parts" or the like.

It is also worth mentioning the numbering of the bars. Usually, in instrumental parts, the bar, which must be repeated several times in the future, is marked with the number "1". At the moment, in MuseScore Studio, you can enable the numbering of only subsequent repeat characters, and not the first bar as well.

Problem to be solved

This will make it easier to read music from a sheet. The performer will not have to look back at the previous system to remember how a repeating bar is revealed.

Additional context

It would be great if the program had an algorithm that recognized which bars are repeated and at the same time are the same and converted these bars into repeat signs in instrumental parts itself (but at the same time the user should still be able to activate/deactivate such recognition).

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 implementation files, tests, or entry points are named. First clarify whether the target is automatic recognition, part-only conversion, repeat-bar numbering, or all three. Done would require agreed behavior for instrumental parts versus the full score and an explicit user-controlled setting.

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.