These screen shots represent an instance of a track that simply will not reload under any circumstances after its original creation on 7.30.2023. In fact, I finally cancelled all instrument instantiations, and resaved a “blank” version. Even that one is problematic. I DID preserve the MIDI files and made another attempt to create the composition in an entirely NEW version using the original instrumentation. That one still had the same problem. I am not even sure of the count of crash reports sent to Steinberg at this point…all resulting from the same file. I made a copy of the coding errors and can send that to you as a PDF, but it is HUMONGOUS…392,789 words…
I should emphasize that this is the only file that I have created in Dorico that has behaved in this fashion.
An anomaly?
Your thoughts?

Screen Shot 2023-08-01 at 11.47.10 AM

You need to send your diagnostic report from the help menu directly here to this forum. The Dorico file as well if you can share it. The experts here will help you.

The report is too large, as you can readily see.

And both Dorico files as also too large…

Screen Shot 2023-08-01 at 1.17.54 PM

Maybe this might get to you…

And this: Dropbox - Kahlenberg.Dorico issue.8.1.2023.pdf - Simplify your life

Sorry that you’re running into problems, Charles. Can you please share the complete file via Dropbox as well so I can get a look at all the crash logs?

I sent this to one of your colleagues: Dropbox - Kahlenberg.Dorico issue.8.1.2023.pdf - Simplify your life

From Dorico’s Help menu, select “Create Diagnostic Report”, and upload the file from your Desktop here, or send it to a team member.

It has much more information than just the crash report.

Per your request: Dropbox - Dorico - Simplify your life

Frustratingly, it appears that the crash logs that were submitted to our crash log collector are not included in the diagnostics you’ve uploaded, Charles. I can’t easily find your specific crash logs in our system because they are scrupulously anonymised as we receive them!

Can I ask you to go looking in /Users/your-username/Library/Logs/DiagnosticReports for any and all files of type .ips whose names start with Dorico 5 and VSTAudioEngine5, then zip those up and attach them here or share the link via Dropbox?

I will proceed as requested. Thanks for your alert. (I have a Zoom meeting with some composer friends so it might be a while before I get the files…)

Per your request:

Dorico (8.72 KB)

Dorico (4.46 KB)

Dorico (5.95 KB)

Dorico (5.95 KB)

Many thanks for the crash logs, Charles. Three of them show a crash on exit that we are aware of (something to do with the shared video engine that Dorico and our other host applications all use), and one of them shows a crash trying to access some data in the audio engine, which had itself presumably either crashed or stalled. Did you find any .ips files with names beginning VSTAudioEngine5 in the DiagnosticReports folder?

I’ll look for those, too.

I found these which I put in a single folder and compressed.

Dorico Audio Engine (271 KB)

I do remember the issue with the video engine problem which occurred when I was scoring a film…

Thanks for the audio engine logs. Several of these are crashes in third-party plug-ins, which you should consider sending to their manufacturers’ support teams to ask for further help, or at the very least check to see whether there are any updated versions of these plug-ins that may run more stably on your system:

Kontakt 5:

Kontakt 7:


SINE Player:

UVI Workstation:


Thanks! I’ll look into that. And here is something that completely stunned me last night. I was about to empty my “trash” and found hundreds of Dorico files listed. I thought that perhaps I had decided to clean excess files in the past and so I “trashed” them. I then worked on a couple of new composition ideas and just out of curiosity, looked at the trash and there they were! I kept trash open, “saved” the files again and immediately new iterations appeared (see screen shot). I checked my Dorico preferences and made sure that I had not listed backup paths to “trash”. Nevertheless I got the same result……

What’s your theory on this one?

When Dorico cleans up backup projects (when you save, it rotates a fixed number of saves in the Backup Projects folder in your Dorico Projects folder) and auto-saves (when you exit Dorico cleanly, or tell it you want to discard any recovered auto-saved projects), it puts them in your Trash/Recycle Bin so that you have one more chance to recover them from there in an emergency.

As to Kontakt 5:

I have taken it off my machine.

No need for it since I have the newer version of Kontakt (with update - according to Native Access).