<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dcpomatic/src/lib/info_file_checker.cc, branch 2758-safe-write</title>
<subtitle>DCP-o-matic DCP tools</subtitle>
<id>https://git.carlh.net/cgit/dcpomatic/atom?h=2758-safe-write</id>
<link rel='self' href='https://git.carlh.net/cgit/dcpomatic/atom?h=2758-safe-write'/>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/'/>
<updated>2024-07-21T21:02:24Z</updated>
<entry>
<title>Add an advanced option to check data against the frame info file when making hashes (#2758).</title>
<updated>2024-07-21T21:02:24Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2024-05-31T00:24:01Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=d520dad61113d9b26f229b8efc8550a49101de9c'/>
<id>urn:sha1:d520dad61113d9b26f229b8efc8550a49101de9c</id>
<content type='text'>
This should show up corruption that happens on the disk/storage, i.e.
between DCP-o-matic writing the MXF and it being read back in again
for hashing.
</content>
</entry>
</feed>
