musescore / musescore/MuseScore

Impossible to change a local time signature if the following bars have content

Open
#25,694 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue type

UX/interaction

Description with steps to reproduce
  1. Add a local time signature on a measure of a staff that has no more content after that measure
  2. Add some content while letting an empty measure in-between the content.
  3. Try to re-change the local time signature on the empty measure
    => ERROR : the measure is not empty (while it is)
    Rem: This error is not unlogical, because this change will impact the next measures which are not empty.

So alternate approach ("Attempt 2" in my demo)
3. Drop the current local time signature on the first non empty measure, in order to avoid that, when dropping a new local time signature on the empty measure, it impacts the next measures.
=> ERROR : the measure is not empty
Actually the measure is not empty, but as we are dropping the exact same times signature (in the demo, a 6/8 on a 6/8 measure), this should not give an error.

Supporting files, videos and screenshots

mcveLocalSignature

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

4.4.3

Regression

No.

Operating system

Windows 10

Additional context

Comes regularly on the forum:
E.g. https://musescore.org/en/node/292768

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 issue in MuseScore Studio 4.4.3 using the steps and the attached demonstration. Trace the validation performed when changing a local time signature on an empty measure with later content, including the case where the replacement signature is unchanged. Done means the valid signature change no longer reports that the measure is non-empty.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.