NFO Questions

[archiel 3]

I have a couple of persistent problems with NFO files and was wondering if anyone else is experiencing these and/or has any solutions.

When adding movies I initially create a basic NFO file with extra data and the files are setup to be UTF=8.  This data is separate to that added and survives the Enby file recognition service. This then allows me to export the data from movies (via mediainfo) and the NFO files to a spreadsheet for further examination. once the move is added  I then lock Title, Original Title, Sort title and  Parental Rating. 

1. When I check the Emby updated NFO the character set is changed from UTF-8 to Western European - OEM US - which can result in special characters  ( ë, ï,  ç, etc) getting changed.  Even when I reset the NFO to UTF-8, if the file is updated again (for any reason) the character set is changed back.   Is there a way to ensure that NFO files are always UTF-8
2. Typically setting the lock setting does not take effect for a couple of days, in particular for Parental Rating.  So if I go to Edit Metadata, set a UK movie to GB-12, click the lock (goes green) and save. It will initially show as GB-12.  However the following day it will show as GB-12A and if I go to Edit Metadata, any previously locked items are now unlocked. There is no fixed time this lasts (never more than 3-4 days) and after that the lock sticks for that movie.

Thanks   Archie

 

 

 

 

[Happy2Play 9780]

Dev will have to comment on 1.

As for 2 that would suggest a write issue for the existing nfo file.  May want to enable debug logging for more info but would need a server log for the initial edit of any example.  As that is really the only way info changes is if the nfo is reread with different info than the db.

[Luke 42078]

Quote

• When I check the Emby updated NFO the character set is changed from UTF-8 to Western European - OEM US - which can result in special characters  ( ë, ï,  ç, etc) getting changed.  Even when I reset the NFO to UTF-8, if the file is updated again (for any reason) the character set is changed back.   Is there a way to ensure that NFO files are always UTF-8

Hi, can you please provide a specific example? This shouldn't happen because all writing occurs in utf8.

[archiel 3]

17 hours ago, Luke said:

Hi, can you please provide a specific example? This shouldn't happen because all writing occurs in utf8.

La Classe Operaia va in Paradiso (1971).NFO

I added a Parental Rating ( mpaa )  via to this file, locked it, <lockedfields>Name|OriginalTitle|SortName|OfficialRating</lockedfields>,  and saved, now  Gian Maria Volontè has become Gian Maria Volont and I need to correct the names and convert the NFO back to UTF-8

Edited June 9, 2025 by archiel

[Luke 42078]

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

[archiel 3]

On 09/06/2025 at 20:42, Luke said:

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

I initially noted two problems (1) the NFO character set being changed and (2) that after adding an item and setting the required locks , the item would later be reset and the locks lost. These appear to derive from the same source, where recently added items are refreshed and replaced. 

I have attached, Echo Valley (2025)_12.04.NFO which is the NFO file from 14 June at 12:04 pm with the locks in place. I have also attached the server log embyserver-63885542400.txt, which is the log file where the data is reset.  The entry at 17:43 was a manual change, but I did not keep a copy this NFO. It appears to be the entries at 21:55 where the data is reset.  

W:\Repairs\embyserver-63885542400.txt (8 hits)
	Line  3455: 2025-06-14 17:43:52.246 Info LibraryMonitor: Echo Valley (2025) (J:\Film\Echo Valley (2025)) will be refreshed.
	Line 10365: 2025-06-14 21:55:05.307 Info App: Removing item from database, Type: Folder, Name: Echo Valley (2025), Path: J:\Film\Echo Valley (2025), Id: 464760
	Line 10369: 2025-06-14 21:55:05.670 Info MediaProbeManager: ProcessRun 'ffprobe' Execute: C:\Users\Media\AppData\Roaming\Emby-Server\system\ffprobe.exe -i file:"J:\Film\Echo Valley (2025)\Echo Valley (2025).mkv" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data
	Line 10371: 2025-06-14 21:55:05.743 Info TheMovieDb: MovieDbProvider: Finding id for item: Echo Valley
	Line 10372: 2025-06-14 21:55:05.744 Info HttpClient: GET https://api.themoviedb.org/3/search/movie?api_key=x_secret4_x&query=Echo Valley&language=en-GB&year=2025

And the current NFO file, where following the removal and re-run of ffprobe fresh, the  lockedfields line has been removed, is also atteched  

This only happens when a item is added.  After it has happened once and the locks reset, it does not appear to re-occur (or at least I have not noticed it)

 

Echo Valley (2025)_12.04.NFO embyserver-63885542400.txt Echo Valley (2025).NFO

[Luke 42078]

Hi, could some other software be updating your nfo files and removing the locks? 

[archiel 3]

I cannot think of anything that would be updating the NFO files. I did have Plex running in the past, which I had considered as a possible cause, but it is no longer running. 

I also have various backup and system admin scripts,   but the times they run do no correspond with the NFO changes.

Finally, it is not clear (to me) whether the changes being made to to the NFO files and then imported or to the to the emby (SQLite ?) database itself, which generates the new NFO.  It seems that it may be the latter, but can you suggest how I can check this?

 

[Luke 42078]

Will be refreshed

@archiel when you see this in the log it means something external from Emby updated the file and Emby server will import the changes. 

does that help you narrow it down?