10.5.1 crashes right away every time!

[HughBass123]

Hey everyone,

 

I just got the 10.5.1 update and it crashes right away every time I open logic. The funny thing is 10.5.1 was working fine just yesterday.

 

All plugins are legit and paid for, I'm running logic on a 2019 macbook pro with the latest version of catalina and logic doesn't even get past the opening logo before going into "not responding" every time I try to open it.

 

Does anyone else have this problem? Anyone know how I can fix it?

 

Cheers,

 

Hugh

[David Nahmani]

See if this helps? viewtopic.php?f=1&t=149548

[Stanleystove]

same problem and nothing has worked for me so far

[David Nahmani]

same problem and nothing has worked for me so far

You could at least troubleshoot your AU components to see which one(s) is(are) triggering the behavior?

[Ashermusic]

Assuming this happens with a new project so that we can rule out a corrupted project:

1. Make a folder on the desktop.

2. Go to Library>Audio> Plugins>Components and drag all of them to the desktop folder.

3. Open Logic

 

Does it still crash? If it does, you have a corrupted installation or OS corruption. If it doesn’t, then the plugins were the culprit and you have to be scientific, a add a couple at a time until you see which are causing the problem.

[Stanleystove]

Thanks I was able to start logic pro and now will go through the components to find the culprit..

[Stanleystove]

