El Capitan 10.11 Compatibility information - Important.

Hi, Art. Thanks for texting El C for all of us.

Your time, effort and expertise are appreciated.

regards,

Scorpii

Opps.

That should read testing not texting

Unfortunately I have upgraded before reading this post. After upgrading I see Logic automatically attempts to reauthorize all of my AU plugins. Some did not authorize. Others that did cause crashes in Logic. 😟 That's a huge issue. I'm very surprised this was not thoroughly tested. All I have is a time machine backup.

Just out of curiosity, whose responsibility is it to make sure everything is compatible when an OS upgrade is released? Is it Apple's, to provide the necessary information to all third-party interests? Or is it the third-party's responsibility to stay up to speed? Didn't the beta drop a while back? Thanks.

Thank you... it's even more surprising to learn that these were known issues. If there are known incompatibles there should be some type of warning to the user as part of the initial system scan prior to upgrading. That should be a basic prerequisite. My NI plugins that no longer function are part of the system level libraries. It should be a simple check prior to install with an appropirate warning.

Regarding the question of responsibility... Apple provides both the OS and the DAW. In my opinion, Apple should be take responsibility to ensure that users can continue to use these products for the intended purpose after an upgrade of this nature.

Yes, Apple provide both the OS and the DAW. They don't however, provide NI plugs or have anything to do with NI coding.

For example, I don't have any NI plugs but I do have iZotope and Waves. Some Stephen Slate stuff… Would I expect Apple to test all of iZotope, Waves and Stephen Slate code before it issued an OS update? Of course not. I'd do exactly what Apple did and that is provide the code, in full, as Apple itself was developing it. They did this not only for the developers but, for the first time ever, the general public too. This way the developers can alter their code and issue updates to their users if any new Apple code affects their own.

If Apple had to check all the code for all the current *possible* plug designers from 3rd party developers there would never ever be an update issued because it would be impossible.

If Logic itself had a massive show stopping bug it would be different because Apple make, as you rightly say, both the OS and the DAW.

The basic point here is that it appears there were known incompatibilities yet there was apparently no information given to users. We are not expecting Apple to test all 3rd party plugins. However, if there are known issues with popular plugins such as NI we would expect to be notified before having our logic sessions broken. Thanks.

Svbullt wrote:

The basic point here is that it appears there were known incompatibilities yet there was apparently no information given to users. We are not expecting Apple to test all 3rd party plugins. However, if there are known issues with popular plugins such as NI we would expect to be notified before having our logic sessions broken. Thanks.

The past 4 or 5 major OS upgrades (starting with Lion) have either broken some plugin compatibility and/or broken some part Logic or caused past projects to perform poorly... from my observation this has been consistent. It usually takes a few incremental OSX/Logic fixes before operation efficiency returns.

Most everyone who relies on Logic do not upgrade as soon as something new is released, many of us are still using older OS/Logic combinations that are considerably more efficient than recent offerings at least on older (2 to 5 years) hardware. Graphics requirements for smooth operation have skyrocketed.

Point taken... Thank you. My bad to not have been more cautious about this update. Hopefully others will fair better.

I hope my time machine backup will save me.