Marcos Sueiro Bal
Marcos Sueiro Bal
Perhaps this is intentional, but adding a marker (not so modifying it) changes the MD5 hash. See enclosed for files with and without markers [cueMD5Tests.zip](https://github.com/MediaArea/MediaInfo/files/9014750/cueMD5Tests.zip)
Hopefully this is not too complicated to implement... trying to have an alternative to exiftool for all our data 😁
Follow up to #163 Add option to remove specific chunks: `--remove-chunks=[NAME]`
- Selecting e.g. three files and then File - > Close 3 Files ... only closes the last one. - Closing a single file or all files still works
- List each file as it is processed -- Show stored MD5 -- Show calculated MD5 -- Show result
I have discovered several hundred WAVE files with multiple fmt chunks (see this [example](https://drive.google.com/file/d/1HDAE6eMhKBENB69P_6L8-tTLwU7j4Rof/view)). It seems that an editing software used by our institution renders WAVE files with several headers...
Use the same "Unified XML metadata" format used for exports. Maybe an import... menu, followed by a window with radio buttons for each (Core, XMP, CUE) (could also include aXML...
See this screenshot (before crashing): 
I could not tell from the code (just from the time it takes to implement the function), but it seems BWFME calculates an MD5 _before_ embedding it with `--MD5-embed`. This...
E.g. a report of results of trying to embed MD5, including errors