I’ve gone ahead and released the fifth demo of the newly re-coded AMSA.
The demo is meant for people who’d like to help me test the new functionality and i’d advise people don’t use this as their primary agent but instead create a new Plex library in order to demo it.
Changes since demo 4:
Tweaked series matching scores (previously some scores were lower than expected).
Switched to using image thumbnails for TvDB & AniDB sources (this reduces the agents bandwidth usage and speeds up initial metadata download times; side effect is reduced quality of images in the Plex edit menu’s though if selected then the full quality images are retrieved).
Added AniDB AntiBan support for various scenarios (including but not limited to multiple servers sharing the same external IP; this will significantly reduce the likelihood of an AniDB ban for large libraries).
thanks for the update and sorry for the late replay.
The AniDB ban was indeed the cause of only half of the metadata getting downloaded. after 24 hours i could download most of the other info. I also noticed that by changing the episode metadata from “AniDB,TVDB,Plex” -> “TVDB,AniDB,Plex” helps a lot with preventing the ban.
About the OVA i also found out something interesting.
It has to do how AniDB and TVDB save their data. AniDB saves all OVA’s as separate entry’s, even when its part of an full anime series. TVDB saves original OVA as its own entry but as soon as its part of an anime series it saves it under that anime.
The problem arises when the metadata agent is finding the data on AniDB but not an 100% title match on TVDB, it then stops with getting any data from any site. The reason why some OVA’s work is when they don’t have any search results on TVDB.
in it self i’m not to bothered with this but it also seem to effect rare anime series with 2 seasons. (example: Black Lagoon)
AniDB sees 2 seasons as 2 separate entry’s (3395, 4597). But TVDB saved it as 1 entry. This results in that the second season will not give a 100% match in the search results of TVDB and it stops downloading the metadata.
The irony is that because the OVA is linked to the series in the TVDB search results it will download the data for the OVA.
I will send you the logs btw. let me know if you want me to test anything.
The agent is coded to cope with the differences between TvDB and AniDB though this depends on a mapping file which can sometimes be incorrect; fortunately once affected series are identified its pretty trivial for me to correct the issue.
In this case however it looks like there’s an underlying bug which keeps popping up and disrupting the process, once I correct this then it should fix the OVA issue.
Could you do me a favour and send over a zipped copy of your AMSA bundles folder (found at “Plex Media Server\Plug-in Support\Data\com.plexapp.agents.amsa_test\DataItems\Cache\Bundles”) as this will help me identify where this issue resides.
As for the AniDB ban, this should be less of a problem with the new demo 5 which contains a few new processes to help balance AniDB access.
@Jackolas126 Just a quick update for you, I’ll look into the issue this evening so hopefully I’ll have good news by tomorrow. Also Ignore Demo 5 for the time being as its got a bug where it can actually hinder AniDB searches in specific scenarios, best to wait for Demo 6 which should include the OVA fix.
I’ve gone ahead and released the sixth demo of the newly re-coded AMSA.
The demo is meant for people who’d like to help me test the new functionality and i’d advise people don’t use this as their primary agent but instead create a new Plex library in order to demo it.
Changes since demo 5:
Fixed an issue which was slowing series matching.
Tweaked the new AniDB AntiBan support behaviour (was on by default in demo 5, now only used when required).
Fixed an error caused by missing metadata.
Added a AniDB ‘Bad Episode Name’ list (the agent will skip AniDB episode title metadata if it matches any pattern in the new list).
@Jackolas126 I believe I’ve managed to track down the issue which was causing your OVA problems, see if Demo 6 fixes the issue; if not then your logs and bundle files would again be appreciated.
reloaded the entire library. the ban thingy is almost completely fixed.
also 99% of all entries are found and it downloads the metadata.
but its not problem free yet (sorry for this)
Atm all movies and OVA’s that share a name with an anime series will download the metadata from series instead of the OVA or movie. Unique movies and OVA’s that don’t share a name work perfectly.
in general this is not a problem but plex has this behavior that 2 items with the same metadata get merged together. and then you get multiple episode 1 etc (the OVA, Serie and movie merged into 1 entry).
Hmmm, sorry. Somewhat noob here. But I copied the files into the users/appdata…plex media server folder. The scanner shows up, but not the agent mentioned in the Readme?
@brushrop03 said:
Hmmm, sorry. Somewhat noob here. But I copied the files into the users/appdata…plex media server folder. The scanner shows up, but not the agent mentioned in the Readme?
edit: Aaaand nvm. Just showed up
Just for anyone who’s experiencing this issue, Plex tends to load agents lazily (only loading them when required) which sometimes means new agents don’t immediately appear. The workaround is to restart Plex which tends to force it to load though even then it might not be immediate.
Each tag within an AniDB series are weighted which roughly reflects how many people have approved it, the AMSA agent has a setting (see below) which allows you to select the ‘minimum’ weight a tag must be before it’s added to Plex as a genre.
The default value for this setting is pretty conservative so try lowering it and see if that helps, if not then could you do me a favour and send over a zipped copy of your AMSA bundles folder (found at “Plex Media Server\Plug-in Support\Data\com.plexapp.agents.amsa_test\DataItems\Cache\Bundles”) and log files (found at “Plex Media Server\Logs\PMS Plugin Logs” - Amsa 1-5) as this will help me identify where the issue resides.
I’m trying to use AMSA alongside Plex Trakt Scrobbler but it doesn’t seem to send watched/collected shows to Trakt. AniDB metadata agents support (HAMA specifically) was added in v1.1.0.6.
@Vustom Unless I’m misunderstanding some of the comments on Plex Trakt Scrobbler’s github they only support the hama plugin (due to the way they’re identifying each series ID); it shouldn’t be difficult to add support for AMSA but they’ll need to add it at there end.
@Dingmatt I’m having some problems with titles for certain shows pulled of off AniDB. For Example: https://anidb.net/perl-bin/animedb.pl?show=anime&aid=9541
Even if I set the First, Second and Third Language preference for the Series title to “en” it still names it after the main name (Shingeki no Kyojin) and not (Attack on Titan)
@Dingmatt I’m experiencing an issue with the metadata for my hero academia season 2 it’s essentially showing up as season 1 episodes even have season one names despite using filebot to fix it
@Immortaldaul These kinds of issues are usually related to the file scanner so lets first try updating that with the following steps:
Download the latest version of Zero-QI’s Absolute Series Scanner from the following page (github.com/ZeroQI/Absolute-Series-Scanner), you’ll need to use the ‘clone or download’ button rather than the version on the release page.
Extract the zip.
Copy the file named “Absolute Series Scanner.py” from the extracted directories (found at ‘Absolute-Series-Scanner-master\Scanners\Series’) to your Plex series scanner folder (‘Plex Media Server\Scanners\Series’); this should overwrite an existing file.
Restart Plex.
Rescan your anime library (the triple dot menu then ‘Scan Library Files’).
Goto ‘My Hero Academia’ within Plex and refresh its meta (the triple dot menu then ‘Refresh Metadata’)
Hopefully that should work, if it does then please let me know and I’ll look to include the latest scanner in the next version of AMSA; if not then could you do me a favour and send over a zipped copy of your AMSA bundles folder (found at “Plex Media Server\Plug-in Support\Data\com.plexapp.agents.amsa_test\DataItems\Cache\Bundles”) and log files (found at “Plex Media Server\Logs\PMS Plugin Logs” - Amsa 1-5) as this will help me identify where the issue resides.
