FileBot

Posted: **27 Mar 2020, 17:27**

I have been running filebot for years on a Linux box and it works great about 98% of the time. I only use it for movies. However, every so often I get a movie that filebot (via TheMovieDB) misidentifies and when it does that it always, as in 100% of the time, identifies the movie as Abduction (2009).https://www.themoviedb.org/movie/175944 ... uage=en-US.

I realize that this may be an issue with TheMovieDB and not filebot, but it has now caused enough of an issue with me having to manually dealing with those movies that I thought I would at least see if there was something that I could do to help resolve the problem.

Here is just a single example:

Movie was downloaded and saved as:
/mount/movies/pre-process/21.Bridges.2019.1080p.BluRay.DD5.1.x264-PbK/f3511c1c13b2455099b0b38977877ca7.mkv

Code: Select all

root@nzbget-1804:/mount/media/pre-process# /usr/bin/filebot -script fn:amc -no-xattr --def ut_label=movie -rename --db TheMovieDB -non-strict "/mount/media/pre-process/21.Bridges.2019.1080p.BluRay.DD5.1.x264-PbK/"
Run script [fn:amc] at [Fri Mar 27 09:26:57 PDT 2020]
Parameter: ut_label = movie
Argument[0]: /mount/media/pre-process/21.Bridges.2019.1080p.BluRay.DD5.1.x264-PbK
Input: /mount/media/pre-process/21.Bridges.2019.1080p.BluRay.DD5.1.x264-PbK/f3511c1c13b2455099b0b38977877ca7.mkv
Group: [mov:abduction 2009] => [f3511c1c13b2455099b0b38977877ca7.mkv]
Rename movies using [TheMovieDB]
Auto-detect movie from context: [/mount/media/pre-process/21.Bridges.2019.1080p.BluRay.DD5.1.x264-PbK/f3511c1c13b2455099b0b38977877ca7.mkv]
[MOVE] Rename [/mount/media/pre-process/21.Bridges.2019.1080p.BluRay.DD5.1.x264-PbK/f3511c1c13b2455099b0b38977877ca7.mkv] to [/mount/media/pre-process/21.Bridges.2019.1080p.BluRay.DD5.1.x264-PbK/Movies/Abduction (2009)/Abduction (2009).mkv]
Processed 1 files

Here is my fn:sysinfo:

Code: Select all

root@nzbget-1804:~# filebot -script fn:sysinfo
FileBot 4.9.0 (r7234)
JNA Native: 5.2.0
MediaInfo: 17.12
p7zip: p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,24 CPUs Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz (206D7),ASM,AES-NI)
unrar: UNRAR 5.50 freeware
Chromaprint: 1.4.3
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2020-03-16 (r625)
Groovy: 3.0.2
JRE: OpenJDK Runtime Environment 11.0.6
JVM: 64-bit OpenJDK 64-Bit Server VM
CPU/MEM: 2 Core / 64 GB Max Memory / 57 MB Used Memory
OS: Linux (amd64)
HW: Linux nzbget-1804 4.15.18-25-pve #1 SMP PVE 4.15.18-53 (Wed, 05 Feb 2020 11:58:15 +0100) x86_64 x86_64 x86_64 GNU/Linux
STORAGE: zfs [/] @ 106 GB | nfs [/mount/media] @ 230 TB
DATA: /root/.filebot
Package: DEB
License: FileBot License P13439121 (Valid-Until: 2021-04-03)
Done ヾ(＠⌒ー⌒＠)ノ

However, when I manually rename the file then it works correctly:
/mount/movies/pre-process/21.Bridges.2019.1080p.BluRay.DD5.1.x264-PbK/21 Bridges (2019).mkv

Code: Select all

Input: /mount/media/pre-process/21.Bridges.2019.1080p.BluRay.DD5.1.x264-PbK/21 Bridges (2019).mkv
Group: [mov:21 bridges 2019] => [21 Bridges (2019).mkv]
Rename movies using [TheMovieDB]
Auto-detect movie from context: [/mount/media/pre-process/21.Bridges.2019.1080p.BluRay.DD5.1.x264-PbK/21 Bridges (2019).mkv]
Stripping invalid characters from new path: Movies/Crime /21 Bridges (2019)/21 Bridges (2019)
[MOVE] Rename [/mount/media/pre-process/21.Bridges.2019.1080p.BluRay.DD5.1.x264-PbK/21 Bridges (2019).mkv] to [/mount/media/Movies/Crime/21 Bridges (2019)/21 Bridges (2019).mkv]
Processed 1 files

I guess I am just wondering if there is anything different that I can do to resolve this mismatching issue or if it is just something that I have to live with.....

Thanks!

Posted: **27 Mar 2020, 17:59**

My educated guess is that your pre-process folder is the root cause of consistently strange behavior:
https://www.themoviedb.org/movie/175944 ... uage=en-US

Rename pre-process to complete and the problem will go away.

Posted: **28 Mar 2020, 01:28**

HAHAHH, you have got to be kidding me....so because the movie has another title called "Process" and my directory is called "pre-process" it basically matches on that instead of the actual title of the movie?

Well, I will change the directory to something different and see if the problem goes away and report back here!!

Thank You!

Posted: **28 Mar 2020, 02:14**

Just a quick update. I took two separate movies that had both been identified as 'Abduction (2009)' and moved them into a different directory (out of pre-process) and they worked perfectly.

Thank you again for such a quick reply and for the answer to the problem, I don't think I would have ever made that connection had it not been for your help.

Posted: **28 Mar 2020, 03:41**

MD500Pilot wrote: ↑28 Mar 2020, 01:28 HAHAHH, you have got to be kidding me....so because the movie has another title called "Process" and my directory is called "pre-process" it basically matches on that instead of the actual title of the movie?

It can happen. FileBot looks at everything, and picks the "best" match, which can easily be wrong if the actual correct match isn't an option in the first place for some reason.

pre-process has been added to the blacklist, so starting next week FileBot will know that's definitely not a movie name:
viewtopic.php?t=360

MD500Pilot wrote: ↑28 Mar 2020, 02:14 Thank you again for such a quick reply and for the answer to the problem, I don't think I would have ever made that connection had it not been for your help.

If you get the same problem for different movies at different times, then the common denominator is likely a common parent folder, or a stray *.nfo file, misleading things.

Posted: **28 Mar 2020, 03:46**

Well, thank you again for the quick pointer, this has been driving me nuts for a long time now

FileBot

Matching Issues with TheMovieDB always defaults to same exact movie

Matching Issues with TheMovieDB always defaults to same exact movie

Re: Matching Issues with TheMovieDB always defaults to same exact movie

Re: Matching Issues with TheMovieDB always defaults to same exact movie

Re: Matching Issues with TheMovieDB always defaults to same exact movie

Re: Matching Issues with TheMovieDB always defaults to same exact movie

Re: Matching Issues with TheMovieDB always defaults to same exact movie