Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
303
OK its up to you Just a suggestion.
Personally I don´t care what Nvidia might have tested.
These drivers has been used by our cards as late as this spring so I don´t see the point and Nvidia will never test a machine like mine either sooner or later because the problem with the Windows- compared to the Mac-world is the endless variations of hardware/software/driver-combinations. The Apple-world is far more limited and controlled for good and bad.
I was recommended another driver to downgrade to by DXO but that driver-version wasn´t even in the list of present drivers for my card at Nvidias page. So who recommended that as a general solution without even checking if that alternative was even possible to download - there wasn´t even a driver there to test :-.
It doesn´t cost anything to test and if it doesn´t work it is just to revert to something else. What is there to loose? … and it obviously was a lot to gain to test by my own instead of just listen to DXO or Nvidia. I don´t know how many different drivers I have tested before I found 572.83. I had limited problems with that too before version 9.0.2 but PL 9.0.2. plus the 572.83 happened to be the match I was looking for as a suitable workaround until the problems are fixed finally by DXO/Nvidia.
I agree with you 100%. I like your reference to “suitable workaround”.
It certainly does not fix all of the issues, but for many of us 9.02 does seem to resolve some of the most pressing ones. I suspect over the next several weeks, and perhaps months, that DxO will continue to address various bugs and performance issues. I am certain version 9.02 is not intended as a final fix, merely an interim update step along that path.
I am very pleased that DxO was able to resolve some of the more serious performance issues for Windows users in this release. Why some Windows users are not having any luck with this release I cannot say.
I’m extremely disappointed with PhotoLab 9. It’s crashing all the time, and the new AI masking feature is basically broken — applying a mask immediately crashes the program. If I add another mask, it just freezes. This makes PL9 impossible to use right now.
Today, I encountered the same error as in the screenshot - “Failed to convert grid to inputimage space”. It’s caused by using Reshape Fusion to slightly improve the building in background, with Deep Prime reduction selected (XD also shows the same error), then using any mask (not just AI!) and attempting to adjust the “Luminance” and/or “Lens Sharpness Intensity” sliders. Using the other sliders, including “Force Details,” doesn’t cause this error. The good news is that it doesn’t crash the program; simply reset both sliders to their default values.
This is v9.0.2, Windows 11 with the current GTX1660 Super 581.xx graphics card driver. The program otherwise works correctly, except when trying to use predefined AI masks. The “add to selection” and “add an area” options work fine. Overall, it’s not a major issue, as I can fix the warped building after exporting the image, but…
I agree with you. Unfortunately, the recommended workaround is not even working for me. I rolled back to NVIDIA GeForce driver version 572.83, but that did not resolve the issue. Has anyone found a solution that works? Any suggestions would be greatly appreciated.
Thank you for your suggestion. I’ve seen in your other posts already. Unfortunately, in Windows world it happens too often that a solution which works for some, may not be acceptable by others.
I don’t use Local Adjustments too often, and then Control Points can mostly do what I need. In few cases when AI masks were useful, I’ve used Capture One (which I use mainly for Face Retouch). Hence I’m not too excited about PL AI masks beta version. Tested it mainly having bokeh smoothing and WB corrections in mind.
For my type of work the key change in PL9 is the ability to preview DeepPRIME results. When switching photos, I have to wait 1-3 seconds for a preview to complete (as expected), but afterwards the the zooming and edits are updated instantly. I like also starting PL9 with the last previewed photo – minor thing but some of annoyance with PL is gone. Not sure yet about Lens Sharpness Optimization changes, but I don’t expect anything spectacular, since there’s little space left for improvement here, for my gear at least.
So far, these new features work flawlessly for me, like other functionality present already in PL8+FP7+VP5. Tested several hundred high ISO raws from concerts in dim light and low ISO “vacation photos”. Too few use cases tested though, so it’s still inconclusive.
EDIT: AI mask problems have probably multiple root causes. Apart from GPU VRAM memory management, it seems there might be issues with OpenCL JIT compiler and perhaps some problems with OpenCL semaphores and Windows interoperabilty. Only insiders can tell…
It same for me as the predefined ones for me and no problems when marked manually. I had an email yesterday to download a diagnostics program to run and sent the resulting ZIP file back. They are clearly at the moment unsure how to resolve.
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
310
It is very strange that all these different Nvidia GPU-cards are reacting so differently to these various drivers. Not even the RTX-cards seems to have a lot in common. Unless they have a common problem I guess the risk is that these problems might not be solved at all and left behind with a recommendation to upgrade the hardware.
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
311
The only thing we can do for now is to upgrade to Photolab 9.0.2. and test the different Studio-drivers available for just your specific card - it is really worth it!
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
312
I guess even you will have to try to downgrade your driver. The one you are using now seems to be the newest driver for your card. Many have problems with the recent drivers. You will probably have to look for the Studio-drivers at the very bottom of the driver list for you card to find one that might work.
When I first saw your picture I recalled that I almost took exactly the same motif when i paased over the bridge to Skeppsholmen in Stockholm.
I found a driver from March '25, but I won’t install it because I’ve been working more with Davinci Resolve 20 lately, and I’m afraid I might have trouble getting it to work. Starting in October, I’ll be using PhotoLab more intensively to re-develop old RAW files from 16 years ago, including those from Sweden. Yesterday, I started my first attempts, organizing the collection into projects, and so far, everything is working. The final image I get from PL9 is much, much better than the one processed a dozen or so years ago. For now, I don’t need to use predefined masks, because both selection options work fine. I also noticed a bug with Reshape Fusion yesterday, but that’s also fixable. I don’t have a problem with exporting, despite the comments of many people, not just in this thread. PL9 is a strange release. On the one hand, I find it very comfortable to work with, but on the other, I’m fully aware that the program still needs significant work on its stability.
Lot of potential with this release but count me amongst those disappointed, I was ready to plop down my money but until all the issues with NVIDIA cards and AI masking are fixed I can’t justify it, which is a shame because DXO is still my favorite and the AI masking works great until it doesn’t work at all.
I upgraded and it didn’t do much. Still buggy, lagging and freezing. I also upgraded to latest drivers like DxO advices. Testing different variations…it is not our job. It is DxO’s job! DxO’s job is to deliver fully working tested product that works perfectly with their recommended setup. It is not users job to do testing.
Perhaps you’re correct. However, I installed the older Nvidia driver 572.83 and installed PL 9.02 and now I’m happily using almost all the functionality with no issues at all.
Complain if you wish and argue that that it is not your responsibility to test workarounds for some of the initial problems with PL9, but, in the end I, and others here, now have a working version that I’m happily using with my images, and apparently you don’t.
On Wednesday I ran a diagnostic program down loaded from DXO as part of my on going contact regarding my RTX 3060 subject masking problems. the resulting .ZIP file was then returned to them.
Yesterday I had this reply from them,
This model is affected by a known issue in WinML. While waiting for a fix from the manufacturer Nvidia, you have two options: use the CPU for these processes or avoid AI mask keywords. We are monitoring the progress of the fix. We will keep you informed once a solution is found with Nvidia.
For me the CPU works but is slow and time consuming I had already found. It is clearly the AI mask keywords that are the problem. Hovering over and clicking on a subject works.
Good for you if you found a workaround, but that doesn’t change the fact that DxO shipped a broken product. Reverting to old drivers just to make a brand-new release barely usable is not a solution — it’s a sign of poor quality control. Users should not have to spend hours testing, downgrading, and troubleshooting just to get basic functionality working. DxO’s job is to deliver a stable, fully tested product on recommended and up-to-date setups. Anything less is unacceptable.
Anyway, congrats on finding a workaround — here’s your cookie … meanwhile DxO should be the one doing the baking, not the users.
The Nvidia driver version 572.83 did not solve the AI errors for me. After reverting to version 572.42, I was surprised to find that I could use the AI mask without encountering errors.
566.36 was the version I was on when I started using it and it didn’t work for me either. It doesn’t seem like using newer, older, or recommended drivers makes all that much of a difference.
… meanwhile DxO should be the one doing the baking, not the users.