Priority of PROPER with --conflict auto

All your suggestions, requests and ideas for future development
Post Reply
sentience
Posts: 3
Joined: 18 Jun 2020, 03:00

Priority of PROPER with --conflict auto

Post by sentience » 30 Jun 2020, 09:41

I'm running filebot with this command:

Code: Select all

filebot -script 'fn:amc' /volume1/NAS/Downloads/complete/tv --output '/volume1/NAS/iTunes Library' --action duplicate -non-strict --order Airdate --conflict auto --lang en --def 'ut_label=TV' 'music=y' 'unsorted=y' 'skipExtract=y' 'emby=localhost:******' 'pushover=******:******' 'seriesFormat=TV Shows/{n}/{episode.special ? '\''Specials'\'' : '\''Season '\''+s}/{n} - {episode.special ? '\''S00E'\''+special.pad(2) : s00e00} - {t.replaceAll(/[`´‘’ʻ]/, /'\''/).replaceAll(/[!?.]+$/).replacePart('\'', Part $1'\'')}{'\''.'\''+lang}' 'excludeList=filebot_amc.excludes' --apply refresh --log all --log-file '/usr/local/filebot-node/data/filebot.log'
According to this thread, --conflict auto should cause PROPER releases to replace existing files; however, that's not the behaviour I'm seeing. From my task's output:

Code: Select all

Skipped [/volume1/NAS/Downloads/complete/tv/show_name.2020.06.25.episode_name.PROPER.1080p.release_tags/show_name.2020.06.25.episode_name.1080p.release_tags.mkv] because [/volume1/NAS/iTunes Library/TV Shows/Show Name/Season 1/Show Name - S01E123 - Episode Name.mkv] already exists
Is there a bug here?

User avatar
rednoah
The Source
Posts: 18537
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Priority of PROPER with --conflict auto

Post by rednoah » 30 Jun 2020, 10:46

--conflict auto is primarily based on media information, such as bitrate, file size, etc. As such PROPER has no effect, unless the new PROPER release does have higher bitrate, better video resolution, etc.

--conflict override is more suitable for use cases where you simply want the most recently downloaded version.
:idea: Please read the FAQ and How to Request Help.

Post Reply