Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Open CL on Mac Pro (cylinder model) OSX Yosemite problem

flashsplash
Hi,

I am running latest 8.3 Capture one Pro on a Mac Pro with OSX Yosemite. As long as I am staying within CO, the open CL acceleration works fine.
Trying to edit a IIQ picture from within the CO "edit with" Photoshop CC opens a Photoshop session , however the picture is corrupted .
Turning of Open CL in the CO settings, then there is no problem with the flow....


So the issue is CO 8.3 and open CL when trying to edit from within CO to PS CC....

Anybody with the same issue ?


Kind regards ,

Steve
0

Comments

16 comments

Date Votes
  • Permanently deleted user
    http://i28.photobucket.com/albums/c223/picpuppa/For%20Posting%20on%20Net/_NIK2000_zpsvepmpctr.jpg

    Does your corrupt image look like this??
    0
  • Permanently deleted user
    Hello, I am running almost identical set up and have lost 10/20% of my library like this.

    Going mad as to what is causing it and obviously loosing more images if I try and work.

    If we are at the beginning of a major upset perhaps Phase 1 should know.

    I am not equipped with sufficient knowledge to fault find myself or trace the cause.

    Really down.

    Appreciate a response.

    Sharkey
    0
  • dale11833
    I am curious what are the specs on your mac pro and what version of mac os 10.10 are you running?
    0
  • SFA
    [quote="Sharkbite" wrote:


    If we are at the beginning of a major upset perhaps Phase 1 should know.



    Agreed. Have you created a support case?
    0
  • Permanently deleted user
    Base model with 16gb ram running 10.10.3

    Phase 1 now know.
    Contacting Apple now.
    and posted the following on other sites I use:-

    ""Hello, This is a from someone not technically savvy enough to explain it in exact terms; aimed at anyone with the following combination of software on their MAC computer (Ido not know about Windows)

    MAC /Intel computer - Yosemite 10.10.3 - Photoshop CS5 (possibly above) - Capture 1 Pro (8.3-8.3.0.52)

    Corruption of all images in your library seems to be possible.

    Don't ask me how. All I can tell you is mine (15%) until stopped by not using anything related to my images and disconnecting my hard drives (all). I have contacted Phase 1 but not Apple so far and another website I use.

    This warning is because I have found one (1) other user with the same problem who has an identical set up as me.

    The corruption in my case have been backed up to both my CCC HD and my TM HD so I can (maybe) retrieve undameged images later. Unless you check visually every (original) image you will not see it. Previews in C! do not show the corruption until the preview is re-done or original opened for work or in another editor.

    Trying not to start a panic but as mine is such a mess thought best to raise the subject.

    If I am wrong my humble apologies. If not someone will find it pretty soon.

    Good luck.

    Regards

    Sharkey
    0
  • SFA
    Sharkey,

    Unless you are specifically overwriting your original images (i.e. if starting from a jpg or tiff) they will not be damaged by any application that is non-destructive.

    If you are telling C1 to send a file to another program for editing then C1 will create an image (usually a tiff file) for the other application to work with. This is a new file not your original.

    The original post on this thread (flashsplash), if I read it correctly, said that the problem could be overcome by turning off the availability of OpenCL functionality suggesting that there is something in the graphics card or its software that is causing a bit of a problem and needs to be analysed - although it may already have been diagnosed elsewhere.

    If you turn off the OpenCL option in the Preferences doe that also remove the problem for your situation? I might guess that the "for Output" setting is the one that needs to be turned off n this case but OpenCL is only a performance boost used in certain situations so there is probably not harm in unsetting both setting options.

    HTH.



    Grant
    0
  • Permanently deleted user
    Grant,
    thank you for that. I do not follow all of it but the corrupt images includes some that have only been viewed in C1; very few have actually been worked on. Some have.

    The OP seems to have found a path to correct his problem (better equipped than I to find it) 😕 so that is good.

    It may be that the incompatibility lies in Yosemite? I do not know. Apple tech has said only real solution in my case is to return to Mavericks and reinstall appropriate C1..

    I pretty much had that in mind but what concerned me most was the hidden nature of the corruption and how I had not recognised it until much damage had been done.

    So back date rebuild and be more vigilant in my case live without some treasured old stuff BUT if it is occurring elsewhere I think I am right to put it out there?

    Regards

    Sharkey
    0
  • SFA
    [quote="Sharkbite" wrote:
    Grant,
    thank you for that. I do not follow all of it but the corrupt images includes some that have only been viewed in C1; very few have actually been worked on. Some have.

    The OP seems to have found a path to correct his problem (better equipped than I to find it) 😕 so that is good.

    It may be that the incompatibility lies in Yosemite? I do not know. Apple tech has said only real solution in my case is to return to Mavericks and reinstall appropriate C1..

    I pretty much had that in mind but what concerned me most was the hidden nature of the corruption and how I had not recognised it until much damage had been done.

    So back date rebuild and be more vigilant in my case live without some treasured old stuff BUT if it is occurring elsewhere I think I am right to put it out there?

    Regards

    Sharkey


    I would wait until you have discussed this with the Capture One support people.

    As far as I am aware there is no way that original files should become damaged in normal C1 use - they are treated as "read only". Viewing in C1 simply creates a file that can be viewed - are these RAW files you are using or some other type? If it's a RAW file C1 will start by displaying the embedded jpg provided by the camera and then run its interpretation of the RAW if you go further than the thumbnail (it sort of depends what you mean by "viewed". But the original RAW file will not be changed in any way.

    If you are dealing with TIFF or JPG files the process is basically the same in that the original files will not be overwritten by the software - especially after just a viewing.

    If you have removed the original files or there is some other part of your activity that somehow works around the "non-destructive" principle that Capture One follows then you might be right but in my experiences of non-destructive software (not just Capture One) I have never lost an original file yet.

    Where are the source files coming from - camera or something else? What type of file are they?


    Grant
    0
  • Permanently deleted user
    OK, I got all that.

    All I can do is try and answer each point you make.

    The problem may not be C1 alone - C1+Yosemite+CS5 - I really do not know. Hence my confusion and worry.

    Files affected are both part of my referenced C1 catalogues (10 off) and images not part of the same.
    File types vary jpg,NEF,CR,TIFF,tiff,Olympus,PNG - I do not want to search more on my main HD at the moment but will on clone tomorrow.

    All editing in all file types has been done in CS5 or C1 or both. But damaged file I have seen are old 9yr+ from scans and have not been touched for years.

    Source files at the moment are all on a Caldigit T3 in speed raid which ever type the is 😕 .

    As I have said I am pretty sure the combination of upgrading to Yosemite 10.10.3 and C1 8.3 are at the root of this and that returning to Mavericks and appropriate C1 version will kill the problem. I t is really the length of time it has taken before I noticed the problem that really concerns me as I do not want anyone else to get caught and suffer.

    Regards

    Sharkey

    PS.... I am waiting for responses from Phase One and Apple before I do anything else but had to share.
    0
  • Permanently deleted user
    Oh yes:- Viewed; browsing through Catalogues in C1 without any editing does not show the original file has been corrupted.

    If you re-do the preview the corruption then appears - so no redo = no knowledge of originals corruption.

    I wonder if running C1 the non referenced way would be better?

    Regards

    Sharkey
    0
  • sizzlingbadger
    Have you actually tested turning off OpenCL in the Capture One preferences ?
    0
  • flashsplash
    I just got answer,

    Open CL based on a AMD FirePro D500 (fitted in the mac pro) is supported on Capture One 7
    but not on Capture One 8 !

    So all what I can do is turn Open CL off in the preferences of CO 8



    Check FAQ on the link for the supported cards, if yours does not show then it is not supported.....
    Then turn off open Cl
    0
  • Christian Gruner
    D500 is supported in CO8 as well.
    The whole range of Mac Pro gpu's are supported, d300, d500 and d700.

    Can you give me your support case number ?
    0
  • flashsplash
    Hi Christian,

    That is good news, however reality is that it is an issue. I have checked the PO FAQ page , and from that it seems that it is not listed as a supported card . Unless that list is not updated and you have more recent information.
    I have not openend a case yet..... Shall I ?
    0
  • flashsplash
    Hi Christian,


    Just opened the case 180843


    TXS
    0
  • Christian Gruner
    [quote="flashsplash" wrote:
    Hi Christian,

    That is good news, however reality is that it is an issue. I have checked the PO FAQ page , and from that it seems that it is not listed as a supported card . Unless that list is not updated and you have more recent information.
    I have not openend a case yet..... Shall I ?


    It is listed here: https://www.phaseone.com/en/search/arti ... nguageid=1

    Yes, listed under CO7, which is indeed confusing and should be corrected. However, if it worked under CO7, it will also work under CO8.
    0

Post is closed for comments.