fogpuppy 1 Posted June 29, 2020 Posted June 29, 2020 (edited) Does anyone know how to make Emby store relative paths for the posters, fan art, etc. in the .nfo files. I've got my library set to store the metadata in the folder with the media but it's putting rooted paths in the .nfo file which is a pain in the butt when I have to move things around or copy them to a new server that might not have an identical setup. Basically I'm trying to set up a reusable media/metadata structure. This is a little snippet of one of the nfo files: <art> <poster>/Volumes/Data/Media/plane/Movies/21 Grams (2003)/poster.jpg</poster> <fanart>/Volumes/Data/Media/plane/Movies/21 Grams (2003)/fanart.jpg</fanart> </art> Ideally the paths would be based off the location of the corresponding media file so something like this: <art> <poster>poster.jpg</poster> <fanart>fanart.jpg</fanart> </art> Or if not that at least make them relative to the "base" of the library which in this care is "/Volumes/Data/Media/plane/Movies" so you'd get something like: <art> <poster>./21 Grams (2003)/poster.jpg</poster> <fanart>./21 Grams (2003)/fanart.jpg</fanart> </art> Edited June 29, 2020 by fogpuppy
pünktchen 1350 Posted June 29, 2020 Posted June 29, 2020 If you store images with your media, i would disable the writing of image paths to nfo files.Even Kodi always prefers local images over the image paths from nfo. And if the local image doesn't exist anymore, the local path in your nfo is also obsolete. So why even bother? 1
fogpuppy 1 Posted June 29, 2020 Author Posted June 29, 2020 Ok so you’re saying it doesn’t matter that the nfo file has rooted paths because Embys going to use the images co-located with the media and ignore the path in the nfo? I ask because after you move a directory the paths are wrong. If they’re going to be ignored then it may not matter ... though it would still be better if they were relative so they were not wrong.
Luke 40137 Posted June 29, 2020 Posted June 29, 2020 For what it's worth, new Emby server installations have this option disabled by default now.
fogpuppy 1 Posted June 29, 2020 Author Posted June 29, 2020 I’m sorry Luke ... what option is disabled?
ebr 15679 Posted June 29, 2020 Posted June 29, 2020 Writing the image paths to the NFO I believe. That is only done for 3rd party apps. We don't use that data.
fogpuppy 1 Posted June 29, 2020 Author Posted June 29, 2020 Ok good to know. So to confirm I can safely ignore the paths in the nfo and Emby will use the files in the same directory as the media file they are for. That means if I copy a directory and it’s contents to a new server it should be “pre-populated” with the right files without having to fetch metadata”....
Happy2Play 9458 Posted June 30, 2020 Posted June 30, 2020 (edited) Correct all existing local metadata and images will be read before looking online. As noted some information is only used by Kodi/third party apps. But you could look at the Nfo Metadata option via Dashboard-Nfo Metadata (server section) or Clicking on Nfo Metadata in Plugins. Edited June 30, 2020 by Happy2Play
fogpuppy 1 Posted July 5, 2020 Author Posted July 5, 2020 (edited) Yes .. thanks. I was able to confirm that the local meta data was used even when the paths are bogus. Plus, I can change the setting to turn off storing the patch in the first place. So as long as all the files are named in standard ways it's good. So this is "solved" from my perspective. Edited July 5, 2020 by fogpuppy
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now