Halkett78 wrote: ↑02 Jul 2025, 17:36
Not sure what's happening, every time I match on TheMovieDB, every single files returns as "MOV (2022)"
Did the issue resolve itself? Did you give up on trying to find a solution? If someone bothers go through the high-effort task of registering here in the forums and writing a post but then not bothering with a the low-effort task of a follow-up then that's something really rather confounding...
Hi everyone,
I’m facing the same issue — all my movies are being renamed as “MOV (2022)”.
Here’s a quick summary of my setup:
Sample paths:
D:\Movies\Inception (2010)\inception.2010.mkv
D:\Movies\The Lord of the Rings (2001)\lotr.2001.mkv
Custom format: {n} ({y})/{n} ({y}) - {resolution}
All movies are in separate folders by title and year.
I’ve cleared cache, restarted FileBot, and tested both TMDB and CLI — same result.
Could this be a matching or cache issue? Any suggestions on what else to check?
$ filebot -rename -r Movies --db TheMovieDB -non-strict --action TEST --log INFO
[TEST] from [Movies/Inception (2010)/inception.2010.mkv] to [Movies/Inception (2010)/Inception (2010).mkv]
[TEST] from [Movies/The Lord of the Rings (2001)/lotr.2001.mp4] to [Movies/The Lord of the Rings (2001)/The Lord of the Rings The Fellowship of the Ring (2001).mp4]
Can you reproduce the mismatch with newly created empty test file paths?
Are there any *.nfo or *.url files that might force a bad match?
Can you share the MediaInfo table for one of the files you're testing with?