this post was submitted on 27 Nov 2023
2 points (100.0% liked)
Data Hoarder
1 readers
1 users here now
We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time (tm) ). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.)