Priority of *.nfo metadata vs. online metadata and is it configurable?

[voodoo5_6k 29]

Today, I reset my emby server (I wanted to do this for a while and had waited for 4.8.8.0). While I set up the libraries again, I noticed something, that felt odd, but maybe I'm remembering things incorrectly.

I thought, that once an *.nfo file is found, there is no more online scraping?

• Example 1:
  I have a dataset on my server with documentaries (library content type is TV shows). All of these have *.nfo files, and poster files available. When I used Kodi, it would see the *.nfo, import it accordingly, and be done with it. With emby server 4.7.x.x it would work the same way. Now, with 4.8.8.0, it takes the *.nfo file, but does also look online. For most of this stuff, there's nothing online, but for some, there is, and then everything's messed up in the library for that "show", including changed episode names and season association (online <> *.nfo). I deleted the library, and then set it up again, with deactivating all online scrapers. Now everything works. But for this library it's easy, because there's currently only stuff which is supposed to be *.nfo only.
• Example 2:
  Another dataset has music concert videos (library content type is Movies). Most of the stuff is "scrapable" online, but some rarities are also *.nfo only. For this library, I need all the standard scrapers, and for some reason, it worked here. The *.nfo only entries didn't get messed up. Maybe because nothing could be found online (need to verify). Or is there a difference in scraping based on the content type selection for the library?

Unless I'm doing something wrong (not unlikely), maybe an additional switch for the library configuration would be good, something like an addition to the *.nfo option which can be activated if required, "Do not use other scrapers when an *.nfo file has been found/processed". That way, the user could decide whether to let the online scrapers fill in the blanks, or to leave the *.nfo scraped stuff as-is.

Thanks!

[GrimReaper 4740]

7 minutes ago, voodoo5_6k said:

I deleted the library, and then set it up again, with deactivating all online scrapers.

As you've already surmised, that is the way to go (or better yet, kill internet connection altogether while initial import) if NFOs present, as Emby will still look at online providers for updated/missing metadata, you'd want to make sure it just doesn't find anything. 

9 minutes ago, voodoo5_6k said:

maybe an additional switch for the library configuration would be good, something like an addition to the *.nfo option which can be activated if required, "Do not use other scrapers when an *.nfo file has been found/processed". That way, the user could decide whether to let the online scrapers fill in the blanks, or to leave the *.nfo scraped stuff as-is.

Sounds like FR in the making. 

[voodoo5_6k 29]

11 hours ago, GrimReaper said:

As you've already surmised, that is the way to go (or better yet, kill internet connection altogether while initial import) if NFOs present, as Emby will still look at online providers for updated/missing metadata, you'd want to make sure it just doesn't find anything.

Thanks for confirming!

11 hours ago, GrimReaper said:

Sounds like FR in the making. 

Haha, yeah, might as well create one in case there's nothing like that in the long list.

@LukeIs this something for a feature request, or is the option already in the code but just not exposed?

[rbjtech 5284]

I've often thought this - why not just combine the Metadata Readers into the Metadata Downloaders section.

Then the 'priority' can be properly assessed - ie putting NFO at the top, means if all the info is available from that, then it stops.   If mandatory data is still missing, then it goes to the next provider and so on.

 

[Luke 42078]

10 hours ago, voodoo5_6k said:

Thanks for confirming!

Haha, yeah, might as well create one in case there's nothing like that in the long list.

@LukeIs this something for a feature request, or is the option already in the code but just not exposed?

I suppose, but most people who think they want this option are going to wind up with cast members with no photos.

[Luke 42078]

6 hours ago, rbjtech said:

I've often thought this - why not just combine the Metadata Readers into the Metadata Downloaders section.

Then the 'priority' can be properly assessed - ie putting NFO at the top, means if all the info is available from that, then it stops.   If mandatory data is still missing, then it goes to the next provider and so on.

 

If we were just starting out today I might do it that way, however there is some internal distinction and special sauce behaviors applied to local metadata sources based on what we know users want. So if it were to become one generic list, then we'd have to find a way to get those things preserved. There's multiple ways to skin a cat. Neither way is right or wrong and so right now there isn't really a strong reason to destabilize things by changing it.

[voodoo5_6k 29]

8 hours ago, Luke said:

I suppose, but most people who think they want this option are going to wind up with cast members with no photos.

Alright, thanks for highlighting this. That wouldn't be an issue in my case, but I can see why many people wouldn't like that sort of downside.

8 hours ago, Luke said:

If we were just starting out today I might do it that way, however there is some internal distinction and special sauce behaviors applied to local metadata sources based on what we know users want. So if it were to become one generic list, then we'd have to find a way to get those things preserved. There's multiple ways to skin a cat. Neither way is right or wrong and so right now there isn't really a strong reason to destabilize things by changing it.

