Open OlliTee opened 1 year ago
And, there needs to be a way (added to the spec) to "accept" changes to the MHL. A flag for the create command that creates a new generation without any errors for missing files or changed hashes. Ideally with some info logging in the MHL that notes what was changed, but future generations wouldn't include.
To cover my bases, I’d like to present my particular use case that is not reflected in the
examples/scenarios
. Imagine a source folder containing an ascmhl file and a tool that will transcode only a particular type of file and copy everything else. The file name of the transcoded output is changed to identify files with the new codec.For all transcoded files, a verification with ascmhl tool would result in an Error: Files referenced in the ASC MHL history are missing, and a new original hash for the newly created output. The verbose output of
ascmhl create -h xxh64 -v /Volumes/PRO-BLADE1/HDE_HDET_asc-verify/A_0001_12NR
would be:And the output ascmhl would show <xxh64 action="verified"… for the two verified files and <xxh64 action="original"… for the newly created files.
Does this implementation look alright for you or should I handle it differently?