![]() ![]() Once again, after multiple rounds of testing, the medium format file exports averaged an improvement of between 30 to 35-percent. The 16-bit TIFF export test on the previous version of Capture One completed in 1,236.2 seconds and the M1 version finishing in only 934.2 seconds for a difference of 301.99 seconds. Exporting 150 100-percent JPEGS in the previous version of Capture One resulted in an average export time of 1,360 seconds when the M1 version did the same job in just 1,008.6 seconds for a difference of 351.4 seconds. With the medium format Phase One photos, I found similar results. The TIFF export test for the Sony files produced similar results, with the previous version of Capture One exporting 16-bit files in 371.1 seconds and the M1 version exporting the same files in just 282.5 seconds for a difference of 88.6 seconds.Īfter multiple rounds of testing, the Sony file exports averaged an improvement of between 30 and 35-percent, which is pretty close to what the company claims in the release notes. On the previous, non-native version of Capture One Pro, that export of the Sony files took 412.5 seconds, while the new native M1 version did the same export in just 304.7 seconds, for a difference of 107.8 seconds. The Resultsįirst up was the export of 100 Sony a7R IV files in 100-percent JPEG and 16-bit TIFF output, and the results were impressive. Every benchmark is the average of at least three consecutive runs to adjust for any inconsistencies. These were used in a series of imports and exports in both session and catalog settings on Capture One Pro version 14.1.1.63 and 14.2.0.136 and were run on a late 2020 model M1 Mac Mini with 16 gigabytes of RAM and a 2 terabyte SSD Drive. Outside of silence, I’d also rather keep the CMP on Mojave which is a much more stable and reliable operating system than Big Sur.To test the various promises that Capture One Pro says its new version offers, I gave the program a sample set of 100 Sony Alpha 7R IV RAW files and 150 Phase One medium format RAW files (Phase One XF with the IQ3 100-megapixel back). Otherwise, I’d go back to running PhotoLab 5 on the Intel Classic Mac Pro. The M1 Mac Mini is really and truly silent even under load. I’ve been building “silent PC’s” and silent Macs for decades now and it’s always been a compromise. My interest in the M1 Mac Mini is it’s the first silent under load computer which I’ve had. PhotoLab 5 works much better under Big Sur on my Intel Classic Mac Pro with a WX7100 and 96 GB of memory (requires OpenCore and a fair amount of tweaking to run Big Sur on a Classic Mac Pro). PhotoLab 4 works much better under Mojave on my Intel Classic Mac Pro with a WX7100 and 96 GB of memory. ![]() While editing, PhotoLab runs fine but I’m not astonished by its power or how agile it is. The M1 Mac Mini more or less completely seizes up while exporting Nikon NEF files with DeepPrime. Keep in mind that I wrote “reasonably well”. The same technique can be applied with the built-in Activity Monitor. I’m running a utility called iStat Menus which allows me to monitor memory (system and PhotoLab) very easily. Thanks to the very fast SSD speeds of an M1 Mac Mini, opening and closing PhotoLab is not that big a deal. ![]() I then quit and reopen PL5 after any significant amount of work, particularly an export. The way I make PL5 run reasonably well on an 8GB M1 Mac Mini is to close almost all applications including browsers (or at least all windows) before opening up PhotoLab (this process is a nuisance and costs productivity). I’m struggling with an 8 GB M1 Mac Mini myself for now but will probably exchange it for the 16 GB version (got a very good deal on the 8 GB version and will not have any deal on the 16 GB version, it’s not just the book price difference). What settings are you using in PL5 to make it go faster ![]()
0 Comments
Leave a Reply. |