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. ⚠️

Capture 7.2.1 OpenCL issues

FLORIAN Le studio
Hi there,

We are now experiencing some issues on Capture One 7.2.1. (I've tried some of the problematic operations on 7.2, with the same results)

On a MacPro Late 2013 : 12 core ; 32 GB RAM ; 2x D700 GPU ; running OSX 10.9.2 :

- When OpenCL in process is set to auto :

Impossible to process jpgs files. (jpg, compress to 80, 2000px on large border)
The computer is totally stuck sometimes, or sometimes, it just does not process the files, and the computer slow down, and need a reboot (hard reboot, as it doesn't shut down by the shut down menu).
Tiff files process many times without problem, and both process well (but slow) without OpenCL.

On a 2011 MacPro : 12 core ; 24 GB RAM ; Ati Radeon 2870 ; running OSX 10.7.5 :

Seems to be slowing down the computer when processing tiff files. Also, it says 1H30s to process 127 P65+ files, instead of 12min without OpenCL.
JPG processing doesn't seem to affect the computer (2m20s to process the same 127 P65+ files).

Quite disappointing to buy some 12GB VRAM computers without beeing able to use OpenCL.

I have been reading that OpenCL works fine on 12core Late 2013 MacPro, except for some black square on jpgs sometimes, but here it doesn't process at all.

So, if anobody as a clue on how to manage this to work, it would be a great news.

Thanks for answers !
0

Comments

6 comments

Date Votes
  • Drew Altdo
    The support team and developers at Phase One might have an idea and would be very interested if you would create a support case, providing details about your machine.
    We have the exact same 2013 MP model and have no such issues so it would be interesting to see what the difference between our two systems is.

    http://www.phaseone.com/en/SupportMain/ ... pport.aspx

    Providing information like the System Profile and Log Files would help expedite things.
    Log Files;
    http://www.phaseone.com/Search/Article. ... nguageid=1

    System Profile;
    http://www.phaseone.com/Search/Article. ... nguageid=1
    0
  • FLORIAN Le studio
    Hi Drew,

    Thanks for the quick answer.
    I have done some more testing about this issue.
    It happens that the problem was coming from the C1 session.
    I've tried with a different session, and everything worked fine.
    With the faulty session, i could manage to get it working by deleting all the capture one .plist and caches before restarting the session.

    I'm gonna continue my tests, and let you know if I encounter any other issue.

    Bests.

    Cédric
    0
  • Drew Altdo
    Thanks Cédric.
    As the session has no bearing on OpenCL, I'm inclined to think the issue was related to something else.
    Perhaps just the recognition of a new OS if you've recently updated to 10.9.2. The deletion of the Plist will have likely addressed that and thus solved the issue.
    0
  • FLORIAN Le studio
    Yes, I was also thinking that it's weird that a session can have an impact on OpenCL.
    The strange thing is that it worked with an other session.
    And the faulty session just doesn't worked with OpenCL enabled, and perfectly fine without openCL. This session also caused some problems with processing with openCL on 7.2 on an older MacPro (mid2012).

    I'm not sure about it, but I may have first install C1 7.2, before updating to 7.2.1. Maybe this could be a reason.
    0
  • Hamish Brown
    Is this issue solely related to the new mac pro ?

    I've been told ( by a quality digi hire company ) that the D300 and D500 graphics cards are causing issues with OpenCL and image processing, but the D700 is fine, but, that's a $500 upgrade. Trying to find out as much info as poss, before dropping some serious $'s on a new machine. Hmmm….
    0
  • Edward Moss
    My D300's don't work, hopefully someone can test the 500's and 700's for you.

    I've been in contact with support and they say it's the Apple graphics drivers causing the problems, fingers crossed the impending 10.9.3 update will help.
    0

Post is closed for comments.