When C1 crashes image settings are lost
Sometimes it happens - C1 crashes. So you restart the computer and continue the work.
One annoying thing with this is that C1 looses the information on what has been done to the images that have already been developed: for the photos already finished and converted to tiff C1 normally remembers the settings for how it was done, but when it crashes all that is lost: the settings for the completed images are back to the standard/defaul settings.
This is, I guess, not a big issue but it would be nice if it did not. My hunch is that some ill-adviced programmer has designed the program so that it writes these settings to a single file during one session and this file is nover saved during the session. so when it crashes, the file is lost since it was not properly closed...
I have been working through a batch of 300 images today. The 80 images I did this morning still have their \"settings\" when I look at them in C1 but the remaining 150 that I had worked on until it crashed have lost their information.
Wouldn't it be cleverer to save the settings after each develop?
One annoying thing with this is that C1 looses the information on what has been done to the images that have already been developed: for the photos already finished and converted to tiff C1 normally remembers the settings for how it was done, but when it crashes all that is lost: the settings for the completed images are back to the standard/defaul settings.
This is, I guess, not a big issue but it would be nice if it did not. My hunch is that some ill-adviced programmer has designed the program so that it writes these settings to a single file during one session and this file is nover saved during the session. so when it crashes, the file is lost since it was not properly closed...
I have been working through a batch of 300 images today. The 80 images I did this morning still have their \"settings\" when I look at them in C1 but the remaining 150 that I had worked on until it crashed have lost their information.
Wouldn't it be cleverer to save the settings after each develop?
0
-
Per K,
Your system crashing would seem more than annoying. Look into your system or OS and drive maintenance i.e. DeFrag etc. Capture One utilizes system resources efficiently and should not be crashing.
For this weeks Raw News, Ulf has written a Tips&Tricks discussing exactly what you are wanting to do, Saving or Archiving your color setting adjustments. Please read this from web site at:
http://www.phaseone.com/Content/Softwar ... tings.aspx
The data is written to a Work file .C1w (which is the Thumbnail) for each one selected and archived.
Sincerely,
k c0 -
Well, it wasn't the system crashing that I found most annoying (and btw, to be precise, it was C1 crashing. Not the system.). It was loosing the information within C1 about how the settings had been done for the already processed images. All thumbnails, and settings in the WB & Exposure tabs go back to \"zero\" for those images that I had worked on in the session that crashed.
Fortunately, the tiffs are there and OK, but it is still a pity. If C1 saved and closed the file where it stores that info after having processed one image, instead of at the very end of the session, that should fix it. (If my theory of what causes the problem is correct.)
BTW: What happens is that C1 (3.6 Pro) occassionally \"freezes\" in the middle of processing an image. Nothing more can be done and the program has to be forced closed. (Windows reports it as \"not responding\")0 -
Per,
I you go to Preferences/Save Options you can configure how COne is saving the image settings.
By default it is saving the settings at exit and when changing collections. You can configure it to save when changing images and at a specified time interval.0 -
Brilliant! I didn't know that. It shold fix this problem! 😂 0 -
Thanks for the good advice Gnordstrom, made me look into this further.
The data that is saved:
[i]White Balance
Color
Crop
Rotation
Exposure Sliders
Film Curve
Sharpening
Noise parameters
MetaData[/i]
These data are saved to each of the Work files ( .C1w ) that reside in the Previews folders. Some users occasionally purge this folder to save space on hard drive and of course all data is lost. This is why saving Archive is an option available. If space is not an issue, then saving each Session's adjustments as you work is quite easy. In Preferences > Preview cache tab, Automatically clean up the preview cache the radio button, Never should be checked in order to keep Work files with data intact.
Cheers,
k c0 -
Keith,
Maybe I missunderstand what you are saying, but when you purge the preview cache from within COne only the preview files are deleted. Work files are not deleted. When you open an image again the preview file will be recreated and all your previous settings will be intact.
The only time COne will delete a work file (to my knowledge) is when you permanently delete a raw file. Then the associated work file will be deleted as well. So, if you don't want old work files taking up space (even though they are small) always delete raw files from COne.
So, it's perfectly safe to clean up the preview cache every know and then to save disc space, as long as you do it from within COne.
Using the archive option to archive the work files with the raw files can still be a good thing to do.0 -
gnordstrom,
No, you did not misunderstand - I did and I was not very clear either. Hopefully I won't confuse folks any further. 🤭
You are correct in that if you use the Capture One Preference settings to clear the Preview cache, the Preview files not affilitated with Captures of a current Session/Collection will be deleted and the Work files remain. Translation: if RAW files are removed from a Session folder to save space, the next time the Preview Cache is cleared, those affilitated Preview files are purged. The Work files still remain. However, when RAW files for a Session are reloaded, New Preview files are created, and the remaining Work files are rewritten as well.
So your advice to set Preferences to Save often is good practice to maintain adjustment data as you work on current Sessions. And finally, if you need to remove Session RAWs to save space, to truly Save the data affiliated with Work files, Archiving is the method of choice.
Work files are quite small at ~ 1K and Previews are a few MBs.
Some Users have made the mistake of directly browsing to their Preview folder and deleting the contents. In this case, since the Previews and Work files both reside here, the Work files are lost along with any data... Bad Method.
Thanks for Keeping me Honest.
Cheers,
k c0 -
Keith,
If you with \"... and the remaining Work files are rewritten as well. \" mean that your previous changes are lost, this is wrong.
You can:
- Open a new collection and make changes to the raw files
- Remove the collection and clear the preview cache
- Copy the raw files to a cd/dvd
- From the explorer (NOT COne) delete the folder with the raw files to save disc space
- Later copy the raw files back to the disc
- Run COne and open a collection with these raw files
- COne will create new previews
All your previous changes to these raw files will be intact and not lost.
/Goran0
Post is closed for comments.
Comments
8 comments