Problem picking up changes in nfo files

[ZmgwsYzhM2nV]

Before I'm going to raise this as an issue on GitHub, I want to make sure whether anybody else is seeing this problem, or perhaps I'm doing something wrong. The problem is that changes in nfo files are not being picked up doing a library scan. I don't use metadata downloaders ("scrapers"), I solely use nfo files for metadata, and my own artwork files. This problem started a few versions (of Jellyfin) ago, and I confirmed it doing an install of Jellyfin version 10.10.1 on a fresh install of TrueNAS Dragonfish-24.04.2.5 (using Jellyfin as a custom docker app), and on macOS Sequoia 15.1. I didn't test some Linux variant as of yet.

- When I add a new movie or show, the metadata in the nfo files is picked up properly.

- When I then edit the metadata in the nfo file and do a rescan, the changed data is *not* picked up at all.

I follow all the rules when it comes to directory structure, file naming etc. Here's an example of a show episode's nfo file:

Code:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<episodedetails>
  <plot>Comic chaos ensues when Edmund accidentally kills King Richard III.</plot>
  <lockdata>true</lockdata>
  <dateadded>2015-02-16 08:06:16</dateadded>
  <title>The Foretelling</title>
  <year>1983</year>
  <imdbid>tt0526541</imdbid>
  <showtitle>Blackadder</showtitle>
  <episode>1</episode>
  <season>1</season>
  <aired>1983-06-15</aired>
</episodedetails>

Any suggestions how to troubleshoot? This behavior started something like 4 or 5 versions (of Jellyfin) ago... Maybe I'm the only one using just nfo files for metadata and not metadata downloaders, LOL!

Thanks for any pointers!

[Efficient_Good_5784]

From what I've been told, NFO data is only used on the initial/first scan into your Jellyfin library.
Afterwards, its contents will not be used. Jellyfin will just resort to whatever is in the database for metadata (which you can edit from the web UI as an admin).

The purpose of NFOs afterwards would be to just allow you to export your Jellyfin library to another service that can use them as NFOs will get updated as you update your metadata through Jellyfin's GUI.

[ZmgwsYzhM2nV]

Hmm, that would be a bummer, as it worked properly a couple of versions ago...

[ZmgwsYzhM2nV]

Just to elaborate a little more, sometimes I add video files for which there's no metadata at sites like the themoviedb.org etc. at all. And sometimes I add segments or chapters to these video files at a later date, and then I want to update the nfo file with a description of that particular chapter. The only workaround I found is removing the directory of, let's say, a show, do a scan, add the directory again and then do a scan again. But that's hardly a nice way of doing things...

[ZhangTianrong]

Highly agreed that jellyfin need to pick up the changes made to nfo files. After all metadata providers are never perfect and the metadata editor of jellyfin is just never prepared for mass editing. Before I figured out that I can move a sub directory elsewhere and then re-add it to a series, I have been made to edit every episode manually like an idiot.

[JazoBurbs]

Separate but related question. I'm starting from scratch on the .nfo train and wondering I should go down that route. And if so, to just have JellyFin create them (if it's stable) instead of using MediaElk or something which seems way more complex. On topic, I agree that jellyfin's metadata and .nfo files should "sync" in case you lose your library and have to rebuild.

[theguymadmax]

I've tried several apps for managing NFOs, and I've found that tinyMediaManager works best for my needs. It's more convenient for me than letting Jellyfin handle it.

[JazoBurbs]

Agree but unfortunately TMM doesn’t create or handle music NFOs from my experience.

[ZhangTianrong]

Did you make an issue about this on GitHub? If you haven't then I would create one.

[theguymadmax]

What issue? Do you have reproducible steps to verify this issue?