Is Creative Cloud 2015 fully compatible with El Capitan (OS X 10.11)?

[WriterGuy]

Just wondering if the early adopters out there -- you know who you are -- are having any issues with the new version of Mac OS X and the latest builds of the Adobe appsbeta

There are a bunch of reports on the web of problems with early Beta versions of El Capitan, but nothing recently -- and certainly nothing I can find since the OS' release this morning.

I'm torn: I want to upgrade immediately. But I also know the rule about waiting for the 0.1 update before updating system software...

Some positive reports would go a long way to ease my fears....

[bsbeamer]

mgray1981 wrote:

An update that happened yesterday when I restarted my Mac - Creative Cloud is finally compatible!!!

can you elaborate on this?  the only recent update is a Creative Cloud App update - and that's causing crash reports to be generated for several (many) users on Macs at the moment...

[Scoop2622]

I call BS on this because I was using adobe this morning and still the same nonsense!

[markjones05]

Compatible in what sense? It has always been compatible to some degree. Have most of the bugs been fixed? Can anyone else confirm this?

[Scoop2622]

‌iit's still real buggy for me.

[Donavan Swin]

I was running Beta 5 of El Capitan 10.11.2 (15c48a) with no issue until I updated Premiere, After Effects and Speedgrade this morning. Now titles do not display correctly, simple dissolves do not work (the only one I got to work was Additive Dissolve) the Lumetri effect on some clips (not all) were changed and I had to go through and check every single clip and readjust to match. This take me back to my Avid editing days and the rule of never updating during a project. When I switched to Premiere it was nice never having an issue when updating but I guess those days are over for Premiere also. I know I'm running an OS that Adobe is not suggesting to update to yet but as of yesterday I can't think of one issue I was having running Premiere on El Capitan but now it's almost not useable. Another issue is if you double click a clip it shows in my second monitor but does not load into the Source Monitor, you have to double click a second time to get it to load into the Source Monitor. Now I have to figure out how to get back to a version of Premiere that works with El Capiton. I've have been wanting to try Resolve so maybe this is my chance.

[Kevin-Monahan]

Hi Jim Swins,

I was running Beta 5 of El Capitan 10.11.2 (15c48a) with no issue until I updated Premiere, After Effects and Speedgrade this morning. Now titles do not display correctly, simple dissolves do not work (the only one I got to work was Additive Dissolve) the Lumetri effect on some clips (not all) were changed and I had to go through and check every single clip and readjust to match.

Sorry for your issues.

I have a few questions.

• Did you test this on a brand new project or a project you updated?
• If it's an updated project, can you try a brand new one?
• If it's an updated project, have you tried creating a new project and importing the previous project into the new one?
• Have you filed any bugs on these issues yet? If not, here is the link.

For other customers, I would not recommend updating to a beta version of OS X with Premiere Pro CC 2015 (9.1) at this time. For those that already have updated to the beta version, please file bugs.

Thanks,

Kevin

[Donavan Swin]

Hi Kevin,

It was an updated project but I also tried a new project from scratch and it had all the same issues. I will fill out a bug report on them but any way to get pack to the previous version of Premiere?

Thanks,

Jim

[Kevin-Monahan]

Hi Jim,

It was an updated project but I also tried a new project from scratch and it had all the same issues.

Sorry to hear that. Feel free to contact support if you decide to update once more.

I will fill out a bug report on them but any way to get pack to the previous version of Premiere?

Thanks for filing a bug report. Here is a link to revert to an earlier version of Premiere Pro.
If you need a dot version, you can obtain them from the ProDesign Tools site mentioned in my blog post here: http://blogs.adobe.com/kevinmonahan/2014/01/29/revert-to-a-previous-version-of-premiere-pro-cc-or-an...

Thanks,
Kevin

[bsbeamer]

Kevin-Monahan wrote:

For other customers, I would not recommend updating to a beta version of OS X with Premiere Pro CC 2015 (9.1) at this time. For those that already have updated to the beta version, please file bugs.

Kevin -

Can you please clarify if Adobe will be "warning" customers NOT to update OSX when 10.11.2 is released, or how that will be handled moving forward?

What is the timeframe before the OS update would be recommended?

