I have just installed PL 9, whilst the AI masking is showing great promise, general performance leaves a lot to be desired, preview generation is very laggy to the point that regardless as to whether or not when making a basic local or global adjustment, the app is basically unusable on my machine, I have tried changing the automatic AI acceleration setting (Apple Neural Engine) to M1 Apple M1 GPU with no effect
My machine specs are;
Model Name: MacBook Pro
Model Identifier: MacBookPro17,1
Model Number: MJ123B/A
Chip: Apple M1
Total Number of Cores: 8 (4 performance and 4 efficiency)
Memory: 16 GB
System Firmware Version: 11881.140.96
I’m running macOS 15.6.1, the issue was present before I updated to the latest OS version
After further testing it seems that the lag when both making local and global adjustments is apparent after making an AI selection, making the actual selection seems reasonably snappy. The files are CR3 files from a Canon EOS R
PL9 works, but it’s rather very slow as soon as I use the AI ​​functions… My configuration: iMac 2020 i5 3.3ghz 6 cores. 24GB Ram, GPU AMD Radeon Pro 5300 4GB, macOS: 15.6.1.
I am also seeing the same problems with lagging when using the new AI Masking. The masking seems to work well enough, although I am still getting used to how it works and what mask to use where. Hopefully this can be fixed soon.
MacBook Pro, M1Pro chip with 32 gb RAM.
It seems like the AI features are really pushing the edge of performance. Only the latest will do. I’m fortuante to have recently bought a M4 Mac Studio and with the Apple Neural Engine selected for AI Acceleration, performace for me, so far, is reasonable.
Also here: The AI masks are far too slow to process when you apply them. It often takes seconds for the effect (e.g. simply changing the exposure) to become visible on the screen.
I think I’ll wait for a few more releases and stick with my current application for now.
Same here, but I managed a workaround by disabling "High Quality Previews’ in the settings. It’s something I can live with, but shouldn’t have to…but does the job until they (hopefully) resolve the issues.
I thought the PL9 problems were just with Windows 10 and 11 operating system software and the vast variation in Windows PC hardware: processor, memory, and GPU, but here are reports of Mac issues as well. I’m inclined to hold off upgrading for now, too. In the meantime, I’ll continue trialing the Nitro Photo app alongside DxO PhotoLab 8, which is still working fine for me.
I’m always about the new shiny things, so I didn’t mind the fact that there are issues with it. I still have 8 installed, so if I want to hold off using 9 until the issues are ironed out, I don’t mind.
I know it’s the nature of product (I’m a product designer by trade), but it feels like the users are the beta testers, even when something is out of beta. This kind of thing feels like it should have been tested before release, but that’s ok.
Quelle est ta version du driver graphique ?
Il y a des soucis avec les dernières versions v58x.xxx, il faut revenir en arrière et installer une 57x.xxx.
Not exactly a performance issue, I will check where to post this adequately, but I am a bit disappointed by the lost ability to use body calibration profiles for color rendering. Maybe I have to reinstall FilmPack, but I wanted to have the body profiles of my R5, R5II and GFXs.
Sorry, Joanna, but you are wrong here. You can have both speed and quality at the same time—just use Lightoom, either C or CC. I am running LrC, LrCC and PL9 on my 16” M1 MacBook Pro with 16 GB RAM, working on the same images for a review, and the difference is night and day. Every change I make in Lr is immediate. As I change adjustment values, I can watch the changes live on a high quality view—even after denoising. Switching between Fit and 100% and 200% is instant with no ’Correction Preview’ to wait for. DxO needs to own up to the fact that PL9 has some serious speed issues that I do not see with Lightroom. Funny how the fanboy reviews have said nothing about this.
I certainly can’t argue that some people are having performance issues but I can’t put my finger on why many of us, even some with older gear, like me, are not having these issues. I have always gotten both speed and quality at the same time with PhotoLab.
I am using an older Windows 10 machine, i7-6700 @240ghz, with 24gb ram. I recently upgraded it with a WD Black 2TB SDD, an Nvidia RTX 4060 graphics card and 750 watt power supply. Most of the raw files I work on are from my full frame Nikon Zf with its 24.5 mp sensor.
Except for the AI mask presets in PL 9, and a performance issue with the local Lens Sharpness Optimization slider, every change I make to every feature is immediate or close to immediate with an occasional lag of 1 to 3 seconds. In general I regard PL 9’s performance on my way less than state of the art machine not just acceptable but actually very good which is quite surprising given the older processor and memory.
Individual file exports using DP 3 take 5-6 seconds. with 8-9 seconds for images using XD2s Those export timings include the use of AI masks as long as I don’t use the AI mask presets. Batched exports are 1-2 seconds faster per image due to the reduction in export overhead needed for individual exports. I have also found that my PL 9 exports are actually a couple of seconds faster than they were in PL 8, which were already fast. I can’t account for why I am seeing this, but so far my comparative test results between the two versions have been consistent.
As a side note, I am not a casual PhotoLab user. I have become intimately familiar with every feature of every version of PhotoLab, Viewpoint, and FilmPack since acquiring the entire PhotoLab 1 suite in 2017 and have used PhotoLab almost every day since then.
I also have licenses for a number of other post processing programs and was a user of Lightroom on this machine years ago. Of all the PP software I have installed on my machine PhotoLab has the fewest performance issues and is by far the most satisfying to use based on my personal long term experience with it.
As I said, I can’t account for the struggles others are having, but I am not one of them.