2021-01-05, 04:20
Quote:What work? It is only a few button presses.
Via export, yes. But that is not what I took away from the make NFO's Wiki. Of course, that could be my fault.
Via export, yes. But that is not what I took away from the make NFO's Wiki. Of course, that could be my fault.
2021-01-05, 04:28
(2021-01-05, 04:20)appropriate Wrote: Via export, yes. But that is not what I took away from the make NFO's Wiki. Of course, that could be my fault.Sure, if there is something unclear or ambiguous, point me to the offending bit and I will fix.
2021-01-05, 04:47
Quote:Kodi uses nfo files as one way of importing metadata into the library. It is also used as a method of exporting the library for various reasons, including backup. See: Import & Export
That quote is from the NFO files Wiki page. I would make this statement a bit stronger as in "See: Import & Export because if you do an export to separate files it will create the NFO's for you."
The caveat, I suppose, is if you have the wrong file name for the (well let's use movie for example) and the wrong NFO gets created then the user should be warned that when the correction is made then a full (overwrite) export should be done. I had a file called RAINMAN.mkv and for a long time it scraped properly. Recently though it went haywire and I had to change the name to Rain Man (1988).mkv to get it to scrape correctly. The issue I would think is if the art and actor photos were done in the original export, the new export wouldn't necessarily overwrite them. Which brings the situation that, if RAINMAN,mkv got an NFO created, it wouldn't be overwritten, and a caution to go and clean up the directory might be in order.
BTW, I now see why individual folders for movies make sense. I wish I knew that a few hundred movies ago. For whatever reason, nothing in the reading I did when getting started made that important to me.