As stated previously, I have less than a 2-week window for updating to the latest OS due to IT security implementations.  I can dual-boot a desktop machine (MacPro5,1) but doing so with my laptop is not really possible for real-world usage.  Having some sort of "official" word from Adobe that I can point to, may allow me to buy another week or two of time...

[Kevin-Monahan]

Kevin-Monahan wrote:

For other customers, I would not recommend updating to a beta version of OS X with Premiere Pro CC 2015 (9.1) at this time. For those that already have updated to the beta version, please file bugs.

Kevin -

Can you please clarify if Adobe will be "warning" customers NOT to update OSX when 10.11.2 is released, or how that will be handled moving forward?

I don't believe that there will be anything specific, as nothing was announced prior to other point releases of OS X. My recommendation was a personal one, based on past experience with beta builds of OS X.

As stated previously, I have less than a 2-week window for updating to the latest OS due to IT security implementations.  I can dual-boot a desktop machine (MacPro5,1) but doing so with my laptop is not really possible for real-world usage.  Having some sort of "official" word from Adobe that I can point to, may allow me to buy another week or two of time...

I do sympathize with your situation. I've been there when I was responsible for installations at a major facility in my LA days. I'll do my best to make sure major OS compatibilities are announced as far in advance as possible in the future.

Thanks,
Kevin

[Ache Brown]

Yes, big problems. I have a brandnew top of the range macbookpro and have more problems than I ever had with CS6.

In Bridge it keeps selecting a different window when i have a number of windows open, that is if i press spacebar for full screen view and then again to get out of full screen view and then again, nothing happens. if i click on the window again then hit the space bar an image from another windo come in full screen view.

in Photoshop I get black squares no matter what I set the performance options to, never happened on my old MacBookPro  using CS6 and OS X 10.9

it makes it really hard to edit a bunch of photographs like 400 +

[thomasl13788744]

I updraded to 10.11.1 and after that I could not use Adobe CC 2015 at all. The computer frozed everytime a started up Indesign, illustrator or Photoshop.

Had to reinstall Yosemite to make it work again. El Capitan 10.11.0 did work fine - but not the latest version.

Do not upgrade!

[Scoop2622]

Since the patch that was released on Tuesday a lot of the prem. problems I had seemed to be fixed. there still are a few bugs, im having issues dragging and dropping items to the timeline or moving things around on the timeline, some transition effects don't latch properly.

[Kevin-Monahan]

Hi Scoop,

There still are a few bugs, im having issues dragging and dropping items to the timeline or moving things around on the timeline, some transition effects don't latch properly.

Sorry to hear that. We can try and troubleshoot those items in a new post, or you can work with support here.

If you have time, please let us know about those issues here.

Thank you!
Kevin

[OHenriques]

Photographer. Just migrated to new iMac with El Capitán 10.11.3. Old Mac had an issue with graphics card. Card discontinued, unavailable, after 5 years. 

First surprise: Adobe does not take migration. We're supposed to reinstall it all.

Second surprise: downloading Creative Cloud. Crash after crash. Impossible to install.

I've already paid for a monthly subscription but cannot use Photoshop, the intended product.

Tried the Cleaner tool, to no avail.

Fed up, frustrated with such issues, at this point. This was not supposed to happen, anymore.

Oh, and Adobe assistance only works from Monday to Friday. Crashes on weekends, forget it; wait till the next business day. But your payment is taken any time, immediately.

Good grief...

[NicoMcLane]

Again, good to note... I have not upgraded and sounds like a real nightmare... other than not being able to work... how is El Capitain? Are there improvements or is the whole thing a sham of  a sham?

[OHenriques]

I'm an Apple fan and really appreciate their way of doing things. Never had any problem with my Apple devices. However, with the updated El Capitan that came with the new Mac I cannot use Aperture [already discontinued] anymore, nor their own Photos new software, which does not open "because of a problem" [I don't use it normally, anyway]. That is, I already had El Capitan in the old Mac, and everything worked well, Photoshop included.

