-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Closed as not planned
Labels
P1Priority: HighPriority: HighcorruptionIssues involving file corruptionIssues involving file corruptionneeds testingTesting is needed (if issue doesn't reproduce or might be fixed already)Testing is needed (if issue doesn't reproduce or might be fixed already)
Description
Issue type
File corruption
Description with steps to reproduce
This issue is created while investigating https://musescore.org/en/node/374264
- Create new score from Treble clef template
- Open parts and go back to main score
- Enter 4 quarter notes in voice 1 and one whole note in voice 2 (voice 2 is required here)
- Enter one note (any duration) to the next measure
- Add double barline before the last entered note
- Save score / close / reopen
- Remove last entered note
- Undo
- Save score - the message about corruption appears
Not a regression.
Reproduced at least in Musescore 4.0.2
Partially reproduced in Musescore 3.6.2
Supporting files, videos and screenshots
Corruption message:
barlines_corruption1.mp4
Dynamics synchronization lost in full score:
barlines_corruption2.mp4
Crash on closing:
barlines_corruption3.mp4
What is the latest version of MuseScore Studio where this issue is present?
MuseScore Studio version (64-bit): 4.5.0-250180301, revision: github-musescore-musescore-2b1f288
Regression
No.
Operating system
windows 10
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P1Priority: HighPriority: HighcorruptionIssues involving file corruptionIssues involving file corruptionneeds testingTesting is needed (if issue doesn't reproduce or might be fixed already)Testing is needed (if issue doesn't reproduce or might be fixed already)