Import multiple errors
I am encountering the identical same two problems when exporting a SmartScore X2 Pro file and importing into MuseScore:-.
I get multiple text “instrument change”. Each need to be deleted individually
I get multiple spurious rests in voices 2,3 and 4 throughout the part(s). As there is no way to multiple delete, each one needs to be deleted individually, it takes hours with a big score.
I have attached an example of each file.
Is a software update needed? In the meanwhile are there shortcuts to correct the errors?
Please advise.
| Attachment | Size |
|---|---|
| Papas Got A Brand New Bag I Feel Good 2018 - Tenor Saxophone.mscz | 24.68 KB |
Comments
What is the xml (?) SmartScore created? What is the source you fed into SmartScore?
In reply to What is the xml SmartScore… by Jojo-Schmitz
Smartscore reads a pdf, puts it into notation format.
If you look at the other voices, Musescore has created multiple rest in addition. It is a known Musescore error apparently. Looking for a shortcut to erase the erroneous rests, notation and text.
In reply to Smartscore reads a pdf, puts… by David Goodwin 2
OK, so you fed it a PDF, but which? ANd what was the XML outcome?
It might be (and probably is) an issue of GIGO (Garbage In, Garbage Out), i.e. the XML is already bad, so MuseScore can't do anything about it but importing what it got
In reply to OK, so you fed it a PDF, but… by Jojo-Schmitz
The resultant notation file from Smartscore had minor edits and the result was perfect. I'd share it with you but you probably couldn't read it. It is an expensive piece of sophisticated software. The developers have confirmed that it is a Musescore error and is well known and yet to be corrected. So, is there a known shortcut to erase Musescore multiple import errors? It may be otherwise easier to use Finale which does not create such errors, I've checked.
In reply to The resultant notation file… by David Goodwin 2
Without seeing the xml no one will be able to see what the "known error" is and fix it. There are some know errors that are being worked on but we have no idea if the errors you are talking about are among them.
In reply to The resultant notation file… by David Goodwin 2
FWIW, I'm one of the developers of MuseScore and I don't know of a specific error on our end that would result in an otherwise correct MusicXML showing extra rests. The cases I know of where this happens are when the MusicXML file itself is in error. So we would definitely need to see the actual MusicXML file in order to investigate further. And yes, we can read MusiXML :-)
BTW, in the score you posted, I don't offhand see extra rests, any particular measure I should be looking at? But again, without the corresponding MusicXML file, there is no way to know if they are in fact "extra" or if the MusicXML file itself had issues.
The Instrument Changes are almost certainly a direct result of the MusicXML file containing changes of instrument. You can either correct the MsuicXML file or delete the changes all at once within MuseScore with right-click, Select / All Similar Elements, Delete.
Anyhow, there is no magic command to detect "import errors" because a) we have no way of knowing what errors existed in the source file, and b) if there are known bugs in our import process, we'd fix them so it works correctly the first time rather than import correctly then make you run a command to fix the error :-)
I get multiple text “instrument change”. Each need to be deleted individually.
Looking at your score...
Right click on a single 'Instrument change', then Select -> All Similar Elements then press Delete.
This will select and delete them all at once. Use the same process for the multiple 'rit' text.
I see no spurious rests in voices 2,3,4 but the same basic procedure holds although maybe you prefer to use Select -> More... and then choose whatever voice you want deleted.
In reply to I get multiple text … by Jm6stringer
Thanks JM, I'll try it as as I get home.
If you go to bar 1 after the repeat beginning, click on the first crotchet, then on voices 2,3 and 4, all the spurious rests appear. I'll try your method to see if they can be erased en bloc. Thanks again. D
In reply to Thanks JM, I'll try it as as… by David Goodwin 2
Of course, when you change a voice 1 note to a voice 2, 3 or 4 note, those other rests show up and fill that measure. Not a bug at all (and nothing to do with import), and those non-voice-1 rests can also get deleted.
So it remains to be checked where those multiple instrument changes stem from, what in the XML triggers this. And what in the PDF...
In reply to Thanks JM, I'll try it as as… by David Goodwin 2
To be clear: if you press a voice button with a note selected, that moves the selected note into the specified voice, which necessarily involves replacing the original with a rest, and also for your convenience in editing it pads the new voice with rests so you can finish entering whatever it was you planned to enter there that caused you to start off by moving a note to that voice . Not sure what your goal was in pressing the voice button, but MuseScore did what you told it. If you explain what you wanted to see happen instead, we can advise better ow to make it so.
Easily and quickly fixed (see above, plus I removed system breaks and some duplicate rit. and fixed the pickup measure to really be one)