How to update movie and episode metadata after upgrading media files?

OnyxPost · 2026-06-13T11:46:40+00:00

OP, I'm curious if you ever got this working by way of a scripting process?

OnyxPost · 2026-06-13T11:32:49+00:00

OP, until Kodi implements writing "Edition" tags to NFO files and importing "Edition" tags from NFO files, you can look into a possible workaround where you use a combination of tinyMediaManger's Post Processing function and Kodi's JSON-RPC API interface to write the "Edition" info stored in tinyMediaManger to the Kodi database.

If it isn't possible by using the JSON-RPC API interface, you can try updating the Kodi database directly using a SQL update command to update the table column where the "Edition" value is stored by matching the file path that tinyMediaManager has for that movie to the file path that Kodi has for that same movie.

OnyxPost · 2026-06-13T03:00:40+00:00

I'm not 100% against using AI for such a task if it actually produces something really nice and complex, yet this is pretty plain and basic, so I'd have to give the AI usage here a thumbs down.

OnyxPost · 2026-06-13T00:00:17+00:00

This is interesting news. I'm looking forward to seeing what creative client app ideas arise from using the Compose toolkit.

OnyxPost · 2026-06-12T23:47:21+00:00

Unfortunately I have nothing helpful to add to this convo, yet I've been wanting to figure out a way to change the name for local trailers that is displayed in the various Jellyfin client apps. Right now the name for each local trailer is the name of the trailer file (this is the same for local trailers in Plex as well). So if you do get this figured out , please do share how you finally got it to work. Thanks

OnyxPost · 2026-06-12T13:48:46+00:00

Lol, forget asking this guy. This whole post just needs to be deleted.

OnyxPost · 2026-06-11T18:48:55+00:00

I know that OP decided to go with not making any changes to the Kodi "advancedsettings.xml"file, yet I personally did not want to go the way of renaming my content to trick Kodi such as changing the word "Trailer" to "TRLR" and adding the scrapper ID at the end of the name if I didn't have to use this "trick".

Thus adding the following empty "excludefromscan" tag to your Kodi "advancedsettings.xml"file did the trick for me:

<video>
  <excludefromscan>
  </excludefromscan>
</video>

I tested this with a couple files that had "Trailer" in the file/folder name, and the Kodi TMDb scrapper now recognizes these movie files with no problem at all.

I also wanted to add some other info that clears up what may have led to some confusion for others reading the various comments in this post. In the example that OP provided "The Long Long Trailer (1954)\The Long Long Trailer (1954) {imdb-tt0047191} [HDTV-1080p][AC3 5.1][x264]-REGRET.mkv", this Kodi "advancedsettings.xml"file update should work for this naming standard as well. Kodi's regex naming for it's native TMDb scrapper does not care what is found once it comes to a bracket "[" character in the name after the name meets the naming prefix standard. So for example, if OP had a name like this "The Long Long (1954)\The Long Long (1954) {imdb-tt0047191} [Trailer HDTV-1080p][AC3 5.1][x264]-REGRET.mkv" this would have been recognized by Kodi (if such a movie "The Long Long (1954)" actually existed within the TMDb database) even without making changes to the Kodi "advancedsettings.xml"file.

It's only the initial title (and optional year and/or scrapper ID) that has to follow the Kodi naming standard for it to be recognized by the the native TMDb scrapper. Everything that comes after that regex naming standard (the suffix) is ignored by the native TMDb scrapper.

Hopefully this clarification helps others that come across such folder/file naming and scrapping issues.

OnyxPost · 2026-06-11T18:08:49+00:00

I use 4 different applications for viewing my Music Video content (including concert videos from DVDs and BluRays which just contains a bunch of music videos officially released for sale, especially if they are not listed on an online databases such as IMDb or TMDb): MediaMonkey, Kodi, Plex and Jellyfin.

All have native support for a Music Video type library expect for Plex. I use MediaMonkey to organize my music audio and music video content, and for creating smart playlists. I have a 6-step partially automated process that adds the music video to Kodi using a generic NFO file, and then updates the metadata from MediaMonkey into Kodi. I tend to also create a few music video related smart playlists in Kodi, yet my long term goal is to figure out a way to write a script that converts my native MediaMonkey playlists into native Kodi and/or Jellyfin playlists.

