Windows: Export may slow down
Implemented
Capture One 16.5.2 contains a change that enables massively parallelized export on machines with dedicated GPU. Under unknown circumstances, the GPU may stop flushing completed tasks and run out of resources during export, which results in an extreme slow-down.
If you think you are affected and want to make sure it is this issue, open Windows Event Manager > Windows Logs > System and if you have a Nvidia GPU, there would be error entries with
Source: nvlddmkm , Event ID: 13
The issue is fixed in version 16.5.5.
#222431
-
Frank Shroeter, very cool thank you. I'm going to try and put something together.
0 -
BTW, this issue also exists on Mac. But it seems a lot less prevalent. We currently have four cases, despite the majority of our users being on Mac. Windows support cases by now are at 45. Thanks to the analytics introduced with 16.5.4, we have a pretty good idea of the reach by now. 7% of Windows users are affected.
Again, we are very sorry for this and try to find a solution as quickly as possible.
0 -
Hello, could you please share the link for the support tickets I can't find the page. Thank you.
0 -
https://support.captureone.com/hc/en-us/requests/new?ticket_form_id=9771276605981
You need to be signed in on the website for this link to work.
0 -
Frank Schroeter submitted thank you.
0 -
DN - I completely agree.
If it is a refund, it is the problem that should be resolved as soon as possible.
1 -
Wait. So I am paying a subscription to revert back to older version? Now.... Remind me why C1 is pushing people to go with subscriptions. I understand that updates can sometimes break a previously fine software. However! It is well documented that this is a major issue and having your paid users to be your beta testers with no compensation is plainly ridiculous. C1 is heading very much like Adobe. I worked for Adobe as a tech support.
I run a business. This is not a simple slowing down of my process. It significantly slows it down to the point where I cannot run my business in a profitable way. So yeas, I reverted back to 16.5.1 which solves my issue but it's not the service I am paying for. Else I would not have gone with the subscription.3 -
An update on this issue: One thing that leads to this bug seems to be a crash in the GPU driver, possibly because we put too many tasks on the GPU. You can check if this is the case for you by opening the Windows Event Manager > Windows Logs > System and if you have a Nvidia GPU, there would be entries with
Source: nvlddmkm , Event ID: 13
One simple way to resuscitate the driver is to switch the screen(s) off and on.
0 -
Hi Frank, thank you for this information, in my case I can see the event in Windows Log >System as described. However, certainly in my case, whilst turning the screen on and off may clear the event and resuscitate the driver, the requirement to close down C1 Pro using task manager is not removed if GPU acceleration for processing is turned on.
The original workaround, "Turning off GPU acceleration" for processing is still the only solution.0 -
Paul Harvey, yes, that is not too surprising; the resource shortage will probably force other functions to not operate. We currently are testing two candidates to avoid running into this state in the first place. For one, I am confident enough to share it if you -or anyone else affected- feel like giving it a go. Let me know and I will share a link via your support ticket.
1 -
Frank Schroeter, I had a similar problem relating to the load on resources:
I running C1 16.5.2 on a Windows 11 Ryzen 7 5700U with a internal Radeon Graphics and I am quite satisfied with the speed. With the new version 16.5.4 I had the problem that the export sometimes no longer worked correctly: the files were processed very quickly and all exported images were partially or completely black. The export only worked again after restarting C1.
I had the feeling that the error always occurred when the CPU was previously at 100% load (from C1 or another program). I switched back to 16.5.2 and the error no longer occurred.
1 -
Goodness me. I was just sent home from a two-day event by a (now lost) client because I could not export images on the spot. Then spent a day cleaning the cooling system of my XPS and reapplying cooling paste, voiding the guarantee and eventually reinstalling windows from scratch. Why don't you guys give an update warning popup for 16.5.4??? That cost me literally 3000 Euros and a client!
2 -
Ard Jongsma I spent a good bit of time arguing against C1, telling them that they should at least inform users of the issue in the changelog, or give us the option to rollback to the previous export engine in the settings. Unfortunately they did neither, despite the fact that from C1's official stats they broke exporting of 7% of windows users.
I'm truly sorry for your lost client. Shame on C1. My work has been impacted by the issue too. It's sounding like they're inching towards a fix at least, but this never should've happened and it better never happen again.
3 -
a few things here.. C1 has had a few issues in the last year or more, which is understandable
os updates and all kinds of drivers, runtimes and so on.
but yes I agree that their inability/avoidance to inform about possible issues is quite annoying
I have had different issues where I had to contact support who sounded or acted surprised only for me to find out it was a known issue - instead of informing and just redirecting to a page of solutions - not that there is anything wrong with the support
I'm just getting tired of troubleshooting, reinstalling drivers, and runtimes - and often having to rollback or switch editor to finish a job
I really do get the comments that this is a subscription and it is annoying to pay for something you cant use, and also have to use an older version for reasons.
and also it gets quite irritating being bombarded with updates about mobile and other things instead of getting informed about fixes and indeed the issue getting fixed, I know new stuff is nice to advertise but so is stability and functionality
sure there is this thread and others - but why do the users have to search and find this themselves why not inform your users actively or even better yet proactively
2 -
Kevin Zhang, I have a very high tolerance level towards software developers. I want state-of-the-art stuff and I realise that there is a price I may have to pay for that. But when a developer discovers a severe bug that potentially affects hardware (and presents itself as a hardware error) and still chooses to continue to release updates that don't fix this error (16.5.3 and 16.5.4), they should simply warn when a potentially affected user (PC users in this case) wants to install. Popup: "Warning: some Windows users with dedicated GPUs experience export problems with this release. If you do, roll back to the last safe release (link) and keep an eye on the update fora (link). It's so simple, really.
1 -
Thomas Schneider, the issue you mentioned with black photos being exported is most likely a different problem; I am not aware of other reports on this. Please contact Tech Support.
Also, to get behind the problematic change discussed in this thread, you would have to go back to 16.5.1 or earlier.
0 -
I noticed the same issue after update to the version 16.5.4.
Export process stopped usually after few pictures.
After this change to Hardware Acceleration settings export works as expected using all hardware resources:
Just for curiosity, here is my configuration:- OS Name: Microsoft Windows 10 Pro
- Processor: AMD Ryzen 9 3900X 12-Core Processor, 3801 Mhz, 12 Core(s), 24 Logical Processor(s)
- BaseBoard: ROG STRIX X570-E GAMING
- Installed Physical Memory (RAM): 64.0 GB
- Graphics: NVIDIA GeForce RTX 2070 SUPER
0 -
I tried the new 16.5.5 now i can't export any images, before it stopped randomly during exports now it stalls before any images are exported.
A new twist, i tried a few times, no matter how many images i add, it randomly registers only 1-3 images before it goes into just using all gpu but making no images0 -
I have a similar issue when exporting more than three images or 1 image with two export recipes ( both .jpg) selected. However, the problem is inconsistent selecting 4 images and two recipes will work, slowly, but selecting 1 image and 2 recipes may not. I have tried this in Auto mode and the dedicated Nvidia GPU card option. Also, a point of notice, Nvidia Studio Drivers updated 30 Jan 25.
0 -
Could you check if you have nvlddmkm error 13 logged in Windows Event Manager?
0 -
After updating to version 16.5.5, the export process freezes after 2-3 pictures when I try to export immediately after editing. However, if I restart the application, the export works fine.
0 -
Hi Frank, yes 13 of them dated 01 Jan 2025.
0 -
More issues I am afraid, I have gone from a very stable version of C1 Pro 16.2 to a very flakey version 16.5.5 - Images take up to 20s to render particularly after down narrowing a few times to move between images. Using spot healing and or the healing tool, clone tool and moving between them causes the tool to work but not render the change made and then after waiting up to 20 to 30 seconds for the change to be made C1 crashes and will not open again. This issue still occurs after re-opening and the GPU preferences set to "never" and "CPU safe mode".
0 -
Paul Harvey, this hints at something else being wrong, beyond the export slow-down that this thread is mostly about. Please reopen your last support ticket or send a new one. We will see if we can troubleshoot this on your system, or if it is another bug.
0 -
Paul Harvey and Frank Schroeter:
I have similar problems with the update from a very stable version 16.2 (no problems for me) to a really flakey version 16.5.5:
Sometimes the images take as long time to render. After a restart is as normal.
Sometimes the big viewer window get dark (often after aplied adjustments for several images): the image is briefly visible and the window is immediately filled with the background again.
It's a really unstable version. It doesn't hang, but sometimes the rendering slows down, sometimes the viewer goes gray, sometimes edits take forever. It's not really clear what the reason is.
Version 16.2 was without problems for me.
(Windows 11, AMD Ryzen 7 5700U with Radeon Graphics, 64 GB RAM)
0 -
Still have the same problem in 16.5.5.2701.
I have logged a support ticket AMD Ryzen 9 5900X Win11 3060Ti 64DDR5
0 -
Frank, I ran some tests on version 16.5.5. As I mentioned in my previous post, attempting to export pictures immediately after editing caused the export to freeze after a few images. However, restarting the application resolved the issue, and the export completed successfully.
Next, I started with a fresh application session, created a batch of 150 pictures, and ran the export 10 times. Each attempt was successful with no issues.
After closing and restarting the application, I ran another export, which also succeeded.
Then, I selected a single picture and created an AI mask. When I attempted to export again, it failed.
Following another application restart, I ran exports for the same batch five times in a row without any issues.
Then I downgraded application to the version 16.5.4.
As mentioned in my older response I used settings:
In this scenario, I exported the same batch of pictures three times, then made some edits and ran the export a few more times, followed by another round of editing and exporting—all without any export freezing.
I suspect that the editing process, which utilizes hardware resources—potentially in combination with multiprocessing—is not properly releasing certain system resources. This could explain why the export works correctly after restarting the application, at least on my system. It’s possible that the issue is related to how editing processes are managed rather than the export function itself.
Overall, I view my testing as more of a personal observation rather than a definitive conclusion. However, maybe this observation can be useful for your dev team.
0 -
After installing the update, my first export was 1532 files, yes 1532 at 1200 on the long edge, 72 dpi, 50%. It took 2min 13 sec. No pausing. C1 shared the load on both the GPU and the CPU. Haven't noticed any slowing down overall. Haven't done a bunch of masking yet but so far so good.
0 -
16.5.5 is buggy too. Not only that, now I have been notified of a price increase?
1
Post ist für Kommentare geschlossen.
Kommentare
59 Kommentare