Deleted coda still shows up in parts, and other export errors
I deleted a 2 bar coda, and it is gone from the main score, but when I export parts, the erroneous two bars still show up at the end of the bass, saxophone, and piano part, along with a spurious end-repeat barline in the measure before.
In the MAIN part, however, not only are those two bars gone (correctly), but the bar before it is missing as well (m. 29) (incorrectly)
The file is attached, along with the parts generated.
| Attachment | Size |
|---|---|
| cape-verde-03-parts.mscz | 63.8 KB |
| cape-verde-04-parts-Acoustic_Bass.pdf | 59.32 KB |
| cape-verde-04-parts-Alto_Saxophone.pdf | 56.1 KB |
| cape-verde-04-parts-Piano.pdf | 71.38 KB |
| cape-verde-04-parts.pdf | 86.9 KB |
Comments
I opened your file, exported all the parts, and couldn’t reproduce the problem.
In reply to I opened your file, exported… by mercuree
Hm. The application tells me I am on the latest version, so I'm wondering what else could be causing this?
I've tried it multiple times with the same result.
Is there some cache somewhere I could clear? It feels like something is stuck in its memory that isn't going away.
In reply to Hm. The application tells me… by mlzarathustra
Usually, closing and reopening the file helps. You can also try closing and reopening MuseScore. There’s no file cache — everything is stored in memory.
If you close MuseScore, restart it, open the file again, and the export still gives the same result, that would be very strange.
Actually, I can imagine your situation being possible. When exporting, MuseScore temporarily generates the parts, and desynchronization with the parts is a fairly common issue in MuseScore. But if we can’t reproduce the problem consistently, we’ll have nothing to report to the developers, and they won’t fix it.
In reply to Usually, closing and… by mercuree
I did close and restart MuseScore, with the same result.
So yes, very strange, if it truly is removing all of its state from memory when you shut it down. That's why I was thinking something might have gotten stuck in the DDE system. But honestly I have no idea.
In reply to I opened your file, exported… by mercuree
I rebooted, and the problem went away.
When I was restarting, it complained about a DDE thread that didn't want to quit. I would easily believe that a DDE glitch was responsible, but who knows, I guess?
I was hoping that the days of needing to reboot to reset applications were in the past, but apparently not!
Thanks for looking at it.
-=m=-