Movie metadata not scanned due to proprietary filename convention

Movie metadata not scanned due to proprietary filename convention - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Media Scanning & Identification (https://forum.jellyfin.org/f-media-scanning-identification)
+---- Thread: Movie metadata not scanned due to proprietary filename convention (/t-movie-metadata-not-scanned-due-to-proprietary-filename-convention)

Movie metadata not scanned due to proprietary filename convention - geohei - 2025-05-29

Hi.

Newbie question (after lots of Google searching).
I installed latest JF on my Synology NAS.
I have the following problem regarding metadata scanning.

My naming is as follows (example): Annabelle (TV - 13.11.2015 1925 169 h264 MP2192en MP2192fr).mp4
I am aware that this is not what JF expects for Movies.
Hence, metadata for media file above is obviously not found (Anabelle (2014), tt3322940) by DBd.

I came up with 3 solutions:

Manually add IMDb Id as JF/Identity to every movie.
Add an .nfo file next to the movie (same basename as media filename, but with .nfo extension).
Appending [imdbid-tt3322940] to the end of the filename (Annabelle [imdbid-tt3322940].mp4).

These methods are time-consuming since all must be done manually.

Is there any possible solution I didn't think of to make the DB scanning process somewhat more automated, while keeping the existing filename convention?

Thanks,

RE: Movie metadata not scanned due to proprietary filename convention - theguymadmax - 2025-05-29

What your doing are the only things I can think of. If your not already doing so, I would recommend use an external tool like tinyMediaManager to create NFOs. It also has a renamer function that can append the ID's the the folders.

RE: Movie metadata not scanned due to proprietary filename convention - geohei - 2025-05-30

Thanks for reply. I'll dig myself into tinyMediaManager.
Suppose I'd like to have a minimalistic manual .nfo, would this be the correct syntax?



<movie>

  <imdbid>tt3322940</imdbid>

</movie>

And this the correct filename to link the .nfo to the actual media (example)?



Annabelle (TV - 13.11.2015 1925 169 h264 MP2192en MP2192fr).mp4

Annabelle (TV - 13.11.2015 1925 169 h264 MP2192en MP2192fr).nfo

This page doesn't specify the .nfo format JF accepts.
I'd like to be sure before starting this job and finding out later on that I could have done better.

RE: Movie metadata not scanned due to proprietary filename convention - theguymadmax - 2025-05-30

There's a Jellyfin preset in tMM.

RE: Movie metadata not scanned due to proprietary filename convention - geohei - 2025-05-31

I found the tMM Jellyfin preset and did some testing.
Works fine, but I have some basic questions regarding the metadata acquisition concept.

Assuming that I ...
- would like to keep my media naming convention (see above)
- would like reduce manual interaction to a minimum in order to gather metadata
... I believe (please correct me if I'm wrong) that either an external tool (e.g. tMM) or Jellyfin can scan media to provide metadata.
Which approach should I give preference to?

Assuming that I go for Jellyfin as metadata provider, what is the minimum and correct .nfo content assuming that IMDb should be queried?

  <movie>

    <imdbid>tt3322940</imdbid>

  </movie>

  <movie>

    <id>tt3322940</id>

  </movie>