musescore / musescore/MuseScore

MultiMeasure actual duration probably should not be alterable in measure properties

Open
#23,683 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

corruption P2
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

File corruption

Description with steps to reproduce
  1. New Score
  2. Multi-measure rest
  3. Change actual duration in measure properties
  4. Score is corrupted
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/7cf1cadf-2274-4fa7-b0d1-b5802e72814a

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

OS: macOS 14.4, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.0-242010302, revision: github-musescore-musescore-5c912b2

Regression

No.

Operating system

Mac OS 14

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

Reproduce the issue in MuseScore Studio by creating a new score, adding a multi-measure rest, and changing its actual duration in Measure Properties. Inspect the multi-measure rest and measure-properties handling; done means the operation no longer corrupts the score.

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.