AniDB metadata agent

Dev Community Dev/API Corner
161

Thanks for this great plugin. Though it took me a bit to find all the pieces of information to make it go. Was thinking you might add some of the following information to your original post to help new users out. Just a suggestion.



F.A.Q:



Q: Where do i input my AniDB.net username and password?

A: You need to manually edit the com.plexapp.agents.anidb.xml file. This file is found in the /Plug-in Support/Preferences/ directory ( depends on your platform). If the file doesn’t exist yet, you can also manually create it with the following template:



<?xml version='1.0' encoding='utf-8'?><br />
<PluginPreferences><br />
<username>username</username><br />
<password>password</password><br />
</PluginPreferences>


**Q:** The scanner shows up now, but I am still unable to select the anidb option. It's grayed out. How do I enable it?
**A:** That's normal. What you're doing on that screen is enabling other agents to contribute to Plex's metadata. It doesn't make sense for AniDB to contribute to itself so it's greyed out. It needs to be the primary metadata agent for the section. Assuming you've got a section created in your PMS manager, open the section you created for your anime TV/Movies, click Edit Session, then on the box that pops up, hit 'Advanced' and change your Primary Metadata Agent to AniDB.

**Q:** My shows are still showing up as Season 1, Season 2, etc, instead of their absolute numbering.
**A:** This happens because the Plex Series Scanner will assume that Episode 100 is Episode 00 of Season 1, and things go haywire. If you are watching shows with > 100 episodes (eg Bleach, Naruto, Fairy Tail, One Piece and so on) you will also want to install the BABS scanner [found here](http://forums.plexapp.com/index.php/topic/31081-better-absolute-scanner-babs/). Once it is installed, open the section you created for your anime TV/Movies, click Edit Section, then on the box that pops up, hit 'Advanced' and change your Media Scanner to BABS.
162


mattrk, thanks for the suggestion, might take you up on that one. Currently my priority is making the plugin work properly with what little time I have. Good summary though!
163

New version out - v10. Handles re-use of open connection better. Install as usual.

164

Hi,

I was wondering how you can pass a different Anime title to Plex. Currently the Official Title (per AniDB) is pass onto Plex as the tv series name, I would like to have the Main Title (per AniDB) be the tv series name.



Thanks,

165


There's no notion of "main" versus "official" title in the API, there are just titles in different languages. Currently the agent selects titles in the order of English, Romaji, Kanji and I suspect that you want the Romaji name? I've been meaning to add this as a configurable element, so that you can choose what languages to use as primary. I'll see what I can do, but in the meantime you can change this yourself in the code if you want to. In the agent main code file (__init.py__), change line 153 from

self.getValueWithFallbacks(anime.dataDict, 'english_name', 'romaji_name', 'kanji_name')

to

self.getValueWithFallbacks(anime.dataDict, 'romaji_name', 'english_name', 'kanji_name')

and line 232 from

self.getValueWithFallbacks(fileInfo.dataDict, 'english_name', 'romaji_name', 'kanji_name')

to

self.getValueWithFallbacks(fileInfo.dataDict, 'romaji_name', 'english_name', 'kanji_name')
166

Hi,

I’ll try the romanji option and see the results. What I was really looking for is that AniDB publishes a animetitles.xml (a copy of it is retrieved as part of this scanner I believe). In it there for every aid there is a list of titles with each title having an associated type. I want to pass this onto Plex as the title of the Anime. Where in adba does it retrieve data from this file, I’m thinking of writing an separate function to use the aid to pull the main title and then pass it onto Plex.

167


The adba used in this agent does not read from the xml files, it retrieves everything from the API, so no luck there. I think that all main titles (almost all at least) are Romaji, so you should get what you want from that.
168

Something I’ve just run into now. I accidentally managed to nuke my server database while upgrading ( <_< ) and so I’m reloading a fair bit of metadata at once. Unfortunately the anidb flood protection kicked in and my IP has been banned. This was okay at first, I was getting messages like:



2012-10-27 23:41:24,809 (-4b510470) :  INFO (__init__:184) - Could not load file data, msg: Not sending, banned


Then it'll throw an exception up the chain and everything continues to the next set of files.

(Side note: it tries to lookup by hash, fails due to ban, then re-tries by name, fails again due to the ban - probably should change this so that it doesn't do a name lookup)

This was happening fairly speedily for a while, but at some point along the way it's slowed down completely and I'm not getting the ban messages. Instead I just get a line starting the search:


2012-10-27 23:51:31,697 (-4be04470) :  INFO (agentkit:914) - Searching for matches for {'openSubtitlesHash': 'e040930a1d497cbd', 'episode': '5', 'episodic': '1', 'show': 'Shinsekai Yori', 'season': '1', 'filename': '%2Fshare%2FMD0_DATA%2FMultimedia%2FVideo%2FAnime%2FShinsekai%20Yori%2F[UTW]_Shinsekai_Yori_-_05_[h264-720p][2CCE22D0]%2Emkv', 'plexHash': '90347e508d40d9f8f73eea0c2237d46a1e882ff6', 'duration': '-1', 'id': '1378'}


And then nothing in the log for five minutes, presumably the lookup is timing out and the system is killing the lookup and moving on.

This is fine I guess but the downside here is that it's going to take about three or four hours for the whole-folder update to actually "complete" so I can re-start it again and at this rate I might have to take several passes at it before I get everything updated again.

AniDB's flood protection says not to send queries more than once every 4 seconds for an 'extended period of time' which they don't define. In my case the update started at 22:51:07 and the first 'banned' message I see in my log was 23:31:23 so I'm guessing the flood protection has a 40 minute window currently (fits nicely with the every 4 seconds thing). This is probably difficult, but the best thing to do would be to simply delay sending any requests for ~30 seconds every 5 minutes or so. Not entirely sure how that could be achieved though, since the calls are synchronous. I suspect doing something as conceptually simple as that would require a whole lot of fiddling.

The first point it looks like I start getting timeouts is at 23:41:27 which is ten minutes after I was banned. I suspect the problem here is that this is when the authenticated connection has died. The idle timeout thread you're running may not be recovering when a ban is happening correctly (alternatively it might be retrying the connection repeatedly which possibly extends the duration of the ban? I hope not)
169

I’m also getting an odd issue where a series will correctly finish pulling data from AniDB, serialize out, but the final metadata doesn’t get reloaded into Plex and the only way to get it to appear is to retry. I don’t know if this is relevant - it might be a coincidental timing issue - but it seems like every time this happens, the CheckConnection thread has fired during the update and then re-schedules itself right toward the end, eg:



2012-10-28 13:36:22,957 (-4b670470) :  DEBUG (runtime:1083) - Starting timed thread named 'checkConnection'<br />
2012-10-28 13:36:22,959 (-4b670470) :  INFO (__init__:27) - Checking for idle connection timeout...<br />
2012-10-28 13:36:25,545 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 21<br />
2012-10-28 13:36:31,536 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 22<br />
2012-10-28 13:36:37,583 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 23<br />
2012-10-28 13:36:43,597 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 1<br />
2012-10-28 13:36:49,530 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 3<br />
2012-10-28 13:36:55,554 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 2<br />
2012-10-28 13:37:01,608 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 5<br />
2012-10-28 13:37:07,563 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 4<br />
2012-10-28 13:37:13,621 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 7<br />
2012-10-28 13:37:19,619 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 6<br />
2012-10-28 13:37:25,619 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 9<br />
2012-10-28 13:37:31,543 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 8<br />
2012-10-28 13:37:37,578 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 11<br />
2012-10-28 13:37:43,640 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 10<br />
2012-10-28 13:37:49,648 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 13<br />
2012-10-28 13:37:55,594 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 12<br />
2012-10-28 13:38:01,613 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 15<br />
2012-10-28 13:38:07,658 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 14<br />
2012-10-28 13:38:13,623 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 17<br />
2012-10-28 13:38:19,607 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 16<br />
2012-10-28 13:38:25,639 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 19<br />
2012-10-28 13:38:31,597 (-4b95e470) :  INFO (__init__:307) - Loading metadata for 'Shakugan no Shana Final', episode 18<br />
2012-10-28 13:38:37,674 (-4b670470) :  DEBUG (runtime:1077) - Scheduled a timed thread named 'checkConnection'<br />
2012-10-28 13:38:37,847 (-4b95e470) :  DEBUG (model:218) - Serializing to /root/Library/Plex Media Server/Metadata/TV Shows/a/b09f04e9667b702a43a67cadb053df11e182232.bundle/Contents/com.plexapp.agents.anidb/Info.xml<br />
2012-10-28 13:38:37,855 (-4b95e470) :  DEBUG (runtime:851) - Response: [200] str, 16 bytes<br />


Should it take that long to do the connection timeout check?
170


Yes, all the code uses a lock so as to avoid parallel calls to aniDB - this goes for the connection reaper thread as well (otherwise it might reap a connection that is in use). The first output, "Checking for idle connection timeout" comes before aquiring the lock, but then the code has to wait for an anime lookup before proceeding - hence the long time before schedule end. I could move the first output line to after aquiring the lock to avoid confusion.
171


The ban issue is a nasty beast. Generally I've been relying on the underlying client (adba) to handle all such things, but as becoming evident - it doesn't. I know that there's some kind of throttle in place, but looking through the code I'm not sure it's working as intended. I'll see if this is something that might have been broken when I ported the client to Plex's runtime or what is going on. Although I would think that the delay caused by Plex's internal handling of each lookup should well account for a general four second delay. At least on my machine it's a lot slower than that over time, but perhaps it's just that I got a slow machine :rolleyes:
172


This is running on my QNAP NAS which is a dual core 1.6ghz Atom, so not exactly a supercomputer. The time to do the lookup for a series is slower, but once it's matched the series, the EPISODE calls run through quite fast.
173


I'm only on a 439-ProII+ so you've got one core more than me ;-) Still, if you look at the log you posted above, there's more than four seconds between every call, even for the episodes. This is what I see also, so there's something fishy here.
174


Actually I'm on the exact same hardware - I hadn't really paid attention to the number of cores (it's always handled anything I throw at it without much of an issue) just seen it running two threads at the same time. Checking now it's single-core but Hyperthreaded.

Perhaps it might simply be sustained traffic over a specific period without a gap that causes the flood protection to kick in. It might be worth asking the AniDB developers - perhaps it's related to the amount of traffic they're experiencing. UDP isn't a good protocol for high traffic unfortunately. Good for streaming and stuff where you can drop packets, not fantastic for what is essentially a database interface.
175


To be honest, seeing the intermittent failures in AniDB that somehow just fixes themselves I think this is something to do with the API implementation on their side. Since they're beeing so secretive about their rules I guess all we can do is ask, but I wouldn't expect an answer. As for the technical discussion about the API, let's just say it's not the way I would have designed it ;-).
176

Digging through their docs & forum a bit it also looks like when you’re getting toward the flood point it’ll start to drop packets more often, which will be why sometimes when refreshing long series (eg 150+ episodes of Fairy Tail) it will time out. I doubt that you could use that as a good thing to hook to know when to take a break though.

177


No, there's no way to differentiate between a bad network line and the flood protection rules kicking in (a dropped packet is simply a dropped packet), so no point in using that one I'm afraid. Another way would be to re-write the agent to utilize the HTTP api after identifying the series/movie. That way the calls would be spread between the HTTP API and the UDP API, reducing the risk of being banned. It would require quite a lot of work though, and it's not something that I will prioritize at the moment I'm afraid.
178

NVM!

179

For some reason I’m not getting any results, seems to be connecting fine. Any ideas?



Running on OSX ML with the v10 AniDB agent and latest PMS.



Marker - Nov 14, 2012 5:06:06 PM<br />
Nov 14, 2012 17:06:14 [0xacaa6a28] DEBUG - Most recent grandchild was episode 12<br />
Nov 14, 2012 17:06:14 [0xb0bbe000] DEBUG - Most recent grandchild was episode 12<br />
Nov 14, 2012 17:06:14 [0xb0bbe000] DEBUG - Issuing search query: http://127.0.0.1:32400/system/agents/search?mediaType=2&id=1140&identifier=com.plexapp.agents.anidb&duration=842645&episodic=1&filename=%252FVolumes%252FElephantine%252FAnime%252FDetroit%2520Metal%2520City%252F[Delicio%252Eus]%2520Detroit%2520Metal%2520City%2520-%252012%2520(1920x1080%2520H%252E264%2520AAC)%2520[97fc6fd8]%252Emkv&lang=en&openSubtitlesHash=18604e5c&plexHash=227cec8f9df8bf956ed78f8cc9aec95673b5879a&episode=12&episodic=1&season=1&show=Detroit%20Metal%20City&manual=1<br />
Nov 14, 2012 17:06:14 [0xb0bbe000] DEBUG - HTTP requesting to: http://127.0.0.1:32400/system/agents/search?mediaType=2&id=1140&identifier=com.plexapp.agents.anidb&duration=842645&episodic=1&filename=%252FVolumes%252FElephantine%252FAnime%252FDetroit%2520Metal%2520City%252F[Delicio%252Eus]%2520Detroit%2520Metal%2520City%2520-%252012%2520(1920x1080%2520H%252E264%2520AAC)%2520[97fc6fd8]%252Emkv&lang=en&openSubtitlesHash=18604e5c&plexHash=227cec8f9df8bf956ed78f8cc9aec95673b5879a&episode=12&episodic=1&season=1&show=Detroit%20Metal%20City&manual=1<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG - Request: GET /system/agents/search?mediaType=2&id=1140&identifier=com.plexapp.agents.anidb&duration=842645&episodic=1&filename=%252FVolumes%252FElephantine%252FAnime%252FDetroit%2520Metal%2520City%252F[Delicio%252Eus]%2520Detroit%2520Metal%2520City%2520-%252012%2520(1920x1080%2520H%252E264%2520AAC)%2520[97fc6fd8]%252Emkv&lang=en&openSubtitlesHash=18604e5c&plexHash=227cec8f9df8bf956ed78f8cc9aec95673b5879a&episode=12&episodic=1&season=1&show=Detroit%20Metal%20City&manual=1 [127.0.0.1:57659] (1 live)<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * mediaType => 2<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * id => 1140<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * identifier => com.plexapp.agents.anidb<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * duration => 842645<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * episodic => 1<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * filename => %2FVolumes%2FElephantine%2FAnime%2FDetroit%20Metal%20City%2F[Delicio%2Eus]%20Detroit%20Metal%20City%20-%2012%20(1920x1080%20H%2E264%20AAC)%20[97fc6fd8]%2Emkv<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * lang => en<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * openSubtitlesHash => 18604e5c<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * plexHash => 227cec8f9df8bf956ed78f8cc9aec95673b5879a<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * episode => 12<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * episodic => 1<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * season => 1<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * show => Detroit Metal City<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG -  * manual => 1<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG - [com.plexapp.system] Sending command over HTTP (GET): /system/agents/search?mediaType=2&id=1140&identifier=com.plexapp.agents.anidb&duration=842645&episodic=1&filename=%252FVolumes%252FElephantine%252FAnime%252FDetroit%2520Metal%2520City%252F[Delicio%252Eus]%2520Detroit%2520Metal%2520City%2520-%252012%2520(1920x1080%2520H%252E264%2520AAC)%2520[97fc6fd8]%252Emkv&lang=en&openSubtitlesHash=18604e5c&plexHash=227cec8f9df8bf956ed78f8cc9aec95673b5879a&episode=12&episodic=1&season=1&show=Detroit%20Metal%20City&manual=1<br />
Nov 14, 2012 17:06:14 [0xb0cc2000] DEBUG - HTTP requesting to: http://127.0.0.1:57378/system/agents/search?mediaType=2&id=1140&identifier=com.plexapp.agents.anidb&duration=842645&episodic=1&filename=%252FVolumes%252FElephantine%252FAnime%252FDetroit%2520Metal%2520City%252F[Delicio%252Eus]%2520Detroit%2520Metal%2520City%2520-%252012%2520(1920x1080%2520H%252E264%2520AAC)%2520[97fc6fd8]%252Emkv&lang=en&openSubtitlesHash=18604e5c&plexHash=227cec8f9df8bf956ed78f8cc9aec95673b5879a&episode=12&episodic=1&season=1&show=Detroit%20Metal%20City&manual=1<br />
Nov 14, 2012 17:06:14 [0xb0eca000] DEBUG - Request: GET /:/plugins [127.0.0.1:57661] (2 live)<br />
Nov 14, 2012 17:06:14 [0xb0eca000] DEBUG - It took 0.000072 sec to serialize a list with 27 elements.<br />
Nov 14, 2012 17:06:14 [0xb0eca000] DEBUG - Request: GET /:/plugins/com.plexapp.agents.anidb/messaging/function/X0FnZW50S2l0OlNlYXJjaA__/Y2VyZWFsMQoxCmxpc3QKMApyMAo_/Y2VyZWFsMQoyCmRpY3QKZGljdAo0CnMyCmVuczQKbGFuZ3M3ClRWX1Nob3dzMTAKbWVkaWFfdHlwZWIxczYKbWFudWFscjEKczYKa3dhcmdzOQpzOAoxODYwNGU1Y3MxNwpvcGVuU3VidGl0bGVzSGFzaHMyCjEyczcKZXBpc29kZXMxCjFzOAplcGlzb2RpY3MxOApEZXRyb2l0IE1ldGFsIENpdHlzNApzaG93czEKMXM2CnNlYXNvbnMxNTcKJTJGVm9sdW1lcyUyRkVsZXBoYW50aW5lJTJGQW5pbWUlMkZEZXRyb2l0JTIwTWV0YWwlMjBDaXR5JTJGW0RlbGljaW8lMkV1c10lMjBEZXRyb2l0JTIwTWV0YWwlMjBDaXR5JTIwLSUyMDEyJTIwKDE5MjB4MTA4MCUyMEglMkUyNjQlMjBBQUMpJTIwWzk3ZmM2ZmQ4XSUyRW1rdnM4CmZpbGVuYW1lczQwCjIyN2NlYzhmOWRmOGJmOTU2ZWQ3OGY4Y2M5YWVjOTU2NzNiNTg3OWFzOApwbGV4SGFzaHM2Cjg0MjY0NXM4CmR1cmF0aW9uczQKMTE0MHMyCmlkcjAK [127.0.0.1:57662] (2 live)<br />
Nov 14, 2012 17:06:14 [0xb0eca000] DEBUG - [com.plexapp.agents.anidb] Sending command over HTTP (GET): /:/plugins/com.plexapp.agents.anidb/messaging/function/X0FnZW50S2l0OlNlYXJjaA__/Y2VyZWFsMQoxCmxpc3QKMApyMAo_/Y2VyZWFsMQoyCmRpY3QKZGljdAo0CnMyCmVuczQKbGFuZ3M3ClRWX1Nob3dzMTAKbWVkaWFfdHlwZWIxczYKbWFudWFscjEKczYKa3dhcmdzOQpzOAoxODYwNGU1Y3MxNwpvcGVuU3VidGl0bGVzSGFzaHMyCjEyczcKZXBpc29kZXMxCjFzOAplcGlzb2RpY3MxOApEZXRyb2l0IE1ldGFsIENpdHlzNApzaG93czEKMXM2CnNlYXNvbnMxNTcKJTJGVm9sdW1lcyUyRkVsZXBoYW50aW5lJTJGQW5pbWUlMkZEZXRyb2l0JTIwTWV0YWwlMjBDaXR5JTJGW0RlbGljaW8lMkV1c10lMjBEZXRyb2l0JTIwTWV0YWwlMjBDaXR5JTIwLSUyMDEyJTIwKDE5MjB4MTA4MCUyMEglMkUyNjQlMjBBQUMpJTIwWzk3ZmM2ZmQ4XSUyRW1rdnM4CmZpbGVuYW1lczQwCjIyN2NlYzhmOWRmOGJmOTU2ZWQ3OGY4Y2M5YWVjOTU2NzNiNTg3OWFzOApwbGV4SGFzaHM2Cjg0MjY0NXM4CmR1cmF0aW9uczQKMTE0MHMyCmlkcjAK<br />
Nov 14, 2012 17:06:14 [0xb0eca000] DEBUG - HTTP requesting to: http://127.0.0.1:57446/:/plugins/com.plexapp.agents.anidb/messaging/function/X0FnZW50S2l0OlNlYXJjaA__/Y2VyZWFsMQoxCmxpc3QKMApyMAo_/Y2VyZWFsMQoyCmRpY3QKZGljdAo0CnMyCmVuczQKbGFuZ3M3ClRWX1Nob3dzMTAKbWVkaWFfdHlwZWIxczYKbWFudWFscjEKczYKa3dhcmdzOQpzOAoxODYwNGU1Y3MxNwpvcGVuU3VidGl0bGVzSGFzaHMyCjEyczcKZXBpc29kZXMxCjFzOAplcGlzb2RpY3MxOApEZXRyb2l0IE1ldGFsIENpdHlzNApzaG93czEKMXM2CnNlYXNvbnMxNTcKJTJGVm9sdW1lcyUyRkVsZXBoYW50aW5lJTJGQW5pbWUlMkZEZXRyb2l0JTIwTWV0YWwlMjBDaXR5JTJGW0RlbGljaW8lMkV1c10lMjBEZXRyb2l0JTIwTWV0YWwlMjBDaXR5JTIwLSUyMDEyJTIwKDE5MjB4MTA4MCUyMEglMkUyNjQlMjBBQUMpJTIwWzk3ZmM2ZmQ4XSUyRW1rdnM4CmZpbGVuYW1lczQwCjIyN2NlYzhmOWRmOGJmOTU2ZWQ3OGY4Y2M5YWVjOTU2NzNiNTg3OWFzOApwbGV4SGFzaHM2Cjg0MjY0NXM4CmR1cmF0aW9uczQKMTE0MHMyCmlkcjAK<br />
Nov 14, 2012 17:06:14 [0xb0f4c000] DEBUG - Request: GET /library/metadata/1140/tree [127.0.0.1:57664] (3 live)<br />
Nov 14, 2012 17:06:14 [0xb0f4c000] DEBUG - It took 0.000662 sec to serialize a list with 1 elements.<br />
Nov 14, 2012 17:06:22 [0xb0eca000] DEBUG - [com.plexapp.agents.anidb] HTTP reply status 200, with 320 bytes of content.<br />
Nov 14, 2012 17:06:22 [0xb0cc2000] DEBUG - [com.plexapp.system] HTTP reply status 200, with 130 bytes of content.<br />
Nov 14, 2012 17:06:22 [0xb0bbe000] WARN - No matches for search.<br />
180

I am having trouble even getting PMS to see the plug-in. It is in the plug-ins folder next to all the other scrapers but it is not an option in the preferences. Anyone have any ideas?