Sibelius First 2018.1 can crash Windows 10

Place your wishlist here. Maybe the Sibelius developers will honor your requests.
JohnDefoe
Posts: 18
Joined: Wed Mar 14, 2018 9:50 am
Sibelius Version: First 2018.1

Post by JohnDefoe » Mon Mar 19, 2018 7:57 am

If you attempt to import ill-formed XML and ignore the warning, not only does it crash Sibelius First, but it also crashes Windows 10. I found this when converting a Personal Composer file to .sib by exporting the .pc file to .nif, importing to Lime , exporting to XML, then editing the XML programmatically to remove the extraneous Attributes at the beginning of each system. The app now works, but I proved the bug on a couple of test runs.


bobp
Posts: 1182
Joined: Thu Dec 27, 2012 12:53 am

Post by bobp » Fri Mar 30, 2018 6:13 pm

Sibelius can be picky about what files import successfully. I think First is even more picky. I think that when you said, "ignore the warning", that was a red flag for me. I'm not surprised to hear that the procedure you used didn't work. Does PC export mid.? It may not be what want but at least it would get something into Sibelius.
Bob Porter
Sibelius 7.5, W10,i5,16 GB ram,desktop

JohnDefoe
Posts: 18
Joined: Wed Mar 14, 2018 9:50 am
Sibelius Version: First 2018.1

Post by JohnDefoe » Sat Mar 31, 2018 7:24 am

Hi Bob
What I was after and have now succeeded in doing was to get my .pc files of Christian songs including lyrics into Sib First. The XML that Lime exports is 1.0 (Sib exports 3.0) so editing it programmatically isn't too bad.The fact that Lime outputs all lyrics as line 1 regardless was one small element in the mix..
But what bothered me as a developer myself was that it was at all possible to ignore the warning and continue. Good programming practice would be to halt the import in its tracks at that point. Especially as it could go on to crash the operating system.
Cheers

John

Post Reply