Completely understandable. I now know how to handle my special cases and understand the obstacles for implementing a "special case" solution. Thanks again Luke!

[Luke 42078]

Quote

That wouldn't be an issue in my case

How do you know that?

[voodoo5_6k 29]

33 minutes ago, Luke said:

How do you know that?

Oh, because in those libraries I don't use that sort of meta-data

[Embodiment 28]

This is a perfect thread for my question. My problem is my ignorance so I don't blame anyone.

I use TMM to primarily manage my .nfo files as Kodi has used them. I 'thought' Emby reads them and does not go to the Internet unless it cannot find its information. I think based on what I am reading here and seeing that is not the case.

I had edited my .nfo files among other things and created a 'duplicate' genre. After doing a refresh metadata, that duplicate genre is now  gone in all my movies. So Emby does not read the local .nfo files, but goes out to the Internet? How do I fix that, or can it be fixed not to update the nfo files unless they do not exist?

Does Emby read them at all? Looks like I need to delete and re-import my library (something I am really getting good at). Will it read the local .nfo files or go to the Internet.

Can I keep Emby from changing my .nfo files by leaving Metadata Savers NFO unchecked? Will it read my .nfo files if Metadata Readers NFO is checked?

 

Edited May 23, 2025 by Embodiment
Edits for clarity

[GrimReaper 4740]

2 minutes ago, Embodiment said:

I use TMM to primarily manage my .nfo files as Kodi has used them. I 'thought' Emby reads them and does not go to the Internet unless it cannot find its information. I think based on what I am reading here and seeing that is not the case.

It is, on initial import. Emby will still reach out to the internet for missing/updated information, but metadata from your NFOs will be read/imported, as local metadata is prioritized on ingestion. However, on Refresh Metadata online providers are prioritized (as Emby looks for latest/updated infornation). To avoid that, you'd want Emby internal meta-downloaders disabled, as stated previously in this thread. 

5 minutes ago, Embodiment said:

After doing a refresh metadata they are gone in all my movies. So Emby does not read them the .nfo files, but goes out to the Internet. How do I fix that or can it be fixed not to update the nfo files unless they do not exist?

Explained above. 

6 minutes ago, Embodiment said:

Does Emby read them at all?

Explained above. 

6 minutes ago, Embodiment said:

Can I keep Emby from changing my .nfo files by leaving Metadata Savers NFO unchecked?

Yes, but that doesn't mean database data will remain unchanged, it'll just not be written back to NFO on Metadata Refresh. 

7 minutes ago, Embodiment said:

Will it read my .nfo files if Metadata Readers NFO is checked?

Explained above. 

[Embodiment 28]

Wow, thank you for the quick response. So  uncheck Movie Metadata Downloaders IE. The MovieDB, The Open Movie Database, TheTVDB and that and along with unchecking Metadata Savers should keep my .nfo files intact? 

And unchecking the Movie Image Fetchers would keep the artwork I already have downloaded from TMM as well I assume.

[GrimReaper 4740]

2 minutes ago, Embodiment said:

Wow, thank you for the quick response. So  uncheck Movie Metadata Downloaders IE. The MovieDB, The Open Movie Database, TheTVDB and that and along with unchecking Metadata Savers should keep my .nfo files intact? 

Correct. 

2 minutes ago, Embodiment said:

And unchecking the Movie Image Fetchers would keep the artwork I already have downloaded from TMM as well I assume.

Correct as well. 

[Embodiment 28]

Your the man, very much appreciated. One last question that ties in with Emby reading the .nfo files the first time.

Emby doesn't read the WatchedState or PlayedCount from the .nfo files during import. Seems like it does not.

[GrimReaper 4740]

2 minutes ago, Embodiment said:

Emby doesn't read the WatchedState or PlayedCount from the .nfo files during import. Seems like it does not.

It doesn't, as to which user it would apply to? 

[Embodiment 28]

True, I see your point.  Again, you made my day with such quick and helpful answers. 

[Embodiment 28]

Just read this post on a similar subject and had question that came to my mind. 

 

Based on some understanding above, IF I uncheck Movie Metadata Downloaders IE. The MovieDB, The Open Movie Database, TheTVDB, BUT LEAVE checked Metadata Savers, would just the watched status be updated in the nfo file and not the genre's and other metadata? Or what would change in the nfo files  if the above was unchecked, but a refresh of metadata was done.

As I understand it too, unless a person does a refresh of metadata, the nfo file does not get written to, which would not then update the watched status.

