musescore / musescore/MuseScore

Duplication of a bar (or part of it) on the next page (after turning over) in the part

Open
#23,919 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

It would be very useful to be able to duplicate the last bar (or part of it) on the next page (which needs to be flipped), while the program itself (automatically) added an inscription ("repetition of bar …") above the corresponding bar + highlighted this bar with brackets so that the player understands that this is not the next bar, but the previous one (before flipping through).
Снимок экрана (470)
Снимок экрана (471)

Problem to be solved

At fast tempos with a dense texture, it turns out to be very useful for the player to duplicate the bar to the next (after turning over) page. The player will be sure that he finished the previous bar correctly (without having to look back). I will add that this is the case with a two-page spread of the score. Also, in the last bar of the right page, "V.S." may be indicated, which means "turn quickly". In this case, it is extremely useful to duplicate this bar on the next page.

Workarounds

At the moment, in MuseScore Studio, you can copy the last bar to the next page, but in this case the entire bar numbering system is lost and a "gap" appears in the full score. I haven't found any other workarounds yet.

Additional context

The very inscription "repetition of bar..." should also be included in the strings for translation into app.transifex.com since "repetition of bar..." is not a universal designation, and in other countries it can be interpreted completely differently.

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 copy-last-bar workaround and the page-turning and layout behavior described in the issue. Confirm how bar numbering and translated strings are handled, then define acceptance criteria for duplication, the “repetition of bar…” inscription, bracket highlighting, and preserving numbering without a gap.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
design, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.