I often have downloads of Repack or PROPER and i noticed that my script kept saying file exist didnt process the file. So i checked and found the --conflict and set it to auto. I reran my script and it processed the file. But now i have another file that is Proper and it is giving me the same problem as before.
This worked:
Run script [fn:amc] at [Thu Sep 15 21:41:04 EDT 2016]
Rename episodes using [TheTVDB]
Auto-detected query: [imposteur]
Failed to fetch episode data: [imposteur]
Failed to match files to episode data
Clean clutter files and empty folders
Finished without processing any files
Run script [fn:amc] at [Thu Sep 15 21:41:15 EDT 2016]
Rename episodes using [TheTVDB]
Auto-detected query: [Catfish The TV Show]
Fetching episode data for [Catfish: The TV Show]
Stripping invalid characters from new path: D:/videos/TV/Catfish: The TV Show/Season 5/Catfish: The TV Show - 5x19 - Luis & Sydney
Failed to read media info: null
Skipped [P:\Torrents\Completed\sonarr_tv\catfish.the.tv.show.s05e19.proper.hdtv.x264-w4f.mkv] because [D:\videos\TV\Catfish The TV Show\Season 5\Catfish The TV Show - 5x19 - Luis & Sydney.mkv] already exists
Processed 0 files
Clean clutter files and empty folders
Finished without processing any files
So how does conflict work in auto? How does it consider file is better like stated in the AMC section
--conflict auto Override existing media only if new media is better
Is conflict the only way to manage REPACK and PROPER files?
2.
Currently, FileBot will sort by Repack/Proper, then Resolution(MediaInfo required), then FileSize. Thus a low-resolution Repack/Proper file is considered "better" than a high-resolution non-Repack/Proper file.
If both files are Repack/Proper then --conflict auto will only override the file if Resolution is higher or if FileSize is higher, but not if the files are considered equally good.
PS: Only files that have the Repack/Proper marker in the filename (or original filename stored in xattr metadata) are considered Repack/Proper files.
Since xattr is disabled, the existing file should never be considered Proper/Repack so override should always kick in. I can't explain the behaviour you're getting.
EDIT: There's a bug when -no-xattr is used, and that's causing the Proper/Repack logic to break.