To nfo or to not nfo....that is the question?

[JXL2112 7]

I noticed the option to use nfo files which I selected. It created a nfo file in every folder. So what happens if I don't select the nfo checkbox?

[Luke 42079]

Then you will not get nfo files for new metadata that is saved going forward.

[Sammy 790]

IIR I don't have nfo enabled but Emby works fine. Am I missing something?

 

Sent from my SM-G960U1 using Tapatalk

[Happy2Play 9780]

I noticed the option to use nfo files which I selected. It created a nfo file in every folder. So what happens if I don't select the nfo checkbox?

 

IIR I don't have nfo enabled but Emby works fine. Am I missing something?

 

Sent from my SM-G960U1 using Tapatalk

 

 

Metadata is only saved in the database.  So if anything happens to the database your media has to be re-identified and fetched from provider sites.  If a nfo file was written Emby would just re-read the existing metadata and not have to search for it again

[hein 12]

To expand on Happy2Play's post, some personal experience:

 

The Emby database layout is subject to change and it has happened several times in the past that major updates caused custom metadata loss, when said metadata was only saved in the internal database.

The combination nfo is standardized to some degree and widely used in the media manager world.

 

While only relying on Emby's internal database for metadata safekeeping provides convenience (and "neat folders").

NFOs give you an easy way to manually edit and backup your metadata (also across Emby versions) and they ensure portability if you should ever choose to switch to another media manager solution. In a best case scenario they also lessen the burden on online metadata providers when it comes to rescans, etc.

 

If you solely rely on external providers for your metadata, never make any manual edits you would be upset to lose, never have to manually identify any contents of your library and can live with a possible longer initial database refresh after major internal Emby database/version changes, then there is no real downside (except possibly hammering external metadata providers) to using Emby's internal database for convenience.

 

When choosing to solely rely on the internal database, don't forget to implement a (verified restorable!!) backup routine. The Emby backup plugin does not backup metadata.

When choosing to have Emby create NFOs, you basically have your first database backup in said NFOs, but I would still consider setting up a backup routine anyway . And be aware that Emby might overwrite any of your own, non-standard NFOs saved with your media. So if you value those, be sure to backup them and best move them out of the way, e.g. in a NFOs subfolder.

[JXL2112 7]

Thanks for the NFO on the NFO's

 

BTW: I've noticed that Emby tends to ignore any manual editing of the NFO's that occur outside of Emby. I tried using Notepad++ but Emby just overwrote the changes.

[Happy2Play 9780]

Thanks for the NFO on the NFO's

 

BTW: I've noticed that Emby tends to ignore any manual editing of the NFO's that occur outside of Emby. I tried using Notepad++ but Emby just overwrote the changes.

 

Depending on whether you system supports Realtime monitoring and if so you having it enabled they will be picked up.  But the item needs to be refreshed "Scan for new and updated files" on the item or run a library scan.

[Sammy 790]

I double checked and am using nfo's. Default I suppose.

 

Sent from my SM-G960U1 using Tapatalk

[Luke 42079]

@@hein if you upgrade from 3.5 to 4.1.0.10 beta you should have a smoother experience now. Thanks.

[Alfsvag 2]

I already have a bunch of custom .nfo files as I used Kodi previously. As I prefer to have my drives spin down (controversial I know). I'd prefer to have all my metadata saved in a database on my ssd instead.

Now, I know that a database will be created if .nfo backup is turned off. However, can that database be created by scraping information from the pre-existing .nfos? If so, can this .nfos then be ignored once the database is created?

[naeonline 27]

Use the .nfo plugin when first building your library and then you can remove it afterward.