I would have preferred you had posted about your problems with the agents in this thread first. The chance you will get help here is much higher, than asking elsewhere.
Even if @ChuckPa doesn’t want your nfo files and discards the agents as incompatible with plex, I think we might get it to work for you, as it is working perfectly fine for others, too.
There is a bug at the moment, that plex will show the series poster as the season posters and use auto generated thumbnails instead of user provided ones. But this bug hits other agents too and is, as far as we know, on the plex side and not on the side of other agents.
To help you, I will need you to enable debug logging in the agents settings and generate a new library with your fitness shows. Zip up plex log folder afterwards. Also please create a zip of one show without the episode files, but all the other media and nfo files you created using TinyMediaManager. Upload both zips to some sharing service and drop me a link so I can download them and have a look.
@ChuckPa:
No need to eat a crow. The error is basically what I described for @mcarthey. It appeared after plex 1.2.7, which is the last working version. I’ll try to collect the info from the other threads I found on this and provide that to you. But I won’t make it on the weekend because of real live matters. Please stay tuned.
Hope @ChuckPa’s reply is not the OFFICIAL answer.
This is the second posts i saw that saying it is incompliant rather than acknowledge or working on it.
And “actual code has long since been written from the ground up (AFAIK)” is not true.
Thanks for the offer of help. FWIW, it was my first post and I wasn’t sure where to start. If nothing else we got some attention here.
I’ve placed my files into a zip on Dropbox and the link is below. Please let me know if you have any issues accessing it.
I did find that the “com.plexapp.agents.localmedia.log” file contains references to the image files as it indicates “Found 1 valid things for pattern …”
Looking forward to getting this working and, again, thanks for the help!
I was playing around and happened to notice that when I’m in “List” view it appears that fanart.jpg shows for the program. It’s the only one I’ve been able to find that has been applied so maybe this is just a naming convention issue? That would be a bit strange though since the log seems to indicate others have been found and applied.
Thanks
@SlrG said: @ChuckPa:
No need to eat a crow. The error is basically what I described for @mcarthey. It appeared after plex 1.2.7, which is the last working version. I’ll try to collect the info from the other threads I found on this and provide that to you. But I won’t make it on the weekend because of real live matters. Please stay tuned.
Thanks for helping spearhead this. My primary official duties are Linux and Synology. As I’m sure you’re aware, Linux is a full time effort. Owning a Synology box (also Linux) and having spent more years with Unix & Linux than I should probably admit helps a great deal.
I gave the source code a through read through again. When I came to a point where I didn’t understand, I sent off a message to the dev team. I’ll know more when they respond.
Regarding the comment about being Official, I can arrange for such an official comment from an “Employee” tagged person. I’ll further point out, It’s been, and will continue to be, a team effort to figure this out and come to good resolution for all. Some of these interactions within PMS are not easy to follow. Keeping it all in one’s head is more than a challenge (even for the day-to-day developers who do nothing but work on it)
For the XBMCnfoTVImporter Agent there is also a discussion on github here:
Its not so easy to get the corrects posts on the matter in the threads, as there is a lot of other chatter going on.
There are reports, that a plex dev has acknowledged the problem, but I was not able to find a post that proves those. Maybe you have better contacts and will be able to get an trustworthy comment on the subject.
In the github issue of the XBMCnfoTVImporter the user heymoe did an very deep analysis of the issue and found this:
As far as I can tell, all the metadata files are created correctly on the file system when comparing my v1.2.7 install and the v1.3.2 install.
In the sqlite3 database though, I’ve found that in the metadata_items table the entry for the season information is more or less the same BUT the entry for user_thumb_url is missing (empty value) in v1.3.2 where as under v1.2.7 it has a entry for the the season poster.
I verified the file “da39a3ee5e6b4b0d3255bfef95601890afd80709” exists on the file system. I tried to manually add the same user_thumb_url entry into the v1.3.2 database which resulted in the season poster to change from the default tv show poster to no poster so that’s something but not the results I was expecting. Maybe caching or other DB entries are missing or something.
Either way, it seems that for some reason all the DB entries are not getting added while all the file system work for the metadata is working which seems to point to an issue on the Plex side and not the agent since I don’t things agents themselves make changes to the sqlite3 database directly.
Please see my previous noted issue here for my previous account.
I’ve taken a look through the server logs and believe I’ve got a better idea of what’s happening, it seems like Plex is trying to load the various meta images from an incorrect directory.
For example I’ve just run a refresh on a show and one of the final lines written to the agents log is the following:
2016-12-08 12:53:30,730 (25a8) : DEBUG (model:229) - Serializing to D:\Plex Media Server\Metadata\TV Shows\c\3ef8708eb888ba77049ada21a5758949ab9cde6.bundle\Contents\com.plexapp.agents.xxxx\Info.xml
This line has been written by Plex itself not by the agent (so the path isn’t something that can be edited), you can also browse to it and all the downloaded images are there as you’d expect.
Now when you browse to that show using the web client none of the seasons have their unique images, instead defaulting to the shows one instead; its also showing the captured screenshot for each episode rather than the downloaded thumbnails.
When checking the Plex Server log I can see its full of the following:
Dec 08, 2016 12:53:32.927 [9880] WARN - XML file for scan didn’t exist [D:\Plex Media Server\Metadata\TV Shows\f\fffc9d60d63744b42517c5e728a4f661c202f86.bundle\Contents_combined\seasons\1\episodes\11.xml]
That whole “fffc…” directory doesn’t exist though the file is seems to be looking for and the subsequent episode thumbnail (in a subdirectory) does exist within the “3ef8…” directory listed in the agent log.
Even odder I’ve just gone into the the properties for three sequential episode of the same show and Plex has tried to access three entirely different folders:
WARN - XML file for scan didn’t exist [D:\Plex Media Server\Metadata\TV Shows\5\d7c9afd73d324650496db9e87fc25b7769f28c6.bundle\Contents_combined\seasons\1\episodes\1.xml]
WARN - XML file for scan didn’t exist [D:\Plex Media Server\Metadata\TV Shows\e\77185ac506ae4b061ffbe21fd4cc47feb2aeaaa.bundle\Contents_combined\seasons\1\episodes\2.xml]
WARN - XML file for scan didn’t exist [D:\Plex Media Server\Metadata\TV Shows\6\47c40bec8bf749af7c81df24f8653a9a5fc88a1.bundle\Contents_combined\seasons\1\episodes\3.xml]
No one was accessing the server during these tests and they were made on a fresh install (as I thought my database might be corrupt), the issue also vanishes once I downgrade to 1.2.7.
That makes me conclude that Plex is now trying to load its metadata information from the wrong directories and can’t display any of it because of this.
EDIT: After checking with a few people on reddit its looking like only 3rd party meta-agents are affected by the issue.
EDIT2: Corrected some grammar and sentence structure to make the account more readable.
tl;dr in the v1.3.x versions Plex seems to be trying to load its metadata information from the wrong directories.
In reading through the Release Notes (internal and public) and the as-distributed packages lists, there was a revision update from Python 2.7.8 to 2.7.12.
This normally doesn’t concern the typical user.
As channel developers, you are very interested in knowing such things.
I’ve just chatted with the appropriate folks. Such information will be documented in the NEW section of the Release Notes
Officially:
- (Deps) Updated Python to 2.7.12
- (Deps) Updated SQLite to 3.13.0
Not being versed in Python, I do not understand the ramifications of the bump but have seen the byproduct.
This is all really good information. Thanks for continuing to dig. For what it’s worth, I’m a developer as well. Although I’ve never reviewed the Plex universe I’d be happy to help out where possible. Please let me know if there’s anything I can do.
@ChuckPa:
The post was not directed at you, but at @mcarthey. It will help him setup his local media files correctly, so they will be recognized in the future, when the bug is fixed.
This is what I ask “Which bug?” If you’re referring to the work you need to do then I apologize and stand down. If it’s a Plex issue, then a I need to learn and address
despite being in the ‘Plug-ins’ folder neither ‘XBMCnfoMoviesImporter.bundle’ nor ‘XBMCnfoTVImporter.bundle’ show in PMS under agents; they cannot be found anywhere. I did restart the PMS. I was assuming this is the bug that is being worked out?
@ChuckPa:
He won’t see the season posters and correct thumbnails until the bug in plex that keeps third party agents from adding those correctly to the database is resolved. Imho what you posted until now still shows the error is on the plex side and needs to be fixed by the plex devs, or do you conclude otherwise from your research results until now? Then I need a clear statement on what I can chance in the agent to make it work again.
@Afullmark:
With the current version 1.3.3.3148 the agents should appear normally. If they are not, something is wrong with your installation. This is not the bug we are talking about.
Steps to reproduce procedure (showing a regression / deviation between specific versions is allowed and very much appreciated as it helps them isolate)
When we’ve got it here, I drop it directly in the issue tracker for them . I’ll get feedback as work happens / it ‘goes through the mill’
The error is basically what I described for 