Filebot named files still require opportunistic mode to be renamed

Support for macOS users and the Mac App Store package
Post Reply
jprokos
Posts: 116
Joined: 09 Oct 2016, 02:01

Filebot named files still require opportunistic mode to be renamed

Post by jprokos »

Recently I made big changes in how I format file names to overcome issues I have run into for keeping editions of single movies. These movie files had already been renamed by FileBot a while back and matched to movies in the TMDB database so I presumed they would be matched using strict mode, but they were not.

What would the reason likely be for this?
If it's a TMDB issue, is there anything a user can do to help?

List of previous FileBot renamed movie files that couldn't be renamed using strict mode:

Code: Select all

22 July (2018)
All Quiet on the Western Front (1930)
Animal Crackers (1930)
Battleship Potemkin (1925)
Blow-Up (1966)
Catch-22 (1970)
Chess Fever (1925)
City Girl (1930)
Dolphin Reef (2018)
Fahrenheit 9 11 (2004)
Fahrenheit 11 9 (2018)
Internal Affairs (1990)
Lego Batman - The Movie - DC Super Heroes Unite (2013)
May 18 (2007)
Metropolis (1927)
Moana (1926)
Napoleon (1927)
Nosferatu (1922)
Old Ironsides (1926)
Pay Day (1922)
Punch-Drunk Love (2002)
Santiago, Italia (2018)
Spite Marriage (1929)
Sunrise (1927)
The Broadway Melody (1929)
The Cameraman (1928)
The Circus (1928)
The Cocoanuts (1929)
The Darjeeling Limited (2007)
The Dumb Girl of Portici (1916)
The Kid (1921)
The Navigator (1924)
The Passion of Joan of Arc (1928)
The Son of the Sheik (1926)
The Thief of Bagdad (1924)
Tillie's Punctured Romance (1914)
Vox Lux (2018)
Wamego - Making Movies Anywhere (2004)
Wings (1927)
Wolf Lowry (1917)
After renaming the above in opportunistic mode there were only two remaining:

Code: Select all

Dolphin Reef (2018)
Wamego - Making Movies Anywhere (2004)
Restarting FileBot and using opportunistic mode those movies remained:

Code: Select all

Dolphin Reef (2018)
Wamego - Making Movies Anywhere (2004)
Finally, those movies were able to be renamed holding down the shift key in opportunistic mode but not in strict mode.

Would there have been a better way? Or is this to be expected for various reasons?
User avatar
rednoah
The Source
Posts: 19130
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Filebot named files still require opportunistic mode to be renamed

Post by rednoah »

If you're processing files that have previously been processed already, then you'll want to use Local Xattr Mode to just load in the previously stored match, thereby bypassing any kind of strict or non-strict matching.

:arrow: viewtopic.php?t=2072
:arrow: viewtopic.php?t=324



EDIT:

:!: I vaguely remember that you have reported issues with Preset + Preset Format + Local Xattr Mode. But you can get around that by clicking on Fetch Data ➔ Smart Mode: Attributes and adjusting your custom format via Double-Click ➔ Edit Format after loading in all the matches.
Image



EDIT 2:

Doing a bit of debugging...
* 22 July (2018) doesn't work because 22 July 2018 is recognized as an airdate pattern that would typically identify an Episode. In this case, Strict Mode ignores the file, just like any other file that includes S01E01 or 1x01 or 2020-01-01 type patterns.
* All Quiet on the Western Front (1930) doesn't work because Strict Mode sanity checks the year and excludes numbers that are outside of the 1931..2049 range. This makes Strict Mode ill-suited for your 1900..1930 movies.
* Blow-Up (1966) works for me.

I'll leave it at that for now. Different file. Different issue. The 1931..2049 limit explains most cases though.
:idea: Please read the FAQ and How to Request Help.
Post Reply