Say i have a hardlink library to browse by movie rating, those ratings can change. When filebot rescans my plex master structure to create hardlinks, it'll format the hardlinks with the new rating - which i want - but won't delete the older one - which i'd want.rednoah wrote: ↑14 Sep 2016, 05:33 Description:
Finding duplicate movie or episode files is easy once all your content has been renamed and xattr tagged with FileBot. This script allows you to view or delete duplicates.
List Logical Duplicates:There are logical duplicates when multiple files refer to the same movie or episode (e.g. 1080p and 4K versions of the same movie or episode).
Code: Select all
filebot -script fn:duplicates /path/to/files
List Binary Duplicates:There are binary duplicates when multiple files are identical byte for byte (i.e. copies of the same file).
Code: Select all
filebot -script fn:duplicates --mode binary /input /output /backup
NOTE: FileBot 4.9.2 (r7667) or higher is required to efficiently deduplicate links.
--action delete delete duplicate files
-mediainfo <options> perform -mediainfo command on duplicate files
-rename <options> perform -rename command on duplicate files
--order input sort duplicates by input argument order (default in --mode binary)
--order quality sort duplicates by highest quality first (default in --mode logical)
--order date sort duplicates by least recently created (according to Media Encoding Date or File Creation Date)
--order time sort duplicates by least recently modified (according to File Last-Modified Date)
- In --mode logical, as per --order quality, the --action delete option will keep only the one file with the highest video quality.
- In --mode logical, this script will not parse or guess any information from the filename. Files that do not contain xattr metadata will be ignored.
- In --mode binary, as per --order input, the --action delete option will keep only the first occurrence of a file according to the input argument order.
- In --mode binary, this script may read files partially or entirely to compute checksums, which are then stored as xattr to speed up subsequent runs.
Can --order time be altered to keep the most recently modified file instead of the least recently modified one?
Always want the new location/name to be kept while the other one gets deleted.
I realize after hardlinking i should run a second process with fn:duplicates at that hardlink location, but i'm not sure what should be the arguments. I want to keep best quality always, and in case those are binary copies i want to keep the new file/location format.