Cannot remove one bar or time signature in a particular piece.

• Oct 3, 2020 - 23:27

I am working on a transcription of a transcription and imported the MXL file. Everything was going fine until I tried to eliminate a bar and remove a time signature. I removed other (redundant) time signatures, but this one is in the middle of a bar and won't let me remove it. And the bar before is an empty bar that I cannot remove. In the attached score it is bars 50 and 51. Please, someone tell me how to get rid of that bar and that extra time signature. I'm stumped until then. Thanks!!

Attachment Size
Freue_dich_des_Weibes_deiner_Jugend.mscz 43.07 KB


OK- I found command+delete, so I could get rid of the extra bar, but still can't get rid of the 3/2 time signature in bar 50.

There is another oddity that I found later in the piece. The 3/2 bars have an added non-printing beat that makes the bars 4/2 bars despite the correct time signature. Why is that, and how do I get rid of the extra beat that MS added to each bar in that section? (See attached screenshot). Thanks again.

Attachment Size
screenshot bar 79.pdf 104.36 KB

When I open the file I don't see a time signature in the middle of a bar. Muse Score reports corruption in bars 112 and 113 and I see a superfluous hidden minim rest at the end of each of those bars. I can ctrl+delete them. I can also ctrl+delete bar 50. I think the 3/2 time signature in the (current) bar 51 is needed there but a simple delete will get rid of it if that is what you want.

In reply to by mike320

All good- The ending is exactly the same as the beginning, so a DC al fine eliminated the remaining issues. This isn't the first time I've had problems importing XML files created with the Capella app. Next time I'll just use a MIDI file or enter everything from scratch. Thanks for your help.

In reply to by

If you attach the XML someone can look to see if the problem is with the Capella export or MuseScore import. MuseScore is good, but we do find bugs with imports at times. In the future, Capella files can be imported directly by MuseScore with no need to export to XML first.

In reply to by

BTW- I only assume that the original was in Capella because the site I found it on only had PDF, MIDI, MXL and Capella formats available. For all I know, the guy did it in MuseScore (or something else) and exported to XML and Capella. I've had plenty of challenges tying to adapt these, especially when there are clef and meter changes. Sometimes I have to change the clef on every page for example.

In reply to by

The .mxl import reports corruptions:
Measure 105, Staff 8 incomplete. Expected: 3/2; Found: 0/1
Measure 106, Staff 6 incomplete. Expected: 3/2; Found: 0/1
Measure 106, Staff 8 incomplete. Expected: 3/2; Found: 0/1
Measure 106, Staff 9 incomplete. Expected: 3/2; Found: 0/1
As long as those are not fixed basically anything can happen. See for various methods to fix them

In reply to by

Wow. Thanks for that article! I'm glad to see there is a way to salvage those files!
I ended up not needing to deal with the corrupted ending of that score, as I deleted the end of the score and put a DC al fine in instead, since the notes were the same in this case.
Am attaching the finished score (pdf) and MS) so you can see how it turned out. I've adapted at least one transcription per day in the week or so I've been using MuseScore. There's a lot to like with it!

In reply to by

If a measure is reported as corrupt and you just don't see it, it will often become obvious if you exhanges voices 1 & 2 twice (to keep your notes in voice 1) using the tools menu. There are some corruptions that different, but those usually cause a crash if you click the corrupt measure.

In reply to by Jojo-Schmitz

Just for grins, I went back to the original corrupted XML file and loaded it to see if the plug-in for fixing corrupted files would work. The plug in said that there was none. But there were all manner of terrible things going on- extra +s all over the place, a 3/2 section with an extra beat at the end of each bar, etc. and even a section out of synch. Then I loaded it from the MIDI file and it had none of those issues. So, I always try the XML versions first, assuming that they have more information. But sometimes the rendering is so messed up that the MIDI version will be more reliable. At least that is some of my experience with the two.

In reply to by

There is a difference between corrupt and modified. If there are + or - over a measure it means you have changed the duration of the measure from what is indicated by the time signature. This is not an indication of a corrupt measure. If you have a corrupt measure MuseScore will usually report it when you open the score and tell you which measure and what's wrong with it.

Do you still have an unanswered question? Please log in first to post your question.