Edits did not save upon closing
I was working with a bunch of RAW files and made a lot of edits. I had to run out and couldn't finish, I closed Capture One and shut down my computer. When I restarted today none of the edits I did saved. The image thumbnail in the selection pane shows up with the edits but when the image loads the edits are not applied. I look at the setting and they are all back at their stock values. The only thing I did differently this time is sort by 5 starring the images for sorting. Then I edited in the 5 star folder. I go into the session folder (In Windows file system) and I can see there is content inside the settings100 folder. I've done a verify on the session and it says its all good to go. Has anyone else had this problem?
0
-
No, but just a thought - try regenerating the pre-views. 0 -
No, not me. And I'm on Mac.
Just a remark:
The CO 11 adjustments go into 'Settings110' folder, not 'Settings100'. Even when using the v10 engine.
Regards,
Hans0 -
I can actually confirm - opened the session from yesterday's photoshoot and created/applied LCC corrections.
Closed the session and ALL my LCC corrections were gone. ALL of them. 731 photos and now I have to search for EVERY LCC file again and re-apply them - but if I close it, they're all gone again.
Windows 10 Pro 64 Bit
i7 7700K
32GB RAM
Samsung 960 NVMe 512GB
GTX 1070
Files are locally stored and not on a NAS.
Interestingly when closing a "saving" window pops up and takes a few seconds before vanishing.
This is very annoying and if not fixed within a few days that will definitely be an issue for me and my clients.
EDIT: This seems to affect LCC files only, changing anything else will be saved.0 -
Windows 10 Creators update recently applied? 0 -
OS Build: 16299.125
Version: 1709
I guess that's the Creators update but I installed Windows 2 days ago and during the installation process it seems to have updated it.0 -
Quick question to the OP:
Did you use a long(ish) file name or a very short one?
I was trying to find a fix for the issue and the only thing that helped was renaming ALL files so they wouldn't be as long.
Now I don't know whether renaming them or the shorter file name did the trick - but now it works as expected AND it doesn't take such a long time to close (and also open) the session.
Capture One does not play nice with long file names.0 -
FWIW I have just taken delivery of a NAS device and I am going through the process of setting it up.
That kicked off with a suggestion to make sure the internal management suite software is up to date. Seemed like a good idea so I did.
So, software updated, new, empty drives all spinning and ... hmm. why is it suggesting there might be another software update? Read the release info note - a couple of bugs to fix.
Read the info about the just released (today) build I have just installed - a load of bug fixes including:
"Fixed an issue where Microsoft Office documents may fail to save when Windows 10 Fall Creators Update is installed."
Food for thought there I think.
Of course it may be entirely unrelated to the similar sounding problems you are seeing.
Grant0 -
I'm really not sure we should blame MS for this one...
If this was a more common occurrence we would see more feedback and an official acknowledgement of the issue.0 -
[quote="C-M-B" wrote:
I'm really not sure we should blame MS for this one...
If this was a more common occurrence we would see more feedback and an official acknowledgement of the issue.
Well, if one was trying to apportion blame, who would be your likely target?
Someone I know well who is currently in the middle of managing a Windows 10 migration for several thousand users with around 1000 applications in use and has a test system and test team working right through the project mentioned to me that it had been suggested by people who would know that the latest update was not something they really needed to rush into. So they have not.
BTW, I'm not sure what you mean by long file names but I use pretty long file names and some very long paths without any problems that I am aware of.
Grant0 -
Are you working with LCCs?
My session file names looked something like this:
2017-12-14_XXX_XXXX-XXXXXXXXXX_XXXX_XXX_XXXXXXX_XXXXXX_XXXXXXX (X = Names of people involved)
Would be pretty nice if the OP could tell us how his files were named and whether this issue was also mainly due to LCC profiling.
I don't want to blame anyone - I'm just saying that this issue has been there for quite some time and even exists in OSX, I doubt that the latest Windows update suddenly caused it here as well0 -
[quote="C-M-B" wrote:
Are you working with LCCs?
My session file names looked something like this:
2017-12-14_XXX_XXXX-XXXXXXXXXX_XXXX_XXX_XXXXXXX_XXXXXX_XXXXXXX (X = Names of people involved)
Would be pretty nice if the OP could tell us how his files were named and whether this issue was also mainly due to LCC profiling.
I don't want to blame anyone - I'm just saying that this issue has been there for quite some time and even exists in OSX, I doubt that the latest Windows update suddenly caused it here as well
Windows has had a 256 character limit on file length including the full path. This can now be overridden with a registry hack or a policy change in GPE if you are using Pro version of Win 10. See for instance http://www.itprotoday.com/windows-10/en ... windows-100 -
Actually the limit was 260 per path segment up to 32 thousand for the whole path: https://msdn.microsoft.com/en-us/library/aa365247.aspx
But you are correct they are lifting that segment limit in an update of win 100 -
again: I doubt that this has anything to do with a limitation by Windows itself.
This issue has also been there with OSX and I can browse, edit and save files with other programs within Windows without any issue.0
Post is closed for comments.
Comments
13 comments