Constant issues with matching (with AniDB)

[blacktorrent]

I've used previous versions of this software in the past and never really had matching issues. With this latest version (5.2.1) i've have no luck matching against anything from anidb. I've been forced to search for the title on anidb, get the anidb number of the show, and shift-click fetch and use the number to get a proper match.

At first i thought that this might be an issue with matching against adult content but that was never an issue before and even the FAQ/other posts state that this should not be an issue. I then thought that it might be a file name issue (even though its only searching against the anime title and not the episode name in the file name) and no dice. I even tried to have it match against my cowboy bebop folder and it wouldn't match (which was renamed via an older version of filebot). I even took a folder/file that was manually done with the shift-click + anidb number to see if it would match again and still nothing.

There is something seriously wrong with this version.

[rednoah]

I cannot fundamentally reproduce the issue. I made a up an example file name and it works just fine here:

Console Output: Select all

$ filebot -rename *.mkv --db AniDB
Rename episodes using [AniDB] with [Absolute Order]
Lookup via [Cowboy Bebop] [Cowboy Bebop]
Fetching episode data for [Cowboy Bebop]
* Cowboy Bebop [23] | 26 episodes | 01-26
[MOVE] from [Cowboy Bebop 01.mkv] to [Cowboy Bebop - 01 - Asteroid Blues.mkv]
Processed 1 file

Can you provide sample file paths as text for files that do not work for you so we can establish a baseline and see if we can reproduce the issue?


Does the log say anything? Perhaps the AniDB search index fails to load for some reason? (see How to Request Help)


AniDB H content is not and never was supported. H results will not appear in search results because they are not indexed for search in the first place. That said, if you enter the ID or have an anidb-12345 marker in the file path, then FileBot will simply use that ID as-is without question even if that ID is an ID for H content, movie content, etc, content that would normally not be supported via search-by-name.