Version 4.4.2: periodic inability to save the score

• Sep 30, 2024 - 17:39

I'm building a brand new score from scratch. After a while, the autosave function just chokes, and ceases letting me manually save the score. I did a save-as with a name change; that worked, allowing me a .mscz with all work saved (for what that's worth). There's little use to continue, until someone can hopefully determine the cause from the diagnostics zip I'm including. :-?

Attachment Size
dgreen_diagnostics_cannotsavescoreprob.zip 1.02 MB

Comments

• Sep 30, 2024 - 18:52

Can you explain what you mean in more detail? Autosave doesn't normally have anything to do with regular saves - even if autosave is disabled, regular saves still work normally. So what exactly are you referring to here - an issue with autosave, or an issue with regular saves? And what specifically goes wrong?

Reply

• Sep 30, 2024 - 19:07

"Comment by Marc Sabatella:

Can you explain what you mean in more detail? Autosave doesn't normally have anything to do with regular saves - even if autosave is disabled, regular saves still work normally. So what exactly are you referring to here - an issue with autosave, or an issue with regular saves? And what specifically goes wrong?"
~~~
Autosave is generating multiple files, for one thing; separate autosave files, by virtue of unique names to each. Is this normal? To my knowledge, it never used to be, with this, or any other program I've ever used (e.g., Framemaker, Word, Sibelius). The autosaving is very obvious when it occurs, by everything freezing. and taking a bit longer to free up each time.
I've from experience have the habit of also manually saving periodically, so it's transparent to me whether or not there's any interplay for good or bad, between these two types of saving the work as I go.
What goes terribly wrong is simply this: after sporadic autosaves that apparently take a little longer to complete each, or the same with each manual save operation, I'm DENIED THE ABILITY TO SAVE THE FILE, period.

Reply

• Sep 30, 2024 - 20:53

I'm quitting for today; I've had it. You want me to do this, that and the other; apparently the diagnostic functionality of the program isn't sufficient to the task...? I'm sorry; even this page changes, denying me the ease of sending inline pics. It would be great on this end if we had an email conversation, rather than all this extra work, to comply with all the stipulations. I'm frustrated, and really damned pissed now; that's why I need to take a break. At this point, perhaps altogether permanently from this program. After a bicycle ride, perhaps my sense of civility will return. Sorry 'bout that, Chief.

Reply

• Sep 30, 2024 - 21:22

Hmm, sorry to hear you're getting frustrated. For the record, I've been quite consistent about stating what we fellow users here would need to help you - the details about exactly what is happening. The diagnostic file is mostly useful if there is a crash, although if someone is able to confirm and reproduce a bug here, it's also conceivable one of the developers might be able to find clues to the cause in the diagnostic files.

The information I am asking for isn't some sort of arbitrary "stipulation" we are imposing on your; it's just the sort of information that anyone would need to diagnose what is happening.

Not sure what sort of problem you are having with uploading pictures, but if for whatever reason you are finding that difficult, that's OK, just be as complete/accurate as possible in telling us the precise filenames and modified times of the autosave files and the full and exact text of the error message you receive. Also don't forget we also want to know about your OS and the status of the folder you are trying to save to.

Anyhow, as free software, Muse Group can't afford to provide free email support, so that's why these forums exist - to allow we dedicated users to help each other out. but the information I've been asking you for is the exact same information I'd be asking for if I were to charge you $100 to send it to me via email :-). It's not one iota of extra work on your part to post here rather than attach to email; iut's just way way way way way easier for those us of volunteering our time to help if a) we can do it collectively (no one person saddled with all the requests for help) and b) we can do it publicly (so anyone else who has the same issue going on with their computers can be helped but whatever we discover).

Anyhow, we volunteers here stand by ready to assist when you resume being ready to accept our help!

Reply

• Sep 30, 2024 - 20:02

You mean there are multiple autosave files all for the same copy of the actual score (e.g., all in the same folder with same basename)? How are the file differentiated?

Anyhow, whatever is going on with your systems - a permissions problem in the folder, perhaps, or faulty sectors on the physical drive, or maybe a backup program leaving locks in place - is presumably the same thing causing problems for both autosave and regular save. But again, I'm confused - what exactly goes wrong when you try to save? What does "DENIED THE ABILITY TO SAVE THE FILE" mean? Some sort of error dialog? What does it say?

Reply

• Sep 30, 2024 - 20:17

Marc, as I said in my reply to you, in the first sentence: "...by virtue of unique names to each.". Yes, they're all there in the same place, same folder, same directory. Each autosave file has the same base name, however, they're differentiated by unique augmentation to the base name. By "DENIED THE ABILITY TO SAVE THE FILE" I simply mean that I am denied the ability to have the score file I'm working on saved any further, and that happened each time I was attempting to save it manually. Is this clear enough? A simple dialog (monolog, really) informs me then, that "Sorry, but Musescore is unable to save the file".
Is the diagnostic zip file enough...? Initially I surmised that this zip file would contain everything needed to discern a clue as to what could be causing this anomalous behavior to occur. IS THERE ANYTHING MORE THAT I CAN SEND YOU?

Reply

• Sep 30, 2024 - 20:23

Yes, I saw that you mentioned unique names, but again, I'm asking what specifically the names are. A screenshot of the folder listing could be useful, showing names and modified times. And similarly, the full and complete exact text of the error message you receive would be useful, and again, possibly a screenshot. Be sure to also say what OS you are on, and whether there are any backup or cloud sync utilities (eg, OneDrive, Time Machine) running in that folder.

Last thing you could do is stop shouting :-)

Reply

• Oct 1, 2024 - 14:02

Marc, et. al. - after thinking that a recent download of TotalAV (to eventually replace Kaspersky when the subscription expires, as this company apparently has tangled with the law somehow, and can no longer conduct their business domestically)....where was I...oh yes, I wondered whether this recent test of TotalAV might have mucked with the registry somehow...? Well, guess what; intuition wins big this time. My issue with struggling to save my score has been relieved; the problem is no more.
There was also a deeply nested PUB found with the Malwarebytes' trial app, but the issue after finding that was still there; a complete uninstall of TotalAV very apparently has laid this issue to rest.

Again, sorry for all the shouting yesterday; the bicycle ride was the best solution for that. B-)

Reply

• Oct 1, 2024 - 11:24

Probably similar report https://musescore.org/nl/node/360598
ZipFileWriter fails to save autosave files in some cases.
Unfortunately, ZipFileWriter does not tell us in its log message what exactly happened, although if you go up the call stack, you can see that such information is there.
zipwriterlog20240110.png
The problem is rare, I found only one mention on the forum (though Google does not index the contents of zip files)

Reply

Do you still have an unanswered question? Please log in first to post your question.