I know you can change a project to the Silence playback template. But that’s not what I need.
I have project that uses the Cantai template. I want to change it to something else as Cantai is too unstable on my system to use. Whenever I go to change the playback template, Dorico crashes. I can change the routing assignments but am unable to delete more than one of the 4 cantai instances from the midi & vst tab before Dorico crashes.
This leaves me with a project I can open without activating the audio (program settings option) but I will forever from this day forward be forced to use the Cantai playback template with it.
If there was a way to open a document without loading the playback template, all would be fine.
I have done this with success to detach from Cantai:
- Go to PLAY mode
- Go to the MIDI/VST tab and change every instance of Cantai to an instance of the desired VST
- Using the Properties tab of each voice assigned to Cantai, validate that each voice is assigned to the desired VST.
- Save your file.
- Assign the desired Playback Template.
- Save your file.
Then, you should be able to change playback templates after detaching Cantai from your voices (instruments) in PLAY mode without crashing. This worked without a hitch.
Oh, and you can change your Preferences to automatically load in the Silence playback template which should avoid new auto assignments to Cantai but it wouldn’t necessarily change an existing file.
I appreciate the suggested way to detach from Cantai but it didn’t work. Dorico kept crashing on me at various points. In the 3rd step did you mean to say that each voice is NOT assigned to the desired VST?
No…sorry. make sure each voice is assigned to the desired VST.
I was able to go through the steps, with the voice assigned to the desired VST. However, after saving the file and trying to change the playback template, Dorico froze. I see in the task manager that cantai.exe is running (even though there was no instance of cantai assigned in the midi & vst panel). Sometimes, but not always when closing the project (before trying to assign a new playback template) Dorico didn’t close correctly and had to be killed in the task manager. It appears, for me at least, if I assign the Cantai playback template I’m going to have issues.
HI @JAMES_GILBERT , could you please post a diagnostic report (Help > Create Diagnostic Report) which will hopefully contain crash dumps, so we can have a look as to why it is crashing.
And if you’d send me your project (to u dot stoermer at steinberg dot de) I think I can apply a little magic and that it then works with the Silence template afterwards.
You could, at worst, import the Flow(s) into a new document. You’d lose any layout-specific work, of course; but you’d get the notation.
Magic would be the ability to choose a playback template before the project opens - a small arrow on the hub that opens a drop-down, defaulting to the last playback template used. 
That’s big magic, I’m not powerful enough for that 
The diagnostics was about 93Mb! I put it on dropbox and sent you an email with the link as well as the original dorico project.
As I mentioned in a previous post I was able to re-assign the vst after following the instructions @kasky1 listed. I always work with a backup project when trying out a new vst so my original was fine. I’ve not had time to look at it today to see if I could figure anything else that might help.
Hi @JAMES_GILBERT ,
thanks very much for the data. The file is so big, because there are lots of crash dumps of the Dorico audio engine contained, and it’s always Cantai that is crashing. So when the audio engine crashes also Dorico freezes because it waits for answers from the audio engine that never arrive and consequently everything is deadlocked.
Now, since it is always Cantai that is crashing, it would be best if you contact the Cantai developers as only they can say something or fix it.
Have a look in the diagnostic that you sent me, and from the Crashes folder take the 4 most recent Dorico 6 AudioEngine crash files and send them to the Cantai developers. They can load them in a debugger and say more about it, resp. fix it.
Thanks. I suspected it was Cantai, but since Dorico was freezing I figured it was worth bringing up here.
No worries, you can bring up anything here, since you don’t know exactly what or who drives whom into crashes or trouble. We’ll take a look and then tell you, that’s the normal course of things here.
Thanks. As a followup, Daniel Spreadbury in another thread mentioned that I had to have remote control turned on in order to see the icon at the bottom telling me when Cantai was done rendering. Once I enabled that all my problems, so far, seem to be solved. It looks like remote control needs to be on for Cantai to work properly.
Thanks very much, this seems to be important information to all Cantai users.
And I suggest that you still forward the crash dumps to the Cantai guys in order that they can make an ever better product out of Cantai.
Cheers
Crash dumps forwarded. For anyone else wanting to submit crash reports, their chat on their support page will give you details on how to. (I don’t want to post the email address here).