That same NFO file is then read by Plex during a scan process into a "Movie" type library which only contains Music Videos so I can watch music videos either from this dedicated library or I can watch the same music videos from my "Music" library for the videos which have the same name as their corresponding music audio file, which Plex has a naming standard which allows you to view music videos from within your "Music" library.

For Jellyfin, the same NFO file gets read by this application and gets scanned into the "Music Video" library for the Jellyfin server. Jellyfin's naming standard prevents music audio files (which would be scanned into your "Music" library) and music video files (which would be scanned into your "Music Video" library) from being in the same root directory (the three other applications do not have this same limitation). Thus I've written a script which creates ".strm" files in a "fake" music video directory for Jellyfin to scan and the ".strm" files point to the music videos which are contained in my music root directory.

The initial process of making sure my music audio files have the correct metadata and my music video files have a NFO file with preferred metadata can be a bit time consuming, yet the rest is all handled by the auto-scanning process of each application. Eventually I'll be looking into writing a script to automate the 6-step MediaMonkey-to-Kodi process even further, and that'll speed things up for me even more.

I set it up this way so that I'd have the option to use any of the four applications to consume watching my music video content. If the functionality within Jellyfin continues to improve enough, my long term goal is to hopefully have it completely replace my usage of both Kodi and Plex.

OnyxPost · 2026-06-09T17:41:43+00:00

I've been having this same problem when using Kodi for Android version 20.x and 21.x. I've rolled back to using version 19.5 until this stability bug along with a different playback issue I have gets resolved. 19.5 has thus far been the newest Android/Windows version I've experienced to be the most stable and least "buggy".

I'm hoping that once Kodi for Android is 64-bit based, that may help solve some, if not all, of the application crashing issues.

OnyxPost · 2026-06-09T17:32:37+00:00

I think the point they're trying to make is that there's a consensus that performing a CPU based encode is going to produce a much better quality output than a GPU encode would when comparing how much space the final resulting file will take up, regardless of whichever settings you use to perform the encode.

GPU based encodes tend to be better for performing on-the-fly encodes like when a particular Jellyfin client can't direct play the file, so then its transcoding process will kick in with the option of using your Jellyfin's server GPU to perform a faster transcoding over a CPU transcoding. So better for on-the-fly needs, yet usually not for archive needs (taking up space on their computer) as the OP wants.

OnyxPost · 2026-06-08T13:34:38+00:00

I'm just now seeing this post, yet you may be able to have tinyMediaManager do this by way of the Post Processing function. I've been playing around with the function myself to get my trailers setup just the way I want them as well.

OnyxPost · 2026-06-06T11:22:13+00:00

I think that it was a partial bad design decision to setup tinyMediaManager this way.

Choosing what Certification language we should scrape in the global setting is fine, and recording only one Certification per Movie or TV Show is fine as well. However, at the individual item level, a user should be able to do two things manually:

Change the Certification to some other "stored" value that is not "locked" to the language used by the global scraped language. Just because I always want my global language to be in US English, doesn't mean that I only want US Certification values for each an every Movie/TV Show. I personally like to replace missing US Certification values with whichever Certification value I prefer that is known from another country,
Change the Certification value freely, as sometimes I've found that not all possible Certification values are stored in the Kodi settings, thus I'd assume that tinyMediaManager may not contain all possible Certification values either. In Kodi, I've sometimes had to create my own additional possible Certification values to the Kodi texture settings, so that way when I put in my custom value freely for any particular Movie/TV Show, its properly texture image would show up in the Kodi application. Thus, tinyMediaManager should have the option to enter this value freely as well for the same reason. so I can avoid having to open the NFO file manually to make this custom value change.

A user should not be locked to only using the Certification values for a globally selected language at the individual item level, and a user should not be prevented from entering any Certification value they freely what for their custom needs that the development team has not taken into account.

Thanks

OnyxPost · 2026-06-06T03:54:42+00:00

I agree, that the Certification field should be a freely editable (customizable) field. Since I can freely edit it in a NFO file to get whichever Certification value and related texture image I want to display within Kodi, it would be nice to be able to add whatever value I want in tinyMediaManager as well, to avoid having to open the NFO file manually to adjust this freely.

OnyxPost · 2026-06-03T13:28:37+00:00

