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

export slower

Comments

12 comments

  • Christian Gruner
    Please create a Support Case and have them take a look.
    0
  • HansB
    After reading about the slower or slowing down export, I got curious and timed the export under different conditions, before and after updating CO. (After booting, after hours of work in CO, after working with other Programs, and after sleep/wake-up.)

    I found that
    - CO 8.2.2 exported 206 images per hour,
    - CO 8.3 exports 114 images per hour.

    It's almost half the speed it was. Interesting.

    18MPix CR2 on mid 2009 MBP (yes, I know it's old), 17", 2.8GHz, 8GB RAM, 1TB HDD. Same referenced catalog (local catalog, images on USB disk), same images. OpenCL setting doesn't matter, I tried with and without.


    Regards,
    Hans
    0
  • Christian Gruner
    Try deleting any icocl.bin files in /users/shared/phase one/imagecore/ (have no reference right here, so the path might slightly different).

    This forces the OpenCL compiler to run again, when CO is started again. Wait 3-4 minutes before trying another process batch.
    0
  • HansB
    The path I found is '/users/shared/Capture One/ImageCore/'. But there is nothing to delete. It's empty.
    Searched for the file with Finder and Terminal ('sudo find / -name icocl.bin'), nothing found.


    Regards,
    Hans
    0
  • gfingerl
    I just did a short search, and the file was there. Maybe it´s just a hidden file. I am using PathFinder for this kind of operation, because I can configure it to show hidden files as well. It´s just because I am not familiar with the command line of OSX.
    0
  • HansB
    gfingerl, you are right. I didn't search for hidden files. I now listed the content of the folder including hidden files, but the folder is definitely empty.


    Regards,
    Hans
    0
  • Paul Steunebrink
    [quote="HansB" wrote:
    gfingerl, you are right. I didn't search for hidden files. I now listed the content of the folder including hidden files, but the folder is definitely empty.

    Hans,

    My assessment is that if no OpenCL is possible, no compilation would take place, hence no compiled file. And that could very well be the case on a Mid 2009 MBP.
    0
  • HansB
    Paul,

    [quote="Paul_Steunebrink" wrote:

    My assessment is that if no OpenCL is possible, no compilation would take place, hence no compiled file. And that could very well be the case on a Mid 2009 MBP.


    I fully agree with your statement, and I didn't expect the old MBP to do openCL. 😄

    But it is a fact that CO 8.3 is only about half as fast as 8.2.2 when processing. ☹️

    [quote="HansB" wrote:

    - CO 8.2.2 exported 206 images per hour,
    - CO 8.3 exports 114 images per hour.



    Regards,
    Hans
    0
  • Dubin Laurent
    Hi !

    that's right ! and not new ...

    see posts on the forum :
    Capture one 8.2.2 processing slowing down
    0
  • HansB
    I cannot confirm that CO is slowing down while processing, but I didn't process a 1000 images.
    CO 8.3 is slower, right from the beginning.

    When I timed the processing, the processing time per image was constant for both versions. No difference between the 2nd image and an image processed after 1 hour. (I didn't time the 1st image because of the time that is necessary to build the queue.) I stopped the processing after 1 hour, stopped all times by hand, and used 'KeepingYouAwake' to prevent my MBP from falling asleep.


    Regards,
    Hans
    0
  • John Kubler
    I noticed that the latest version on C1 8.3.0.52 was very slow to load. I deleted the ICOCL.bin file as suggested above and now C1 starts and loads my catalog in less than a minute. Before, I would have to wait several minutes and sometimes had to force quit the app and restart. What a change!
    0
  • Dubin Laurent
    Hello !


    but I discover how to eliminate the slow problem of my mac :
    all C1+pref uninstall and reinstall !
    I never did it, just install the new one each time.

    that's all !

    Laurent
    0

Post is closed for comments.