View Bug Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001380||DCP-o-matic||[All Projects] Features||public||2018-10-16 09:55||2019-01-08 01:11|
|Priority||high||Severity||minor||Reproducibility||have not tried|
|Target Version||2.16.0||Fixed in Version|
|Summary||0001380: Could check MXF hashes from info file as the CPL/PKL hashes are being calculated|
Which would detect corruption between writing the MXF to disk and reading it back.
|Tags||No tags attached.|
|Estimated work required||Unknown|
Thanks for creating this issue.
Personally, I think this would be a good idea. Much as you can't trust the network to transmit data 100% correctly, I don't think the filesystem should be trusted either. It's mostly trustworthy, but to be bullet-proof, it'd be ideal if the hashes were checked when the files are read back from the drive.
Would it be difficult to implement?
For anyone who comes across this issue, the context is a conversation on the DCP-o-matic mailing list. I made a large batch of DCPs but discovered that the drive I made them on was faulty and was corrupting data. Because DOM writes the MXF files to disc and then reads them back again to creates the hashes which are stored in the DCP XML, if the data has been corrupted on the disc in the meantime, that corruption would be "baked in" to the DCP's MXF files and the hashes would reflect the corrupted data. So hash-checking the DCP would not reveal whether this has happened or not.
Probably not too difficult. Maybe could be optional with 0001381 if performance is a problem.
|2018-10-16 09:55||carl||New Bug|
|2018-10-16 10:07||overlookmotel||Note Added: 0002716|
|2018-10-17 09:32||carl||Relationship added||related to 0001381|
|2018-10-17 09:32||carl||Priority||normal => high|
|2018-10-17 09:32||carl||Status||new => acknowledged|
|2018-10-17 09:33||carl||Note Added: 0002719|
|2019-01-08 01:11||carl||Target Version||2.14.0 => 2.16.0|