I’ve upgraded from PL 7 to PL9 and am having such significant problems that I whether PL9 is compatible with my MacBook Pro Intel Core i9 system, or my Sony 61 MB RAW files.
The biggest problems are with AI masking, but there is also loss of functionality in the basic Image Browser function, so that the new stacking feature is unavailable.
As a great DxO PL fan, it saddens me to write that I find the AI masking function essentially unworkable - flickery and unstable, inaccurate, slow, crashy. The subject pre-sets don’t work at all. I haven’t yet been able to produce anything worthy of export, but I fear further problems there.
I would be very happy if someone could tell me that I’m doing things wrong or that there’s a simple answer to this. I’m even ready to upgrade my computer if it means that PL9 works as well as it evidently does for some users!
Naive question: is the AI function self-contained in the downloaded software, or does PL go online each time it is used, for external AI input? Might my low quality internet connection be part of my problem?
…that got me and my i9 iMac, but I also have a 2020 M1 MacBook Air. AI masking works okay on it, but DPL9 still has a lot of things that need fixing.
I’d stay away from DPL9 until it’s 9.2 or higher…and I’d also not update to macOS Tahoe, which is almost as difficult to use - from a UI design point of view - as DPL.
I am a 100% wintel person who does not use AI masks in PL, so I am fine … when / if I need such masking I pass the output from PL through Adobe’s ACR instead of 1/10 cooked products.
AI masking in PL9 appears to demand far more system resources compared to earlier versions. On older Intel-based MacBook Pro machines, especially with very large RAW files like 61 MB Sony images, the software can become unstable. A clean reinstall and checking for the latest GPU drivers might reduce some of the flickering and crashes.
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
7
Have you tried avoid using the premade AI-masks in the drop downlist and instead just hoover over the areas you want to to select and just click them or use the area tool and just select the objects you want to mask. That way of doing it do not use the premade AI-models that seems to overload or crash the process. It works perfectly fine and is far more fast and effective than the other method.
So there is in fact two ways of doing AI-mask selections on Photolab - the one based on the use of premade AI-masks that do not work for many and perhaps the less obvious the freehand-hoovering-clicking-masking-method that seems to work perfectly fine for most people after downgrading at least especially older Nvidia RTX-cards with the driver DXO has recommended or using the 572.83-driver that works for many others od Windows users.
There are several treads here at DXO Forums where you can read about these problems. When a lot of people starts to create an endless number of new treads it just gets more confusing than thisalready is.
Echoing this advice - the pre-made AI masks don’t work for me (subject, sky etc.) but the AI object selector tool does work, albeit a little slowly on my machine.
I didn’t even have to downgrade my drivers for this one. It works with the latest game-ready ones from nVidia, so long as I don’t select the “pre-made” drop down options.
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
9
Yes for some systems but for me it has been so bad that Photolab crashed as soon as I have opened it with 580.x or 581.x- drivers.The only thingvthat worked for my card was the 572.83-driver.
It seems like every type of card may have its own special problems. It has been very much a case of trial and error.
