After starting Dorico, can you try doing Help > Create Diagnostic Report, and then attach the resulting zip file, which will be saved on your desktop, to a reply here in the forum?
I can see from some of those previous logs that it appears Dorico or the Audio engine may be crashing when loading the choir samples. I’m not aware of any known issues with these sounds. Do you have the problem if you load a different score with other instruments? One possibility could be that this is an issue with your specific CPU. Can you have a look in the %LOCALAPPDATA%\Crashdumps folder to see if there are any files for Dorico2 or VSTAudioEngine2? These may give us more information. See also the section on crashlogs in: Frequently asked questions: try this thread first - Dorico - Steinberg Forums
Had to do a Google drive because the file is too large for the forum but here are my only 2 bugs (one is my glorious attempt to launch a string quartet):
Could you please double check that there are no crash dumps for VSTAudioEngine2?
Also, could please try the following? Go to Edit > Preferences and scroll all the way down to the Play section. There is the option “open VST plug-in windows when opening projects”. If you untick that and then load a project, what does happen?
Also tried to uncheck “open VST plu-in windows when opening projects”, but project still freezing after opening a SATB template, same with 2-3 other templates
Thanks for the data. Now, that is a bit strange: The dumps from June look same to the problem that few other people have, i.e. HALion Sonic SE is crashing the audio engine when opening the HALion editor window. But from July you have only one dump file, and the callstack from the July dump looks completely different to the others.
As you just said yourself, you tried with several templates and each time Dorico was freezing, so I would expect dump files for each of those attempts.
Since the TaskManager in Win10 does not reliably show all running processes, I would like you to get the developer tool Process Explorer (free download at Process Explorer - Sysinternals | Microsoft Learn), then run Dorico to the point where it freezes, start Process Explorer and then with Ctrl + F, search for a process called VSTAudioEngine2.exe. Please be patient, it might take a few seconds. But that would prove if the audio engine is still running or not.
Many thanks again. Excellent job. So that clarifies things a bit. If the audio engine is still running and only Dorico going down, that means we have several issues here.
As I said, in regards to the audio engine dumps from June and the crash in HALion Sonic, we are already on that case, but it is difficult to solve.
The one audio engine dump from yesterday. Well, that does give not any clue of where it crashed. Could be an aftereffect of Dorico going down.
Dorico itself going down. At this the London team needs to have a look.
Long time since last post. My Dorico still doesn’t work.
Just updated to Dorico 2.1, projects are now launching but when I want to change an instrument still crash.
Tried on demo musics : I can change instruments on Coldplay but inevitable crashs occurs when I do the same with Rameau !
I have a similar problem after updating to Dorico 2.1 Pro from Dorico 2 Pro. When I open a project that I created in Dorico 2, it is automatically converted to Dorico 2.1. When I try to play it back, many problems occur with dynamics being incorrect, instruments not playing at all and crashes occurring when I open the VST Engine and try to change or reload an instrument, especially the clarinet combi. See the attached crash dump and screen shot.
If I create a new piece in Dorico 2.1, these problems do not occur.