I added BFD3.Ivory.Spectrasonics stuff(omnisphere2,keyscape,trillian,waveshell9,macFive,plugsound ,motu effects .have not added native instrument stuff Tassman ,lounge lizard

Everything works as it should.

I thank you all for helping me help myself...

spoke too soon ..now BFD3 is not passing plugin manager testing

Edited July 10, 2020 by Stanleystove

[David Nahmani]

Great, good to hear — you're welcome!

[benjamin119119119]

Assuming this happens with a new project so that we can rule out a corrupted project:

1. Make a folder on the desktop.

2. Go to Library>Audio> Plugins>Components and drag all of them to the desktop folder.

3. Open Logic

 

Does it still crash? If it does, you have a corrupted installation or OS corruption. If it doesn’t, then the plugins were the culprit and you have to be scientific, a add a couple at a time until you see which are causing the problem.

 

Why is everything so complicated! I looked in Library>Audio>Plugins>Components and three of my Plugins are installed there.

 

Any way, to jump on the back of the first poster, also running 10.5.1 on Catalina 10.15.5 on a brand new Mac Pro, and it's completely unusable. Various sessions wont open at all. Crazy CPU spikes (with 192 GB ram and 16 cores on a MP 7.1). Audio drop outs. Errors with Kontakt 5. Kontakt 6 doesn't remember any settings. All in all, I would seriously beware before updating.

[David Nahmani]

MacOS is an account based OS so you have at least two accounts: the root account and your user account. This makes sense only when you start having multiple user accounts, where each user has access to their user data while every user can access the root data.

 

Root plug-in location is:

Mac HD/Library/Audio/Plug-Ins/Components/

 

User plug-in location is:

Mac HD/Users/Your-user-name/Library/Audio/Plug-Ins/Components/

 

To access the user library, hold down Option as you choose Go > Library in the top menu in the Finder.

[benjamin119119119]

Thanks, yep removing the Kontakt 5 component and my sessions open up just fine. It sucks because 90% of my plugins are Kontakt.

 

Weird thing is, some sessions open fine with Kontakt, and some sessions just constantly crash, or won't open at all.

 

Edit: A workaround for those struggling with Kontakt 5 specifically, but may also work for other plugins. Remove the Component as described previously, then load the problematic session, and create a blank region using the pencil tool at bar 1 on every track that uses the problematic plugin. Save as and close. Put the component back in place and open session.

[sempatika]

I have the exact same problem.Tracks I was opening and closing two days ago will not open at all today. Logic blames Waveshell, then AD2, then Izotope Tonal Balance Control.

Do I need a new computer with more storage or does Logic want us to stop using 3rd party plugins?

[David Nahmani]

Edit: A workaround for those struggling with Kontakt 5 specifically, but may also work for other plugins. Remove the Component as described previously, then load the problematic session, and create a blank region using the pencil tool at bar 1 on every track that uses the problematic plugin. Save as and close. Put the component back in place and open session.

Great to hear! Thanks for sharing. Let's hope it works for other Logic users as well?

 

Also I wonder if deselecting File > Project Settings > General > Only load plug-ins needed for project playback would achieve the same thing as the region creation workaround?

[benjamin119119119]

Edit: A workaround for those struggling with Kontakt 5 specifically, but may also work for other plugins. Remove the Component as described previously, then load the problematic session, and create a blank region using the pencil tool at bar 1 on every track that uses the problematic plugin. Save as and close. Put the component back in place and open session.

Great to hear! Thanks for sharing. Let's hope it works for other Logic users as well?

 

Also I wonder if deselecting File > Project Settings > General > Only load plug-ins needed for project playback would achieve the same thing as the region creation workaround?

 

That's a really good idea actually. Unfortunately, my workaround is now not working. Just loaded up my session that was working perfectly yesterday (with my fix) and it no longer opens. Crash report says Kontakt 5 is the culprit. I'm unable to get more than a few hours of work done a day, and spend around 8 hours trying to find ways to load sessions.

 

I've been a Logic user for around 11 years, but as of yesterday I've started watching videos on Ableton and considering whether I could make a switch, or if I should go back to Pro Tools - that's how bad this is. After spending so much money on the Mac Pro 7.1 I'm kinda beyond frustrated.

[rAC]

Have you thought about going back to 10.4.8?

[sempatika]

Native instruments knows there is an issue and they are working on a fix. Just look up Native instruments users forum for any updates on the issue. It is only a few of their plugins not Kontakt itself. I managed by opening Logic and unchecking all Native instruments I don't use and asking for a rescan of Kontakt ,Battery etc, and I have no problems now.

[benjamin119119119]

Have you thought about going back to 10.4.8?

 

I've never had 10.4.8 on this machine as it's brand new. As far as I could see from the App Store, 10.5 is the earliest I can get.

[benjamin119119119]

Native instruments knows there is an issue and they are working on a fix. Just look up Native instruments users forum for any updates on the issue. It is only a few of their plugins not Kontakt itself. I managed by opening Logic and unchecking all Native instruments I don't use and asking for a rescan of Kontakt ,Battery etc, and I have no problems now.

 

Thanks, I'll try re-scanning. FWIW it's not just Kontakt/NI that is causing crashes - of the last 72 crash logs (one week) I've sent to Logic:

 

36 Kontakt

13 Korg Triton

8 Waves Factory Cassette

8 Waves

4 Omnisphere

2 BBC Spitfire SO

1 UVI Workstation

[lorenzolamasse]

Same here alas, I used to have some crashes on 10.4.8, now I have regular forever spinning ball when opening some porjects, and some others just crash at load. I have rebooted, re-done full plugins validation, only workaround that works for a moment is to create an empty project and import the tracks of the crashed one.

Something really weird seems to screw up the projects themselves, as the same tracks with the same plugins work fine for a while on the imported tracks !

Not sure if I should switch to Ableton as it has his fair share of bugs and is way less versatile, but I'm pissed off beyond reason as, not being a full time musician I have only a few hours here and there to produce, and I lose them trying to sort out these bugs !

[kerochan]

Really sorry to hear of these problems, and I really hope things get sorted asap.

 

I am on Logic 10,3,2, with no crashes, spinning balls or problems with 3rd party plug ins, not trying to rub it in, just saying if you find a Logic version that is stable with your system, why not stick with it?

[lorenzolamasse]

The issue is that more and more of us are upgrading to Catalina, or changing their computer, leading them basically to have no choice here. I'm starting to think that Apple is trying to force us to use stock plugins by making it harder and harder for third parties to work without glitches, so as to lock us with Logic: this is by no way a good strategy, I'm almost using NO stock plugin but still using Logic because I like the workflow of it

[rAC]

Have you thought about going back to 10.4.8?

 

I've never had 10.4.8 on this machine as it's brand new. As far as I could see from the App Store, 10.5 is the earliest I can get.

 

Do you have access to a Mac still on High Sierra? Log in to your App Store there and download 10.4.8. Or a Mac with Logic 10.4.8 still on it? You can copy it to a USB stick and transfer it to your machine that way. Also noting how recent your purchase is have you tried Apple support?

[ralphonz]

Hi folks,

 

I am getting lot's of crashes loading various different projects with 10.5.1. The crashes, like the one described here are always the result of an AU unit. However, the same project can crash on different plugins from as many different plugin developers so I do believe this is a Logic issue.

 

So far I've had crashes from:

 

Sonarworks Reference 4

Waves (v12) API comp, LA-2A, and numerous others

Plugin Alliance Vertigo VSC-2,

Fractal Audio FAS-FX Reverb,

iZotope Neutron and Ozone

Slate Virtual mix rack

Ignite amps PTEq-X

And possibly more - memory fails me at this point. The point is it's happened with a huge array of plugins.

 

I'm running the latest versions of all of these plugins.

 

Sometimes the project loads after several attempts and "ignoring" the crash. Most of the time though, a re-install of the plugins fixes it; at least for one or two sessions but the issue soon comes back. Sometimes (as with Sonarworks Reference 4) reinstall won't work and the only way to load the project is remove the plugin from the system and restart the computer. Often when a project won't load, removing the plugin that crashes actually leads to the project crashing with a completely different plugin. I had one situation where PTEq-X was crashing the project, so I removed it, but then the same project crashed with Vertigo VSC-2, so I removed that and it crashed with iZotope. After reinstalling all the plugin alliance and iZotope AU's it worked again. The behaviour is not plugin-specific, but project specific - so currently one of my (very recent) projects won't load with sonarworks reference 4, but all other projects will (I tend to have this plugin loaded on every project.

 

I have of course tried deleting the AU cache. I've also reinstalled every single plugin and removed old superfluous ones. It's a constant battle to open projects - new and old. I also have super slow internet here (nothing can be done to speed it up that won't cost millions) so downloading plugins constantly to re install is very time-consuming.

 

Needless to say, I'm spending more time trying to get projects to load than I am working. At this rate I'm going to have to find a different DAW as livelihoods depend on it.

[des99]

There are existing threads on this issue but no real solutions that don't involve removing third-party plugins.

 

For the people having problems with it (it is only affected a small number of people if this forum is an indication), it might just be better in the short term to go back to 10.4.8 where this didn't happen, and wait for a fix in 10.5.2/whatever, if it is (as I suspect) a 10.5.x issue.

[ralphonz]

The work around of loading a blank project and adding the offending plugin, then loading your crashing project worked just now for me. Here's the original post: viewtopic.php?f=1&t=152787&p=801593#p801593

 

Looks like iLok is the culprit here.

 

Looks like this issue has been around for some time now, it's infuriating and is costing me loads. I'll write to apple AND iLok/PACE, it's just not good enough if you\re a professional and have paid £1000's for plugins. It's like the developers are making us, the end users, pay for their security with our time and inconvenience. Using iLok is not a nice user experience and never has been.

 

I understand developers want to protect their plugins from hackers but if it breaks things it's simply not worth it. I always hated iLok with a passion but alas, if you want the best-sounding plugins and lots of choice of components to work with you have to use the iLok cloud at least.

[ralphonz]

Sorry for the rant...

[des99]

Thanks - yes, it was me that had the issue and found it was related to iLok *in my case*. However, the OP in that thread had the problem with Dune3, which is not an Ilok-protected plugin.

 

As I suspect, it's a Logic plugin loading issue, rather than an iLok issue - otherwise, this behaviour would *only* happen with ILokked plugins. In my case, the iLok protection failed but I think it was because the plugin wasn't instantiated properly, not because it was an iLok problem.

 

As I say, from the reports I've seen, I think this is a more general Logic problem affecting some people (we just haven't found any hard reproducible cases or system commonalities yet.)

[ralphonz]

Thanks - yes, it was me that had the issue and found it was related to iLok *in my case*. However, the OP in that thread had the problem with Dune3, which is not an Ilok-protected plugin.

 

As I suspect, it's a Logic plugin loading issue, rather than an iLok issue - otherwise, this behaviour would *only* happen with ILokked plugins. In my case, the iLok protection failed but I think it was because the plugin wasn't instantiated properly, not because it was an iLok problem.

 

As I say, from the reports I've seen, I think this is a more general Logic problem affecting some people (we just haven't found any hard reproducible cases or system commonalities yet.)

 

I found this on the Fabfilter forum which explains it a bit further.

 

https://www.fabfilter.com/forum/6069/pro-q3-causes-weird-crash-in-logic-on-latest-systems?replies=6

 

This is the exact same crash report I see in logic every time, no matter the plugins involved. I can view them all in the console, they're all the same!

[des99]

In your case (and maybe also mine) it might be that bug - I was indeed aware that there was this Pace/iLok issue, but until my one instance o fthe crash I hadn't experienced anything - it was probably from that FF page iirc - I do remember seeing it before. Note the initial crash log in there was with 10.4.8, so this Pace issue has been around for a while.

 

My random crash log was different to that though - that log shows Logic crashing, but in my case, it was the *plugin* crashing taking Logic down.

 

The random crashing thing though as I say has affected more people and plugins that aren't using Pace though, and the random plugin crashing thing has only really been a thing here (on this forum) since 10.5. So ultimately I think it's likely there are two different things happening here, with a similar-looking outcome (crashing plugins that are seemingly random).

 

(It's also possible of course that in the eg Dune3 case, the user did indeed also have iLokked plugins that caused the issue, but they weren't reported. I would be interested to see that when people have random plugin crashes, whether they have *any* Pace/iLok plugins in the sessions that are crashing - ie if this is still happening for people that don't have Pace on anything at all.)

 

It is annoying for those affected, but the fact there's a workaround is going to be helpful in the meantime. I've only had it once so far and it's not come back - fingers crossed!

 

Note - you can write to Pace, but it's extremely unlikely they will do anything to help. They don't regard the end-user as their customer, their customers are the developers who buy in the protection system for their software. They have a long track record of general user-contempt, is my experience. If they *do* help, let us know what they say!

[ralphonz]

I don't know if you missed t in that thread but apparently you could see non-iLok plugins crashing as a result of it:

 

This is a known issue, which seems to be caused by the PACE framework, as used by iLok-protected plug-ins from companies such as SoundToys or Slate. These plug-ins seem to occasionally corrupt the memory space of other plug-ins like ours.

 

Sounds to me like the same issue? You could be right of course. Either way, fingers crossed someone release some sort of fix soon! At least we have the workaround