M1/M2 Pro & 5k screen experience
Hi, Looking at replacing my MBP15" 2018 with an apple silicon to better support C1 and use with LG 27" 5k screen. Cause today its NOT satisfying. To much mosaic when going forward and backward between photos.
I am enthusiast user with a budget going for M1/M2 Pro. Either new Mini or a MBP again. I only doing basic culling and edits. No panorama, HDR or thethering. But I wish that new computer would give me no delays when viewing previews in full screen and doing basic adjustments.
Camera files are currently RAW 20-24 MP from Nikon, Fuji, Sony.
With this goal it's not easy to know if a Mx Pro 10/16 or 12/19 core would be enough. Specially if 16 GB RAM is enough.
So super interested to know both positive and negative experience using a M1/M2 Pro or even basic M1/M2 with Capture one. But important parameter I understood is the resolution of monitor which is 5k in my case.
-
I have an 8GB Ram MacBook M1 Air. I've noticed delays in the creation of previews with 4k display. I'm using an external drive to hold my images and I think that may be the problem. Its not SSD and as C1 uses proxies for images it is constantly reading from that external disk.
A fast SSD and USB-C connectivity are likely as important as RAM, if I were buying a new laptop I would go for something with at least 16GB maybe even 32.
There are other posts in C1 v22 forum about poor response times with C1. I think C1 does a lot of processing in the background whereas M1 chips seem to run faster with foreground tasks. I could be wrong about this, perhaps someone with more insight will add their opinion.
0 -
Thanks LVS for response. I did find some interesting threads in C1 22 forum. Mostly about standard M1.
I notice that import and export is used to measure performance. But those tasks I don't care much of. For me it's important the performance when working with photos.
0 -
Hi Olof,
I am currently using a Mac mini equipped with a M1 chip with the same LG display as you are using.
Performance is frankly disappointing with Capture One. There is a lot of lag when scrolling through pictures in full screen. I am not using external drive so this is not the source of the issue. I believe Capture One is just very poorly optimised to take advantage of Apple own chips. I have found that reducing the size of the C1 window to about a quarter of the full screen resolves the problem but of course this is a very frustrating solution.
I ordered a Macbook Pro with an M2 Max chip a few days ago hoping that it will make things better. I can report back when I get it if any interest.2 -
Etienne Cosnefroy Thanks for sharing. For sure interesting to hear how you experience the upgrade to M2 Max. Please share cores & RAM. And also if you have possibility to connect to an external monitor with higher resolution.
Not only that C1 is not maximizing performance, its complex to understand when CPU, GPU and RAM is used.
I also experience improvements on my MBP2018 by reducing image size. Stepping down from 5120 to 3840 preview size makes difference. Viewing photos in 3840 means I don't go full screen. What I find tricky is that it's then also impacted by how exact the image viewer matches preview size. Meaning if image viewer is 3800 C1 must recalculate, comparing with 3840.
0 -
Sure I'll keep you posted. I should receive it by end of this week.
I ordered with these specs: CPU = 12, GPU = 30, unified memory = 32Gb.
0 -
Hi Etienne,
any news on this?
I am just asking because I also plan to order a M2 Max for CaptureOne.
0 -
Hi Christian,
I received my MBP with the specs I described earlier (M2 Max, CPU = 12, GPU = 30, unified memory = 32GB). Performance with a 5K display is better than my previous Mac mini M1 but still not great, which is frankly appalling knowing the computing power of this machine. Performance is great when using the laptop on its own.
When I use the display I still get a little lag when browsing across my pics in full screen. Reducing the size of the preview helps, as does reducing the size of the C1 window.
0 -
Hi Etienne,
thanks a lot for your reply.
For me, this is good to know, as I have the 5K LG Display, too.
I am currently using C1 23 on my MacBook Pro (2,9 GHz 6-Core Intel i9) with 32 GB RAM and the lag when browsing the pics (2s - 3s) is really obstructing the workflow.I guess the lag is for you below 1s when using full screen on the LG?
0 -
It's about 1sec in full screen with preview size set at 3,840px (which is the best setting in my opinion)
0 -
Etienne,
Very interesting. I am about to order a M1 max 10CPU/30GPU 32MB which being sold out in my location.When you view in non full screen mode. How is the performance then wen going forward and backward between images. With panels visible the image should be very close to 3840 px.
As I understood the program works you should have 5120px preview for optimizing performance in full screen. Hopefully it works better.
BR Olof
0 -
I might be misleading when saying full screen. I mean with the C1 window occupying the entire screen. I always have panels visible.
When reducing the size of the window then the performance improves dramatically.
0 -
OK. In that case it’s even worse. If zero lag is a relevant goal..
Thanks a lot for sharing. This is more useful than YouTubers
0 -
My Macbook M1 Pro runs also slowly when I switch between images. My PC from 2018 runs faster.
According to Capture One, the native resolution should be used for the preview images. A smaller or larger pixel width delays the loading of the images.
The Macbook needs 3456 pixels. But Capture One only offers 3840 or 2880. That's probably why it's slower while loading.
0 -
The Macbook needs 3456 pixels. But Capture One only offers 3840 or 2880. That's probably why it's slower in the store.
Well I remember (from the back of my head) it should be the next bigger setting, so 3840 in your case, but it is only a rule of thumb and depend on the machine in question and your usage (e.g. zoomed in when switching and the actual pixel size of the C1 viewer window). It might even be that the smallest possible preview size (forcing C1 to develop the raw on demand rather than actually using the preview) is equally fast (or slow). On my machine (custom build PC) I do not notice any real difference actually. Play with it, also maybe play with hardware acceleration on vs. off. Note this comes from a pure Windows user so maybe there are Macbook M1 Pro user who have a more specfic advice.
0 -
Hi, now having a M1 Max I experience still performance issues when working with 5k screen. I met C1 product management in a mini exhibition some weeks ago. Learned that when browsing photos the program cache 3 photos in the direction going. By that I learned to slow down a bit when doing my culling. Product management representative also told be that its better than to big preview than to small. If too small the program will render a new one. If too big it will try to fit.
FirstName LastName My testing is that working window should be as close as possible as then preview size. I do my work mostly with toolbar on top, miniatures on the right and menu on the left visible. Then the view size of the photo is really close to one of the preview size. I have a monitor 5160 wide. I do previews in 3840. For you I would recommend render 2880 and find a working area matching that. I have done screenshots to measure dots in width.
With apple Silicon my understanding is that hardware acceleration shall be auto. At least if running an C1 version where optimization have been done. Turning off was an option with Intel machines.
1 -
The 3-photo cache is very obvious when using C1.
It does not change anything to the fact that C1 implementation on Mac with 5k display is a disgrace.
1
Please sign in to leave a comment.
Comments
16 comments