![]() This was one of the first projects I was genuinely proud of and now all of that progress is lost. Though I am certainly not an expert on notation technology, I have noticed the measures where I utilize the copy and paste function (quite frequently used for the sake of increasing my productivity and workflow) are the measures that have the issues which is what I am assuming caused the files to be corrupted. When I open the now corrupted files, tens of hundreds of the measures I had wrote now have incorrect number of beats in them (i.e, 3 quarter notes and 5 eighth note rests in a 4/4 measure) and several engraving and consequently playback issues. I then updated to Musescore 4.1 and am still experiencing these issues despite the update claiming to have fixed these issues. ![]() ![]() So do try uninstalling and reinstalling those. But anyhow, it does seem the issue relates to Muse Sounds specifically, like maybe that installation is corrupted on your machine. I had been using Musescore 4.0 and had experienced IMMENSE and frequent corrupted file reports and just lost 4 weeks (6 minutes) worth of music that entirely relied on Musescore due to these seemingly random file corruptions. OK, so its one of those runs - where you first start MsueScore normally, then open a score - where it would be good to see the log from.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |