El Capitan 10.11 Compatibility information - Important.

Thank you to everyone that has replied. I guess I should be prepared for this kind of drama when I have to upgrade an operating system, but I always end up irritated.

According to WAVES:

Why does my Waves Update Plan cost more than $300?

Once you confirm that you use all selected products on one computer at a time, all your non-overlapping Waves products (e.g. Platinum & SSL or Gold & Restoration, etc.) are capped at $300 per account per year.

If you choose to extend your Waves Update Plan for multiple products, the Waves Update Plan for all selected products will be extended by one year from the coverage end date of the product with the latest coverage end date.

This may cause other selected products to be extended by more than one year. Since the coverage costs $300 per year, Waves Update Plan fees will be higher than $300.

This may be easier to understand using an example. Let’s assume that today is March 1st, 2013.

Say you own two products: Diamond (current Waves Update Plan end date: September 2013), and SSL 4000 Collection (current Waves Update Plan end date: March 2013).

When extending Waves Update Plan for both of them, the new end date for both would be September 2014, which is a year from the product with the latest end date (Diamond, in this case.)

While Diamond coverage is extended by exactly one year, SSL coverage is extended by 1.5 years (from March 2013 to September 2014.)

In this case, we add the cost of 6 months of Waves Update Plan coverage for SSL 4000 Collection to the $300 cap.

So, the actual answer is that WAVES (unlike any other software developers out there at this time) wants $300 (or more) a year for you to play with their toys. I guess because their plug-ins will automatically get you a hit song or something that will create a lot of money for you to justify throwing them this gift every year.

For obvious reasons, I prefer to pay for my plug-ins on a one time per lifetime basis. Unless, of course, the developer comes along and greatly improves the plug-in. Then, I don't mind paying the developer a reasonable fee to upgrade to the new and improved version of the older plug-in. But a yearly fee is ridiculous for plug-ins.

Fortunately, most plug-in developers are very reasonable and don't try to hold their clients captive by introducing a licensing procedure that locks them out using plug-ins that they've already paid for. WAVES are not cheap to begin with. It hardly seems fair to require taxation year after year.

Native Instruments is not compatible with updates and a reset procedure. iZotope still officially claims they aren't.

http://www.finalcutprox.guru/support/supportblog/

Hello BenB:

Most, if not all my Native Instruments are now working, but I had to reinstall my Yosemite OS and re-update to OS 10.11.1.

iZotope 2, and Stutter Edit are working, however, the original iZotope is not showing up. Maybe that's by design.

As mentioned in another post concerning the Apple OS updates. El Capitan OS 11 (or any Apple OS update) is essentially a BETA, until they get to 11.2 or 11.3. I do understand that releasing a new OS, will cover all the software produced by Apple, but may not be compatible with 3rd Party Developers until the OS is tweaked or the Developers tweak their software.

Just an FYI for any WAVES users, I've learned that you can only update plug-ins, during the paid update period. Currently, $300 covers 1 year of updates. My update period was over and by updating my OS and installing the new WAVES Control Center, all my V9.3 plug-ins were erased by the app, when I purchased a few V9.6 plug-ins and installed them. There was no way to get my 200 + plug-ins operating again, except to pay the fee of $300, which then allowed the WAVES control to put them back on my OS. So, essentially I lost my licenses, once I tried to use the (new) WAVES Control Center. I believe this was by design from the WAVES people that wanted to get the older WAVES users to PAY UP!!!

It's a friendly World we live in today!!

Through many emails with WAVES, they have agreed to reimburse me for the $300 update fee for the V9.3 plug-ins that were lost during the upgrade using their new WAVES Control installer and license authorization app. It always seemed to me that this (new & improved) app should see the V9.3 plug-ins and update them to V9.6 rather than remove them completely from your system, which is what the controller did. I do appreciate the fact that WAVES did finally step up and resolve the situation.

Hi, Muzicman.

Glad to read your Waves problems have been sorted.

regards,

Scorpii

Hi, Art.

I just checked the Native Instruments site, and found the following in the support section.

OS X 10.11 (El Capitan) Compatibility News

This article provides the latest information regarding the compatibility of Native Instruments products with OS X 10.11 (El Capitan).

Currently two major compatibility issues concerning KOMPLETE, MASCHINE and TRAKTOR products have been identified. Should you have updated to OS X 10.11 (El Capitan), please proceed as explained below in order to resolve the corresponding issue.

Validation of AU (Audio Units) Plug-ins Fails in Logic Pro X

Please download and install the OS X 10.11.1 update by clicking on the Apple symbol in your Desktop and choosing Software Updates... This update fixes an issue whereby Native Instruments Audio Units plug-ins will not pass the AU validation and therefore will not be available in Logic Pro X.Note: If your AU plug-ins do not appear in Logic Pro X after updating to OS X 10.11.1, please rescan your plug-in folders by going to Logic Pro > Preferences >Plug-in Manager in Logic's toolbar. In the Plug-in Manager window, select all entries for which the validation has failed (as shown in the Compatibility column) and then press Reset & Rescan Selection.

Kernel Panic when Using Legacy Native Instruments Devices

Incompatibility between some older NI devices and OS X 10.11 has been discovered. This issue triggers kernel panics that crash the connected computer immediately, resulting in loss of any unsaved work, or serious disruption of a performance.The following hardware is affected:

There are drivers already available that fix this issue. You can download the driver version 2.8.0 for your corresponding device here.

Art, if I read this correctly, the latest El C update fixes the NI plugin problem and they should all be compatible.

However, you may already have this info on your list. If so, please disregard this message which will self destruct in five seconds.

regards,

Scorpii

This article has been last updated on 2015/11/03.

Hello All,

I stupidly updated my iMac which is running Logic pro 8 without first checking if this was doable, yes I know ******* move. I was actually doing this as my phone was not synking properly. No I did not make a back up, yes I need my head read. Question is, If I update to the latest version of Logic Pro will my previous track run ok? Or is there a way of reversing what I did without a back up?

Regards,

Peter

Hi, Groovjam.

I've opened projects created in LP 8 & 9 in LP X.

You will get a message saying the file format is not compatible, so LP X will create a new version.

IMPORTANT> rename the project. ie. LP X {track name]

That way the original is preserved, and a new exact copy compatible with LP X is created for you to work on. (and you know which one is which!

You can call or rename in any way you like, but for me that was the easiest.

As for reversing. I think EL Cap has a way to revert to your old OS. Check apple support by phone or web.

regards,

Scorpii

Brilliant!! you saved the day!

Thank you,

Peter

Glad I could help.

Enjoy making music.

regards,

Scorpii

I might be late to the Party with this but here's the update from iZotope's Bolg

Compatibility Chart

Below is the full list of products that iZotope supports for El Capitan. Find your product(s) to determine next steps.

Tip: If you are uncertain of your current product’s version number, follow these instructions.