Laptop <-> Desktop Dorico crash

Dorico
1

I have Dorico 6 latest on both my windows desktop (Win 10)/laptop (Win 11).

I’ve recently discovered that when I open a project I’ve created on my desktop - on my laptop, next time I try to open it on my desktop it causes Dorico to crash. I can still open/access the project ok on my laptop but can no longer work on it on my desktop.

Has anyone experienced this and or have any clues as to what might be happening?

When I try to reopen Dorico on desktop, it tells me it crashed and I send the dump to Steinberg….perhaps there is a way to capture the dump and send it to Ulf or someone here?

2

Yes, after it crashes, restart Dorico and do Help > Create Diagnostic Report. That will create a zip file on your desktop, which you can upload here.

1 Like
3

Found latest crash dump - too big for here - diagnostics too large as well

4

Can you upload the diagnostics to Dropbox or something similar, and then post the link here?

1 Like
5
6

Thanks for all the data @kloewen .
I’ve entered your issue into our bug database and someone from the London team will have a deeper look into the crash file on Monday.

7

It looks like it might be a problem with file permissions on your desktop computer, @kloewen. Dorico is trying to extract the soundtrack from the video attached to the project, and it’s crashing at some point during that process. It’s only a guess, but I wonder whether you might find that if you can clear the temporary data Dorico uses, it might start working as expected.

Please try quitting Dorico, and then in Windows Explorer open the %TEMP% folder. You should see a Dorico 6 folder in there: delete this, and then restart Dorico and try opening the project again.

1 Like
8

Thank you both for your attention to my post! It amazes me how attentive you are to the thousands of users here! Thank you for the wonderful support you give your product!

I loaded up my original file just now to test your theory and before I did anything, it just loaded fine on my desktop. I have no idea what the original issue is/was/or is still lingering waiting to come up again. I will note your suggestion @dspreadbury in case it occurs again but for the time being…..this issue seems to be resolved

1 Like