search

ZeroQI / Absolute-Series-Scanner

Seasons, absolute mode, Subfolders...
1.01k stars 155 forks source link

Forced ID mode ignored on recent scanner update #344

Closed jvmunhoz closed 3 years ago

jvmunhoz commented 3 years ago

I'm trying to put Durarara in absolute order so that the specials go where they belong.

https://thetvdb.com/series/durarara/seasons/absolute/1

But even though ASS does it's job, HAMA only gets metadata for episodes 01-24, with no regard for the 2 specials added on the absolute ordering.

And that's very odd, I have a Linux with Durarara as well (I'm migrating everything to my Windows desktop) but everything is ok there. (ASS is an older version though)

I have done the Plex Dance, and cleared the Plug-in Support/Cache/com.plexapp.agents.hama and Plug-in Support/Data/com.plexapp.agents.hama folders MULTIPLE times, so I don't think it's a cache problem. What's could the problem be?

Here are the necessary logs: Durarara!! [tvdb5-133341].agent-update.log Durarara!! [tvdb5-133341].scanner.log

Update 1: downgraded my ASS and Hama to the version my linux machine has, and it's now working as intended. On Linux, I cloned the files on feb 14th, so I went back to the first commit prior to this date on both repos.

Went back to commit b3afa638e58615b5959456b6367f385dcc6729f9 on hama and commit f57c3770b41f43451d4e099f0d216900c26bee41 on ASS

The logs when it worked: Durarara!! [tvdb5-133341].agent-update.log Durarara!! [tvdb5-133341].scanner.log

ZeroQI commented 3 years ago

Both scanner logs show s00e02 mapped as s01e26 using tvdb5 mode. If the ep is showing in plex at the correct season and ep number, the scanner did it's job.

Agent logs show 26 eps when working and 24 episodes when not working which is not consistent.. I believe you had a scanner bug and just 24 eps showing in plex... Please confirm...

Will reproduce when I can with latest version

jvmunhoz commented 3 years ago

No, episodes 1 through 24 had metadata and episodes 25 and 26 were named "Episode 25" and "Episode 26" respectively. Episode 13 was indeed episode 12.5 and was where it should be, but with episode 13 metadata on it. So they were mapped correctly. And I repeated this process about five times, after deleting all possible caches each time.

If indeed it is a problem on HAMA's end, it can only be the last commit, since I only went back 1 commit. If it is an ASS problem, then I went back several commits...

I'm still migrating my server, but when I'm over I'll do some further testing.

ZeroQI commented 3 years ago

Scanner was right then as eps were in right position... Unique ID was 'anidb-6671' when misbehaving and tvdb5-133341 when working so that makes sense... Ep 25 26 there but no metadata so consistent

If the folder name was change after showing and matched in plex the series would have kept the original ID without tvdb5 indication...

jvmunhoz commented 3 years ago

Sorry, I didn't get the last part...

But the folder didn't change names at all throughout the entire process.

ZeroQI commented 3 years ago

When metadata was wrong, the id assigned was anidb, not tvdb5. Simply re-matching would have sol ed the isue

jvmunhoz commented 3 years ago

Upon further testing, it's most likely a problem with ASS.

For some reason, HAMA is recognizing all tvdb5 IDs as anibd ones when using the latest version of ASS.

ZeroQI commented 3 years ago

Pushed to master code fix, had broke forced id...

jvmunhoz commented 3 years ago

Ah, glad to know it's fixed. I'll test it tomorrow morning to confirm everything is ok.

jvmunhoz commented 3 years ago

After testing the latest version of ASS, I can confirm it now works as intended. Closing the issue, and thank you for the help.