Skip to main content

OS X 10.11 El Capitan

Comments

131 comments

  • tatuvaaj
    I've been running CO 8 through several developer betas and the only *major* problem has been OpenCL - it hasn't worked in any beta and still doesn't work with the GM release.

    The problem seems to be in Apple display driver code so it probably must be fixed by Apple (or Nvidia) but remains broken even in 10.11.1 Beta
    0
  • ncbp
    [quote="georgebrooksphoto" wrote:
    With the release of El Capitan tomorrow, I was wondering if Phase has offered any official word on whether or not Capture One will be fully supported off the bat?


    I guess this is as official as it gets:
    viewtopic.php?f=55&t=20763&start=15#p97968

    Regards
    N.C.
    0
  • alessandro cecconi
    [quote="tatuvaaj" wrote:
    I
    The problem seems to be in Apple display driver code so it probably must be fixed by Apple (or Nvidia) but remains broken even in 10.11.1 Beta


    It's always apple problem isn't it?..... 😄
    0
  • NN635770922769309595UL
    CO8 works fine with 10.10.5 but not with 10.11 GM. Your options are stick with what you have until the PhaseOne update is with us - or give 10.10 a try (it's quite good and would be an intro to what to expect from 10.11). And of course some folks would recommend not updating until the .1 release of the OS.
    0
  • Stefan Segers
    Tried it today but with official el capitan it's not working ☹️
    0
  • Maraker
    My C1 works nice with official El Capitan. My machine not contain nvidia card.
    0
  • Marc Pecquet
    Phase One just posted a note on Facebook recommending not to update until Capture One comes out with a new release.
    Like many other Aperture lovers I am new to C1 and am still using Aperture for my file management... Anyone out there tried Aperture with El Capitan ? Does it still work ?
    0
  • James Kachan
    I don't see why the developers at Phase have been sleeping on supporting OS X 10.11 — It's unacceptable.
    Professional software should be supported within the beta period so that bugs can be filed by beta testers, worked out with revision builds and a stable release can be offered by the time a major OS launches publicly.

    When an OS goes live publicly, there is zero excuse for expensive and professional software to not support the most current OS.
    0
  • SFA
    [quote="jameskachan" wrote:
    I don't see why the developers at Phase have been sleeping on supporting OS X 10.11 — It's unacceptable.
    Professional software should be supported within the beta period so that bugs can be filed by beta testers, worked out with revision builds and a stable release can be offered by the time a major OS launches publicly.

    When an OS goes live publicly, there is zero excuse for expensive and professional software to not support the most current OS.


    I think there are many developers who might take issue with your assumptions. Not just Apple developers who will no doubt be finding things as released are not entirely the same as they were for the last beta and so will be spending a lot of time "fixing" stuff they did not know was going to be broken - all at their cost.

    The same can apply to Windows, the various flavours of Linux, to all the variants of the mobile operating systems and development tools and to the tools that people have to use to be able to develop their applications.

    There is a long history of such issues and the adoption of "agile" (and so "frequent") releases could be seen as either the solution to thee problem or the origin of a new set of problems. Or both.

    If you look back to the posts made around the time of earlier major updates to Operating systems (and not infrequently intermediate software updates pushed out by hardware manufacturers) you will find various threads about certain problems and response to the problems often with explanations about why the problems have arisen (if they have been diagnosed).

    The chances of any company being able to test everything, guess which parts of what it has seen in beta testing will be released and which things they have not seen will be included and then expand that test to all possible combinations of hardware and third party software configurations is remote in the extreme.

    To put that another way, if anyone had the resources to do it we would not be able to afford the product they produced.

    Just my opinion of course.

    Grant
    0
  • Marc Pecquet
    Nicely said Grant !
    0
  • HansB
    Fully agree, Grant. In our world today, that's the way it is.

    OS X, Unix, Solaris, Linux, Windows, IOS, Android.
    Embedded, mobile or desktop.
    I have not seen a flawless OS upgrade on any of them.
    And it is not only 3rd party software that suddenly fails.


    Regards,
    Hans
    0
  • ---
    [quote="SFA" wrote:
    [quote="jameskachan" wrote:
    I don't see why the developers at Phase have been sleeping on supporting OS X 10.11 — It's unacceptable.
    Professional software should be supported within the beta period so that bugs can be filed by beta testers, worked out with revision builds and a stable release can be offered by the time a major OS launches publicly.

    When an OS goes live publicly, there is zero excuse for expensive and professional software to not support the most current OS.


    I think there are many developers who might take issue with your assumptions. Not just Apple developers who will no doubt be finding things as released are not entirely the same as they were for the last beta and so will be spending a lot of time "fixing" stuff they did not know was going to be broken - all at their cost.

    The same can apply to Windows, the various flavours of Linux, to all the variants of the mobile operating systems and development tools and to the tools that people have to use to be able to develop their applications.

    There is a long history of such issues and the adoption of "agile" (and so "frequent") releases could be seen as either the solution to thee problem or the origin of a new set of problems. Or both.

    If you look back to the posts made around the time of earlier major updates to Operating systems (and not infrequently intermediate software updates pushed out by hardware manufacturers) you will find various threads about certain problems and response to the problems often with explanations about why the problems have arisen (if they have been diagnosed).

    The chances of any company being able to test everything, guess which parts of what it has seen in beta testing will be released and which things they have not seen will be included and then expand that test to all possible combinations of hardware and third party software configurations is remote in the extreme.

    To put that another way, if anyone had the resources to do it we would not be able to afford the product they produced.

    Just my opinion of course.

    Grant


    ....and with every os update we get the same boring explanations and excuses. some companies have no problem to deliver a ready version and some have. c1 is as alway not ready for the new os. i think this tells more about phase one than about os upgrades in general. the vast majority of apps work flawless under 10.11 affinity photo, adobe cc... all use the graphic engine and nothing is broken maybe it is only bad coding on the c1 side.....
    0
  • Christian Gruner
    [quote="Horseoncowboy " wrote:
    [quote="SFA" wrote:
    [quote="jameskachan" wrote:
    I don't see why the developers at Phase have been sleeping on supporting OS X 10.11 — It's unacceptable.
    Professional software should be supported within the beta period so that bugs can be filed by beta testers, worked out with revision builds and a stable release can be offered by the time a major OS launches publicly.

    When an OS goes live publicly, there is zero excuse for expensive and professional software to not support the most current OS.


    I think there are many developers who might take issue with your assumptions. Not just Apple developers who will no doubt be finding things as released are not entirely the same as they were for the last beta and so will be spending a lot of time "fixing" stuff they did not know was going to be broken - all at their cost.

    The same can apply to Windows, the various flavours of Linux, to all the variants of the mobile operating systems and development tools and to the tools that people have to use to be able to develop their applications.

    There is a long history of such issues and the adoption of "agile" (and so "frequent") releases could be seen as either the solution to thee problem or the origin of a new set of problems. Or both.

    If you look back to the posts made around the time of earlier major updates to Operating systems (and not infrequently intermediate software updates pushed out by hardware manufacturers) you will find various threads about certain problems and response to the problems often with explanations about why the problems have arisen (if they have been diagnosed).

    The chances of any company being able to test everything, guess which parts of what it has seen in beta testing will be released and which things they have not seen will be included and then expand that test to all possible combinations of hardware and third party software configurations is remote in the extreme.

    To put that another way, if anyone had the resources to do it we would not be able to afford the product they produced.

    Just my opinion of course.

    Grant


    ....and with every os update we get the same boring explanations and excuses. some companies have no problem to deliver a ready version and some have. c1 is as alway not ready for the new os. i think this tells more about phase one than about os upgrades in general. the vast majority of apps work flawless under 10.11 affinity photo, adobe cc... all use the graphic engine and nothing is broken maybe it is only bad coding on the c1 side.....



    A quick Google search will reveal that i.e. Photoshop also have issues with 10.11. Please see my responses in this thread: viewtopic.php?f=55&t=20763&st=0&sk=t&sd=a&start=15#p98036
    0
  • Thomas R.
    [quote="georgebrooksphoto" wrote:
    (...) I won't be upgrading to El Capitan for at least a couple weeks after release or maybe even a .1 version to root out any other compatibility issues, but I skipped Yosemite and am still running Mavericks on all of my machines so I'd like to get El Capitan sooner rather than later. I didn't ever install Yosemite because I wasn't a huge fan of the new UI and I was concerned about the "iOSification" of OS X, but I'm pretty excited about some of the new features in El Capitan so I'm willing to overlook those concerns and get with the times!


    I'm still running Mavericks (10.9.5) too. After more than two years I think about upgrading the OS to a newer version, but not yet, maybe in a few months after the first issus are fixed and every application is supported, fixed and works stable (".1 versions").
    What's the reason for me to proceed this "easygoing-way"? I have no fun upgrading the OS of my production computers every year again. I need a stable system for a long time without spending time fixing bugs or using workarounds all the time. So for me it's not necessary that an application supports a new OS at release day.

    -- phaseone, please feel free to test a few more weeks and approve 10.11 support in a stable version. Quality first, then everything else.
    0
  • Thomas R.
    [quote="Horseoncowboy" wrote:
    ...and with every os update we get the same boring explanations and excuses. some companies have no problem to deliver a ready version and some have. c1 is as alway not ready for the new os. i think this tells more about phase one than about os upgrades in general. the vast majority of apps work flawless under 10.11 affinity photo, adobe cc... all use the graphic engine and nothing is broken maybe it is only bad coding on the c1 side.....


    Really? The most majority of apps work flawness? What are the most majority software/apps? Adobe CC and affinity photo are majority? I think it does not apply for everyone, right?

    Have a look at this (sorry, it's a german site):
    http://www.heise.de/mac-and-i/meldung/M ... 35239.html
    There is an upgrade warning for applications from "steinberg", "native instruments" some publishing/layout software like "QuarkXPress 2015", "MS Outlook" and so on. They all have problems with 10.11! Please note that.

    Best Regards!
    0
  • ---
    ....fine than c1 is at least in good company, but as a photographer i don´t care much about music software and as far i can see all raw converter i use and all image editors work just fine except.

    http://forums.macrumors.com/threads/os- ... s.1890772/
    0
  • Thomas R.
    [quote="Horseoncowboy" wrote:
    ... and as far i can see all raw converter i use and all image editors work just fine except

    Fine. But where's your problem now? Why do you need capture one if all raw converters and editors you use work fine? And what is the reason to switch to a new operating system on release day? Why do you can't wait a few weeks? It's a nice to have or did your old system stop working unexpected yesterday? I can't understand your trouble but I will stop this kind of discussion for me at this point. I dont' want to bore someone with my opinion. 🙄

    -- The early bird catches the bug!

    Best Regards and have a nice day
    0
  • Jim_DK
    Feel like there needs to be a right to reply here...

    No one remembers 10.7 updates breaking color management by renaming all the internal color profile names the same? or 10.8 breaking Canon's SDK when it worked just fine in the pre-release? No? Just me then 🙄

    Apple much as we love them are far from exempt from the occasional faux pas. It's software. Made by people.

    So call us cautious (or cynical) but we will keep the powder dry this time around until we have smoked the public release.

    Irrespective of all that - it looks fairly stable. Our main issue now is a bug in the Apple OpenCL which we are already on top of - however it is easy enough to work around by disabling OpenCL.

    If the new software is too much to resist, then please make sure you have a back-up to roll-back to if you find for whatever reason you have problems. You can do this quickly using any half decent sync utility or partitioning the HD.

    Expect an announcement shortly for an official supported release.
    0
  • ---
    jim thanks, so nothing really new with 10.11 - open cl does not work under 10.10 on my macpro anyway. but considering all the problems c1 has i would not point fingers at apple...
    0
  • NN635770922769309595UL
    Thank you James for a measured response and the welcome news on the update.
    0
  • Christian Gruner
    [quote="Horseoncowboy " wrote:
    jim thanks, so nothing really new with 10.11 - open cl does not work under 10.10 on my macpro anyway. but considering all the problems c1 has i would not point fingers at apple...


    Please create a support-case, and we will get you up and running, if you have supported hardware.
    0
  • Scott Sobers
    There is a lot of emotion each time a new release comes to market. Additionally, there are also a host of undocumented benefits as well. Working in the software industry I can appreciate the emotion to upgrade, but most software companies recommend for the .1 release for their enterprise customers - especially where the software is mission critical. That said I am a prosumer user. If I were a photographer and my business relied on a reliable release, I would hold off until Apple puts out their .1 release.

    I don't work for P1, but I can bet that they are not just sitting around. Apple didn't even lock down their gold master until just a few weeks ago.
    0
  • NN635623006837493918UL
    [quote="Marc PK" wrote:
    Phase One just posted a note on Facebook recommending not to update until Capture One comes out with a new release.
    Like many other Aperture lovers I am new to C1 and am still using Aperture for my file management... Anyone out there tried Aperture with El Capitan ? Does it still work ?


    Although I haven't tried it, I have heard that Aperture will work as long as you do an upgrade to El Capitan rather than a clean install. I too am relatively new to C1 but would find it very difficult to go back to Aperture.
    0
  • NN635770922769309595UL
    Yes, I tried Aperture from El Cap and it worked fine; with the caveat that since I no longer use Aperture it was a fairly light try out; I know of at least one post elsewhere that said the user had problems with some (unspecified) heavy editing tasks.
    0
  • Mark Moore
    If, like me you upgraded to 10.11 only to find Capture One immediately crashing on startup, there is a work-around.

    Open the Terminal.app (from /Applications/Utilities) and enter the following commands:

    defaults write com.phaseone.captureone8 UseOpenCL 0
    defaults write com.phaseone.captureone8 UseOpenCLForProcessing 0

    This will stop Capture One from using OpenCL. The commands are equivalent to changing the OpenCL options under "Hardware Acceleration" (General Settings). When Phase One have a fix, you can re-enable via the preferences...

    -- Mark
    0
  • Bernard Boudon
    Thank you Mark.
    Your tips work fine for me. 😄
    0
  • NN635465122454575120UL
    My C1 installation is a bit of a mess. I can't export photos and I can't "edit with".
    Waiting for a fix. Oh, and please add Nikon J5 support. Thanks.
    0
  • NN635465122454575120UL
    I have to admit that for NEF, I can get good results going the TIFF route (NXD) and then NIK or MacPhun. If I dump my X100 T (which I am close to doing), I can probably live without C1, although I like the rendering. But they are too long in providing support for semi-new cameras.
    0
  • NN635482157414920081UL
    I'm having some rendering problems since upgrading to OS X 10.11 on a (new) Mac Pro with dual AMD FirePro D700 cards. After editing a few photos, photos are half black - the left-hand side goes black. I've also had (once) a vertical split where the top half is darker or lighter than the bottom half of the photo with a lighter line separating the lighter/darker. The black half-screen rendering bug happens every time - restarting CaptureOne resolves the problem.

    I've reported this to PhaseOne.
    0
  • Richard Brown
    I installed on a macbook pro and my older version of C1 would not work, however downloaded C1 8 and it worked for 12 hours of shooting on location yesterday without even disconnecting, even unplugging the camera and back and it connected every time unlike my past experiences. I did have one odd experience that I never had before where a series of shots, about 15 frames did not come up on screen, usually this was a disconnect and it would then write to the CF card however the images were not on the card or the computer.. just vanished.
    Once again, why can't we write to the camera card and C1?
    0

Please sign in to leave a comment.