Crash when closing projects

Dorico
21

You’ve got Kontakt and SINE Player VSTs. There is a known crash on quit with SINE Player, so you might want to remove that and see if that fixes it. At the very least, it looks like you’ve got version 0.1 of SINE, which you ought to update.

There is a newer ARIA Player, too, which gives you Multi-output VST3.

Padshop and Retrologue are not native to Dorico, I think. Again, try without.

You’ve also got a third-party microphone. See if there’s any difference without that.

You should update Monterey to 12.6.8, too.

2 Likes
22

Updated to OS Ventura, 13.5.2 → still crash
Uninstalled Kontakt and Sine → Still crash
I’ve searched for a more recent ARIA-player version but can’t find anything newer than my version (1.959)
I guess Padshop and Retrologue are from Cubase and nothing I’m using in D5.
No microphone connected to the computer.

Here is a new report after all these updates.
Dorico Diagnostics.zip (413.9 KB)

23

IIRC the new multi-output VST3 Aria player is only updated for the Mac. On Windows the multi-output Aria VST is still VST2.

(Would love to learn otherwise.)

1 Like
24

Is there a newer version than 1.959 for Mac?

25

According to the logs, you still have SINE Player installed. (And Kontakt).

2023-09-16 13:28:45 : Register VST3 Plugin ---------- (8):
2023-09-16 13:28:45 : Name   : SINE Player
2023-09-16 13:28:45 : Vendor : Orchestral Tools
2023-09-16 13:28:45 : Categ. : Instrument
2023-09-16 13:28:45 : Vers.  : 0.1.0
2023-09-16 13:28:45 : SDK    : VST 3.7.4

2023-09-16 13:28:45 : Register VST3 Plugin ---------- (5):
2023-09-16 13:28:45 : Name   : Kontakt
2023-09-16 13:28:45 : Vendor : Native Instruments
2023-09-16 13:28:45 : Categ. : Instrument
2023-09-16 13:28:45 : Vers.  : 6.7.0

Noteperformer is also 4.0. Latest version is 4.1.

You also have three Microphones drivers installed.

2023-09-16 13:28:40 : Categ. : ASIO Driver
2023-09-16 13:28:40 : Name   : EpocCam Microphone
2023-09-16 13:28:40 : Vendor : Kinoni Oy
2023-09-16 13:28:40 : SubCat.: 
2023-09-16 13:28:40 : Vers.  : 5.0.0.16
2023-09-16 13:28:40 : SDK    : ASIO SDK 3.0
2023-09-16 13:28:40 : Component ---------- (13):
2023-09-16 13:28:40 : Categ. : ASIO Driver
2023-09-16 13:28:40 : Name   : Extented Audio Recording Driver
2023-09-16 13:28:40 : Vendor : Apeaksoft
2023-09-16 13:28:40 : Component ---------- (14):
2023-09-16 13:28:40 : Categ. : ASIO Driver
2023-09-16 13:28:40 : Name   : ZoomAudioDevice
2023-09-16 13:28:40 : Vendor : zoom.us
2023-09-16 13:28:40 : SubCat.: 
2023-09-16 13:28:40 : Vers.  : 5.0.0.16

I’ve no idea whether microphone ASIO drivers can affect Dorico, but … until you’ve tested, you won’t know.

Latest ARIA for Mac is here:

Even if you’re not actively using them, they are still loading into the program. Everything that’s not ‘factory’ is suspect until ruled out!

1 Like
26

I didn’t know that! I’m struggling with those kinds of crashes with Relab Development’s LX480 and with Superior Drummer 3. Maybe there’s a pattern? Moddart’s tech told me they “solved” the problem with a workaround in JUCE. Does SINE use JUCE? If it does, it could be useful to send them the workaround…

27

One thing important to mention here, Mats’ diagnostics report contains only one crash file and that is a crash in Dorico itself, not the audio engine. So all the speculations about VST plug-ins here go in the wrong direction, since they have no impact on Dorico. So @dspreadbury needs to take a look at the Dorico crash file.

@MatsHall , it looks like you have NP 4.0 installed. You might want to update to 4.1.

1 Like
28

So, now I’ve updated NotePerformer, hopefully removed the last remnants of Sine, Kontakt and some unused audio drivers and updated Aria to 2.026.

Dorico still crashes. I attach a report here. (And
as I mentioned earlier, this is not a huge problem, since the crashes only appears when exiting or closing projects…)
Dorico Diagnostics.zip (394.9 KB)

29

Just to add that I also encounter very frequent freezes and crashes, (Dorico 5 in Monterey), at least 10 times a day. I’m attaching a diagnostic in case someone can have a look.
Also to mention that in large scores few functions like copy paste take at least 7-8 seconds to complete (even copying a couple of bars).
Thank you.
Dorico Diagnostics.zip (920.0 KB)

30

Thanks for the data @GagarinMoore , but there are no crash files contained. There is only one diagnosis file for the audio engine and nothing more.
Could you please create another diagnostics as soon as you have another freeze? Thanks

31

The Microphone drivers are still there! :grinning:

1 Like
32

Gaaah, I thought I deleted all prefs. I’ll se if I can find the rest just to clear out unused stuff, even though @Ulf mentioned earlier that this hasn’t anything to do with the crashes.

33

@Ulf
This is during a freeze, don’t know if on any use. Of course I’m not bashing the software, fully abandoned Finale and also crashes give time for stretching,

Dorico Diagnostics.zip (1.1 MB)

34

Hi @GagarinMoore ,
actually, in the new diagnostics is one crash file, but that one is from Dorico, no audio-engine crash or wait.
When you try freezing the VSTAudioEngine again, can you make a spindump via the Activity Monitor.? You know how to do that?
We need to see what the dorico engine is doing while in the frozen state. Thanks

35

ok, it seems easy just googled the spindump, you never have a proper crash when you want it!

36

I’ve already looked at Mats’s crashes, as I said much earlier in the thread in this earlier reply:

37

Hi, here are few spindump files.
One of Dorico during a “not responding” state:
Spindump_D_not responding.zip (362.0 KB)
VST engine at the same time:
Spindump_vst.zip (280.7 KB)
VST engine when Dorico was properly working but with no sound coming out:
Spindump_audio engine.zip (313.8 KB)

38

It looks to me as if the audio engine has crashed or hung, and so when Dorico is attempting to save or auto-save your project, it’s waiting for the audio engine to send it the data about the current state of the loaded VST plug-ins, but it receives no response, and hence it hangs. Hopefully Ulf will be able to determine what’s going on in the engine.

39

First thing tomorrow morning I will have a look. A little patience please, thank you.

40

Hi @GagarinMoore , I’ve sent you a private message via this forum. Please check.