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

C1. 11 running slow on 2018 Mac with i9 chip

Comments

22 comments

  • Eric Valk
    I'd say open a support ticket right away.

    You're the first poster I've seen here with this kind of Mac.
    0
  • Paul Rossaint
    Hey Mark,

    for your information, i have got the same problem... same Macbook and totally poor performance. Did you open an support ticket right now?

    Best,

    Paul
    0
  • Mark Tomaras
    yes, I wrote the same description above to the support people at the same time I wrote it here.

    anyone mind confirming this? on your Mac, of any kind, (higher perforce models better than entry level), import 500+ raw files, let C1Pro render previews, and watch activity monitor to see the percentage of the cpu's multiple core performance. can also report this with an export to tiff.

    iStat Menu's by Bjango software is great by the way - I use this to real Time monitor the activity. It draws the data from activity monitor, but it's a better interface, and it has more information.
    0
  • Grant Hodgeon
    Outside of the C1 Optimisation argument, I stand that the i9 in the MBP 2018 is insufficiently cooled for peak/sustained performance.

    What you see is expected, and sucks. Return the thing like I'll be doing.
    0
  • Mark Tomaras
    [quote="photoGrant" wrote:
    Outside of the C1 Optimisation argument, I stand that the i9 in the MBP 2018 is insufficiently cooled for peak/sustained performance.

    What you see is expected, and sucks. Return the thing like I'll be doing.


    perhaps, but I just ran some tests... here are my results:

    exporting 50 raw files to tiff took 3min33sec with the open CL Off. It took 1min 44 sec with the open CL on. when the open CL was on, the graphics processor was running at 70-80 % capacity. when open cl was off, the cpu was running at 60-70 % capacity. Little else was running either time, so I would have liked to see more use of either chip. furthermore, wouldn't the i9 6 core chip have a lot more processing power than the Radeon Pro 560X ? Strange to see the i9 take double the time.

    Next, with preview generation (or re-generation from the menu) of 500+ raw files, either processor was woefully underused. It took a long time and the chips ran at 10-20% tops of capacity.

    Compared to Alien Skin Exposure X3, the cpu ran at 85-96% during an export, and during import, Exposure X3 also tipped the cpu up to 80+ %. Of course this is another program, and I am not going to compare speeds, but the cpu usage is interesting.

    My issue issue is the low usage of the chips. why not throttle the heck out of these? If I bought an eGPU to speed things up, would I only use 2/3 of its power? That is no fun.

    My next test will be with the session folder on an external SSD drive. so far all tests were with the session folder on the MBP boot volume.
    0
  • Mark Tomaras
    speeds with the session folder on an external SSD were the same as the boot volume
    0
  • Jack Strutz
    Mark will you keep us posted if the High Sierra 10.13.6 update fixes your problems with CPU under-utilization?

    Very curious to see how this shakes out as I have a machine with identical specs pre-ordered from B&H right now. This will be a replacement for the fully-spec'd 2017 model I bought and subsequently returned when the 2018 model was announced 2 weeks after my purchase. The 2017 model kept up ~ok~ with my A7Riii files while tethering on location but would definitely be running hot. Very concerned about the thermals of the i9 machine being able to keep up in on-location scenarios. Wondering if I made the wrong decision to return my 2017...
    0
  • Dustin Betterly
    Having issues here as well, installed Apple update the day it came out. Shooting IQ250 after about 200 images, the previews start to backup, processor cores go full max, temp is low though, and it seems like C1 almost stalls or crashes but never does...Very frustrating!
    0
  • travisdrennen
    I’m experiencing the same problems as James with the D850 before and after Apples 10.13.6 patch. On location in LA (94 degree air temperature)the internal CPU temperature hit 201 degrees. At that point there was a 54 frame preview queue that took 10 mins to finish. Completely unusable. Switched back to the maxed out 2017 and preview delay was never more then 4 frames. Never took more then 6 seconds to render all images. Will be returning the 2018 and using the 2017 until this is sorted out.
    0
  • Mark Moore
    For what it is worth, I am running CO11 with a 2018 MacBook Pro i7 2.6GHz.with 560X GPU. Performance is an obvious step up from my previous (late 2013) MacBookPro. The i7 and i9 are virtually identical aside from the clock and a little extra cache memory.

    Most of the gain seems to be from the GPU and from the (ridiculously) fast internal SSD. CPU based tasks never seem to make use of all six cores and so will not make the most of the 8th gen Intel parts.

    CO11 still lags behind Lightroom for editing smoothness (particularly when rotating images), but I do not seem to suffer the sometimes multi-second editing lags that I was seeing with my previous late 2013 15" MacBookPro. I am actually pretty happy with the upgrade both for performance and the larger SSD.
    0
  • Mark Moore
    I should have added that I am mostly working with 80MP film scans, shot using an Olympus in HiRes mode - so these are always a struggle performance wise. What is most useful from the laptop upgrade is the vastly better performance when editing layer masks.
    0
  • Gustavo Ferlizi
    MacBook Con 2018
    0
  • Tobin Bennett
    I feel there is more going on here. Back in May I bought the latest top of the line MPB to replace my top of the line Mid-2015 model as I purchased a BenQ 27" 4k monitor and display performance slowed down drastically. The brand new 2018 MBP wasn't any faster AT ALL than my 2015 model, processing a7riii files or display performance. So I returned the 2018 and went back to my 2015. Things were working fine for a while aside from slow preview rendering because of the 4k display. Now suddenly I'm having major issues with mask drawing, extra slow preview rendering, RGB readout not showing above the main image, images randomly come in fast then sometimes take forever. Most recently while trying to draw a mask the mask doesn't show up and when I take my finger off the mouse button the selection point shows up from where I started to draw and does a snail crawl along the path I just drew yet the mask isn't displaying. Lots of strange frustrating things happening. I shoot almost all tethered in studio with client, they are getting frustrated too.Basically all around performance has seemed to have slowly gotten worse.
    0
  • Dustin Betterly
    Interesting...so maybe it’s not an apple issue but a C1 issue. I’m not giving up on it, I think it will get better just need to manage the client expectations for the moment.
    0
  • Chad Dahlquist
    been debating about a new macbook

    I built up a PC for C1 (capture in studio and developing etc.) and its insane but its a PC and I hate the file management (file explorer)

    but having used C1 since its launch I can say sadly it might be a C1 thing and one of the things about the company being rather small are strange things like this happening also they seem to take on this its not us
    I can see why they do not offer support for the med format fuji but that ties back to them making software for their cameras and offering it out as a 2nd thing it feels sometimes ?

    very curious how this all turns out
    0
  • mbp
    Appreciate the comments here so far. Does anyone have anything further to add?

    I'm currently holding off on purchasing the 15" 2018 MacBook Pro until there is some more positive feedback for it with Capture One 11.

    Has anyone been able to do some speed/temp comparisons between the 15" models based on high throughput usage in Capture One? Perhaps someone has also tried the new 15" base model, 2.2Ghz i7 with Radeon 555x?

    Based on the information out there, it does sound possible that both the lower spec CPU and GPU could provide better performance in Capture One due to generating less heat? Any more opinions on that?

    Hoping to hear from more digital techs or photographers who have used the 2018 MacBook Pro for fast tethered shooting (50-100MP files) combined with 1-2 external 4k monitors (via DisplayPort) and a USB-C hub running 2-3 bus powered drives.
    0
  • Whitesnake
    How is performance in crop/rotate mode compared to older MBP? How responsive are the ruler for exposure? For me it‘s very important. I‘m just handling 24 MPx files.
    0
  • Peter Guyton
    [quote="mbp" wrote:
    Appreciate the comments here so far. Does anyone have anything further to add?

    I'm currently holding off on purchasing the 15" 2018 MacBook Pro until there is some more positive feedback for it with Capture One 11.

    Has anyone been able to do some speed/temp comparisons between the 15" models based on high throughput usage in Capture One? Perhaps someone has also tried the new 15" base model, 2.2Ghz i7 with Radeon 555x?

    Based on the information out there, it does sound possible that both the lower spec CPU and GPU could provide better performance in Capture One due to generating less heat? Any more opinions on that?

    Hoping to hear from more digital techs or photographers who have used the 2018 MacBook Pro for fast tethered shooting (50-100MP files) combined with 1-2 external 4k monitors (via DisplayPort) and a USB-C hub running 2-3 bus powered drives.


    Great questions. I'm in the market too for a new MPB and am debating the high end 13" (perhaps with an eGPU when docked) vs 15". One thing of note is a PhaseOne post describing how C1 takes advantage of OpenCL:

    Open CL will dedicate memory to several actions in Capture One.
    The following outlines the softwares demand;
    • Preview Update with different settings, styles etc: RAM
    • Sorting/Rating: CPU cores and SSD speed
    • Fit Image to Screen: GPU cores
    • Process time: GPU processing units and CPU's and RAM


    Of note is that the GPU seems not to play a part in Preview Update or Sorting/Rating. Looking at the Geekbench CPU scores, the i9 doesn't seem to bring much additional to the table; yeah, it's a tad faster but not that much. So the question of whether the lower end "15" base model, 2.2Ghz i7 with Radeon 555x" suffers same issues is a good one.

    Personally, I'm considering a 13" loaded with the eGPU (when docked). That's roughly the same price as a 15" i7 (1TB SSD in both cases). But right now I'm on the sidelines waiting for some of these things to sort out.
    0
  • C-M-B
    I think this is less the fault of CaptureOne and more and more the fault of the overall backwards design for the Apple hardware.
    They've been using the same general built for the last 6 years - and they were fine for most of the time. But now we're reaching "critical mass" so to speak and Macs are not the only ones feeling the heat. Throttling occurs on just about every thin and light laptop of the current generation, at least on those running a powerful CPU and GPU combo.
    On the PC side DELL with their XPS also has some heavy throttling after a few minutes of intense editing in CaptureOne, rising to 90°C and even beyond when playing with the exposure slider for a bit.

    It makes however no sense whatsoever to get the i9 when you use the CPU and GPU at the same time - the temperatures simply will not allow for anything faster than what the i7 would be capable of. And for photographers (=people using C1) that applies 100%.
    0
  • NNN636707252531857449
    To be honest, I can't imagine this being just a Mac issue.I am running a Windows laptop with i7-3630QM and 16GB memory, it also uses in between 23-28% CPU on average when exporting images.
    0
  • Permanently deleted user
    I did test today my imac i7 4ghz to import 14k images and creating previews.
    Cpu usage was constantly about 45% and gpu processor as well
    0

Post is closed for comments.