-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Combination of pickup measure and linked staff makes score corrupted #26233
Comments
Thanks for this post and the link to my post and attached score. Interesting that the metric corruption occurs with just the pickup and linked staff. Those were there from the start and I only got the corruption alert, as reported, after adding the percussion staff and added a three measures and a few notes. Thanks for being so gracious! After I posting in your other thread I noticed I was off topic. Should I delete my comment from that thread and place it here? |
Interesting, but I can't reproduce it.
Please don't delete your comment. I already reference it in this issue. |
Thanks for your continuing interest in illuminating and eliminating corruption causes. Here's an uncorrupted version of the score |
This version not only does not have a percussion staff, but it also does not have a linked staff, so there is no corruption in it. |
Issue type
File corruption
Description with steps to reproduce
This issue is based on a report from #24970 (comment)
Two String Concerto No. 1 FrTB MS4 - Corrupted??.mscz.zip
Change staff type to Tab. 4-str. commonUPD. This step is not requiredReproduced in Musescore 4.0.2 and 4.5.0 master
Can't reproduce in Musescore 3.6.2
Supporting files, videos and screenshots
linked_staff_corruption.mp4
What is the latest version of MuseScore Studio where this issue is present?
MuseScore Studio version (64-bit): 4.5.0-250240302, revision: github-musescore-musescore-73c5d40
Regression
Yes, this used to work in MuseScore 3.x and now is broken
Operating system
windows 10
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: