Request a new feature, or support for a camera/lens that you would like to use in Capture One.
When dealing with images those might be corrupted a) during copy/transfer or b) silently after a while on the storage system. I experienced several times due to a flaw in the osX network storage implementation of cifs/smb that I imported images with the "copy to destination option" that the files ended corrupted on the network storage. Due to the proxy/preview image this was invisible until one edited the file and it was rendered again. This is NOT capture ones fault but by implementing and incorporating a hash/checksum procedure (maybe optional checkbox) during all image importing/copy/moving operations, this could be prevented/taken care of. An additional option for checking the whole Catalog and its images for silent bitrott would be , even if extremely time consuming, very useful to ensure data integrity. Like the "re-render preview images" option in the menu. This is what I use now after each import of images which where edited in captureone- mobile to check at least visually every image for corruption. (sidenote: my cifs-osx problem could be workarround on my side by disabling jumbo frames on the network adapter :-/ ... )
Current workaround
Do the hash calculation and comparison on my own after each import into the catalog. Use a file system like ZFS being able to cope with silent bitrott. |
ZFS doesn't seem to be well supported on Windows, so I would say this is even more important on Windows. I've run into issues with the C1 database experiencing corruption internally, so they really need to investigate this and release patches for all versions of C1 for free. This is a sanitation issue. They shouldn't be allowed to force us to pay for an upgrade to receive basic sanitation. This is less a "feature" and more a basic requirement.