I didn't add this so far because I fear that people breakt their programs by changing the names, so the files are no longer found. Therefore external checksum files should be used whenever possible. Also I have never seen files with MD5 or even SHA1 checksums in the name - the name would be extremely long...
• Maybe the option could add the CRC as a (descript.ion) comment (info-text) ? Doing so, on one hand, the user could see the CRC and,
on the other hand, the names themselves would remain unchanged, no matter which lenght the CRC is…
- Just a thought.
ghisler(Author) wrote:I didn't add this so far because I fear that people breakt their programs by changing the names, so the files are no longer found. Therefore external checksum files should be used whenever possible. Also I have never seen files with MD5 or even SHA1 checksums in the name - the name would be extremely long...
A "Calculate CRC Checksum and copy to clipboard" option could solve this?
(and please also add the two brackets)
Another possibility to include CRC32 (or any other checksum) in filename is to have LotsOfHashes content plugin installed and to use the following pattern in multi-rename tool
How about adding a CRC parameter to the Multi-Rename function? For example [SFV].
This could be handled in two ways;
1. The CRC is calculated for each file as it goes. Maybe it displays a warning the first time that the process can take a long time if there are large selected with a checkbox not to show the message again.
2. If an SFV file exists with the name of the current working directory, TC would look inside that file to find the CRC values. Or maybe it could allow the user to select the SFV file, similar to how "Load names from file" works.
The two methods could optionally be combined; TC could look inside an SFV file if it exists, rename whatever files it finds listed inside and generate CRCs for the rest on the fly.
By separating the creation of SFV files from renaming the files, it would prevent people from accidentally renaming important files and screwing something up. They would have to intentionally tell the program to rename then files to add the CRC value to the name.