![]() ![]() 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. I assumed it was just a bug that had been fixed with version 4.0.1, so installed the new version but kept having the same problem. 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. It would show the startup thing and then crash in a few seconds, whether i started the program from the dock, launchpad, apps list in finder, opening a saved score, whatever. I then updated to Musescore 4.1 and am still experiencing these issues despite the update claiming to have fixed these issues. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |