So i did a test with a anime called Angel Beats!
First, i don’t know if this is by design but no matter which episode i search for, Fanzub always returns the same results…I doesnt look for only episode 2 if that is what im searching for.
Second, It seems to return only the first 100 result which seems to be a problem in this case with this anime since it has result with non-english version that seem to be the first to be returned. So when i do a auto search i get nothing downloaded because all the engligh 720p are after those 100 results. When i check on Fanzub directly, i see the 720p version that dont show up at all in Drone.
So i dont know if you could extend the result to like 200 or 500 or ignore non-english so that the 100 results are only english content?
Just tested Anime Black bullet and again it wont even pickup episode 1 because its not within the first 100 result.
Thats Fanzub’s searching, it doesn’t take the episode number into account properly when searching. AFAIK they don’t have paging, making 200 results the absolute max to get in one call, we have set it to 100 to be inline with what other indexers provide.
Ic, well this is a issue cuz so far every anime i tried doesnt seem to pick up e1 because its not part of the 100 results. Both Angel Beats and Black Bullet
saitoh183: That is a result of the way NZBDrone currently searches. When searching for something like Episode 1 of Angel Beats, it looks for Angel Beats! 1 on Fanzub. This returns a ton of results because the number 1 shows up everywhere in those files, normally as part of the hash or the resolution. There was a commit yesterday that fixes this issue though, by searching for 01 instead of 1. This gets rid of most of the garbage search results. Whenever the next release happens, that should fix your issue.
@meris608 that change went out yesterday after it was merged. It does not solve the problem, it only improves it slightly. @saitoh183 and I qlked about this earlier and we seem to have a reasonable solution that I’ll be working on.
i think this thread can be marked as resolved because of the latest commit which has addressed the issue