Strange 128th rests in XMP import

• Oct 20, 2013 - 09:32

I have version 1.3, rev. 5702. I tried to move sheet music from Encore (a rather old one, probably the first version with XML export) to MuseScore. I know Encore does not a very good job in that and my problems relate to that. But I thought maybe MuseScore could still handle the problems. What I get is a sheet that looks almost right, but there are a lot of 128th rests there, set as invisible. Everything seems to be in voice 1. What puzzles me is how MuseScore holds the uneven amount of notes and rests in one measure. Looking at the measure properties, the time signatures are 4/4. If I could find a way to delete the rests, I'd be fine.
Attached is the original xml export and the mscz file.

Attachment Size
Små sakerpiano.mscz 3.56 KB
Små sakerpiano.xml 77.71 KB


In reply to by Jojo-Schmitz

I downloaded the latest build and it didn't recognize the file as valid. I got this error message:
Fatal error: line 650 column 24 Element tied is not defined in this scope.

I loaded it anyway and it crashed. So 1.3 did a better job. At least it opened something.

I saved your .mscz file as midi to look at measure #3. It had a 33/32 time signature (in Anvil Studio). Elsewhere, other note timings appeared problematic.
Abandoning that approach, and back in MuseScore, I merely inserted 3 new measures and entered new notes, then deleted the measures with the 128th rests. See attachment.
As I'm not familiar with the piece, I don't know if you want to keep the 4/4 nominal vs. 5/4 actual measure durations found elsewhere viewing 'measure properties'.
(Also, there's that weird double flat in measure #18.)


Attachment Size
sakerpiano.mscz 3.36 KB

In reply to by Jm6stringer

You came as far as I would have wanted to, almost. Not quite sure what you did there, how you managed to delete rests, unless you totally rewrote the measures.

No, there shouldn't be any 5/4 measures. I guess some errors relate to Encore's cross staff handling. Some might relate to a real time midi input I did for this song. There might even be some peculiar timing issues because of some inserted ritardandos. Like the 5/4 in measure 4 - I might have added a tempo change there to simulate a fermata on 4th beat, which probably lead to the stupid 5/4 time signature. Encore might have tried to adjust varying tempos elsewhere by adding the 128th rests, don't know. This all sounds very stupid, because one would think that XML exporting should be about sheet music, not about playback. Anyway, I've almost abandoned Encore totally. Too bad I have tons of sheet music written with Encore and as you see, transporting via XML doesn't work very well. While writing this, I remember I forgot one important step before exporting to XML, and that was aligning playback to note values. That might have helped a lot.

Another annoying thing with Encore is that I need to have at least three versions of it on my old PowerBook, because the newest one I have doesn't read my oldest files. The original score is vocal + piano and I had to split it into two separate files. Exporting a vocal + piano sheet went totally crazy.

The strange double flat note in bar 18 must have been a "typo" at some point.

Just tested this software.

It did a marvellous job. I just read the pdf file, then exported it to MusicXML, then opened it in MuseScore. Not a single thing had to be corrected! So the best thing for me seems to be to create pdf files of all my old Encore sheet music, then use PDFtoMusic Pro to convert it to a format that MuseScore understands.

In reply to by jotti

I've done the same thing with a bunch Capella files MuseScore wouldn't want to tmport directly or completly. It worked quite well, but not without manually fix things here and there.
Printing from Capella Reader into a PDF printer (PDF24), then PDFtoMusicXML. Fortunatly all sheets where only one pages, so the demo version was good enough for me ;-)

In reply to by jotti

I believe that PDFtoMusic Pro is a good toolbox addition, although the venerable ChurchOrganist might disagree:

Anyhow, here's a quick litmus test (see attachment) you can perform on a .pdf:
Dragging the (select) cursor in Adobe Reader on a .pdf score will reveal whether score elements (eg. titles, clef, notes, etc.) are present (and therefore a good candidate for PDFtoMusic Pro); or if the .pdf score is an embedded (scanned) image (no score elements - so perhaps something like Audiveris may work, or manual transcription will be necessary).

Ironically, the two pdf's of the Bach chorale pictured in my attachment were actually from ChurchOrganist:
where he kindly provided two pdf's - one of which I was able to process through PDFtoMusic Pro and into MuseScore for the original poster, who was struggling with midi.

Regards to all.

Attachment Size
Image vs score elements.JPG 175.31 KB

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