previews not resolving
My previews are not generating on my new C1P 21. An activities window shows up to tell me how many seconds are left but the preview never resolves. Anyone else experiencing this or have any solutions? I have not experienced this issue with any other version of C1.
-
The only fix I have been able to use has been to shut down the software after every exposure. This won't work so well for when I am shooting models!
0 -
Are you auto adjusting all images?
Which tools in the Auto adjust?
Do you need to do that? What happens if you turn it off?
0 -
Hi SFA, Thank you for your reply, however, I am not auto adjusting. My image stays in that unresolved state whether or not I have made any adjustments at all. In fact, if I do make adjustments such as white balance, crop or levels, none of them will hold. With any other version of C1, if I make an adjustment to one image, it should apply to the next image. We are going to try to delete and reload the software.
0 -
As you are not Auto Adjusting I'm wondering why the Activities window is reporting an Auto Adjust process - which then hangs.
Re-installing seem like a reasonable idea.
I would also wonder if some temporary files or user related settings files are in some way providing influences that are introducing unexpected activities. If that is the case and user settings files are involved they would likely be classed as data and so not be deleted. If the problem persists after re-install it may be worth looking in that direction for further ideas.
0 -
Thanks. yes, the reinstall did not work. It is doing the same thing. Can you possibly direct me on how to look into user settings files?
0 -
Hi Cindy,
Firstly it may be worth simply closing Capture One and then rebooting you system 2 or 3 times WITHOUT opening any applications.
Windows seems to undertake some file cleaning activity for old work files and stuff (that would not be too easy to do "manually") when it starts up. Sometimes, it seems, there can be dependencies of one file to another and each reboot removes an other dependent file in the chain. Some types of file, if not removed, become active again in the next session and them end up with another dependency. Or something like that. That means that faulty operational values may repeatedly appear.
I know it sounds odd but I have tried the multi-reboot process several times (usually when I have failed to free up disk space when needed and the system has ground to a problematic halt) and it seems to have the desired effect of cleaning up orphaned or erroneously connected files.
The other possible problem I can envisage is a rogue value in the user.config file. That holds constantly updating information about the current state of your C1 activity and past activities on a per session/catalog basis. If, as part of some Windows managed disk activity a value has been set or not unset somewhere ion there you could see unpredictable results.
User.config can be removed since C1 will regenerate a fresh one if needed BUT if you do that all of the last known settings for session/catalogs and one or two tools will become unavailable until they have been recreated. In general that is not a serious problem - better that than the problems you currently have.
The user.config file for C21 can be found here. This may be a hidden folder unless it has been previously unhidden.
C:\Users\[Username]\AppData\Local\Capture_One\CaptureOne.exe_StrongName_[a long string of characters]\14.0.x.xxxx
Username is the User name as known to Windows.
Note the underscore for the "Capture_One" folder name. There should be another one without the underscore but we are no interested it that at this point as far as I can tell.
The long string of characters is exactly that. Basically something that looks like a randomly generated file name.
For V21 there will be a folder for each build that has been installed and V21 Build numbers start with 14.0 currently.
In those folders you will find a user.config file. In theory you may only need to work in the folder named for the current V21 build version. HOWEVER when a new release is installed and a new folder is created I think the entry in the previous folder is used as the basis for the version of the file in the new releases' folder. .
Whether the same thing happens if C1 encounters an empty folder with no user.config file on opening I'm not sure. So if the problem persists after the suggested file removal test that will need to be checked.
Make a copy of it, move it or add a subfolder and put it in there so it could still be retrieved if necessary.
Ultimately you want to remove that file or have it called something else somewhere else for this test. Only get rid of it once you have closed Capture One.
Now restart C1 and you should get a new user.config file.
Now test the activities that were failing before.
If it now works - great.
If not we need to look elsewhere - but I think after the Temp files clear up by Windows (Above) user.config would be my next test.
Decisions after that can be based on what is discovered during testing.
0 -
thank you again for your help. Repeated restarting did not resolve the issue. My IT dept is submitting a ticket for help beyond that. Take care and have a good day
0 -
Cindy,
You could get your IT dept to take a look at the log files to see if they suggest anything.
You could also try setting the "Use Hardware Acceleration?" setting to "None" to see if that changes anything in the process.
It may be a completely false clue of course but I'm puzzled as to why that activity is being reported.
Presumably the user.config file removal did not do anything either?
Very odd. It will probably be something simple but working through ideas without having hands-on becomes less and less fruitful once past a certain point.
Are you operating fully tethered or using a hot folder?
0 -
I will pass this info on to them. They are hesitating doing anything else until they hear from C1. We do use our system fully tethered. No hot folder.
I am not comfortable doing any of these things myself. Just a photographer, not an IT person. Too bad this is not a simple fix
Thanks again
0
Post is closed for comments.
Comments
9 comments