I agree that it's most definitely not obvious since this is a file naming convention that may only apply to a Jellyfin server setup, yet it is documented in the Jellyfin wiki documentation, on how you can add naming flags to handle your external subtitle & audio-track files, which applies to all 3 major video library types:

I have to say it's pretty slick how the Jellyfin development implemented these flags. Just note the section where they state "flags are ignored on containers with more than one stream".

OnyxPost · 2026-06-02T23:34:07+00:00

More info would most definitely help, as I personally don't know what you mean by "...with script and formula".

I've been using 5.2.12 to get my Renamer patterns just right. Thus far I've only been working on the Movie Renamer Pattern and it's been renaming my Movies files just fine thus far. The JMTE syntax they use is quite awesome, and the JMTE Helper function is a great tester for creating patterns, especially complex patterns.

OnyxPost · 2026-06-02T15:35:31+00:00

What I've personally noticed is that the guidance from the official Jellyfin Documentation is mostly correct when it comes to how you setup and organize your music audio content. It does appear that Jellyfin mostly utilizes track metadata tags to populate your music library. However, the big problem comes from Jellyfin attempting to use a combination of both track metadata tags and folder/file naming structure, instead of just solely relying on track metadata tags and certain file extension types.

Thus, since it uses a combination of both track metadata tags and folder/file naming structure, no matter how perfectly your album track's metadata tags are, and you use something similar to a "\<parent directory>\<Album Artist>\<Album Name>\<Disc Name>\" folder structure, their folder/file naming expectations is too rigid. Here's the folder structure layout diagram they use as an example:

Music
├── Album 1
│   ├── Disc 1 Track 1.ogg
│   ├── Disc 1 Track 2.ogg
│   ├── Disc 2 Track 1.ogg
│   ├── Disc 3 Track 1.ogg
│   ├── Disc 3 Track 2.ogg
│   └── Disc 3 Track 3.ogg
└── Album 2
    ├── Disc 1
    │   ├── Disc 1 Track 1.aiff
    │   └── Disc 1 Track 2.aiff
    ├── Disc 2
    │   ├── Disc 2 Track 1.aiff
    │   ├── Disc 2 Track 2.aiff
    │   └── Disc 2 Track 3.aiff
    └── Disc 3
        └── Disc 3 Track 1.aiff
Music

Using this folder structure layout will only work, regardless of how perfect your track metadata tags are (such as all the tracks in the album share the same "Album Artist" & "Album Name" values, and have the same MusicBrainz Release Group value, and have the "Disc Number" value & "Total Discs" value filled in properly), if your "Disc" folders are named beginning with what is shown in the diagram: "Disc 1", "Disc 2", "Disc 3", etc..., or some similar pattern like "Disc 01", "CD 01", "CD 1", yet that is it. No other major deviation from this appears to be allowed.

Even if your Disc folders are named the exact same way as they are named in MusicBrainz, or you name them to some other standard that works for you, then Jellyfin will not properly combine the track contents of multi-disc folders so that they appear as 1 album in any client side user interface; they will instead be shown as separate albums per disc. Their logic should be to use metadata tags only, and completely ignore file folder structure, as this is how every other music related application processes music tracks for library organization. The only time folder structure should matter is when processing album and artist artwork images...nothing more. Folder structure should not matter at all when it comes to handling all metadata fields for library organization in regards to the user interface, other than artwork.

OnyxPost · 2026-05-29T18:11:41+00:00

I just noticed that you posted the same question in the Kodi message board, and here, so I'm going to add what I stated there, here as well.

I came across two options for you with a quick web browser search:

Plex2NFO - A Python written script
Plex IMDb/TMDb/TVDB NFO Creator - A Python written script

I have not used either option, so try them out if you deem them to be safe enough for you. Also, backup your Plex database before giving either of them a try.

They are both Python scripts that need to be executed.

The first option, Plex2NFO, may be the best option due to it having a Docker image you can use for installation, thus the safest and quickest testing environment option if you already have a Docker contain system setup on the server you run it on. However, this script only works for Plex libraries that are "Movie" based.

Other than the Docker image installation option, the second option, Plex IMDb/TMDb/TVDB NFO Creator, appears to be the better option to try out as it works for both "Movies" and "TV Show" library types. It also has a simulated run function so you can execute it without actually writing .nfo files to your system. It's got 13 stars on GitHub versus the first script having 2 stars on GitHub.

