thank you
with the nvidia studio 572.83 it’s ok
1 Like
Sure Laptops might be a different problem and some times we have to make compromises. I might have had to do that too if I had been a gamer but I´m not. 
In my case version 9.0.2 made a world of difference - night and day - but so far just with 572.83. For me the latest driver doesn´t work at all. For others it does. The only one that can check what is working for you is you and especially if there are compromises to do. I´m glad I don´t need to do any this time.
2 Likes
Maybe the quiet ones are happier. I’ve spent about three hours editing RGB, ProRaw, and RAW files using v9.0.2 Build 68. No problems with any of the AI masks or otherwise. Will report back if that changes, but so far, so good. Notice that I have not updated the NVIDIA driver, adhering to the old school advice: …“if it ain’t broke, don’t fix it.”
Windows 11 Pro
GIGABYTE Z890M AORUS ELITE
Intel Core Ultra 9 285K
DDR5-5600 64GB
NVIDIA GeForce RTX 4070 SUPER 12GB with studio driver 566.36 (12/03/2024)
NVME PCle Gen4 M.2 SSDs (primary and secondary)
2 Likes
Yep, same here, when checking for an update
That’s a good point. Interestingly, ‘Capture One System Requirements and OS Support’ state the following:
For Users with 4K Monitors
Working with 4K displays is more demanding. For a smoother experience in Capture One:
- Double the base system specs (e.g., 32 GB RAM, high-core CPU, faster SSD)
- Use a high-performance GPU with ample VRAM (8 GB or more on Windows)
- On macOS, opt for Apple Silicon Pro or Max chips, which handle 4K editing efficiently
From C1 16.6 release notes:
4K monitors
For optimal performance on 4K monitors, we recommend doubling the initial specifications due to the increased computational demands. Additionally, investing in a high-performance GPU with ample VRAM is highly recommended for these configurations to handle the intensive graphics processing.
1 Like
Yes, I updated my trial but cannot see any difference. Find a subject still causes it to fail and have to restart. I find I can hover over various parts of the image such as the sky, people, animals and vehicles and they are detected and masked. It just seems to be when you request the AI to find things from the drop down menu.
Yesterday I recieved an email to down load a program to run a diagnostics and send the resulting ZIP back. Hope it helps to resolve this NVidia problems.
I think they are taking it well over the top there Wlodek.
I don´t have any problems at all using Capture One with 16 GB RAM and 8 GB on the GPU. … and a 4K monitor I have too.
There is a trade off for them. Putting the demands high will give them less support problems when they always can refer to the official system requirements - if the customers don´t meet them. BUT, it may as well put customers off so they go elsewhere instead.
There is also at least two problem scenarios:
The first is driver or software problems where bugs results in errors that totally stops a process and in worst case is not properly taken care of and in worst case results in so severe problems that the whole program stalls and a reboot will be the only way to release the stop.
The second is that it is so demanding that some hardware configurations chokes. To some extent that can be handled by diffent optimization and in some cases one can at least prevent crashes to the price of a little longer processing time. Historically we have seen many cases where the processors kernels and threads has not been utilized efficiently.
I’m pretty convinced the developers at DXO will improve this situation relatively fast since they have this as a top priority now and they have already done a lot even if they haven’t adressed everybodys specific performance issues yet . Even Capture One had serious performance problems when their AI-masking was new and it has been improved in several steps that specifically have targeted the performance issues.
Thanks for testing the driver versions - I’ll stick with 576.52 which works - although PL9 is still very slow …
I have no issues using Capture One with AI masking on my 6Gb GPU … neither Affinity Photo … really good performance. PL9 is so slow compared to PL8.
When you get a crash - Internal Error that prevails there is quite a lot of ways to handle that depending on what system you are sitting on.
As usual I asked Chat GPT that gave me a long answer below. As a Windows user i have picked the most simple way for a user to clear problems like that if they occur:
So for Windows use: “CTRL+Shift+Windows-button+B”
It is a hopeless sequence that works best pressing the first three with the left hand and the B with the rigt. What this doeas is to restart just the GPU driver and it takes just a second.
Below is the whole GPT 5 answer:
How can I clear the memory on my Nvidia Geforce RTX 3060 Ti GRU-card? Is there a command for this?
ChatGPT sade:
Yes — you can clear (or “free”) GPU memory on an NVIDIA GeForce RTX 3060 Ti, but the method depends on what you mean by “clear” and what environment you’re in. There isn’t a single OS-level “clear GPU memory” command, but there are several ways to reset or free VRAM that’s being used.
Here’s a breakdown:
1. If You’re Running CUDA or ML Code (e.g., PyTorch, TensorFlow)
When running machine learning code, GPU memory often stays allocated until explicitly freed.
For PyTorch:
import torch
torch.cuda.empty_cache()
This releases unused memory back to the CUDA driver so other processes can use it.
For TensorFlow:
You typically need to clear the session:
import tensorflow as tf
tf.keras.backend.clear_session()
2. Using nvidia-smi
The NVIDIA System Management Interface (nvidia-smi) lets you check GPU memory usage and manage processes.
- To see what’s using GPU memory:
nvidia-smi
- To kill a process that’s holding VRAM:
nvidia-smi
Find the PID of the process using memory, then:
sudo kill -9 <PID>
This will free the memory that process was using.
- To fully reset the GPU (Linux only):
sudo nvidia-smi --gpu-reset -i 0
(-i 0 selects GPU 0; change if you have multiple GPUs.)
Warning: This will kill all processes using the GPU and reset its state.
3. Rebooting the GPU Driver
If memory is “stuck” due to a crash, restarting the driver can clear it:
- Windows:
- Press
Ctrl+Shift+Win+Bto restart the graphics driver. - Or simply reboot the system.
- Press
- Linux:
sudo systemctl restart display-manager
(or restart gdm, lightdm, or whatever display manager you use).
4. If You’re Gaming or Using General Apps
There’s no direct command to “clear VRAM” like with system RAM. The GPU memory is automatically managed by the driver — closing the app using VRAM (game, browser, video editor) is the only way to free it.
Would you like me to give you step-by-step instructions for using nvidia-smi to identify and kill memory-hogging processes (the most common way to clear GPU memory without rebooting)?
Below I have tried to compare a picture made by just freely hoover and click an area and add three different parts: Background and then the bird and the log (with two submasks). I have desharpen and blurred the background and sharpen the bird. With this method I see no problems at all using Photolab 9 and it is really fast and responsive too when working with the picture.
I have exported two JPEG in 100% quality - one in full size and one in 4K. The first took 14 seconds and the reexport took 13 seconds.
Below I have masked the same areas but using two of the premade AI-masks instead (Animal and Background). I had to mask the log on free hand because that was the only way to do it. I added about the same changes to each mask as with the first one before exporting two JPEG in 100% quality - one in full size and one in 4K.
BUT and here is the BIG thing:
The first two exports of the two images made with the AI freehand masking-hoovering-click select-method on the upper RAW took 14 and 13 seconds to export with Deep Prime 3 and the changes I had applied to the masks.
The third export of the two images made with the AI-predefined masking preset method on the lower RAW took 1 minute and 11 seconds or 71 seconds to export with Deep Prime 3 and the changes I had applied to the masks.
it is 5 times longer export time. So, I see this a very clear example of how much more demanding the premade AI-masks are for the system resources to handle.
The lesson I take with me from this little test is that I will always better use the freehand hoovering method instead of the premade AI-masks when working with a single picture at the time. It is faster and much more efficient in all respects both when editing and printing and it will protect you from pushing your system to Internal Error crashes and repeated reboots.
It also has to be said again: I´m using a Windows 11 machine with 16 GB RAM and an Nvidia Geforce RTX 3060 Ti with 8 GB VRAM and Photolab 9 .0.2. which is the last version today 20th september. I´m using a 17 generations old GPU-driver because it is the one that has proven to be the most stable so far (not the one recommended by DXO but version 572.83).
With using the Add-selection and/or Add-area tools with the freehand-hoovering-select-method I have no problems what so even with speed. responsiveness, printing or exporting no matter what I do with the pictures AS LONG AS I DON’T USE THE PREMADE AI-MASKS IN THE DROP DOWNLIST. Using them today might seriously affect both your productivity and/or your system stabilityy.
1 Like
From what I can gather, the difference between “hovering selection” method and predefined AI masks, is that if you have a set of photos from a burst shooting method then you can copy the masks from one photo to all the others and AI will handle the slight changes in subject from one photo to the next.
This could be a big time saver but not one I would generally use as I would left one or two of the best from the burst and manually edit those.
Other than that, I work the same as you and either use the hover method and, depending on the difficulty of the subject, I may even use the Auti Mask tool.
I am using the latest NVIDIA drivers which work well except PL9 fails on the predefined AI masks, so I simply avoid using that tool until it is fixed.
You are absolutely right. When I avoided using the AI presets and selected the area to be masked manually the overall performance and export times were excellent. While there seems to be some performance issues remaining such as when using the Local Lens Sharpness Optimization slider, all in all PL 9 now works extremely well.
Mark
Yes we will definitely have a need for the premade AI-mask presets too, like they have shown with the workflows in Capture One but for me that is not a show stopper noe,
Mark, what I have hard to grasp though is the fact that the present performance differences are so huge. I really hope they manage to sort this out ASAP.
1 Like
(typos in previous post - 6.01 and 6.02 should be 9.01 and 9.02)
Update:
With my Graphics computer (32gb, i5-10400F CPU, GTX1660 Super 6Gb, Driver 511.09) updated to PL9.02, I have now processed 77 photos each with several AI masks and various other edits for lighting (night scenes). Processed with DP3.
There were no issues during processing and exporting with an average export time of just under 10 seconds each.
I find that the average processing time is about the same as PL7 but, with the AI masking, I tend to spend more time adjusting scene elements.
On this computer, I don’t see much difference between 9.01 and 9.02 as some others have but 9.02 did not work on my office computer as I mentioned above.