Filebert for Windows
The graphical version of Filebert is a native Windows application that runs on Windows XP thru Windows 10. Like the console version, .NET 4.0 is required. In operating systems other than Windows, use the console Filebert.
Below is the application at startup. Settings are shown at the top with results below the settings.
Input a file or folder name in the Name textbox. If the name specifies a folder, files in that folder and all subfolders will be checked. Files or folders may also be supplied by dragging from File Explorer to the File label or navigation wheel. When ready to begin, hit the Check button. There is no cancel button so close the application to terminate.
A text report is shown in the Console tab for files as they are checked. The Scope of the console report may be changed at any time. After all files have been processed, files with known formats will appear with one tab for each extension.
A plethora of hashes may be generated on files or portions of files. To generate file hashes on files with unknown extensions, a filter must be supplied that includes the target files. These generated hashes are available on individual file tabs or in the console tab. The console report displays a format that may be selected and copied to the clipboard. Then the clipboard contents are suitable to paste to digest files.
Check Intrinsics to generate various types of hashes depending on the individual file format. These generated hashes are typically used to verify a portion of that file.
Check File MD5 to generate MD5 hashes of entire files. This is the oldest and shortest of the available hashes at 16 hexidecimal digits.
Check File SHA1 to generate SHA-1 hashes of entire files.
Check File SHA256 to generate SHA-256 hashes of entire files. This is the newest and longest of the available hashes at 64 hexidecimal digits.
Check Meta SHA1 to generate SHA-1 hashes of the non-media portions of .flac and .mp3 files.
This hash is not very useful.
Check Media SHA1 to generate SHA-1 hashes of the media portions of .flac and .mp3 files.
Media-only hashes remain unchanged when changes are made to metadata such as tag edits.
These generated hashes are appropriate for a .sha1x file.
Check PCM MD5 to validate the embedded MD5 checksum within FLAC files. This slows diagnostics and is mostly redundant considering all the other checks.
Check PCM CRC-32 to generate hashes of the audio portions of .flac and .wav files.
These are the same values used by the EAC and XLD applications for their track copy CRCs.
Check Exists to validate file references in playlist and CUE files. Check any of MD5, SHA1, SHA256 to perform validations of the respective digest files. These can be time consuming operations so are unchecked by default.
Rip checking is folder-level diagnostics
that validates the extraction of the contents of audio compact discs.
CD extractions must be performed by either the EAC or XLD programs
with the generated .log file placed in the same folder as its associated audio files.
Only one log file may be in the folder.
Beyond the usual battery of file-level diagnostics, rip checking provides the additional step of determining whether all present MP3 and FLAC files represent a correct EAC/XLD rip.
Check Match FLACs to comparing expected log track CRC-32 values against actual FLAC CRC-32 values. This diagnostic is crucial to validating a rip is archival quality.
Check Count MP3s to compare the expected track count from the log to the actual MP3 count.
Check FLAC tags to diagnose FLAC tag metadata such as correct date format and consistency of album-wide tags.
Check EAC log hash to verify that EAC log files have not been modified using the trailing log checksum available starting with EAC version 1.0. This step requires sending the log file to EAC over http. Support for XLD signature verification is not supported at this time.
Check Enable to escalate the severity of selected diagnostic issues. For EAC log checking, enable strict mode to ensure that rips are of the highest quality.
Check Enable to provide a post-diagnostic step to correct repairable issues. Repairs may be made by pressing the Repair button for each issue. No changes will ever be made to files without hitting Repair first. Enabling repairs will hold locks on files with pending repairs.
Leaving the filter textbox blank will tell Filebert to ignore any file that is not a known extension. This will exclude files with otherwise known formats that are misnamed to an unrecognized extension. However if a filter is supplied, then any file satisfying that filter will be included.
Another use of the filter is to limit diagnostics to a single extension such as using *.log for EAC/XLD log checking only.