Jump to content

prevent change of existing nfo files


killwack
 Share

Recommended Posts

killwack

Hi.

 

Currently I am using a MYSQL Database and several KODI Clients with different profies accessing my music and movie library on a local NAS. Since more than 10 years I am using XBMC, now KODI and all my library metadata and information is locally stored and mannaged in the appropriate nfo file of the movie, or tv show. This according to "Kodi standard rules", managed by my prefered, really great and simple Ember Media Manager tool used for years.

 

Now I tried emby the first time as an mysql alternative on my NAS, but found out, that after an sucessfull scan with emby of all my ~2000 movies, that all my NFO files have been deleted and renamed to .info by emby after the scan has completed.

 

This change and deletion brought me into big troubles, because I was unable to re-edit or change existing information in the "new" .info file afterwards. My manually placed information in some nfo files has been overwritten by emby, and I was unable to re-edit it because Ember Media Manager is currently not compatible with the .info file. I would assume, the .info used by emby is not 100% compliant to KODIs xlm format, used for their generated .nfo files.

 

I had luck, because I have had a backup :) to be able to restore all local .nfo information of my library. EMby seems to be a great server, because the scan and artwork seems to be very "uncomplicated" compated to the effort needed in using a mysql based backend database for KODI.

 

So I want to ask, if there is a way to prevent emby from changing my local .nfo file?

I have found some settings on the web interface to change the location of the emby metadata or the emby database (tumbnail?) cache, but have not found any way to prevent emby from deleting my local nfo file and re-create a .info instead of it, afterwards.

 

Any idea how I could force emby not to delete or change my existing nfo files stored in my media (movie) directory? I have nothing against, if emby stores the .info file additionally with the pre-existing nfo file in the same, or a different location within my movie directory.

 

I would appreciate your help or any idea, how you have realised or managed your existing emby/KODI media library.

 

BR,

Rainer

 

 

Link to comment
Share on other sites

However, this statement is simply not true:

that all my NFO files have been deleted and renamed to .info by emby after the scan has completed.

There is no part of our system that saves files with the ".info" extension.

 

We do save with the ".nfo" extension which sounds like what you want considering that you're looking for Kodi compatibility.

Link to comment
Share on other sites

horstepipe

In library settings uncheck "save pictures and metadata in media location" (or similar, my Emby is not English).

Then your files should be unaffected and Emby collects all files somewhere in its working directory.

Link to comment
Share on other sites

killwack

Thank you very much for your fast response. I will try both settings and start a library scan again of a media files in a test folder, I have created now.

I come back to you.

 

@@Luke.: I'll also try to reproduce, what kind of program could have changed my existing .nfo to .info. I assumed that this has been created by emby, because I realized the change after it's scan.

 

Thank you,

Rainer

Link to comment
Share on other sites

mastrmind11

Thank you very much for your fast response. I will try both settings and start a library scan again of a media files in a test folder, I have created now.

I come back to you.

 

@@Luke.: I'll also try to reproduce, what kind of program could have changed my existing .nfo to .info. I assumed that this has been created by emby, because I realized the change after it's scan.

 

Thank you,

Rainer

Ember Media Manager is the thing that's renaming your files.  According to http://forum.kodi.tv/showthread.php?tid=205271 EMM renames to .info if it thinks it's discovered an error in the .nfo file.  Get rid of EMM and use Emby for scraping/etc.

  • Like 1
Link to comment
Share on other sites

horstepipe

Get rid of EMM and use Emby for scraping/etc.

I recommend this, too.

I love EMM but combined with Emby you only have trouble.

At least that's the experience I made.

You should bite the sour apple and recreate all .nfo files with Emby. By using Emby for Kodi you have no missing information.

Edited by horstepipe
  • Like 1
Link to comment
Share on other sites

killwack

Hi.

 

Thank you all for your help and hints. I can commit now that Ember Media Manager was the cause of renaming my existing .nfo files to .info, which has been changed during the library scan of emby. (A file compare with the "original" one showed some additional entries after the scan).

 

However I am fascinated of the extreme performance and sync functionality with KODI as a client. So I have to do some test now to understand the feature set and working of emby including it's media manager with movies and tv shows.

 

If you have any suggestion for me, how to read into this topic (sync, configuration, metadata management with emby...) elswhere than using your wiki, I would appreciate your feedback.

 

BR,

 

Rainer

Link to comment
Share on other sites

killwack

In special this will be the auto organize feature and how to figure out a efficient use of your meta data manager. I'll raise a new topic if I have an issue in handling both features. First of all I need to gain a better experience in using emby.

THX

Rainer

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...