2024-05-30, 03:21 AM
(This post was last modified: 2024-05-30, 09:08 AM by MrFusion. Edited 2 times in total.)
I use local .nfo and store artwork in folder for similar control freak reasons. Just follow naming convention and you can pre-add posters etc before import. I’ve also manually created nfo’s and they will be used to pull from before a fetcher scan.
A few caveats - some special characters in a manually created .nfo can mess up the import. For example an ‘&’ in description will stop the .nfo from being used, the movie won't pull the metadata.
Option here was to remember to (or go back and) type '&;amp' and such - or just cut the description info from the failed nfo import, scan without it, and then add into the jellyfin edit metadata description field to clean it up. Both work and the update either way is pretty much instant.
When I first set up my library it was using ‘file.jpg’ which bugged massivly, it didn’t use all my manual Plex posters. But poster.ext works and now everything saves that way (no clue on if or why).
I wrote (asked chatGPT) a bash script that renamed them all to ‘poster.ext’ and jellyfin was not upset in the slightest. I also had a script to remove image links to folder.ext references in the .nfos and replaced with links to poster location without issue. Just needed do a library scan afterwards.
I also did a script to remove <trailer> tags from the .nfo as I decided I didn't want any YouTube connections after messing with that plugin. Totally fine… ran the script edited all the .nfos, and Jellyfin removed the trailer icon from the detail page of all the movies except the ones I had a local trailer for.
I also renamed some <genre> to <tag> manually in the .nfo and not only was Jellyfin fine with that, it rewrote the nfo and moved the <tag> from the list of <genre> to its correct spot when I did a metadata update.
A few caveats - some special characters in a manually created .nfo can mess up the import. For example an ‘&’ in description will stop the .nfo from being used, the movie won't pull the metadata.
Option here was to remember to (or go back and) type '&;amp' and such - or just cut the description info from the failed nfo import, scan without it, and then add into the jellyfin edit metadata description field to clean it up. Both work and the update either way is pretty much instant.
When I first set up my library it was using ‘file.jpg’ which bugged massivly, it didn’t use all my manual Plex posters. But poster.ext works and now everything saves that way (no clue on if or why).
I wrote (asked chatGPT) a bash script that renamed them all to ‘poster.ext’ and jellyfin was not upset in the slightest. I also had a script to remove image links to folder.ext references in the .nfos and replaced with links to poster location without issue. Just needed do a library scan afterwards.
I also did a script to remove <trailer> tags from the .nfo as I decided I didn't want any YouTube connections after messing with that plugin. Totally fine… ran the script edited all the .nfos, and Jellyfin removed the trailer icon from the detail page of all the movies except the ones I had a local trailer for.
I also renamed some <genre> to <tag> manually in the .nfo and not only was Jellyfin fine with that, it rewrote the nfo and moved the <tag> from the list of <genre> to its correct spot when I did a metadata update.