[steve fletcher]

Great. Thank you!

[steve fletcher]

Cool. Thank you!

[steve fletcher]

Those two are basically the same project, just different pre-crash attempts. Here is a different one. Same thing. Won’t open after crashing.

If that helps.

Thank you.

1

Thanked by: Olof Hermansson

[steve fletcher]

Yes – I was using shakers and tambourines on most of these, if I recall correctly.

I’m attaching 2 projects that crashed and I am now unable to open in SD3.

Thank you for the efforts here. I appreciate it greatly.

[steve fletcher]

Oh – someone said maybe the Logic files, too. Attached those, fwiw.

[steve fletcher]

Great. Thank you for the tip on how to do that!

Zipped and attached.

[steve fletcher]

Also, while I’m thinking of it, one of the recurring causes of a crash is as follows:

1. Try to copy a part from one song block to “selected” song block. Say, snare only on top of a different kick part.
2. Maybe I accidentally had the whole track selected or not, I’m not sure, but it will paste a blank block over all preceding song blocks.
3. When I go to ‘edit-undo…’ and hit ‘undo’ the whole project and SD3 crashes. Just shuts down. And, in some cases, it has not allowed me to re-open that project.
4. This has happened to me more than once.
5. I’ve only been running Sd3 for a week.

Sorry to go on and on, but I just thought the circumstances of the crash might be significant.

Thank you.

[steve fletcher]

OK – So I’ve gone through the steps outlined above. Re-installing and clearing the AU cache, rescanning plugins, etc.

However, now SD3 crashes even in standalone mode. It’s also unpredictable.I have a few projects where it works even within Logic, no issues. I have other projects where it just crashes and I can’t open the project I’ve started. I really don’t get it. I’m on a brand-new Mac with sufficient horespower for most anything.

Is this a Catalina thing? A 3.2 thing? Am I doing something wrong?

It’s the same “Superior Drummer quit unexpectedly” error message, whether in standalone mode or as a plugin in Logic.

Operating system: macOS Catalina (10.15)

[steve fletcher]

So, I managed to open and run SD3 in standalone mode. While it was working, I decided to take advantage of the opportunity to program drums for one of the songs that I had lost with the Logic/SD3 crashes. I got the parts where I wanted, and then exported the individual tracks as audio, and loaded them into Logic.

The upshot of this is: of course, the drums sound great (SD3 is amazing, coming from years of EZD [which I love] it is a huge leap forward in sound and especially the programming interface). Programming in SD3 is great. Also, having the drum tracks in Logic as audio decreases the CPU hit by a huge margin.

Personally, I could work like this. I am used to workarounds and problem solving. However, theoretically, I “should” be able to run SD3 as a plug-in within Logic without issues, though, right? The fact that it is crashing means I still have to find a fix somewhere. Having to work in standalone then bounce is not normal, is it?

Thank you!

[steve fletcher]

Does SD3 open as expected in standalone?

It does. Is this an indicator of anything? Should I be starting my drum programming in standalone mode, then importing it to Logic when I’m ready? Or, just using SD3 as an insert plugin on a midi channel in Logic? I have been doing the latter.

Did you try to open the Plug-In manager in Logic to Reset & Rescan?

Yes, I just did this again.

Have you Custom saved a Default Project?

No, should I? Should I have a default project setup as a starting point in general?

Have you tried re-installing the plug-in?

No, I am trying to avoid this, if possible. I will do so if things keep going as they are. I’ve never had to do that with any software. Maybe I’ve been lucky heretofore.

Thank you for the input!

Operating system: macOS Catalina (10.15)

[Author]

Replies