FCPX And El Capitan

I use it now and then and just tested Hy Color pro, and no issue. But I had my first crash since update to EC and it was caused by Crumple Pop, Auto balance

thank you

So ... it's been not quite three weeks since El Capitan was released ... is FCP X officially up to speed for the new OS yet?

I see almost every other Apple app has been updated, I wonder why so long for Final Cut ... it's not as if they've been keeping OS X 10.11 hidden in a secret vault.

I'm in no hurry, I have a break between major projects coming up soon and if I can't make the switch then, I may have to wait until early 2016.

Hey Butch,

As always, no-one can tell when there will be another update for FCP X. The current version seems to work well with El Capitan, except for some cosmetic issues that could be resolved with a bug fix. If you are going to be between major projects soon, I would update the OS if you require any of the new features it offers.

- Ronny

But what about the AU validations? I'm holding out for the 10.11.1 update so I won't have to deal with that, but Apple are taking their sweet time to get that update out the door...

BTW. Apple actually deserves some credit. AVID and Premier doesn't appear to work in El Capitan yet. FCPX does work with the exception of the cosmetic issues on the timecode display. The validation issue is going to require some updates from the AU creators.

tpayton wrote: BTW. Apple actually deserves some credit. AVID and Premier doesn't appear to work in El Capitan yet. FCPX does work with the exception of the cosmetic issues on the timecode display. The validation issue is going to require some updates from the AU creators.

Yes, but AVID and Adobe don't build their own operating systems that accompany their editing apps! Not to mention building purpose-built hardware… Remember the late 2013 MacPro?!

Thinking that Apple's OS accompanies their editing app is giving too much credit to FCP X. Actually it's the other way around. With any major OS update the FCP X team has to adapt their software, just like anyone else. The same goes for all third-party software and hardware manufacturers. Many products have already been announced to fully support El capitan, others are still under qualification.

The 10.11.1 update will change nothing with regard to the AU validation problem of specific audio plugins. It's up to the manufacturers to make their plugins compatible, and not the other way around. Waves have already announced full compatibility, Native Instruments are still working on it.

I don't see any reason why anyone would absolutely need to be in a hurry to install El Capitan. Everyone knows that it's never a good idea to blindly install a new OS without having checked if the hardware and software you run is fully compatible with it or not. Some manufacturers are fast with qualifying their products for a new OS, others need more time. Here's an up-to-date list of different audio products and their current status with El Capitan:

www.sweetwater.com/sweetcare/articles/el...ibility-information/

- Ronny

ronny courtens wrote: The 10.11.1 update will change nothing with regard to the AU validation problem of specific audio plugins. It's up to the manufacturers to make their plugins compatible, and not the other way around.

But I've seen reports that the 10.11.1 update does fix AU validation.
Someone claimed that an earlier beta fixed it in Logic and the latest one fixed it in FCPX... What's up with that then?

For example:
ask.audio/articles/apple-fix-el-capitan-...in-os-x-10-11-1-beta

Hi Dimitri,

The article mentions the report of one user only, based on his specific system configuration and the specific software he has installed. And in his case it only relates to NI and to Arturia plugins. If plugins cause kernel panics (which is the case for NI plugins on EC) this can be resolved by a bug fix update of the OS. Waves have fixed the validation errors for their plugins themselves and they work perfectly with EC. So this information is very unreliable, and I would be very careful to base any conclusions on user reports. Your system and your software are different. The only reliable source of information is the official compatibility information published by every single vendor, which you should always check before updating.

As I said, there is no reason at all why anyone should be in a hurry to update to El Capitan. It's better to wait until every vendor has had the time to make their products compatible, and until the initial bug fixes for the OS have been released and thoroughly tested. As we all know from the past, bug fixes can also introduce new bugs.

- Ronny

But I have seen more reports of AU validation being fixed than that one.

But maybe you're right (you usually are)
Hmmm... What do you mean wait? I've never waited this long with an OS update before, I'm going mental here!

Plugins not passing validation is just a symptom of underlying compatibility problems in the plugins, it's not the cause of the problems.

I don't know why you should be in such a hurry updating the OS. It doesn't make any difference for video or audio work at this time anyway. Not until the audio and video applications you work with also have been updated to take advantage of any new underlying technologies in EC. Until that happens, updating to EC can cause much more trouble than benefits. I have EC on my test system, but I would never even think of updating our production workstations at this time. It usually takes 2 to 3 months before you really can trust any OS update, considering all the vendors that need to adapt their products to it. And even then you always should check with your third-party vendors to see if their products have been qualified for the update.

- Ronny

I've spoken with several audio plugin developers, and they all verify that there is an issue with Apple's AU unit verification process, it has changed, and it has bugs. There are fixes being worked on hard by both sides, Apple and developers are cooperating very well. It its a serious issue, thus will take time. This is much more than cosmetic. Even some of Apple's own audio unit plugins don't work at the present time.

There are anecdotal stories of BETA versions of 10.11.1 fixing the audio unit issue. But I'd not hold my breath until the developers on both sides release updates and publicly state it is fixed.

Like Ronny says, never be in a hurry to update/upgrade anything, ever. Wait until the bugs are worked out. Every update/upgrade ever released has had bugs. That's part of the IT beast we have to live with.

Have the Sony SxS card issue been fixed yet?
Have the Mac Pro slow downs in rendering and exporting been fixed?
Does iZotope work yet (vital to many editors workflows)?

That's more than cosmetic...

I have had no problem with my Mac Pro (late 20013) regarding to slower rendering and sharing, on the contrary it feels faster. I don not know what is "wrong" with my MacPro :dry:

Well, there's an update:

www.macrumors.com/2015/10/21/apple-relea...-10-11-1-el-capitan/

Resolves an issue that prevents certain Audio Unit plug-ins from functioning properly.

Hopefully resolves that FCPX timecode window thing.

Does not fix Timecode display or RX4 AU for me. Maybe it fixes Logic AU issues.

Will probably need app updates as well to fix the problems

bump...