Nevertheless, if you’re ready to trash the DB regularly, you need not worry about restoring a DB. If you’ve used it for a long tome, it might have wandered off and list files that have moved or been deleted while DPL was closed. In such a case, you’d also restore the mismatches. PhotoLab has no built-in functionality that checks for such mismatches, but DxO might be working on it silently and come up with something in a few weeks/months/ears/millennia…
….after 9 years w/o change I‘m upgrading to a Mac Mini M4 Pro, 64 GB RAM, 1 TB SSD, 14 Core CPU / 20 Core GPU with 2 external Samsung 990 Pro 4 TB SSD‘s plus a ZikeDrive USB4 for each SSD.
On the monitor I haven‘t finally decided yet - probably I‘ll go for an EIZO ColorEdge CS2731.
A year ago I switched from 24" FullHD to 27" 4k (CS2740), costing me a good lens. With 164 ppi at 50-60 cm distance, it’s perfect for me, no turning back. The 27" size is the maximum I would use. The drawback of 4k was that I soon switched from 16/24mpx camera combo to 45mpx
Thanks a lot! So the 2560 x 1440 pixel resolution (CS2731) was no option for you obviously. I‘m just thinking because of some people mentioned the size of the text in the menues is very small with 4k…
After Win11 installation, I switched the setting System->Display->Scale from recommended 150% to 175%. No problems with that so far, even with my old eyes. It’s a personal thing, so better check yourself.
I tested Photolab 8’s Deeprime XD2s on both my five year old Win PC (i7-8700 CPU, 16GB memory, AMD 6650XT GPU) and the new Mac Mini M4 (24GB/512GB) using the Egypt and Nikon (5 images) raw files. To my big surprise, here are the results (both fresh install):
Something odd is going on here. From the results in the Deepprime Processing spreadsheet, the base Apple M1 has essentially the same export performance as your old Win PC. The M4 Pro should be much faster than the M1 from 2020…
@foto16 , @CHPhoto The following is from a batch run of 60 Egypt images (1 [M]aster and 59 VCs), VCs because they take a lot less space and work to create and manage.
The hardware is not particularly exotic, a Ryzen 9 5900X (Win 10) but matched with an RTX 3060 and the image resides on an NVME and exports are to the same NVME and the results are
So we have the CPU being throttled by the lack of GPU power and we get 516 seconds for 60 exports, i.e. 8.6 seconds per export with 3 export copies.
The 5900X has no onboard GPU (iGPU) so the 3060 GPU is handling the graphics output for the monitor which is expending a little GPU processor to keep those graphs and counts going, it mainly has a GPU memory impact but the 3060 is a 12GB card so no real problem there.
If anyone wants the DOP for the their own timing runs I have the 60 image DOP (easily tailored for less or even more images) and another DOP for a 10 image run.