Kodi Community Forum

Full Version: Changing the default location of nfo/fanart
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Is there anyway I can change the default location for nfo, fanart and background images to a different location? I have a database of over 4tb of video files on a nas, but I keep the nas off most of the time (to preserve power). I was wondering if I could change the default location xbmc scans the info from to c:\movieinfo\(name of movie)\(name of movie).nfo Or something along those lines.
Why does it matter?

You only need to run a scan when you've added something new and XBMC will then only connect to your NAS to actually play something.
Because if it's not that difficult to setup I would prefer to use it this way.
XBMC will only look for an nfo/images/etc during a scan when it has actually found a new media file. What you propose makes no sense in terms of how things work internally.
althekiller Wrote:XBMC will only look for an nfo/images/etc during a scan when it has actually found a new media file. What you propose makes no sense in terms of how things work internally.

How does it not make sense? If i'm going to make nfo's for 6000+ videos, I would only have 2 options, leave a 8tb nas on for hours on end or make all of them while it's off and go through the task of moving them to the nas later. Option 2 seems ideal, but if I'm going through the effort anyways and I can just change a couple lines of code, it would be easier to just leave them on the htpc to start with.

Even that aside I can think of a lot of good reasons to set it up like that. Less clutter in the video directories, for people who use really large allocation sizes for video editing and storage, thousands of small files will end up taking a ton of empty space on the array, I can make changes to video data with out having to turn the nas on, I can have all my movie infos from many different sources in the same folder for easy editing.
The nfos are only read at scan time and their info stored in a local db. At this same time, the images are all cached locally. These are what are accessed when you browse about the GUI during normal usage. We only hit your NAS when you play something.
althekiller Wrote:The nfos are only read at scan time and their info stored in a local db. At this same time, the images are all cached locally. These are what are accessed when you browse about the GUI during normal usage. We only hit your NAS when you play something.

I'm aware of this fact. I would still prefer it this way for multiple reasons. If it's that hard of a thing to explain, then don't worry about it. I'll just make do with how it's setup now. However, if you can help me with this I would appreciate it. I would prefer to have thousands of smaller files on a filesystem setup to handle them, I would prefer not to have the clutter in my video directories and I would prefer not to have the nas running while I prepare all of the nfo files by hand. Can I please get some help?
not possible. i do not even think a patch is welcome.
If you delete a nfo and images after you add the movie to the library, does that affect anything later?
Once a file is added to the Library it get a record in the DB, it stores in the DB thumbnails and such. The DB is stored locally on the HDDs of the client. In other words once the video is added to the DB it doesn't need to access the NFO/TBN files from where the file is located anymore. They can be deleted for all the DB cares. They're only there for purposes of retention in the instance that something might happen to your DB, like an upgrade, or maybe a catastrophic failure.
sentinel41 Wrote:If you delete a nfo and images after you add the movie to the library, does that affect anything later?

If this is your plan of action, why don't you just use the scrapers that are already built into XBMC? That way you don't need .nfo and .tbn files at all.....
he wants to use ONE GLOBAL FOLDER for all nfo/tbn files to avoid cluttering his media dirs.
Erm, if you delete the nfo/images that's going to change the path hash and force a rescan.
joebrady Wrote:If this is your plan of action, why don't you just use the scrapers that are already built into XBMC? That way you don't need .nfo and .tbn files at all.....

Most of the content won't work with scrapers.

althekiller Wrote:Erm, if you delete the nfo/images that's going to change the path hash and force a rescan.

Maxim Wrote:Once a file is added to the Library it get a record in the DB, it stores in the DB thumbnails and such. The DB is stored locally on the HDDs of the client. In other words once the video is added to the DB it doesn't need to access the NFO/TBN files from where the file is located anymore. They can be deleted for all the DB cares. They're only there for purposes of retention in the instance that something might happen to your DB, like an upgrade, or maybe a catastrophic failure.

Those seem to conflict. So I can or can't delete all the nfos and artwork after adding it to the library?