Updated to 10.11.3 this morning [I've had the new Mac since yesterday evening] to see if the bugs had gone away, and still no good news.

Cannot judge, but it begins to sound like I have a PC with a new Windows version.

Thanks to this I'm back to Photoshop Elements, which still works, and to Phocus.

Can't wait; looking forward to the next, improved and compatible OS X, El General...

[Paul Whitehead]

After reading this thread, I won't be upgrading to El Capitan for a long time..  I normally do a fresh cleaning on my hard drive every 6-8 months...  Currently I have Yosemite on my system, I'm gonna downgrade to Mavericks.  Even with Yosemite, its a ram hog and it slows down my maxed out 2014 iMac a lot.

[ColbyFulton]

Illustrator and Adobe Animate won't open, but photoshop seems to work. Can I switch back?

[developmentd12781439]

InDesign CC2015 has lost all progress bars on El Capitan but they are there in Yosemite. Dialogs don't always close when supposed to although they eventually do.

Also if any one is having difficulty building plugins with the 11.2 sdk one problem I have found the copyresources.sh mac script doesn't run because it has windows line endings. Why a Mac shell script has windows line endings is beyond me and also explains a lot when it comes to buggy Adobe products.

Can't really tell if the issue is fixed in 11.3 as there is no sdk released for this yet.

If your using InDesign CC2015 and you need it to work correctly I would stay clear of El Capitan even now months after release!

This subscription thing doesn't really work does it Adobe. You can't get your latest software running correctly on the latest OS.

You can't supply developers with SDKs for new versions in a timely fashion. So that peoples plugins will be upgradeable before you even release the latest Apps. Meaning the plugins no longer work when people upgrade.

Just poor all round.

[Jason Toemmes]

I have spent thousands on the latest mac equipment. This Adobe bug crap has been happening since Yosemite that didn't get resolved months after it was released last spring. I've been periodically checking in to see if they have fixed the problems with El Capitan and see they have not. I find this completely unecceptible when paying $50 a month for a subscription. I'm now seeking other design application alternatives. Any suggestions ?

[makeitmove]

I felt like this, instead just switched to PC after waiting for bug fixes, saved £1000's and equalled MacPro spec Adobe CC is running nicely in all programes.

Re-training wise maybe took me a week to get used to Windows.

Switching to PC is probably an easier and actually less drastic solution than having to re-train on other software suprisingly.

In my case the closest replacement to After Effects is Nuke which costs £1k a year, then I'd need to purchase FCP and some image editing, vector software too, I'd imagine it'd work out being around £2k a year, Adobe is £600 a year.... plus re-training on Nuke would take ages.

So the costs and time to re-train out-weighed switching to PC, sold my iMac to cover the PC costs, I've actually broken even, so no costs and have a much faster system.
Don't get me wrong, I am a massive Mac fan and have kept my Mac Book Pro for working on the go, just when needs must you know!

[noel888]

The move to PC still doesn't help when Adobe roll out updates before even releasing the SDK. Meaning anyone relying on plugins for anything could end up with plugins that don't work till

Adobe rolls out the SDK to developers and the developers rebuild the plugins. The simple act of releasing the SDK a couple of weeks before the update and notifying registered developers in

a timely fashion. Would be a good start to ironing things out a little. Followed by making sure the samples in the SDK actually compile on all systems it's supposed to.

Plus personally I feel that when the software is running properly using the Mac version is just better all round. But yes PC version does do exactly the same. Just not as nicely.

[makeitmove]

I've not had a plugin issue since switching 6 months ago, I use a ton of plugins, trapcode, duik, rubber hose, motion, gopro studio and all kinds of plugins for After Effects on PC, have updated the software a bunch of times and always stable.

Personal preference is fair enough. Personally I've not noticed any difference to my PC, still work on my Macbook Pro when on the go, maybe the finder is a little more intuitive, I use a Mac keyboard on PC with Mac shortcuts, so probably why.

As a work around I'm just saying switching to a PC and keeping Adobe is probably easier than investing in new software and training (which was the comment initially). Personally I would lose out on thousands if I were to re-train and put all my client projects on hold to do so, not to mention that a lot of my clients work with Adobe software, so I'd probably lose clients if I start sending them Nuke files instead of After Effects!

It will take a lot to shift people away from Adobe.

[noel888]

You misunderstand. I was talking about InDesign not After Effects. Adobe have rectified the issue over the last few iterations of Indesign and provided the SDK well in advance of going live. So all is now good.

Just one issue really. It's very difficult to process CC2021 InDesign Documents through a none existant InDesign Server 2021 and InDesign Server 2020 it no likey CC2021 documents!