For the past three times trying to close two different projects, I have pressed Command-Save, then pressed the red Close button, and the whirling ball just whirls and I have to force quit Dorico. I’m on a Mac, OS Sonoma 14.6.1 using Dorico 5.1.60.2187. When I then double-click to open the errant project again, the Auto-Save message comes up, and two copies of the same file open; they look exactly the same. When I tried to upload the diagnostic report, the message said the file was too big; there are only 68 bars. Just now I opened the file again, and when I clicked the Close button without clicking Save, it closed just fine.
So, it is now working fine? Or it is random and just happened to work fine this time?
If it is random, upload the project and we can test it.
Thanks for your swift reply. When I opened the project, did no work, and clicked Close, it closed. When I made a copy of the project—which I am attaching—opened it and did no work except resizing the whole window, then clicked Command-S to save it, then clicked the red Close button, the whirling ball appeared and I had to force quit Dorico. Here is the file.
(attachments)
Scalabration copy.dorico (3.86 MB)
Thanks for uploading the project.
I’m on a Mac too but I can’t reproduce this. I tried closing using File > Close Project, the red X, making a copy and doing the same thing…
Sorry.
If you can reproduce this consistently with the previous project:
- Upload the precise steps to follow in detail
- Also upload a Diagnostics Report as soon as you reopen Dorico (Help > Create Diagnostics Report). This will be for the Dorico team to check out at their convenience.
Thanks for checking it, Daniel. Here’s the latest. However, there may be no reason to read it because the whirling ball/hangup behavior didn’t happen. I’ll certainly write if I the whirling ball appears again. Thanks for your testing and response. — Nancy
I clicked Recover Selected Projects. When the percentage reached 92%, the ball briefly whirled, then the two projects opened as Flow 1 in Scalabration—2 and Flow 1 in Scalabration copy 2, one on top of the other. I moved …copy 2 to my auxiliary monitor. In copy 2, in Write, I switched to the Full score from Ukulele I. It closed without incident.
I clicked on Flow 1 in Scalabration—2 on the MacBookPro, and switched to the Full Score layout. I clicked Save. The title that appeared in the Save window was Scalabration for Count In.dorico, not Flow 1 in Scalabration—2; the name on the about-to-be-closed-project changed to Flow 1 in Scalabration for Count In. I typed the comment I just typed, then clicked on the file on the Mac, and the name changed back to Flow 1 in Scalabration. I typed, then clicked the Close button, and got this message:
I clicked Save. The project closed as Scalabration copy without incident. Sigh of relief.
Aargh! Another file misbehaved. I opened “25th of the 12th” and duplicated a player, added tablature staves to the new player’s notation, copied and pasted from the original player, adjusted a few staves in the new part in Engrave mode, then went to Print (on the left side of the Print window), made PDFs, and pressed Command-S to save what I’d wrought. Came the message that I’d modified the file on disk, did I want to (I forget what), but I clicked Yes). The file looked the same. I may have pressed Command-S again, then pressed the red close button…and there’s the whirling hangup ball. This is a different file from the one that hung up two days ago.
When I opened Dorico again:
(Attachment Dorico Diagnostics.zip is missing)
Hi @Nancy_Piver , when the spinning beach ball appears when saving a project that very often means that the audio engine has died or is in a funny state. Therefore I’d like to see a diagnostic report from your computer.
It appears as if you already wanted to attach one, but it did not succeed somehow. If it is too big for uploading here, instead please send it directly to u dot stoermer at steinberg dot de. Thanks
Hi Nancy, thanks very much for the data that you’ve sent via private message.
Now, the audio engine always keeps the logs of the current one plus 10 runs of the past. About half of these logs suddenly break off with out the audio engine being properly shut down, so it appears as if it crashed or maybe killed by you. Unfortunately there is no crash dump contained in the data either. So I wonder what it going on there.
Could you please keep the Activity Monitor.app open while you work and then when the spinning beach ball happens, look for the VST Audio Engine process and see how it behaves. Is it shown as “not responding”?
Sorry, but we need to approach your problem step by step, so there is no instant answer there, yet. Thanks for your patience.
Hello, Ulf —
Dorico has been behaving nicely since November, until today; attached is the Diagnostics report. The “Roller Derby Queen" was imported from a .xml file; I’m wondering if that might have something to do with the problem. Today I mostly entered lyrics and chord symbols and chord diagrams; the last thing before trying to close the file I tried to untangle the mess with the Coda and Outro, clicked Save, then clicked the red Close button. I didn’t have the Activity Monitor app open because the files I’ve worked on lately have closed correctly. Thanks for looking at this sporadic mystery.
(Attachment Dorico Diagnostics.zip is missing)
Hi @Nancy_Piver , in your last reply the new diagnostic report is missing. Please upload again or if it becomes too big, send it directly to u dot stoermer at steinberg dot de. Thanks
Hello, Ulf —
Dorico has been behaving nicely since November, until today; attached is the Diagnostics report after the spinning ball of death and re-opening the file. The “Roller Derby Queen" was imported into an often-used template from a .xml file created in PlayScore 2; I’m wondering if that might have something to do with the problem. Today I mostly entered lyrics and chord symbols and chord diagrams; the last thing before trying to close the file I tried to untangle the mess with the Coda and Outro. I didn’t use playback. I just clicked Save, then clicked the red Close button. I didn’t have the Activity Monitor app open because the files I’ve worked on lately have closed correctly. Thanks for looking at this sporadic mystery.
File was too big to send in an email. Here is a link to the Diagnostics file in Box.
https://app.box.com/s/6fex979gkn3qrmraqx4i13to5a141bgl
Thank you,
Nancy Piver