MuseScore freezes
Yesterday I updated to MuseScore version (64-bit): 3.0.4.5763, revision: cda4080. My OS: Windows 7 SP 1 (6.1), Arch.: x86_64. Today MuseScore keeps freezing. Where do I start to fix this, please?
I'm type-setting over 500 hymns and can't afford to keep repeating edits because MS has frozen again.
Comments
Try: https://musescore.org/en/handbook/3/revert-factory-settings
Meanwhile, in order for us to understand and assist better, please attach a score that is giving you a problem, and if possible, give us steps to reproduce the problem.
In reply to Meanwhile, in order for us… by Marc Sabatella
The first step was to load a Music XML file. The language in the example is from S.E. Asia. Then apply a customised Style to ensure that hymn number, lyricist, sub-heading, and composer reproduce the sizes and layout of the original printed score. Next it was a matter of inserting notes in voice 2 (typically where the original has unison notes). At every stage it was possible to Save the file. But after a while, MS would hang necessitating a forced shut down. Restoring the session made no difference. Starting again with the file XML file and deleting the content of poorly formatted bars made no difference.
The XML file is the focus of my suspicions but I cannot see where the problem lies. Attached are:
-The raw XML file
-The PDF I'm replicating
- the mscz files in visible and hidden forms
- the Style file
You should not need the Kayan Unicode font.
In reply to The first step was to load a… by Chiff
Problem not solved, but circumvented. First by removing text to concentrate on the music. Second by copying & pasting bars wherever possible. There is still a distinct problem around the change of time signature. Splitting or joining bars to reproduce the score caused the time signature to jump a bar earlier. Gave up and left it where it is with the triplet that starts the refrain placed on the last beat of the 3/4 bar.
In reply to Problem not solved, but… by Chiff
I think the corruption in the file here is getting in the way, I'd start by fixing that. Otherwise, hangs and crashes are to be expected, I'm afraid.
In reply to I think the corruption in… by Marc Sabatella
Agreed, but trouble-shooting XML files is beyond me. This is the first failure amongst the MusicXML files output by my music OCR software, an error rate so far of around 0.5%.
In reply to Agreed, but trouble-shooting… by Chiff
See https://musescore.org/en/node/54721
In reply to See https://musescore.org/en… by Jojo-Schmitz
Thank you. The problem here was that MS did not flag the file as corrupt. Clearly it was. Later, working through the files for this project, I did get a "corrupt file" warning so I've now met this feature. Thanks again.
In reply to Agreed, but trouble-shooting… by Chiff
To fix your corruption, insert a measure before the last measure. Copy the few measures with notes in them to the new measure, then select the last measure, which is the corrupt one, and press ctrl+del to get rid of it. Your corruption will be fixed and there is no need to wade through xml.
In reply to To fix your corruption,… by mike320
Your remedy is roughly what I did. It took several dead-end attempts before I figured where the corruption might be , and how to skirt round it. Thanks.