ZeroQI / Lambda.bundle

Local Media Export, a reverse Plex 'Local Media Assets' agent to export metadata locally
GNU General Public License v3.0
134 stars 18 forks source link

Trying to understand multi-version set on tvseries #43

Open docbill opened 3 months ago

docbill commented 3 months ago

This does not seem to be any sort of bug in your code. Rather it is a usage scenario I'm trying to understand. I replicated all seasons of Doctor Who to know seasons e.g. Season 08 to Season 108, resorted the seasons but not the specials in DVD order, added a 0 to the end of the episode numbers, and then inserted webisodes and such I wanted to see in sequence in between. So I can watch the series in sequence without trying to remember when to skip back to specials.

I used the .plexignore files so plex never sees both versions the same file in the two different folders, as that seems to badly confuse it.

After much trial and error, I got it to work. There is no chance thetvdb, or such will ever accept such a sorting into there database... So I have to maintain it custom. Which is why I waited until the series was essentially complete, so I wouldn't need to scan further updates.

Now this solution works for all seasons except Seasons 8 and 9. For those I see the following when scanning:

com.plexapp.agents.localmedia.log.5:2024-05-30 11:01:40,731 (153dd7d00b38) : INFO (localmedia:198) - Doctor Who (2005) - S108E120 - Death in Heaven.mkv looks like part of a multi-version set, won't contribute to total media file count.

for all the episodes in those seasons. On the surface this seems like a harmless message. But the consiqunece seems to be the episode is never even passed to the lambda bundle. So episode title and such are never assigned from my nfo files.

I worked around the issue by manually assigning all the fields for those two seasons in plex. However, if you have any ideas on what I did wrong and how to correct it, it would be greatly appreciated.

ZeroQI commented 3 months ago

Lambda is a secondary metadata agent, it relies on the primary to work and provide the unique id Local media Assets agent may not like seasons on 3 digits

Try a primary metadata agent using nfo as source, mine is to back and restore but not a primary agent

Tried this one? You could even call it manually on your library for the few items that need custom entries https://github.com/adamjakab/Plex-NFO-Import-Agent

docbill commented 3 months ago

Years ago, plex used to have problems with 3 digit seasons. However, they fixed that at some point. So I have long since been naming all blue-ray bonus features as Seasons 9xx seasons. So for example, and bonus features I found on the blue-ray for Season 01, became Season 901, unless of course I could identify it as a special.

However, somewhere along the lines they also implemented indentifying the same video file, independant of filename. I really don't understand how it works. But if I do symbolic link, copy link, or even copy reflink, they sucessfully they are the same video and then will toggle it back and forth where it is shown each scan. When this happens it seems regardless of which folder it is detected in it is not passed to the next scanner in the chain. So my best guess is that plex somehow things these video files still exist in another folder.

I was really just hoping you have seen this type of issue before and knew how to resolve it. As it seems like making of these reports I'm seeing in the issues reports about lambda not reading or writing complete metadata could have a similar type cause, but a more obscure way that cause it.