You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several free software photography tools like darktable store all the metadata, and the changes they make in the image in an xmp file with the same name. Original file is never touched.
Would anybody be interested in giving bitrot a feature where the bitrot information is stored in these same xmp files instead of the SQLite database file?
The main benefits of this, is that other apps like darktable or digikam that will also be able to access and use the bitrot information from the xmp file. Bitrot could even be integrated and launched from these apps directly.
Most photographs don't store checksums of their photos, but just like everybody else , they suffer the consequences when it happens. This way, as soon as bitrot occurs it can be detected and the photographer can delete the corrupt file and restore a backup of just that file.
The text was updated successfully, but these errors were encountered:
Several free software photography tools like darktable store all the metadata, and the changes they make in the image in an xmp file with the same name. Original file is never touched.
Would anybody be interested in giving bitrot a feature where the bitrot information is stored in these same xmp files instead of the SQLite database file?
The main benefits of this, is that other apps like darktable or digikam that will also be able to access and use the bitrot information from the xmp file. Bitrot could even be integrated and launched from these apps directly.
Most photographs don't store checksums of their photos, but just like everybody else , they suffer the consequences when it happens. This way, as soon as bitrot occurs it can be detected and the photographer can delete the corrupt file and restore a backup of just that file.
The text was updated successfully, but these errors were encountered: