New user - import errors, deleting rests

• Mar 13, 2018 - 03:08

I am new to Musescore. I imported a .xml and a 1/16th rest appears in the first measure, and some others. I would like to remove this extra rest. How?

Thanks!
(p.s. I purchased the music, I am playing with transposing the vocal to tuba)

attached 1) what I am working on 2) pdf of original copy. I am using Music Scanner iphone app to convert image to .xml.

Attachment Size
Try And Love Again.mscz 23.03 KB
Tala-purchased.pdf 377.63 KB

Comments

Most likely the generated MusicXML file produced the superfluous rests. The simply way to turn those measures into whole rest measures is by clicking anywhere in the measure (not on the existing rest) to select the measure, and then press delete on keyboard.

In reply to by ericfontainejazz

Upon reading again, I realize now that you were not just wanting to fix the measures of rest in the Tuba staff, but you also wanted to fix those other measures. I'm noticing that a lot of measures for some reason have the notes in voice 2 while the rests in voice 1, so for those measures, you could select the measure and go to Edit->Voices->Exchange Voice 1-2. Then those rests can get deleted once they are all in voice two.

Unfortunately, your program did a pretty bad job of the conversion, it's going to take a lot of work to clean up, probably more than re-entering from scratch. But FWIW, the first measure, right click, Measure Properties, change the actual duration from 17/16 to 4/4, then re-enter the notes starting from the place when things got off (beat 2). Similar process for a bunch of other measures I'm afraid.

Thanks for the feedback. Here is the .xml file I used as input. I am wondering where in the process the extra rests are being inserted. The output playback of the scan to ,xml does not have them.

Attachment Size
Try And Love Again.xml 49.87 KB

In reply to by Rentsch42

The XML file is already quite messed up; MuseScore is simply making the best of it. In the first measure specifically, the sixteenth note G-E chord is specified using MusicXML code that says, basically, "make it look like a sixteenth but last as long as an eighth", which is where that extra hidden rest in the middle of the measure comes into play. The bottom staff simply has an eighth there. I guess the program wasn't able to figure out the bottom note was really a sixteenth and did its best to reconcile this, calling it an eighth on the bottom but a a sixteenth on top, then lining up the next notes normally from there, yields an extra sixteenth. Similar errors elsewhere I'm sure. This is pretty common with attempts to convert PDF to MusicXML - it's just still very experimental and unreliable technology, unfortunately.

Not sure what you mean about "output playback of the scan" - do you mean the program that actually did the conversion to MusicXML has playback facilities? If so, then it seems that program recognized what it was supposed to be doing but wrote the MusicXML file incorrectly.

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