3
Checksum for original files came out unreadable (alien.top)
submitted 2 years ago by [B] to c/datahoarder@selfhosted.forum
9 comments fedilink hide all child comments
 

Does that mean there was bitrot ready in the original file? Something else? How is the checksum even generated successfully if it's corrupted or undreadable in the first place.

Any way to fix?

you are viewing a single comment's thread
view the rest of the comments
[–] [S, B] 1 point 2 years ago (1 child)

Its an audio file. I can play it but cant tell easily without playing through it to see if it is corrupted at certain parts.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [B] 1 point 2 years ago

    Then you have to assume that the file already is at least a little corrupt. What you need to determine is if the level of corruption is so bad that it is a problem. If it crash an audioplayer or the file sounds bad. Ideally you have a backup copy that is better or you can download or create a new file that works OK. Possibly you can re-encode the file to fix problems. It will degrade audio quality if the encoding is lossy. But perhaps not enough to be noticeable.

    Some audio file formats have embedded checksums. FLAC or WavPack. Perhaps more? You should be able to find utilites that can compare the embedded checksum with the current stored data.

    In the future use a checksummed format or store separate checksums. Or zip the files. The zip format has embedded checksums. (Same with all(?) other compressed formats.)

  • permalink
  • fedilink
  • source
  • parent