16.2.1 constantly freezing
Hi,
I’ve just upgraded from version 21 to 23 16.2.1, and I really wish that I hadn’t. The software is constantly freezing, maxing out my processor and making me kill the app from task manager. I’m lucky to get more than 5 minutes use out of it before it freezes again. Tasks such as auto exposure or applying a star rating to an image can take 10 seconds or more. This is driving me crazy, I need to get some wedding photos processed as soon as possible. Please can you advise or issue and update to fix this.
-
Here is my advice:
For the wedding photos, assuming you are in a hurry, deinstall v23, reinstall v21 or v22 and start a new session from scratch.
For the future, never upgrade C1 on your production system before you performed a decent test phase with the new version (major or minor upgrade), unless you have no obligation to deliver your photos.
1 -
Thanks BeO for the advice. I'm not sure if my 16.2 v23 license will work with v22 or even 16.1 but I'll give it a go.
Thankfully, my wedding photography is not my main source of income, my day job is as a software development manager, leading a team of 12 software engineers developing Windows software for the life sciences industry. With nearly 30 years of sw development experience I should have known to try out the new version beforehand!!
However, it does raise some important questions for CaptureOne. With the comments on this forum, they clearly have major issues with 16.2 that should have been caught by their test team. End users do not appreciate being beta testers! I can understand the pressure on the dev team to release, especially with the Agile mantra of release early and release often. But you can very easily alienate and lose customers. They're in the unfortunate position of having a relatively mature product, I expect that many users only use a small percentage of the features of C1 and few users actually need to upgrade now. I'm sure this is one of the main reasons for their new draconian licensing policy -- again, don't alienate your users! I only upgraded to get support for the Fuji XT-5.
Anyway, I'll stop waffling and download some older versions!
0 -
Fully agree with all you said (except maybe the "small percentage of features...", I use every feature (of their main product) except direct printing, watermarks and the cull view (I'm still on v22), but of course I don't know for others).
Yes, they're in the unfortunate position of having a relatively mature product, however there are still big features of competitors missing (e.g. AI noise reduction) and better auto-masking, their catalog implementation is not good enough for big catalogs (and their metadata IPTC version is old), HDR seems lacking too, same for C1 Live, and they regularly introduce new issues and have quality issues.
They upped the prices (for no better service) and lowered the conditions for perpetual users, alienating with me and many others, and I don't think that a raw converter on the smartphone will contribute much to their overall success. I cannot look behind the scenes, but to me it seems they do a lot of things wrong.
Re. your license, I think you are entitled to run older versions.
1 -
-
Update Capture One: Check if there are any available updates for Capture One. Visit the official Capture One website and download the latest version. Software updates often include bug fixes and performance improvements that may address freezing issues.
-
Check system requirements: Ensure that your computer meets the minimum system requirements for running Capture One 16.2.1. Verify that your hardware, such as the processor, RAM, and graphics card, meets or exceeds the recommended specifications. Inadequate hardware resources can cause freezing problems.
-
Clear cache and temporary files: Accumulated cache and temporary files of skullcandy-crusher-2014 can sometimes cause performance issues in applications. Clear the cache and temporary files within Capture One by going to the Preferences menu and selecting the appropriate options. Restart the software and check if the freezing issue persists.
-1 -
-
Hi,
I've updated to 16.2.2 and things have improved a small bit. C1 is no longer hanging after 4 or 5 operations.
But you still definitely have a problem. This time it's taking 10 - 20 commands in a row before it freezes.
To replicate.
1. I'm using a Fuji raw file. Windows 11 22H2
2. Go to the Adjust tab and individually select the auto adjust option for White Balance, Exposure, HDR, Levels. Repeat with various commands, but the issues I'm seeing usually occur with the auto adjust commands.
3. After a few minutes of this, commands take longer and longer to complete, the memory and CPU max out and the Activities window is displayed. The text displays the auto adjusting 1 of 1 variants - about 0 second left and the progress bar appears to be at 100% complete. Sometimes the activities dialog will eventually close and the CPU returns to normal, but it can take over 5 minutes for this command to complete. I'm usually pretty p*ssed off by now and just kill C1. Even when recovered the same thing will happen again after 1 or 2 more commands. The only option is to restart C1.
In conclusion, your devs are getting closer to fixing the issue with 16.2.2 but it's still not properly fixed.
Your instructions on clearing the cache appear to be incorrect. There is no Preferences menu. Under the Edit menu is the Preferences dialog, but there are no commands or options for clearing the cache in the Preferences dialog. Have I missed something?
Thanks for your support.
0 -
The post above yours that talks about clearing the cache is unfortunately the malicious work of a scammer or a bot or both - as you can see from the link to some spurious website or other, and from the generic unhelpful information. Unfortunately the forum seems to be plagued by this kind of crap.
You're right - there is no command for "cleaning the cache".
I don't know why you are having such problems, and it's no comfort, I am sure, to be told that it is working well for many of us users. Have you tried things like turning hardware acceleration off, updating graphics drivers, and so on?
Ian
0 -
Hi, yes I have tried turning off hardware acceleration etc.
Unfortunately, this is a classic race or deadlock situation in software development. Races are usually caused by a threading issue where two threads are using the same data and due to timing, the data is accessed in the incorrect order. A deadlock is caused when two threads are trying to lock the same data. Unfortunately, both issues can be very difficult to find and fix because it is down to timing, often at the milli-second or less level. What can work on some PCs will fail on others. All because of timing differences. Running the software in debug mode or under a debugger will usually work because the timing is completely different to running the software normally. I don't envy the C1 devs trying to fix these issues! However it is incredibly satisfying when you do find the issue and fix it!
Unfortunately, I don't have another spare PC to try it out on. But, I think I will clear everything out and reinstall. Maybe go back to 16.1 and test that. Although my catalog has been updated and I'll need to go back to a backup to try 16.1
Thanks
0
Post ist für Kommentare geschlossen.
Kommentare
7 Kommentare