If I can just get the watched status updated in this case, Tiny Media Manager could read those NFO files and I would not have to manually update each movie in TMM.

[GrimReaper 4740]

1 hour ago, Embodiment said:

Based on some understanding above, IF I uncheck Movie Metadata Downloaders IE. The MovieDB, The Open Movie Database, TheTVDB, BUT LEAVE checked Metadata Savers, would just the watched status be updated in the nfo file and not the genre's and other metadata? 

Emby would rewrite complete NFO, most (all?) of the actual metadata would remain unchanged but header and some tags/nodes would be changed and some new/changed tags/nodes would be written in Emby format; whether TMM would "understand"/know how to read back those tags/nodes is anyone's guess, depends if they have introduced support for it. To summarize: it is never a good idea to have two different software write/rewrite same NFO, as that is bound to create issues down the road, rather sooner than later. 

 

1 hour ago, Embodiment said:

As I understand it too, unless a person does a refresh of metadata, the nfo file does not get written to

Or if you select Edit Metadata and just press Save in that dialog. 

1 hour ago, Embodiment said:

If I can just get the watched status updated in this case, Tiny Media Manager could read those NFO files and I would not have to manually update each movie in TMM.

Emby would still rewrite compmlete NFO (as per first paragraph). TMM might read that tag, but would likely have issues with reading/importing some of the Emby-specific NFO tags/nodes. Nothing prevents you to test it, though. 

[Embodiment 28]

Great information.

For the benefit of others who might read this thread. I did find an interesting observation. When removing the library and re-adding it, Emby did indeed restore my uniquely created genres written in my nfo files.

BUT ALSO to my pleasant surprise, Emby retained the watched status of movies I was marking manually to match my four years of Kodi. So despite deleting and re-adding the same library (so I could get it to read my nfo files), it kept the watched status. I find that very interesting and in my case a great thing.

[GrimReaper 4740]

17 minutes ago, Embodiment said:

BUT ALSO to my pleasant surprise, Emby retained the watched status of movies I was marking manually to match my four years of Kodi. So despite deleting and re-adding the same library (so I could get it to read my nfo files), it kept the watched status. I find that very interesting and in my case a great thing.

Items are tracked by ProviderIDs and will retain/preserve their Playstates even if/when removed/re-added to the library (save Home Videos/any other item without external IDs). 

Edited May 24, 2025 by GrimReaper

[Clackdor 109]

One of the things mentioned earlier in the thread is that disabling external metadata providers for a library will result in no images for people.

On 6/6/2024 at 3:31 PM, Luke said:

I suppose, but most people who think they want this option are going to wind up with cast members with no photos.

Would it be possible to have additional options to separately enable metadata/image providers for people only?

In my case all of my nfo files and images are managed by a "primary" emby instance and stored alongside media folders. Another emby instance on the same machine is pointing at those same folders and is running as a user with read-only permissions as to prevent unwanted changes/conflicts. Ideally I'd like all of the read-only instance to have metadata providers turned off and rely completely on nfo files to keep metadata/images consistent with the primary emby instance.

[Embodiment 28]

As a follow-up to the test I did based on our above conversation.

I marked the movie " 20 Million Miles to Earth" as watched. No immediate change in .nfo file (as expected). Did a metadata refresh just on that movie. Instant  update to .nfo file.

But while it must have made some change, IT did not change the watched status. Still set to ''false' and no reference anywhere to the movie being watched.

So Emby does not change the watched state in .nfo files upon a refresh metadata. Nor does it read the watched state as we already know.

Ironically, with Kodi Omega, this is now built into the application. https://github.com/xbmc/xbmc/pull/20842

[Happy2Play 9780]

3 minutes ago, Embodiment said:

But while it must have made some change, IT did not change the watched status. Still set to ''false' and no reference anywhere to the movie being watched.

So Emby does not change the watched state in .nfo files upon a refresh metadata. Nor does it read the watched state as we already know.

Did you configure the NFO plugin (click on the plugin) to write that user watched status?  As Emby being a multi user platform it sort of becomes useless at least to Emby.

[Luke 42078]

Yes you need to do that to get Emby to save the data to nfo files. But it will only do that for one user, and Emby is a multi-user system. We added support for that so that you could have Kodi import the data, but it is not really suitable for Emby's uses. 

[Embodiment 28]

That was the trick! Didn't know that plugin had that ability. I am just now looking at profiles for Emby; but my wife watches little and I have just set tags for things I think she would be interested in so we have just one profile on Kodi. See only sees tagged items from the customized home screen on Kodi on her TV.

Thank you for helping me see this trick. It worked, changed the nfo file and Tiny Media Manager recognized the status change.