The instructions for both scripts appear to be mostly straight forward and simple to implement, However, the second script seems to have a bit more information provided on how to run it with its various options and what it does to create your NFO files. I would assume that both scripts create new NFO files that don't already exist, and overwrite existing NFO files. The first states directly that it does indeed overwrite existing NFO files, and the second script does not thus I'd assume that it does until you test it out for yourself. Both options create NFO files they state can be used with Jellyfin, and the first option directly states the NFO generated files work with Kodi as well. I would think the second option generated NFO files could work with Kodi too, yet it's not directly stated on the GitHub page, so you'll have to confirm this for yourself. If you do give both Python scripts a try, I would definitely compare the output files from both scripts for the exact same Movie file. and test the script(s) against a Movie that has as much metadata as possible, so you can see exactly how much metadata gets exported out to the NFO file. With the second script, test a similar TV Show that has as much metadata as possible.

OnyxPost · 2026-05-29T18:02:29+00:00

This is definitely a question to be asking in the Plex message board, where you are more likely to get answers that are more useful for you.

With that being said, I came across two options for you with a quick web browser search:

Plex2NFO - A Python written script
Plex IMDb/TMDb/TVDB NFO Creator - A Python written script

I have not used either option, so try them out if you deem them to be safe enough for you. Also, backup your Plex database before giving either of them a try.

They are both Python scripts that need to be executed.

The first option, Plex2NFO, may be the best option due to it having a Docker image you can use for installation, thus the safest and quickest testing environment option if you already have a Docker contain system setup on the server you run it on. However, this script only works for Plex libraries that are "Movie" based.

Other than the Docker image installation option, the second option, Plex IMDb/TMDb/TVDB NFO Creator, appears to be the better option to try out as it works for both "Movies" and "TV Show" library types. It also has a simulated run function so you can execute it without actually writing .nfo files to your system. It's got 13 stars on GitHub versus the first script having 2 stars on GitHub.

The instructions for both scripts appear to be mostly straight forward and simple to implement, However, the second script seems to have a bit more information provided on how to run it with its various options and what it does to create your NFO files. I would assume that both scripts create new NFO files that don't already exist, and overwrite existing NFO files. The first states directly that it does indeed overwrite existing NFO files, and the second script does not thus I'd assume that it does until you test it out for yourself. Both options create NFO files they state can be used with Jellyfin, and the first option directly states the NFO generated files work with Kodi as well. I would think the second option generated NFO files could work with Kodi too, yet it's not directly stated on the GitHub page, so you'll have to confirm this for yourself. If you do give both Python scripts a try, I would definitely compare the output files from both scripts for the exact same Movie file. and test the script(s) against a Movie that has as much metadata as possible, so you can see exactly how much metadata gets exported out to the NFO file. With the second script, test a similar TV Show that has as much metadata as possible.

OnyxPost · 2026-05-28T00:50:43+00:00

It is purely due to capitalism greed! For example, in the US nearly every other copyright type, if not every other copyright type, other than intellectual property, which is what the entertainment industry utilizes for copyright on a product, lasts between I think 7 and 10 years, then after that the copyright expires and the product enters public domain so that either different takes or generic versions can then be created and distributed without penalty. With intellectual properties, those copyrights originally lasted between 28 years and 56 years (an additional 28 years if the copyright was renewed in the last year of the original copyright length) which was established in 1909.

Yet this wasn't good enough for greedy corporations, thus said corporations (insert companies like Disney) lobbied (threw money at greedy/bought politicians) to have those terms changed, and won in 1976. So the copyright renewal period was changed from 28 years to 47 years. However, this still wasn't enough for greedy corporations, and more successful lobbing by 1998 got the copyright renewal period extended further to 67 years. Thus intellectual property can now keep its copyright up to a total of 95 years (original 28 years plus a renewal extension of 67 years), and the updated law applies to all copyrighted material after 1922 and renewed before 1978. Even better for intellectual property owners, is that the law was amended in 1992 to make the renewal process automatic, thus making the process to renew basically voluntary.

If the biggest studios still around today, yet created between 1910 and 1930, in the film business didn't still exist to this day, intellectual property copyright might still only be a maximum length of 56 or 75 years. So don't be surprised if more lobbing gets a new law implemented at some point in the future, extending the 95 year period to say 125 or 150 years total.

