Logic Pro 10.5 crashing plug-ins

It was in a different thread, but Logic did not upgrade any GUI requirements or OpenGL requirements. What changed is that Logic now is build against macOS 10.15 (Catalina) to use some of the new features and that – as a side effect – all Audio Units have to be compatible with macOS 10.15 as well, instead of just being compatible with macOS 10.13 (as was the requirement with Logic Pro 10.4). So, this change showed a bunch of incompatibilities with Audio Units towards macOS 10.14 and macOS 10.15. The same would happen if any other DAW switches to a recent version of the developer tools, Logic was just the first one.

That also means: if you have an Audio Unit, which does not work correctly, you need to contact the developer for an update.

I just had to bite the bullet and pay to update my waves plugins to v11. Once I did that, erased all remnants of waves from au, vst, preference and audio support folders and reinstalled clean, I was able to resolve.

best of luck. It was an extremely frustrating experience and I was not impressed by waves support team. Best of luck to you!

Update:

The repair function in Waves Central has fixed the issues for me.

Mac mini 2018, Mojave 10.14.6

As previously mentioned, the crashes have to do with a new GUI requirement- most developers have provided updated fixes and others not yet, while some are unaffected. With regard to Waves, I was on V9 when I updated logic to 10.5 & had the corruption (blank black plugin windows), then updated Waves to V11 and they all work perfectly. Native Instruments on the other hand has a list of plugs with problems that they’re still working on.

R

For anyone who's looking for a (hopefully) temporary fix that doesn't require reverting to a backup, you could go to your display preferences, and check "open plugins in controls view" under the "mixer" tab. This at least makes it feasible to open and adjust plugins that are already in use. It's what I've been doing to keep old Waves plug-ins from crashing Logic. It doesn't necessarily making loading a new instance of those plugins very appealing (controls view is not sexy), but it does make opening sessions that already have instances of those plugins much easier to work with.

Update:

Izotope has release an update for this - You can download the fixes for Insight 2, Doubler and Vocal Synth 2.

https://support.izotope.com/hc/en-us/articles/360047676354-iZotope-products-in-Logic-10-5

Hope this helps!

wrightbrainedmusic.com

UPDATE: I've updated my CLA Mixdown app to v11 and that seems to have done the trick.

I had the same problem with my V9 of Waves after updating to Logic 10.5... the plugins all loaded, but the GUIs were just black windows. Upgrading to V11 fixed them all.

Yes, I just tweeted them and they tweeted me back. They said that Logic Pro updated their OpenGL requirements and sent me the link you just posted. They are working on an updated release.

Thanks,

Andrew

Apple simply does not and also can not guarantee compatibility of 3rd party code and specifically Audio Units with their hardware or software. How should they? You even mentioned "niche boutique firms" – there are probably 10000 Audio Units in existence, that is impossible to test for anyone.

If an Audio Unit is no longer working, your first contact should be the manufacturer of that Audio Unit. Many of these now crashing Audio Units are actually crashing, because of bugs in them, which only showed up because Logic was updated. They did not get broken by Logic; they always were, but now it shows – sometimes dramatically. The Logic application can't fix these bugs. Of course it is the easiest to blame Apple for all that, so let's do that.

Professionals update one machine only and test their specific setup before committing to new versions of hardware or software on all their machines. Often they are keeping old machines around for specific use cases. I remember used Atari ST computers being bought via eBay to have backup machines for a certain setup from the early 1990s.

BTW: Always have backups, so you can go back if something fails.

I've just tried Waves GTR and Isotope Neutron 2 on 10.5 and all seems fine here (so far) - What Wave versions?

Are they showing as validated in plug in manager OK?

Try opening a completely blank project (no templates) and trying to add them there - any difference?

Nobody from Apple saying anything?

1. Logic is now unusable. To be able to open some projects with plugins that crash I have to open a new project, open the plugin in there and open the saved project with the crashing plugin... Every time, for all the plugins. It is happening so far with Denise Perfect Room, Amplitube and some others. It takes 10 minutes before I can open a project...
2. Plugins from niche boutique firms that can not keep up with the requirements are being excluded... but I paid my good money for them. The system is not even willing to open them. It gives you no option. Included, many free components as the Mercuriall pedals for example and many others.

I have not seen anything like that ever. I am really angry with Apple. I chose you for the ease of making music not to be stranded with an arrogant thinking attitude that all the world should follow you. Not even Native Instruments or Izotope have been able to follow you. Incredible.

I am wondering what professional studios are doing.... It must be crazy. If I were in this position I would sue Apple.

Having the same issue as everyone else here. Certain WAVES plugins cause sessions to crash. Currently the SSL Channel Strip Plugin and the Scheps OminChannel. I can open the GUI but once I try to close it, the sessions crashes. This is AFTER I spent $250 to upgrade all my WAVES plugins to V11; what their service/support said were fully compatible to Catalina. It's beyond frustrating that I can't mix anything at the moment.

My only workaround is to HIDE the AU's and then unhide them when I want to work with one. Absolutely unacceptable and really souring me on this latest update.