musescore / musescore/MuseScore

Automatic Rehearsal Marking Generation Inconsistency

Open
#24,510 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P3 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. Create two rehearsal marks at least 3 bars apart.
  2. Create a rehearsal mark one bar after the first, observe that a number has been appended to the previous letter.
  3. Create a rehearsal mark one bar after the mark created in step 2.

Expected behaviour: The appended number to the new rehearsal mark should be incremented from the previous rehearsal mark created in step 2.
Actual behaviour: The rehearsal mark simply shows 'B1' regardless of the preceding rehearsal mark.

Supporting files, videos and screenshots

Screen Recording 2024-09-06 at 18.19.44.zip

What is the latest version of MuseScore Studio where this issue is present?

MuseScore Studio version (64-bit): 4.4.1-242490810

Regression

I was unable to check

Operating system

OS: macOS 14.6, Arch.: arm64, MuseScore Studio version (64-bit): 4.4.1-242490810, revision: github-musescore-musescore-0b3dd00

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

Start by reproducing the three-step rehearsal-mark sequence in MuseScore Studio 4.4.1, using the attached recording for comparison. Trace the rehearsal-mark generation behavior and verify that the third mark increments the numeric suffix from the preceding mark instead of remaining “B1”.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.