No products in the cart.
Hi, when I try to load superior drummer 3, as the title says, Logic stops responding. It’s in a project that I’ve already had for awhile. I tried loading a new project and superior drummer 3 opens just fine. I tried reverting the project to an old version when I know SD3 was working and it still caused Logic to stop responding. I also tried importing it to a new project and the same thing happened. Is there any way for me to access it to export the midi and load a new instance of SD3 or any other way for me to fix this?
Have you tried opening your project in the standalone application and doing your exports there?
| redgearmusic.com | instagram | YouTube | Roland Kit |
Hi,
have you tried ‘Reset & Rescan’ of your plug-ins in the Plug-In Manager and/or clearing the AU cache?
BR,
John
John Rammelt - Toontrack
Technical Advisor
Jonathan: That SD3 works okay in a new Logic project points to it not being strictly an SD3 problem. It may be a plugin other than SD3 that’s causing Logic to crash. And it doesn’t necessarily have to be a plugin in the project but one that resides on your machine. The problem is to find the plugin causing the crash. I seem to remember that recently (March) there’s been issues with Sonoma causing crashes.
Jack
aka musicman691 on other forums
Superior Drummer 3.4.0
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
What do you mean by “stop responding”? Try loading a copy of your project with CoreAudio disabled and remove all of the other plug-ins and see if loads with Superior Drummer then.
jord
Good idea. But unfortunately all the midi I did in SD3’s grid editor is saved as part of the logic file and not in it’s own file so there’s no way to open it in the standalone.
So the way I have logic set up, if it doesn’t see a channel being used, it doesn’t load it till I click on it. Since I do all the midi programming on SD3’s grid editor instead of Logics piano roll, Logic thinks that the channel isn’t being used since it doesn’t see the midi. So the Logic project opens just fine but when I click on SD3 to load the Virtual Instrument, the loading icon appears and never goes away. If I right click on the Logic icon, it says the application is not responding.
So good news is I left it on that loading icon all night and when I came to check it this morning, SD3 had finally popped up and allowed me to export the midi. I’m still not sure what the root cause was. Maybe there was a little glitch in the initial loading procedure in my logic project and letting it just load for a while finally worked it out.
I will definitely keep your ideas in mind if I run into this issue again. Thanks for the suggestions!
Good idea. But unfortunately all the midi I did in SD3’s grid editor is saved as part of the logic file and not in it’s own file so there’s no way to open it in the standalone.
Ahhh, didn’t think of that. My work flow is to always save a .sd3p file when done with my Logic projects in case something like this happens. I’m even export the tempo map out of Logic and into SD3…
I’ve learned my lessons over the years.
| redgearmusic.com | instagram | YouTube | Roland Kit |
So the way I have logic set up, if it doesn’t see a channel being used, it doesn’t load it till I click on it. Since I do all the midi programming on SD3’s grid editor instead of Logics piano roll, Logic thinks that the channel isn’t being used since it doesn’t see the midi. So the Logic project opens just fine but when I click on SD3 to load the Virtual Instrument, the loading icon appears and never goes away. If I right click on the Logic icon, it says the application is not responding.
Put an empty MIDI region in Logic’s instrument track. This will load Superior Drummer. Or, you can disable the feature in the preferences.
And yes, it is always good to save an SD3p.
jord
No products in the cart.