musescore / musescore/MuseScore

Cut time removed repeated bars

Open
#32,099 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

awaiting reply from user
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Choose option...

Description with steps to reproduce
  1. Write music in 4/4
  2. Add repeated bars (one or two)
  3. Add cut time before those bars
  4. The repeats will disappear
Supporting files, videos and screenshots

Fritiof i Arkadien.zip
(I put some back before saving this file, and can't find my autosaves anywhere.)
Repeats disappeared from bars 22-24 and 50-52, along with plenty "repeat last two bars" at H and I

In which versions of MuseScore Studio is this issue present?

4.6.5-253511702, revision: github-musescore-musescore-653f38d

Regression

No.

Operating system

Windows 10 Version 22H2 or later, Arch.: x86_64

Additional context

No response

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

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

Open the attached Fritiof i Arkadien.zip in MuseScore Studio 4.6.5 on Windows and reproduce the steps: create 4/4 music, add repeated bars, then add cut time before them. Compare bars 22–24, 50–52, and the repeated sections at H and I; done means the repeats remain after cut time is added.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
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.