How does the "compare by file content" function work? Does it generate a file hash and compare? What this tells you is that the original and backup do not match; it does not say which one is "correct".
This would be a great new feature for backup of FLAC music files. FLAC files contain internally an MD5 that was generated when the file was created. If FFS would read that and compare to the original and backup, it could determine which way to sync each file in order to retain the original. It could also highlight any files for which the original and backup are both non-matches. This would tell the user that those CDs need to be re-ripped.
From Gemini AI:
FLAC files store an internal 128-bit MD5 signature (often called the FLAC fingerprint) inside the mandatory STREAMINFO metadata block at the beginning of the file.
Question about "compare by content" and new functionality suggestion
- Posts: 2
- Joined: 25 Aug 2026
