Dorico often stops responding when I try to load Synthogy Ivory II Grand Pianos. Here is a crash log resulting from creating a new project with a template in which Ivory is the only instrument. On other occasions Dorico does not crash, but Ivory won’t load: it appears to be loaded in the VST and MIDI tab, but in the Track Inspector tab it is greyed out. Should I just use a different piano?!
Dorico Diagnostics.zip (2.2 MB)
The diagnostics you’ve uploaded don’t contain any crash files. Is it possible that Dorico is merely hanging, and not crashing? If so, please reproduce the hang again, then use Activity Monitor to take a spindump, zip it up, and attach it here:
Daniel, thanks, and I’m sorry to be so clueless. I couldn’t find anything in the manual about diagnostic reports, crash logs and so on. I’m not certain now but Dorico probably did hang yesterday (I’m assuming that “hang” = “freeze” and “crash” = “quit altogether”?), though it has sometimes been crashing too. I suspect that Ivory was probably involved on each occasion.
It seems that Dorico is happy when I first open it and create a project which uses Ivory. But if I close that project, and (a couple of minutes later) create another such project, I get the behaviour shown in my screenshots. I can’t open the VST window; I can input notes, but playback does not work. If I then try to close the project, Dorico hangs (i.e. I get the spinning beachball). On the most recent occasion I created a spindump, which is attached.
Incidentally, Ivory is my only sample library that uses iLok, and I am currently using a physical, 1st-generation iLok for it. I don’t know whether that’s relevant.
Spindump.txt.zip (277.0 KB)
In the spindump, there’s no evidence of the VST audio engine process, which makes me think that it’s crashing, but in such a way that no crash dump is left behind (pretty unusual, but not unheard-of). It does seem likely to me that Ivory is somehow bringing it down. If the audio engine crashes, Dorico will eventually hang, because it’s expecting to be able to talk to the audio engine, and it’ll sit there waiting forever for an answer that won’t come.
My instinct is that Ivory is somehow causing the engine to crash. Do you definitely have the most up-to-date version of Ivory installed?
There was indeed an update to Ivory that I had missed, and first signs are that installing it has solved the problem. Ivory now loads properly even if I create and close a project several times in succession. Assuming that the problem doesn’t recur, I’m sorry to have wasted your time with this.