Bad format
I can't load a score recorded a few minutes before, mscore 2.0 tells "bad format" but I can load all the generated parts.
| Attachment | Size |
|---|---|
| Capture du 2014-12-07 11:30:38.png | 16.83 KB |
| sophisticated_lady_parts.mscz | 242.08 KB |
I can't load a score recorded a few minutes before, mscore 2.0 tells "bad format" but I can load all the generated parts.
| Attachment | Size |
|---|---|
| Capture du 2014-12-07 11:30:38.png | 16.83 KB |
| sophisticated_lady_parts.mscz | 242.08 KB |
Comments
And this is the output:
Debug: htmlToString: read token: Invalid (...\MuseScore\libmscore\xml.cpp:650, void Ms::XmlReader::htmlToString(int, QString*))
Debug: htmlToString: read token: Invalid (...\MuseScore\libmscore\xml.cpp:681, QString Ms::XmlReader::readXml())
Debug: C:/Users/joschmitz/Desktop/sophisticated_lady_parts.mscx: xml read error at line 269 col 166: font (...\MuseScore\libmscore\scorefile.cpp:1160, bool Ms::Score::read(Ms::XmlReader&))
It apparently stumbles over the flat symbols in the instrument names
Attached an attempt to fix it, by deleting all the instrument names that contain accidentalFlat
I don't suppose anyone can come up with steps to reproduce this?
It's ok with your file,
Thanks
Let's not close it yet. It would still be good to understand how it happened in the first place.
I don't know what happened but I guess I made an syntax error in the xml text. Have a look to the picture.
(By the way, I'll send some suggestion about this process, because each staff properties have to be modified after each exportation.)
It's normal to see markup in text imported from 1.3 or that has had certain types of manual formatting applied. What I'm wondering is what steps might have led to MuseScore saving a file it could not open. Are you saying you typed that markup yourself, though? If so, then I guess that could be the problem, although still, we should probably handle that case better.
Yes, importing things from 1.3 is necessary : Otherwise, I can't set up a staff with an Aldo Flute or a Fluglehorn. It's important too to keep control of the parts file name, I modify them according to my rules :
- I replace all the blanks by underscores
- I use English names for the instrument (to avoid accents on letters)
- the number of the part follows behind a -
Ex : Alto_Flute-1 , Trumpet-2
What do you mean you can't set up a score with alto flute or flugelhorn? Both instruments are present in 2.0, maybe not in the "Common" subset, but in ORchestral or All categories they are there.