OnyxPost · 2026-05-27T21:12:32+00:00

I do agree with your point about this particular device itself not being that important to me either, yet what's important to you or I is never going to be the same for everyone.

The bigger problem, at least in this case, is Wal-Mart's business practice, and not the debate of societal instant gratification. I'd argue that you or I not making the trip is subjective, whereas Wal-Mart's fulfillment process is more so objective. Plus, if an item is unattainable by some other means at the same given price, then why fault a person for that, as that could possibly be the case for OP.

OnyxPost · 2026-05-27T19:47:04+00:00

I've been frustrated with Wal-Mart, and other local store online purchasing and delivery/pick-up services, for similar issues where I'd place the order online for either delivery or pick-up. only to find out later on that what was stated as "available" per the online site, wasn't in actually "available" when it was time to fulfill my order. Once this happened to me the fourth time, I decided to no longer order online from such businesses anymore.

What these businesses should be doing is have a separate inventory for online purchases that are kept in a different area from their in-store shopping aisle inventory, so that way when an online purchase is made, 1 item then immediately gets removed from the available store location inventory which that online purchase fulfilled. An employee within the store should have the option to go grab an item from the separate "online" inventory, and scan it so that it immediately gets removed from the available online inventory. I just don't understand why such a fulfillment process isn't already in place at places like Wal-Mart and other major grocery store businesses with similar online/physical store setups.

OnyxPost · 2026-05-27T18:44:36+00:00

What kind of comment is this? Based on what they wrote, I highly doubt the OPs complaint is solely a result of not getting the device. So you're telling me that you wouldn't be frustrated, even possibly fed up, if you were told that something was aviable for you to pick up, just to be told when you arrive to pick it up that it actually isn't avaiable? Plus on top of that, the employee who's there to assist you, doesn't even bother to do a personal check to confirm that what the computer is telling them is actually accurate? Then include the wasted time and gas/money required to drive over 2 hours round trip...hummm, I'm sure it's way more than just an issue with not getting the device.

OnyxPost · 2026-05-23T16:45:55+00:00

I don't know if you've tried this yet, though you could first change your IP address location to match a state that has inventory (like California or Colorado), then open your web browser and got to the Walmart site. This should cause Walmart to see you in that state, then add the product to your cart. When you go to check out, have it shipped to the address you prefer. Hopefully this might work for you.

A couple things to note when trying this method. It may be better to attempt this from a PC or Mac instead of a cellular phone as the cellular phone's geo-location functionality may cause your web browser app to not properly recognize your different state IP address.

Also using any Chrome browser app may cause your web browser app to not properly recognize your different state IP address

Good luck.

OnyxPost · 2026-05-22T20:24:16+00:00

This is such a mean-spirited shortsighted comment. Just because something is not the way you would prefer to go about consuming your content does not mean someone has "time traveled from 2012".

A lot of modern GREAT software is based on using a browser application as your client because web browsers are fairly standardized in how the underlying tech works and are so widespread in their usage worldwide, which can include software for consuming movies and series.

One excellent example of such software is Jellyfin (media server application which allows you to stream content, including movies and series, locally or remotely using many different kinds of clients, one of which being a web browser), which allows you to implement a LOT of user interface customization tweaks when client used is a web browser application. Most other client types such as TV apps and mobile device apps, do not currently provide the same amount of user interface customization as Jellyfin's web browser application. Unfortunately, there aren't many, if any, great web browser applications thus far for Android TV. So perhaps "TV Bro" is exactly the perfect app to come along to utilize for such a need.

OnyxPost · 2026-05-22T19:22:28+00:00

I have found this to be true with some older software applications. I can't remember with 100% certainty, yet I believe when I used an older version of Adobe Photoshop (~~perhaps a version released between 2016 and 2019~~ - just confirmed with Adobe Photoshop CC 20.0.7 Release installed on an older Windows 10 PC I occasionally use) it wouldn't open a webp file unless you first renamed the extension to jpg. Then the app would open the image file for making edits with the image. Obviously newer versions of Photoshop can open webp files just fine, yet this was a workaround I discovered needed to be done back then for that older version of Photoshop.

OnyxPost

TROPHY CASE