Media diagnostics · Primary-source explanation; no UK IPTV implementation or account test. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Start with a harmless metadata change
Consider a personal FLAC file whose album title is corrected while its audio samples remain unchanged. The file now contains different metadata bytes, so a checksum calculated across the complete file can change. That does not by itself show that the decoded sound changed. Conversely, a tool reporting an audio checksum is not necessarily checking cover art, comments and every other byte in the file. Identify the scope before interpreting two digest strings as contradictory.
Use the format field for its defined purpose
RFC 9639 specifies an MD5 value for the unencoded audio data in FLAC stream information, with zero representing an unknown value. This lets a decoder check the reconstructed sample data against that field when an actual value is present. It is a different operation from hashing the stored container bytes. Neither operation, by itself, authenticates who published the recording or whether it is the desired edition. An attacker or a mistaken export process can supply internally consistent data, so integrity and provenance remain separate questions.
Choose the comparison you need
If checking that a transfer copied a file unchanged, use the same whole-file digest method at both ends and retain the original expected value. If checking whether a metadata-only edit preserved audio, use a documented decoded-sample comparison with matching channel and sample interpretation. Keep the tool and result, rather than substituting a filename or duration match. This article does not claim that two particular files were tested. Its practical decision is to match the check to the bytes that matter before deleting an apparently redundant copy.