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

Very slow export

dredlew
Not to be that "Aperture Guy" again, but well, I am. Unfortunately, during my trial period of C1 I did not edit a full shoot and export the whole batch, just one offs for test. All seemed fine. Now I finally did take the plunge, bought C1 and did a full edit of a batch of some 200+ images. Nothing crazy, some cropping, color correction, sharpening. No masks, compositing or the like. Then tried to export as high-res jpgs (no resizing) and had a mild shock when the export dialog showed 40mins and counting up, not down. - I ended up falling asleep waiting for it to finish and the next morning I saw that it took C1 a solid 2hrs(!) for some 200 images. And that's a small shoot...

Again, since I'm an Aperture guy, I have to draw the comparison to Aperture, that old dinosaur that still gives every other Raw editor a run for their money. Needless to say, Aperture completes this task of exporting 200+ images in 10mins(!) flat. Well, why is that? Aperture's export is multithreaded, where it appears C1's is not. Aperture is capable of simultaneously taxing all 8 cores of my i7 to 50-100% whereas C1 struggles to even get 1 core at a time above 5%.

While I appreciate the speed improvements in C1's UI (compared to Aperture) that are likely due to OpenCL, the excruciatingly slow export seems like a serious workflow issue to me. So I'm just putting my findings out there and I would be interested to know how other switchers experience this. Is there something that can be done to improve C1 (from a user perspective) or does it mean waiting until C1's export is multithreaded (which I believe is not something trivial to implement).

Thoughts?
0

Comments

7 comments

Date Votes
  • H. Cremers
    I think you should raise a support case. This is not normal.

    I tried this with 292 images on my duo core macbook pro and it took roughly 16 minutes. Not the fastest in the world, but very acceptable to me.

    I think, by the way, that you should be looking at ImgCoreProcess and not at CaptureOne in the task manager. For me, that one is taxing the CPU fully, so i do believe it is multi-threaded.

    I couldn't get a clear picture from your post what kind of system you have, where your images are, where your catalog is, versions (of CO, OSX) etc.

    For me this is CO 8.2.2 on OSX 10.10 (latest updates) on a 2013 macbook pro, duo core, 16GB and images on SSD running CO in session mode.
    0
  • David Papas
    There are several other reports on this, where it starts fast, but then slows down, hence the progress bar going up, seems to be a bug. If you quit the program and process one image it should go really fast, it slows down as you go in a large que. At least for me.
    0
  • H. Cremers
    Did the same test again on my main machine (macpro 5.1, 6-core, 48gb) session on ssd with images on spinning hd.

    Without opencl: 9 minutes
    With opencl: 4 minutes

    With opencl on the cpu is not getting taxed at all (as one would expect).

    EDIT: meant to say "is not getting taxed" iso "is getting taxed"
    0
  • dredlew
    Ok thanks for the feedback, that's actually good news. In the sense of, it shouldn't be that way. Will check out the other posts.

    @HCS, as for my setup:
    - C1 8.2.2 on OSX 10.10.3
    - iMac (27-inch, Late 2012)
    - 3.4 GHz Intel Core i7
    - 32 GB 1600 MHz DDR3
    - NVIDIA GeForce GTX 680MX 2048 MB
    - FusionDrive
    0
  • dredlew
    From what I found was, that when starting the app fresh, exporting 50 images, then relaunching the app and export another 50, etc. I was able to get acceptable export times. Basically, the longer the app is open and the more images are exported, the export time exponentially increases. Relaunching the app seems to reset this at least temporarily but it's a pretty bad workaround.
    0
  • H. Cremers
    [quote="dredlew" wrote:
    From what I found was, that when starting the app fresh, exporting 50 images, then relaunching the app and export another 50, etc. I was able to get acceptable export times. Basically, the longer the app is open and the more images are exported, the export time exponentially increases. Relaunching the app seems to reset this at least temporarily but it's a pretty bad workaround.


    Thanks.

    I haven't tried this after CO's been open for a longer time.

    Perhaps something to verify is the memory usage on your system. While you seem to have plenty of RAM, i'm not so sure how OSX uses it sometimes. Also when you have other apps open. Just a thought.

    I'll give it a try to repeat my test after CO's been open for an hour or so before running the batch.
    0
  • dredlew
    [quote="HCS" wrote:
    I haven't tried this after CO's been open for a longer time.

    Well, open in the sense of doing edits. So after a bunch of edits, if I wanted to export, I would have to quit C1 first before exporting and then no more than 50 at a time before restarting the app again.

    [quote="HCS" wrote:
    Perhaps something to verify is the memory usage on your system. While you seem to have plenty of RAM, i'm not so sure how OSX uses it sometimes. Also when you have other apps open. Just a thought.

    Yeah, RAM usage is fine, with the few apps I have open, it usually doesn't go much over 15GB. So there is plenty to spare. I pay fairly close attention to that since the last versions of Aperture had a serious memory leak where it would over time gobble up the full 32GB of RAM and force everything into virtual memory. Needless to say, everything slowed down to a crawl.
    I do not see a memory leak in C1 although it definitely has a performance issue (aside from export) as well that keeps growing over time. Very noticeable in the "Rotate & Flip" tool. When starting the app fresh, adjusting the angle works in realtime, like it should. However, once I've edited 50-100 images, this tool gradually becomes like molasses and rotation feels like stop-motion. Restarting the app and it's back to normal. Just like Aperture. 😉

    And unfortunately, the 8.3 update does not fix these performance issues. Hopefully they'll be addressed in the next update...
    0

Post is closed for comments.