Slow processing

Sigurdur Gilbertsson

May 10, 2016 22:55

Try setting OpenCL to NEVER and also make sure to set Preview Image Size to 5120 and see if this helps.

0

Phillip Bond

May 11, 2016 03:37

Thanks for the advice.

Are you suggesting setting both OpenCL Display and Processing to Never? (or just one or the other)
Also, everything I've read suggests that one should set the Preview Image Size to just under the viewer display pixel size. You're recommending upping it to the maximum size?

I'll give it a go but I just wanted to try to understand why I'm doing what I'm doing.

0

John Doe

May 11, 2016 09:07

You should set it so that CO won't have to constantly regenerate previews even when you view your images in "to fit" size. So unless you're in full screen mode, that would be somewhere between your viewer window size and your screen size.

0

Christian Gruner

May 11, 2016 12:22

[quote="NN159196UL" wrote:
Thanks for the advice.

Are you suggesting setting both OpenCL Display and Processing to Never? (or just one or the other)
Also, everything I've read suggests that one should set the Preview Image Size to just under the viewer display pixel size. You're recommending upping it to the maximum size?

I'll give it a go but I just wanted to try to understand why I'm doing what I'm doing.

In general you should the preview size to the size of the Viewer. So if you are using a lot of full screen viewing, full 5k previews is the way to go on your 5k monitor. However, if you are exclusively shooting in portrait orientation, you can go quite a bit lower (like the height in px's of the screen).

Another thing, turning off OpenCL for your 5k imac is probably the worst thing you can do, performance-wise. Compared to a MBP, you have 4 times the number of pixels on-screen, but the CPU is not even 50% faster than a modern MBP. You need all the computing power you can get. The GPU will help significantly in FPS when adjusting, and render-times when processing.
As a rule of thumb, only turn off OpenCL if you see artifacts or get corrupted files.

0

Phillip Bond

May 11, 2016 13:52

n general you should the preview size to the size of the Viewer. So if you are using a lot of full screen viewing, full 5k previews is the way to go on your 5k monitor. However, if you are exclusively shooting in portrait orientation, you can go quite a bit lower (like the height in px's of the screen).

Another thing, turning off OpenCL for your 5k imac is probably the worst thing you can do, performance-wise. Compared to a MBP, you have 4 times the number of pixels on-screen, but the CPU is not even 50% faster than a modern MBP. You need all the computing power you can get. The GPU will help significantly in FPS when adjusting, and render-times when processing.
As a rule of thumb, only turn off OpenCL if you see artifacts or get corrupted files.

This what I've read and believed to be the case. The original advice seemed to contradict this and, unsurprisingly, did not help. Quite the contrary.

I'm just surprised at the performance of C1 on my hardware. Granted, I'm working with fairly large image files and a lot of screen pixels.

I also use Lightroom for many things and it performs much better on this system than does C1.

0

photo by FA

May 11, 2016 14:58

From my own experience with late 2015 full spec iMac, there is a problem with OpenCL and CO9. I have filled a support ticket already and technical team is aware and working on it. Hopefully they will publish a fix soon. What happens to me is, if you turn on OpenCL then drawing the mask while showing it is getting laggy and really slow.

Cheers,

Fatih

0

Sigurdur Gilbertsson

May 11, 2016 19:38

[quote="Christian Gruner" wrote:
[quote="NN159196UL" wrote:
Thanks for the advice.

Are you suggesting setting both OpenCL Display and Processing to Never? (or just one or the other)
Also, everything I've read suggests that one should set the Preview Image Size to just under the viewer display pixel size. You're recommending upping it to the maximum size?

I'll give it a go but I just wanted to try to understand why I'm doing what I'm doing.

In general you should the preview size to the size of the Viewer. So if you are using a lot of full screen viewing, full 5k previews is the way to go on your 5k monitor. However, if you are exclusively shooting in portrait orientation, you can go quite a bit lower (like the height in px's of the screen).

Another thing, turning off OpenCL for your 5k imac is probably the worst thing you can do, performance-wise. Compared to a MBP, you have 4 times the number of pixels on-screen, but the CPU is not even 50% faster than a modern MBP. You need all the computing power you can get. The GPU will help significantly in FPS when adjusting, and render-times when processing.
As a rule of thumb, only turn off OpenCL if you see artifacts or get corrupted files.

Having OpenCL turned on on my Retina iMac completely renders Capture One uselessly slow and in fact totally unusable in every way, so I whole heartedly disagree with Christian and his comment about having it turned on. I am sure Christian has not tried using Capture One on an Retina iMac and therefore does not speak from experience...?

The only thing that makes my iMac able to run Capture One at all is to turn off OpenCL to Never for both Display and Processing and also set Preview image to the same size as your display or 5120. And from what I have read on this Forum (and there has been a lot of previous discussiona about how horribly slow Retina iMac's run Capture One) is that this seems to be affecting almost everyone with Retina iMac's and turning OpenCL off seems to work better for most.

I think the good people at Phase One need to look a lot closer into this problem since I have already filled two support tickets about this issue and it still persists like it did when CO 9.0 came out ☹️

I also use Lightroom and it has always worked a lot faster that CO on the same machine.

0

dredlew

May 12, 2016 05:22

Yup, the blanket statement of it being the worst to turn off OpenCL is simply not true. It depends on your hardware and use-case. There's an older thread about a MacPro and OpenCL issues that shows the problem quite clearly in detail and I myself experience the same thing, with just a regular iMac. But as siggibg mentioned, Retina iMacs seem to be most affected by OpenCL, there are several threads about them.

While it is true that OpenCL takes the load off the processor(s), there is a bug in C1 (apparently at least in the Mac version) that causes performance to exponentially drop over time. Most noticeably for me during batch export. Hence, I have my OpenCL turned off. The processor takes the hit and runs at about 80% during export but at least the performance remains steady. With an i7, there really isn't much to worry about though, it's got room to spare.

Again, YMMV based on your hardware (gfx card, see MacPro thread) and use-case. I would try out different scenarios of on/off to see what works best for you.

0

Christian Gruner

May 12, 2016 08:50

[quote="siggibg" wrote:
[quote="Christian Gruner" wrote:
[quote="NN159196UL" wrote:
Thanks for the advice.

Are you suggesting setting both OpenCL Display and Processing to Never? (or just one or the other)
Also, everything I've read suggests that one should set the Preview Image Size to just under the viewer display pixel size. You're recommending upping it to the maximum size?

I'll give it a go but I just wanted to try to understand why I'm doing what I'm doing.

In general you should the preview size to the size of the Viewer. So if you are using a lot of full screen viewing, full 5k previews is the way to go on your 5k monitor. However, if you are exclusively shooting in portrait orientation, you can go quite a bit lower (like the height in px's of the screen).

Another thing, turning off OpenCL for your 5k imac is probably the worst thing you can do, performance-wise. Compared to a MBP, you have 4 times the number of pixels on-screen, but the CPU is not even 50% faster than a modern MBP. You need all the computing power you can get. The GPU will help significantly in FPS when adjusting, and render-times when processing.
As a rule of thumb, only turn off OpenCL if you see artifacts or get corrupted files.

Having OpenCL turned on on my Retina iMac completely renders Capture One uselessly slow and in fact totally unusable in every way, so I whole heartedly disagree with Christian and his comment about having it turned on. I am sure Christian has not tried using Capture One on an Retina iMac and therefore does not speak from experience...?

The only thing that makes my iMac able to run Capture One at all is to turn off OpenCL to Never for both Display and Processing and also set Preview image to the same size as your display or 5120. And from what I have read on this Forum (and there has been a lot of previous discussiona about how horribly slow Retina iMac's run Capture One) is that this seems to be affecting almost everyone with Retina iMac's and turning OpenCL off seems to work better for most.

I think the good people at Phase One need to look a lot closer into this problem since I have already filled two support tickets about this issue and it still persists like it did when CO 9.0 came out ☹️

I also use Lightroom and it has always worked a lot faster that CO on the same machine.

We have got a iMac 5k, but I cannot see the behavior you describe. I am not saying you are wrong in your observation, but we cannot reproduce it in-house currently. We are looking deeper into 4k/5k issues, and hope to be able to repro.

0

Phillip Bond

May 12, 2016 14:03

On the one hand I'm glad that the problems I'm experiencing aren't just my own, and that others â€“ most importantly the developers â€“ are aware that there is an issue.

Upon further testing I should say that although it is generally more sluggish with OpenCL turned off, some things do seem to be appreciably better. For example, the image seems to react to most of the sliders much more slowly, however the painting of masks is somewhat more tolerable.

Overall, very upsetting performance. I sincerely hope this is remedied soon.

0

Sigurdur Gilbertsson

May 12, 2016 14:52

[quote="Christian Gruner" wrote:
We have got a iMac 5k, but I cannot see the behavior you describe. I am not saying you are wrong in your observation, but we cannot reproduce it in-house currently. We are looking deeper into 4k/5k issues, and hope to be able to repro.

Christian, you say that you have not been able to reproduce the extremely slow behaviour of OpenCL on your in-house Retina iMac. Therefore I just submitted a new case with Technical Support, case number : 219087 and there I included a Screen Recording showing how totally useless Capture One is when OpenCL is turned on and also how it works with it turned off. I hope it helps to show you how incredibly slow and horrible this is.

So now I really am hoping for some answers on this and comments about what can be done. Is there a fix coming ? Or is this not something I can expect to be worked on any time soon if ever since I have been waiting for a fix since the Release of Capture One 9.0 ?

And just for the record, I really Love Capture One and after having invested a lot of time and money making the switch from Lightroom I truly hope this will be looked into seriously since I know there are so many people having the same issue here on the Forum.

0

Sigurdur Gilbertsson

May 12, 2016 16:51

The Tech Support team was extremely quick to answer my case and inform me about how things are progressing with this OpenCL issue. See reply from Tech Support below:

We are currently working to optimize better for the 5K iMacs. It has been a challenge because the computers are a bit underpowered for the number of pixels in the screen. You should see a big update coming not in the next bug fix update, but the next one after that.

In the meantime I suggest working with OpenCL off and a Preview size set to either 3840 or 5120 in Preferences.

Best regards,
Phase One Technical Support

This means that we should finally expect an update soon regarding the OpenCL issue!

P.S. Christian, Tech Support confirms my initial recommendation to turn OpenCL off and use Preview Size at 5120 😉

0

Phillip Bond

May 12, 2016 17:34

Very similar to the response I just received from tech support, to wit:

I would suggest starting with setting OpenCL to Never for Display (Capture One Preferences > General tab > harware accerleration). Then restart Capture One. Basically, OpenCL allows Capture One to leverage the computational power in the video card to perform certain tasks (for a more in-depth read, here's a Knowledge Base article concerning OpenCL: https://www.phaseone.com/en/Search/Arti ... nguageid=1). Particularly with the retina iMacs (both the 4k and 5k varieties), the sheer magnitude of the screen resolution leaves little GPU processing power for Capture One's additional tasks. Setting it to Never with these machines will generally show you a performance boost. This issue is something our R&D team has been working on resolving, but Capture One is limited by the power of the hardware driving the integrated displays.

Also, I would also make sure you are setting the preview size correctly in Capture One preferences in accordance with your Preview Window on screen (Capture One 9 menu > Preferences > Image > Preview Size > Try 3840 (If your viewer is set for full screen on the 5k display, set it for 5120 preview size). Then Restart Capture One and go to File > Regenerate Previews. See if this makes any difference.

Kind regards,

Phase One Technical Support

0

Wesley

May 12, 2016 19:35

5k iMac is like lifting weights in a sauna...
I don't get the thinner body on a desktop and mobile parts.
That baby needs some breathing room & more graphic power for a 5k.

0

Christian Gruner

May 13, 2016 13:20

[quote="NN159196UL" wrote:
Very similar to the response I just received from tech support, to wit:

I would suggest starting with setting OpenCL to Never for Display (Capture One Preferences > General tab > harware accerleration). Then restart Capture One. Basically, OpenCL allows Capture One to leverage the computational power in the video card to perform certain tasks (for a more in-depth read, here's a Knowledge Base article concerning OpenCL: https://www.phaseone.com/en/Search/Arti ... nguageid=1). Particularly with the retina iMacs (both the 4k and 5k varieties), the sheer magnitude of the screen resolution leaves little GPU processing power for Capture One's additional tasks. Setting it to Never with these machines will generally show you a performance boost. This issue is something our R&D team has been working on resolving, but Capture One is limited by the power of the hardware driving the integrated displays.

Also, I would also make sure you are setting the preview size correctly in Capture One preferences in accordance with your Preview Window on screen (Capture One 9 menu > Preferences > Image > Preview Size > Try 3840 (If your viewer is set for full screen on the 5k display, set it for 5120 preview size). Then Restart Capture One and go to File > Regenerate Previews. See if this makes any difference.

Kind regards,

Phase One Technical Support

Can you post your Support Case number as well ?

BTW, you don't have to restart after switching OpenCL from one state to another. It happens regardless of application restart.

0

Christian Gruner

May 13, 2016 13:26

[quote="siggibg" wrote:
The Tech Support team was extremely quick to answer my case and inform me about how things are progressing with this OpenCL issue. See reply from Tech Support below:

We are currently working to optimize better for the 5K iMacs. It has been a challenge because the computers are a bit underpowered for the number of pixels in the screen. You should see a big update coming not in the next bug fix update, but the next one after that.

In the meantime I suggest working with OpenCL off and a Preview size set to either 3840 or 5120 in Preferences.

Best regards,
Phase One Technical Support

This means that we should finally expect an update soon regarding the OpenCL issue!

P.S. Christian, Tech Support confirms my initial recommendation to turn OpenCL off and use Preview Size at 5120 😉

I saw your video, and that made me able to reproduce the problem. We are looking into it.
Regarding setting OpenCL to Never, in this case case obviously makes sense, as there is a downright bug in the system, but my original advice still stands. In your case, you could leave OpenCL to Auto for processing, and Never for display. That will give you the benefits of faster processing to file, while working around the performance-bug in the Viewer.

Regarding an upcoming fix, then I have to be more vague about "big changes". As I mentioned, we are looking into it, and will try to fix as much as the time-line allow.

0

Sigurdur Gilbertsson

May 13, 2016 15:05

[quote="Christian Gruner" wrote:
[quote="siggibg" wrote:
The Tech Support team was extremely quick to answer my case and inform me about how things are progressing with this OpenCL issue. See reply from Tech Support below:

We are currently working to optimize better for the 5K iMacs. It has been a challenge because the computers are a bit underpowered for the number of pixels in the screen. You should see a big update coming not in the next bug fix update, but the next one after that.

In the meantime I suggest working with OpenCL off and a Preview size set to either 3840 or 5120 in Preferences.

Best regards,
Phase One Technical Support

This means that we should finally expect an update soon regarding the OpenCL issue!

P.S. Christian, Tech Support confirms my initial recommendation to turn OpenCL off and use Preview Size at 5120 😉

I saw your video, and that made me able to reproduce the problem. We are looking into it.
Regarding setting OpenCL to Never, in this case case obviously makes sense, as there is a downright bug in the system, but my original advice still stands. In your case, you could leave OpenCL to Auto for processing, and Never for display. That will give you the benefits of faster processing to file, while working around the performance-bug in the Viewer.

Regarding an upcoming fix, then I have to be more vague about "big changes". As I mentioned, we are looking into it, and will try to fix as much as the time-line allow.

Thank you so much for your answer Christian, I highly appreciate you looking into this and I am glad you saw the Video and where able to reproduce the problem in house. Any and all improvements that can be made on this issue will be greatly welcomed by me and so many others on this forum.

Since you want to be a bit more vague on these changes, I really hope it don't mean this issue will be left out of the things to fix list for long 😉

0

Nick Manklow

May 18, 2016 22:08

It's encouraging news that some sort of fix is on the way, because as it stands, CO9 on a retina iMac is a horrible experience. I have a fully specced out late 2015 model and I am currently doing some basic adjustments to a D750 file, it doesn't take much for it to start freezing. Looking at the OSX activity monitor and I am seeing 400%+ CPU usage. I don't accept it's a hardware issue and while I do appreciate it's a lot of pixels to push about, I can take the same file in to Photoshop, add a ton of layers and get no slowdown.

I have tried OpenCL on and off and I can't see any discernible difference. Same goes for changing the max pixel size setting to match the display.

0

Phillip Bond

May 20, 2016 14:12

I don't accept it's a hardware issue and while I do appreciate it's a lot of pixels to push about, I can take the same file in to Photoshop, add a ton of layers and get no slowdown.

I recognize that there are an extremely large number of pixels to attend to but it's true that my machine seems to be able to deal with it well in Lightroom (and Photoshop).

Perhaps C1's architecture makes it more difficult?

0

Jeffrey Jakucyk

May 20, 2016 15:18

I find it fascinating that a current top-of-the-line iMac chokes on Capture One while my 2008 Mac Pro works fine considering how old it is, and this also with Nikon D750 RAW files. No it's not speedy, and I can't use OpenCL (it makes it worse) but it doesn't freeze or hang or exhibit the other problems I hear about with the iMacs.

0

Sigurdur Gilbertsson

May 21, 2016 10:19

[quote="jjakucyk" wrote:
I find it fascinating that a current top-of-the-line iMac chokes on Capture One while my 2008 Mac Pro works fine considering how old it is, and this also with Nikon D750 RAW files. No it's not speedy, and I can't use OpenCL (it makes it worse) but it doesn't freeze or hang or exhibit the other problems I hear about with the iMacs.

I totally agree with you, I have a mid 2010 15 inch MacBook Pro (six year old hardware) and this machine still works flawlessly with Capture One 9 and it makes my new Retina iMac look like a totally outdated machine in comparison. And since the Retina iMac is able to run both Photoshop and Lightroom at great speeds it confirms that there is something hugely wrong with Capture One's architecture.

0

FirstName

May 21, 2016 10:32

I have a late 2014 Retina, 4GHz, 32GB and AMD R9 M290X 2GB. C18 worked faster on my 6 year old iMac ... and now I have C19 and really its just pathetic. PTGui, photo stitching, uses the GPU well and is very fast. SO its not the computers fault!

And cache preview size ... this is what I observe: A small import, 4 images, each with sharpening and curves adjustment, in the browser I select the first, it takes 2 seconds to render, then I select the next and the next again and then the last. Each takes a few seconds to render.

Now I select the first image again, and it takes 2 seconds to render ... so where exactly was the preview image cached? Well, sometimes if I'm lucky it will be cached, but normally not, even if I cycle between just two images, most of the time C18 or 9 is regenerating the image. Most of the time there is _no_ caching going on - at that is what makes C1 really suck.

If it takes 2 seconds to render and image, or even 5, I can deal with that - IMO it should be faster, but I don't get the feeling the GPU is being used. However, what is really difficult to accept is that simple switching between two images should require constant image regeneration. There is clearly a fault, either mine by using a wrong setting, or one with the application - a generated image preview should show in an instant.

Now thats just one instance where it is slow, there is also incredible delays when drawing masks, to the point where its not worth bothering with, and on and on and on.

0

Jeffrey Jakucyk

May 21, 2016 16:31

[quote="FirstName" wrote:

And cache preview size ... this is what I observe: A small import, 4 images, each with sharpening and curves adjustment, in the browser I select the first, it takes 2 seconds to render, then I select the next and the next again and then the last. Each takes a few seconds to render.

Now I select the first image again, and it takes 2 seconds to render ... so where exactly was the preview image cached? Well, sometimes if I'm lucky it will be cached, but normally not, even if I cycle between just two images, most of the time C18 or 9 is regenerating the image. Most of the time there is _no_ caching going on - at that is what makes C1 really suck.

If it takes 2 seconds to render and image, or even 5, I can deal with that - IMO it should be faster, but I don't get the feeling the GPU is being used. However, what is really difficult to accept is that simple switching between two images should require constant image regeneration. There is clearly a fault, either mine by using a wrong setting, or one with the application - a generated image preview should show in an instant.

This is my observation as well. Despite everyone saying to set preview size as large as possible (which does slow import/preview generation as you'd expect) I still never see any difference in speed flipping through images. C1 does pre-cache the next image in line, but if going too fast through them, or going back, it just regenerates it on the fly every time, no matter the preview size. It's not slow per se, but it's not fast either. The 2 second rendering time seems about right. There's about 1 second of super pixellated image, then 1 second of slightly pixellated image, before it's finally fully rendered.

Here's a video. Be sure to watch at 1440p https://www.youtube.com/watch?v=fp8XDwfSdl4

0

Sigurdur Gilbertsson

May 21, 2016 18:18

[quote="jjakucyk" wrote:
[quote="FirstName" wrote:

And cache preview size ... this is what I observe: A small import, 4 images, each with sharpening and curves adjustment, in the browser I select the first, it takes 2 seconds to render, then I select the next and the next again and then the last. Each takes a few seconds to render.

Now I select the first image again, and it takes 2 seconds to render ... so where exactly was the preview image cached? Well, sometimes if I'm lucky it will be cached, but normally not, even if I cycle between just two images, most of the time C18 or 9 is regenerating the image. Most of the time there is _no_ caching going on - at that is what makes C1 really suck.

If it takes 2 seconds to render and image, or even 5, I can deal with that - IMO it should be faster, but I don't get the feeling the GPU is being used. However, what is really difficult to accept is that simple switching between two images should require constant image regeneration. There is clearly a fault, either mine by using a wrong setting, or one with the application - a generated image preview should show in an instant.

This is my observation as well. Despite everyone saying to set preview size as large as possible (which does slow import/preview generation as you'd expect) I still never see any difference in speed flipping through images. C1 does pre-cache the next image in line, but if going too fast through them, or going back, it just regenerates it on the fly every time, no matter the preview size. It's not slow per se, but it's not fast either. The 2 second rendering time seems about right. There's about 1 second of super pixellated image, then 1 second of slightly pixellated image, before it's finally fully rendered.

Here's a video. Be sure to watch at 1440p https://www.youtube.com/watch?v=fp8XDwfSdl4

You are luckier than I am, rendering times for me are more like 4-6 seconds and it is unbelievably frustrating... And regarding the cache, more often than not it needs to re-render the image when I select a new one and go back. CO is the only software on my Retina iMac that behaves this slow and it is driving me nuts since it the the software I use the most 😭

0

Jeffrey Jakucyk

May 21, 2016 20:49

It does seem like simple math is causing a big part of the problem here. I can see improvement in rendering time if I shrink my C1 viewer window, as you'd certainly expect. While the resolution of a 5K iMac is double that of my non-retina 27" cinema display in length and width, that means there's 400% as many pixels total. What if that 4x increase in pixel count translates into a greater than 400% increase in required processing power?

Even if it really is just a linear relationship, CPUs aren't 400% faster today than they were 8 years ago, they're about 70% faster at the same clock speed. So a 4.0 GHz Skylake iMac is still only 240% faster than a 2.8 GHz Harpertown Mac Pro in single-threaded tasks. In multi-threaded tasks though (which is what image processing in C1 is), the 4-core iMac is only 20% faster than the 8-core Mac Pro, while still having to push 4x as many pixels. So I can see how if the GPU can't handle the task for whatever reason (and GPU speeds have been increasing significantly compared to CPUs), then disabling OpenCL isn't going to help much unless you shrink your C1 window down to fill only 25% of the screen.

0

Morten Obbink

May 22, 2016 11:46

in my MacBook pro i7 ssd drive the captire one pro is so slow that it is useless. Lightroom works pretty good.
so I hope there will be a fix soon

0

Christian Gruner

May 23, 2016 19:03

[quote="NN634936040085233037UL" wrote:
in my MacBook pro i7 ssd drive the captire one pro is so slow that it is useless. Lightroom works pretty good.
so I hope there will be a fix soon

Can you be more specific? We can't do much with a report saying "it's slow" really.

0

Christian Gruner

May 23, 2016 19:26

An advice for all of You running with the 5k iMac. We have found that using anything above "Best for display" in regards to screenresolution, can have a serious performance impact. If using the "looks like 2880 x..." or "looks like 3200 x ..." OSX actually tells CO that it's resolution is respectively 5760 px or 6400 px wide. That means, given a big enough Viewer, that even the 5k previews are not big enough. Thus full pipeline runs, not using the proxy.

Also, when buying a 5k iMac, get the GPU with 4 gb memory, not the 2 gb version. This also increases performance, as the more data / bigger chunks can be loaded into ram immediately.

We are looking into ways of speeding up performance, but I can't say much just yet.

Edit: We have just launched a new Beta-program, please sign-up. The more 5k iMac users we can have in a tight feedback-loop, the better.

viewtopic.php?f=61&t=23786

0

Sigurdur Gilbertsson

May 24, 2016 17:30

[quote="Christian Gruner" wrote:
An advice for all of You running with the 5k iMac. We have found that using anything above "Best for display" in regards to screenresolution, can have a serious performance impact. If using the "looks like 2880 x..." or "looks like 3200 x ..." OSX actually tells CO that it's resolution is respectively 5760 px or 6400 px wide. That means, given a big enough Viewer, that even the 5k previews are not big enough. Thus full pipeline runs, not using the proxy.

Also, when buying a 5k iMac, get the GPU with 4 gb memory, not the 2 gb version. This also increases performance, as the more data / bigger chunks can be loaded into ram immediately.

We are looking into ways of speeding up performance, but I can't say much just yet.

Edit: We have just launched a new Beta-program, please sign-up. The more 5k iMac users we can have in a tight feedback-loop, the better.

viewtopic.php?f=61&t=23786

I've already signed up for the Beta program ! Looking forward to take part and see some improvements on my Retina iMac 😉

0

Morten Obbink

May 24, 2016 18:13

[quote="Christian Gruner" wrote:
[quote="NN634936040085233037UL" wrote:
in my MacBook pro i7 ssd drive the captire one pro is so slow that it is useless. Lightroom works pretty good.
so I hope there will be a fix soon

Can you be more specific? We can't do much with a report saying "it's slow" really.

I have imported images set the images preview to 5120 px but after it is Finnish it can take me up to 30 seconds before i can view the image in 100% view. i have set it to never expire and it does this every time i try to zoom in, trying to go throw images takes about 15-20 seconds often before i can view the image and same with next image etc.

0

Comments