Section Breaks in scores created with MSv2.3.2 do not import when loading score in MSv3.6.2
My score (created in MS v2.3.2) contains Section Breaks between movements. When I load the score in MS v3.6.2, all of the Section Breaks are missing and have to be added back in manually
Comments
I can't reproduce this
In reply to I can't reproduce this by Jojo-Schmitz
Attached is a score created w/v2 (section breaks between movements). Also attached is the same score after loading from MS v3 (all section breaks missing).
In reply to Attached is a score created… by Mike Magatagan
I can confirm with that. Not sure what triggers it though?
In reply to I can confirm with that. Not… by Jojo-Schmitz
Ah, it has a section break and a system break, that's the trigger, only the system breakes gets imported, but it is superfluous in MuseScore 2, as a section break also is a system break and in MuseScore 3 and 4 you can have only one of them.
In reply to Ah, it has a section break… by Jojo-Schmitz
Yes. Very common to include both, especially after automated pagination. Did not create a problem prior to 3.x and both work fine in "Send to YouTube".
In reply to Yes. Very common to include… by Mike Magatagan
MuseScore 3 automatically removes system breaks when you add section breaks, so it's not common at all anymore to have both. I guess 2.3.2 lacked that feature, though, some older scores might still have this problem. Not sure why it would be common to add both, though. What you mean by "automated pagination"?
In reply to MuseScore 3 automatically… by Marc Sabatella
Marc, I have over 4K scores in v2.3.2 so it's common (for me) is to place the section breaks first between movements and only after the score is complete do I choose the 'Edit-->Tools-->Add/Remove System Breaks'. Unfortunately, in v2.3.x, it faithfully adds the System Break at the end of every line; regardless if the line already ends with a section break. So by common, I'm referring only to my practices.
In reply to Marc, I have over 4K scores… by Mike Magatagan
Wow, I knew you had been prolific, but I had no idea how so! Anyhow, I see, not so much automatic pagination, but automatic adding breaks every four bars or whatever. So indeed, if you had been in the habit of doing that after already adding section breaks, you'd see this often. In the four years since MuseScore 3 was released, I don't recall this having been reported before, which is why I say it doesn't seem to be a common problem in general, but obviously, it's common within your own body of work, which is still very unfortunate.
Probably a sufficiently clever & motivated person could write a Perl or Python script to process all those files, find the instances of section & line break pairs, and remove the latter. Or even just produce a special build of MuseScore 3 with the bug fixed, and use that to run a batch import operation.
But, assuming the bug does get reported to GitHub, I would also assume a fix will be forthcoming for MuseScore 4. I wouldn't bother with MuseScore 3 at this point with MuseScore 4 probably no more than a week or two away.
In reply to Wow, I knew you had been… by Marc Sabatella
Marc,
Now that I know what the trigger is, I can mitigate it before loading into MSv3/4. I will certainly get a copy of v4 as soon as I can.
Thanks!
In reply to Ah, it has a section break… by Jojo-Schmitz
If MSv3 supports only the Section break (implied system break) then (IMHO), the import should convert the System/Section combo to the single Section break and not require the user to manually locate and then replace the mission elements.
In reply to If MSv3 supports only the… by Mike Magatagan
Yes, I agree. Section break should take precedence over system break, not the other way round
In reply to Yes, I agree. Section break… by Jojo-Schmitz
Looking at the MSCX, the section break was written first. My guess is, last one wins. A fix would probably just mean, don't add the line break on read if a section break already exists.
In reply to If MSv3 supports only the… by Mike Magatagan
Certainly. I'd suggest opening an issue for this on GitHub for MuseScore 4 (a bit late to be worrying about MsueScore 3 at this point, although I'm sure if there is a fix, Jojo will port it to his "special" branch.
Hello! Could be something specific to that score; if you post it here e can take a look. Of course, the real question is whether it works loading into MuseScore 4.
In reply to Hello! Could be something… by Marc Sabatella
Marc, I posted above. It's all my scores that have section breaks. Very easy to reproduce.
In reply to Hello! Could be something… by Marc Sabatella
Yes, MuseScore 4 RC1 is affected too
If there is a system break and a section break on the same measure (possible only in MuseScore 2), the latter gets lost on import
In reply to Yes, MuseScore 4 is affected… by Jojo-Schmitz
Thank you for finding this. In the meantime as a mitigation, I will ensure my scores (those containing the Sys/Sec combo) contain ONLY the section break prior to importing/loading into v3/4