Developing images is something that I don’t watch either. I recently developed 60 test images with PureRaw and got them developed, with DeepPrime, in about 6-8 seconds per image.Ĭomments: While I tested all this on a 2020 M1 MacBook Air (which is not the most powerful Apple Silicon Mac around), I’d not see an immediate need for you to buy a new MacBook. Please note that DPL4.1.1 is not yet made for M1 and had to run using Rosetta 2. MBA spec.: 13in 8 core CPU, 8 core GPU, 16 GB RAM, 1TB SSD IMac spec.: 27in 8 core 3.6 GHz i9, Radeon Pro 580X 8GB, 40 GB RAM, 2TB SSD Here are the figures for the export of 60 images (identically set on both Macs) to 16bit TIFF: I’ve tested a set of images on a 2019 iMac and a 2020 M1 MacBook Air. I’m pretty sure about it because it’s the way to go. Should I really expect images to process in about 40% of the time on an M1 machine? Or do the benchmark figures not really directly relate to images processing times? And do the main chip multi-core figures relate to the processing speeds? Or is that more the speed of the graphics card chips? My MBP multi-core benchmark figure is about 4700 (and is currently set to process 5 images simultaneously) with the new M1 MBP multi-core benchmark figure being about 12,200, or about 2.5 times higher. When I process raw images with PL5 it generally takes a little less than 4 seconds to generate jpgs, with my latest test processing 27 raw images in 100 seconds. But I am curious about how much the multi-core benchmark figures actually translate into higher processing speeds with software like PL5. When I bought the MBP I purposefully bought a model with high specs, thinking that it would dissuade me from wanting to upgrade quickly, and that has pretty much worked out. My wife recently suggested that I might want to upgrade to a new M1 MacBook Pro since they have significantly higher benchmark figures, but I am not sure how much the multi-core benchmark figures really apply to image processing. I currently have a 2018 MacBook Pro (i9, 32GB RAM) running Monterey.
0 Comments
Leave a Reply. |