Custom location for metadata

[kidnappervan 4]

I'd prefer to keep additional files out of media folders, how can I set a custom location for metadata (NFO & Artwork)?

Edited December 12, 2021 by kidnappervan

[Happy2Play 9783]

6 minutes ago, kidnappervan said:

I'd prefer to keep additional files out of media folders, how can I set a custom location for metadata (NFO & Artwork)?

Well these are a per library option to write nfo files and save images into media folders.

There is an option for a custom /metadata location on Library, Advanced tab.  But note if this is not set before ever creating libraries you will have entries in the database that will point to default location and all new items will point to applied custom location.  So you will have to maintain both unless you are going to Refresh everthing.

There is no custom location for nfo files, they are with media or info only contained in the current database.

[kidnappervan 4]

Why can't the nfo files be sent to the same custom location as the images?

[Luke 42085]

23 hours ago, kidnappervan said:

Why can't the nfo files be sent to the same custom location as the images?

HI, it's possible, it's just not something that's come up before.

[Carlo 4561]

Hi, Keep in mind why the option is there.  Putting things like graphics, bif/thumbnails and NFO files with your media has two positives.

First it reduces the size of the meta-data folder needed as it can be spread out over many disks (with your media).  Otherwise the many people who run the OS and Emby on SSD would need huge SSD drives to hold this.

Second, it puts this content with the media so if something were to ever happen and you had to setup/reload your libraries it would allow you to turn off all meta-data providers in the library except NFO and load your libraries quick!  Then after the normal load you put the settings back.  That makes sure to keep/use all the hand editing you've done in the past and save you from having to re-identify the problem media.

Having an option to put this somewhere else could be a big negative for the intended purpose and confuse new users.

That doesn't mean we can't look and think about this but it's just letting you know why it's there in the first place and what obstacles this could make.

[kidnappervan 4]

First, the metadata does not need to be stored on the OS drive, it could be stored on a media drive in it's own folder not cluttering up media folders.

Second, metadata would still be stored locally so we would still be able to rebuild offline, quickly and without losing custom edits or re-identifying media.

Third, I would argue that it's already confusing to new users as the option to save metadata with media is not turned on by default. 
For example, I've built a library over a few years, and now that I need to move the server, I have no way of saving customised metadata. 
I would have had to know to turn that option on immediately while I was still experimenting with the software or else have it stored in a database that gets wiped when reinstalling.  
Seems like a much less messy solution to just have all metadata saved to a metadata folder that could be backed up, moved or copied.

I appreciate you taking the time to explain your reasoning and I thank you for listening to why I disagree with that reasoning. 
 

[pwhodges 2014]

I'm sure that many people would be more interested in learning about saving metadata and images with their media if there was a way - even if it's an offline program - to transfer their default internally stored metadata to the media (or alternative) directories.  As it is, the certainty of losing everything they've done previously ensures that they quickly lose interest.

Paul