Nested Tuplets Corrupt The Musescore File
Hello Musescore Community,
Musescore allows you to write nested tuplets however, after you save the score, close and then try to open the saved score, musescore shows a dialog box stating the file is corrupted with incomplete measures.
If musescore will allow me to write the rhythm, why is it removing the nested rhythm once the file is closed?
I am attaching an image of the written rhythm with in a measure and an image of the rhythm as it appears when the "corrupted file" is opened.
Is this a bug or a known issue? Is there a work around?
Thank you for your insight and help.
-Sean
| Attachment | Size |
|---|---|
| Musescore-file-corrupt.png | 106.85 KB |
| Nested Tuplet.png | 140.89 KB |
| Altered Rhythm.png | 55.81 KB |
Comments
I have tried to reproduce your problem with a small example and nested tuples, but in my case the score could be store and reopen just as it was previously stored in MuseScore 4.5.2 and Ubuntu 22.04 LTS without any problem. Maybe if you posted your score and explain which MuseScore version ans OS youz are using, some one can help you.
In reply to I have tried to reproduce… by puggbma
Same here Musescore in 3.7 . Score saved and reopens fine.
I tried it on Windows 11 with 4.5.2 and had no problems. You must have done something wrong...
First, select a half note and then press Ctrl+3. Next, select the first quarter note of the triplet and press Ctrl+5, then the second with Ctrl+6, and finally the third with Ctrl+7. Fill in the notes and correct the beams.
Thank you all for commenting and sharing your examples. Perhaps this is an issue with .musicxml files. This is an older score that I exported out of Finale. When I brought it in the nested tuplets displayed broken as I shared in the attachments. I deleted the offending measures, added new ones and rebuilt the melodic figures. All looked good until I saved the file and reopened it.
I hate the think I will have to re-engrave the entire score. But perhaps that is what I will have to do. Thank you again for your help. At least I know it is most likely the file and not Musescore.
Regards,
Sean