-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Filebert is a Windows program that scans directories for media files and verifies the integrity of those files. While media players take a fault-tolerant approach to issues such as file corruption, this application will report extensive diagnostics.
The following types are supported:
aif/aiff/aifc, ape, asf/wmv/wma, avi/divx, cue, db (Thumbs), flac, flv, gif, ico, jpg/jpeg, log (EAC), log (XLD), m3u, m3u8, m4a, md5, mkv/mka/webm, mov/qt, mp3, mp4, mpg/mpeg/vob, ogg/ogm/ogv, png, sha1, sha1x, sha256, wav
Filebert will verify any internal CRC or self-hash against the file contents and report mismatches caused by bit rot, truncation, tampering, etc. Types that store CRCs and self-hashes include FLAC, JPEG, MP3 (LAME only), OGG, PNG, and EAC and XLD logs. Filebert makes no assumption of content based on extension - every file's contents are analyzed for its actual type. Total errors will be displayed at the end along with total file counts. Zero errors and zero warnings are good.
Some reported issues may also be repaired. This is a two-step process. First, repairs must be enabled with the /R
switch (or checking the box). Then each repair must be requested by pressing the Repair button. (Or confirming in the console version.)
Here is an example screen showing an analyzed MP3:
A red nightmare indeed.
Settings are always shown with file diagnostics organized into tabs below the settings bar. At the bottom are diagnostic messages. There is one tab per file type plus the console tab which is always on the left. The console tab provides output that is identical to the console version of the program.
Next is diagnostics of a different MP3.
This track has many issues. With the Repairs checkbox enabled, these issues can be fixed by clicking the Repair buttons at the bottom. Without enabling the Repairs checkbox, these buttons appear disabled.
Next, two of these issues will be repaired.
The filter box is for performing operations against files with a specific extension.
In the next example, EAC log self-hashes are checked online.
Be sure to uncheck the rip check boxes when using filters.
Next, switching to the console tab shows a history of results.
This output shows that two EAC logs and one XLD log were found. Log self-hash checks were performed against EAC only.
Folder-level media validations may be performed against folders created by either of the popular CD ripping programs EAC or XLD.
In this example, three EAC rips were found under the Rips
folder and all validated OK.
Beside analysis of individual .log
and .flac
files, this check verified that the CRC-32 values
match between the log file track entries and the actual .flac
file CRC-32s.
This step ensures that the folder's .flac
files are correct for their corresponding .log file.
Rip checking may be taken to the next level by checking the enable Strict box. This will ensure quality of the highest standard.
Next is an example that is not up to the higher standard of strict mode.
The gap handling setting of EAC was incorrect and this FLAC rip was a reject.
This is an example of a successful MP3 rip check.
While MP3 rip checks can't match files based on CRC-32, other rip-level checks can be performed
such as matching the .mp3
file count to the .log
file and ensuring that all tracks have been ripped to the same profile (V2 here).
These checks are in addition to the usual battery of file-level checks of all media files in the rip folder.
In the previous example, a red tab header foreground denotes an issue with a .m3u
file.
Because the Validate Exists setting was checked, a missing file was reported as an error.
Rip checking also includes validation and repairs of CUETools type .cue
files.
These files are generated by disc extraction programs such as EAC.
Below is an example of a rip check using the .cue
file as generated by the EAC program.
Because repairs were enabled, the .cue
file names may be replaced with the .flac
names of the rip.
Next is the result of clicking the Repair button.
In order for this update to be successful, all file names must be Windows-1252 clean.