Measure count is off in one part and unable to fix
The first violin part has an extra half beat in the selected measure and is short a half beat in the measure that follows. The other three parts of the quartet have the correct measure count, and the measure properties show that there are only four beats in the measure. I've tried deleting the note, adjusting the duration of the note, copying another note on top of the note that is in error - nothing corrects the problem.
| Attachment | Size |
|---|---|
| Measure count off 4-3-23.png | 138.15 KB |
Comments
We'd need the score itself, not pictures of it
I assume you probably also see a message about the score being corrupt when you try to save or open it? To fix corruptions, see https://musescore.org/en/node/54721. If you need further assistance please attach the score itself.
I guess i'ts also possible you enabled the experimental option to display notes across measure barlines in Format / Style / Score - if so, you can stop experimenting with that now :-)
In reply to I assume you probably also… by Marc Sabatella
I am not getting a corrupt file message at save or opening -- or any other time. I hadn't wanted to experiment, but sure enough, the "experimental" button was checked. I unchecked the box and saved, but the program freezes and crashes every five minutes or so, then box goes back to being checked. On a different note, I just installed MuseScore 4 on this (new) computer. This machine is pretty robust - 16 GB RAM, good graphics, etc.
In reply to I am not getting a corrupt… by emailly
Hmm, after the crash, MuseScore is probably trying to recover an autosave copy of the file and that's how the box keeps rechecking. So, first, I recommend closing the score after making that change, then reloading it. If you continue to have crashes, that's a separate issue of course, but let us know if you figure out precise steps to reproduce that problem.
In reply to Hmm, after the crash,… by Marc Sabatella
Reloading and saving helped with the recheck/uncheck issues and the associated crash that resulted, I've reset preferences to default and very carefully added back a few settings. It still freezes when I attempt to adjust the composer info.
In reply to Reloading and saving helped… by emailly
I've opened your scotre then double-click the composer field on the score and typed a little, and didn't encounter any problems. Same with subtitle, where you have placed the arranger info. Can you give more precise steps to reproduce the problem?
In reply to I've opened your scotre then… by Marc Sabatella
I open the score, click on "composer" to highlight the field, then click on "properties" to modify. I receive a notification on the top band of the app saying "not responding" and everything goes gray. It stays locked up until I close the program using Task Manager.
In reply to I open the score, click on … by emailly
I can't reproduce
In reply to I've opened your scotre then… by Marc Sabatella
I found the problem, and MuseScore may need to work on a fix.
It seems that every problem was included in an error log within the MuseScore App. Given the very many crashes that I experienced, the error log continued to grow until it (literally) filled up my hard drive. The lack of space on the hard drive caused the program to behave erratically -- like being unable to adjust the composer properties -- creating further error log files.
Out of a half terabyte storage environment, I had less than 5% space available. Everything except program files are stored to the Cloud, so the fill was 100% attributed to the applications/programs resident on the computer.
I don't know what is included in the error logs, but whatever it is, it is a huge storage drain on the system.
How can this be addressed?
(BTW - the tech support person removed the error log file from MuseScore and my machine went back to having 95% storage available.)
In reply to I found the problem, and… by emailly
That's indeed worth a bug report on GitHub, MuseScore should not fill the disk with logs
I assume you probably also see a message about the score being corrupt when you try to save or open it? To fix corruptions, see https://musescore.org/en/node/54721. If you need further assistance please attach the score itself.
I guess i'ts also possible you enabled the experimental option to display notes across measure barlines in Format / Style / Score - if so, you can stop experimenting with that now :-)