Am I doing something wrong to use nfos then?
I add a new library, tv shows, selected the test folder, advanced, agent Plex NFO Series, checked use season titles, added library.
It scans and updates meta data but nothing. I only get the episode thumbnail to update. No episode names, descriptions or anything. Everything worked fine when i used the TVImporter add on.
Edit: I’ve used https://support.plex.tv/articles/using-nfo-metadata-files-with-plex/ for reference to update my files.
If you can provide server logs I could take a look at what your issue might be.
Any updates on when we might be able to get NFO support for “Other Video” libraries?
How do i do that.
Follow the instructions in the link: server logs
Drag the output zip file to your forum reply.
Any chance to see the certification tag support added? @drzoidberg33
For example, I will use the certification tag Australia:G which populates the content rating field to au/G
The credits field doesn’t seem to be parsing to the writers field in plex when scanning - a bug?
Any chance to reverse the order of id and uniqueid?
I use the ID field to distinguish between various versons of the same movie and this works well this way.
The Custom Metadata Agent Configuration doesn’t work. The instructions here - https://support.plex.tv/articles/using-nfo-metadata-files-with-plex/ don’t work
Is it possible to have this changed doing a secondary fail-back match against the next provider?
Reason I ask is because of → [Supernatural Season 5 missing from Plex] ← where the episodes come up blank due to them becoming unavailable in the plex backend. This is now the second time I’ve had this happen since moving to NFO, the other time was with [Pokémon].
could you please add support for the producer tag?
could you please add support for the edition tag?
Already supported. Please post the NFO file you’re using.
Ye, currently not supported as it wasn’t obvious to me how those were written in NFOs - writers and directors don’t follow the same format as actors and producers and directors are under a director field but writers are just called credits which is why it was missed. I’ll add support for that in a future release.
No, you can just use the editions naming convention for this (i.e. Movie Name (2000) {edition-Director's Cut}.mkv)
You’ll have to be more specific.
This is supported.
E.g.
<producer tmdbid="59344">
<name>Bastian Griese</name>
<role>Co-Producer</role>
<thumb>https://image.tmdb.org/t/p/h632/gX1rdOluyY7YZ454QYDoaoAmskW.jpg</thumb>
<profile>https://www.themoviedb.org/person/59344</profile>
</producer>
This wasn’t part of the Kodi spec, but tools like TMM do have custom extended fields for this. This isn’t currently supported but you can use the file naming convention as mentioned above which does work.
I can investigate doing this in certain scenarios.
Thanks for helping and for this great feature @drzoidberg33 amazing!
1. Attached a sample NFO, where the certification doesn’t work.
2.Custom Metadata Agent Configuration - when I go to the instructions which says agents (legacy) under the Plex NFO dropdown there are no options present at all.
3.Any chance to have a toggle in the library where the plex ‘summary’ field gets populated by either the outline or plot tag, depending on what I choose as sometimes the plot could be about 250 words long and the outline is preferable.
4.How does the ratings NFO tag work with rottentomatoes? I can’t find any help files on this.
5.The ‘tag’ NFO field doesn’t populate the collections field in plex.
6.Could the NFO agent please fallback to using ‘releasedate’ if the ‘premiered’ field is not present?
Thanks for answering the other questions I asked yesterday.
Bumblebee (2018).2160p24.nfo.txt (31.5 KB)
Are you referring to this section of the article?
https://support.plex.tv/articles/using-nfo-metadata-files-with-plex/#toc-7
If so, the first point should tell you to select Settings → Metadata Agents. That is where custom metadata agents can be created. (The article should be updated.)
thanks mate
It would be much simpler if you just did that in the NFO.
The current public version only supports tomatometerallcritics, the beta version (1.43.2) supports the full RT ratings, e.g.
<ratings>
<rating default="true" max="10" name="imdb">
<value>7.9</value>
<votes>1443456</votes>
</rating>
<rating default="false" max="10" name="themoviedb">
<value>7.6</value>
<votes>32541</votes>
</rating>
<rating default="false" max="100" name="tomatometerallcritics">
<value>81.0</value>
<votes>334</votes>
</rating>
<rating default="false" max="100" name="tomatometerallaudience">
<value>51.0</value>
<votes>1923</votes>
</rating>
<rating default="false" max="10" name="tomatometeravgcritics">
<value>7.5</value>
<votes>334</votes>
</rating>
<rating default="false" max="10" name="tomatometeravgaudience">
<value>6.1</value>
<votes>2345</votes>
</rating>
</ratings>
The <tag> element isn’t meant for collections, for that you use <set>, currently supported in the beta version (you also need to enabled it in the Advanced settings of the library).
Which NFO generator is using that? We currently check premiered and fall back to aired.
As for your certification question, I checked your NFO and it provides mpaa as well as numerous certification countries, including two for Australia. We only read one and use mpaa first, just get rid of everything else except the one certification you want.
The old legacy plug-in generated collections from tags. Anyone used to that behaviour will have to adapt their .nfo files a bit. tinyMediaManager does it just fine. 
Thanks for the info, but yes this will definitely have to change in the NFO as people would get a ton of junk entries if we had to read those as collections.
