Special hangs during converting RAWs
I hope I can explain an issue which brings Capture One to hang. It affects Capture One V20 (from the first version on) only, OC ist Windows 10. Hardware acceleration is off. Fast HDDs and SSDs, 32GB RAM, i-7-9700, Nvidia GeForce 970.
When I'm working with C1 it happens sometimes that changing from one image to another shows this next image blurred. When I at this point try to get back to the last image before or change to any other image nothing happens. No adjustment will be done at this point.
To say it clear: C1 is not really crashed at this point, I can close it nearly normally via close button. After the next start it not will beginn with the last edited image but with an image I have edited long before. Seems so that the problems begin rather before it comes to that hang.
As I noticed that the issue comes to light more often when I use "keystone correction" (I hope the English interface shows this label, in my German it's calles "Trapezkorrektur"). When I use this tool, I use it with right-click and mousewheel instead of setting the lines. Maybe this makes a difference.
The problem is mostly solved after restart but sometimes it comes again in a short time, then there are several restarts needed.
This behaviour drives me crazy. On a normal day of work this issue happens four to six times. I hope anyone can solve my problem.
Thanks for help in advance
Ernst
-
Ernst,
I would suggest that you should create a Support Case to get personalised advice from the Capture One Support team.
Is seems likely that there will be some clues in the process Log Files but it is an obscure sort of problem and for that some insider knowledge and understanding of the log files may be required to identify the possible problem area (or areas).
https://support.captureone.com/hc/en-us/requests/new
If this happened on my system I would be suspicious of things like the temporary work files and maybe the userconfig file's existing settings where there may be anomalies in the information contained therein.
These are local system level files and so any problems with them makes it very difficult and perhaps impossible to diagnose using another system or a different approach to how you apply the adjustments. For example the mousewheel adjustment, if it might be part of the problem, might only be a problem with the mouse driver program used on your system. In which case it could be pure luck if someone else discovers they can reproduce the problem.
When you mention if may happen 4 to 6 times a day ... does that by any chance relate to a similar number of image edits inbetween occurrences?
Are you using catalogues or sessions?
0 -
Hi SFA,
thank you for quick answer and for your engagement!
You are quite right with support ticket - but a have years long experiences with Capture One Support and a lot of tickets as I use C1 under Windows normally. It needs very much effort to come to a result there - if at all possible (30-40%). And they ever insist on videos even when they know that there cannot be any when erros or problems happen maybe in one minute, maybe in some hours. Ans in doubt it is ever Windows, Adobe or something else causing the named issue. But of course to create a support ticket is the last way to go.
To your questions:
Temporary workfiles should disappear when C1 is closed. Do you have some hints in this direction?
Userconfig recreated - no change.
Local systemn level files, I agree, could cause problems like this. But if this problem appears on another Windows machine 800km away? (And it appeared and appears from V20 up.)
Mouse Wheel? I am surprised. My Mouse wheel i running the other wa round, means the Mac way because I do work on Mac too. I can try to cancel this behaviour. It would trun my workflow badly but in it helps... (Til today no other software in the last years was irritated by this. not even Capture One up to Version 12.)
General mouse driver? I use the Windows integrated. Could only be the registry entry "FlipFlopWheel" in "HKEYLOCALMACHINE/SYSTEM/CurrentControlSet/Enum/HID" set to 1 (see above).
At least one of my friends can reproduce this problem. We both use the German interface - I hope this will not bother the functionallity of C1.
No, sorry, there is chance relate to a similar number of image edits inbetween occurrences. The first I try is to get a hand on reproduceability. (I was software tester for same years.) If issues can be repeated then you can find the cause easily.
I use more catalogs, sometimes (especially mobile) sessions. This behaviour I could find working on catalogs only. But the possibility to test this on sessions is rare. And, we never should forget while testing, I need to get my paid work ready. Therefore I use a well paid software. I am not paid for testing. ;)
Kind regards
Ernst0 -
Just had an idea: I nearly always work with two or more catalogs at a time. Will try to work with only one for some days...
0 -
If you are working with large catalogs (or large files) it may be possible that the system memory and file handling resources are having to work hard.
There are also possibilities for one set of programs to be working with 2 sets of underlying "options for the Userconfig file and perhaps other places (Appdata files for a Windows installation for example.) . I often work with multiple sessions open and sometimes multiple session and a catalog. Usually things are OK but if I find I am low on available memory (usually as a result of running other applications at the same time) it seems possible to introduce system instability (Windows 7) that can compromise some of the tasks in C1. (Or any other application.)
I work on a notebook with a trackpad. English language. I have not seen any reversed actions with that set up. When I used Keystone correction I mostly use the graphical version rather than the slider or numeric values in the tool. I could imagine that making direct adjustments when editing many images concurrently might slow things down but on my system and my not very large RAW files there processing speed (compared to most other edit actions) is slower than normal but not by much.
As for "testing" - your will be testing every day for Microsoft and anyone who provides hardware and software for your system components or updates them from time to time, sometime with results that are detrimental to your immediate needs. It is the way of the modern world where things move fast and "agility" is considered "good". Often at any cost.
If you want an application that is evolving to be 100% error free you also need to expect restricted hardware choices and a much higher price tag. And constraints about how rapidly "new" "technology" can be supported.
0 -
First: One catalog or many - makes no difference.
Hi SFA,
I appreciate your fast and competent answers. They help me to eliminate some possible causes and see some potential ones.
CPU performance and RAM of the mentioned machine is really enough. Nerver uses more than 55% of physical memory. And waiting (up to half an hour) does not change a bit. ;) In Task Manager I can see that C1 does not do need much CPU (0,1-0,3%) or memory (2,25GB, all used software products together use 34% of physical memory). My cataloges hold from 8-12.000 images per catalog. This is not a large catalog for me.
And - we should not leve the focus: This issue is NEW since V20. I had no such issue up to V12! The machine and used software is "the same" all the time.
There are also possibilities for one set of programs to be working with 2 sets of underlying "options for the Userconfig file and perhaps other places (Appdata files for a Windows installation for example.) .
This sentence I have to think over; at the moment I cannot understand the whole meaning. But I will handle with when have got it. Memory should never be short is this case.
As for "testing" - your will be testing every day for Microsoft and anyone who provides hardware and software for your system components or updates them from time to time...
This statement is right but makes me run out. NO OTHER SOFTWARE including Windows 10 by it's own steals my time in a similiar amount. Really. There are some (not one) database problems in C1 on Windows version only since I use is (V10 up) that never where fixed till today! I needed MONTH to proof and explain it to Phase One support. Reproduceable problems. The latest answer was like "We can see it now, we do not know how to fix easily. We see it as a minor problem as most customers use Mac and you can at least work on under Windows (with the instable database)." Theese problems I have described on my (German) website and got some mails back "Oh, I can reproduce easily." Sorry this had to come aut when touching this point.
If you want an application that is evolving to be 100% error free...
;) Don't tell a former database programmer and software tester things he has to know by heart. ;) On the other hand: C1 is not a cheap anything compared with other products. I use it with all the issues because of it's very, very good output. But what I expected was that knows issues would be fixed, especially if the customer helps. Even when a customer uses Windows. And that there is a support which does support at all. And of course you are not the addressee, but just to know what I am thinking about. ;)
I have invested too much money and time in moving to Capture One, I rely on fixes from Phase One.
Kind regards
Ernst0
Post is closed for comments.
Comments
5 comments