Storing and Editing Person Metadata as .NFO Files Not Working

[Happy2Play 9780]

10 minutes ago, Luke said:

Is that 4.8 or 4.9?

That was 4.9 but see the same in 4.8.

[Luke 42077]

10 minutes ago, Happy2Play said:

That was 4.9 but see the same in 4.8.

OK I've got the saving resolved for the upcoming 4.8.4 release. Thanks.

[haoylee 1]

9 minutes ago, Luke said:

OK I've got the saving resolved for the upcoming 4.8.4 release. Thanks.

That's really good to hear, thanks a lot!

 

And sorry for the troubles by raising this question in a possibly wrong section.

Edited April 5, 2024 by haoylee

[adminExitium 355]

While on the topic of Person NFO metadata, is there any way to allow only reading it from an Emby instance while another instance is allowed to write it?

Something similar to the split read/write NFO settings in the Library.

[Luke 42077]

1 minute ago, adminExitium said:

While on the topic of Person NFO metadata, is there any way to allow only reading it from an Emby instance while another instance is allowed to write it?

Something similar to the split read/write NFO settings in the Library.

There is no way to do that, but you don't have to worry about any realtime monitor going crazy reacting to the changes. There is no realtime monitoring of these files if you were to edit them from outside of emby.

[adminExitium 355]

To expand on this request, I have a metadata instance with the TMDB plugin installed whereas the streaming instance doesn't have it installed (since it's supposed to only read the NFO files updated by the metadata instance), but they both share the same people folder.

I am just worried about the streaming instance overwriting the NFO files with partial info since it doesn't have the TMDB plugin.

[Luke 42077]

Quote

I have a metadata instance with the TMDB plugin installed

I wouldn't suggest doing that because you only get the skeleton people list when you import a new movie into the database.

But the details for a particular person (e.g. description), are not fetched until needed, like when the user clicks on that person. So your server without the MovieDb plugin won't be able to do that.

[adminExitium 355]

Understood, thanks. I have a script gradually refreshing all the person info (couple of entries per hour or so), but I guess there's still a race condition where the new media is scanned in but the person info hasn't been updated which will result in partial info being written via the streaming server, which I wanted to avoid.

Guess I will just install the TMDB plugin on the streaming server too. But does it need to be enabled in any library, or can I leave it disabled in the libraries?

[Luke 42077]

15 hours ago, adminExitium said:

Understood, thanks. I have a script gradually refreshing all the person info (couple of entries per hour or so), but I guess there's still a race condition where the new media is scanned in but the person info hasn't been updated which will result in partial info being written via the streaming server, which I wanted to avoid.

Guess I will just install the TMDB plugin on the streaming server too. But does it need to be enabled in any library, or can I leave it disabled in the libraries?

It should be ok not enabled on libraries.

[Happy2Play 9780]

Appear resolved in 4.9.0.13 beta.

[pj223 1]

@Luke @Happy2Play

On 12/04/2024 at 17:31, Happy2Play said:

Appear resolved in 4.9.0.13 beta.

This error is back in 4.8.10 and 4.9.0.30-beta, Person data is saved but not to the NFO files in the metadata folder, pictures cannot be seen in 4.8.10 but they can be in 4.9.0.30-beta, in both versions the re-uploading of pictures works but is impractical for 100s of people that are not listed on online databases.

[pj223 1]

1 hour ago, pj223 said:

@Luke @Happy2Play

This error is back in 4.8.10 and 4.9.0.30-beta, Person data is saved but not to the NFO files in the metadata folder, pictures cannot be seen in 4.8.10 but they can be in 4.9.0.30-beta, in both versions the re-uploading of pictures works but is impractical for 100s of people that are not listed on online databases.

 

I dropped back to 4.7.14.0 as this the last working version I had time to test, NFO files for Person data is generated when edited correctly. This data is generated by me not found on the internet and I it deem to be important so I have turned off automatic updates till this is fixed.

It is too time-consuming to regenerate this data everytime there is a database problem. If Person data is going to be hosted in the database i.e. library.db then the Person data should be modularised and separated in another db to prevent loss when there is has been a failure.

Edited October 6, 2024 by pj223
Typos

[Happy2Play 9780]

1 hour ago, pj223 said:

@Luke @Happy2Play

This error is back in 4.8.10 and 4.9.0.30-beta, Person data is saved but not to the NFO files in the metadata folder, pictures cannot be seen in 4.8.10 but they can be in 4.9.0.30-beta, in both versions the re-uploading of pictures works but is impractical for 100s of people that are not listed on online databases.

Sorry but I don't follow as do you have specific examples as everything appear to work just fine here.

2024-10-06 08:04:51.685 Debug SqliteItemRepository: GetitemById Person 121881 A:\Emby-Server\metadata\People\J\James McAvoy
2024-10-06 08:04:51.748 Debug App: Running MovieDbPersonProvider for A:\Emby-Server\metadata\People\J\James McAvoy
2024-10-06 08:04:51.748 Info HttpClient: GET https://api.themoviedb.org/3/person/5530?api_key=‌f6bd687ffa63cd282b6ff2c6877f2669‌&append_to_response=credits,images,external_ids&language=en-US
2024-10-06 08:04:52.019 Debug App: Running TvdbPersonProvider for A:\Emby-Server\metadata\People\J\James McAvoy
2024-10-06 08:04:52.020 Info HttpClient: POST https://api4.thetvdb.com/v4/login
2024-10-06 08:04:52.233 Info HttpClient: GET https://api4.thetvdb.com/v4/people/311034/extended
2024-10-06 08:04:52.373 Debug App: Running PersonNfoProvider for A:\Emby-Server\metadata\People\J\James McAvoy
2024-10-06 08:04:52.424 Debug App: Saving nfo metadata for A:\Emby-Server\metadata\People\J\James McAvoy to A:\Emby-Server\metadata\people\j\James McAvoy-tmdb-5530\person.nfo.

Only thing I don't quite understand would be paths as it is somewhat garbage now with paths with and without providerid littering the entire people folder do to changes over time.

Quote

Saving nfo metadata for A:\Emby-Server\metadata\People\J\James McAvoy to A:\Emby-Server\metadata\people\j\James McAvoy-tmdb-5530\person.nfo.

 

But I guess I need to test with people with on online presence/providerids?

Edited October 6, 2024 by Happy2Play

[Happy2Play 9780]

But can see "by name" people always being an issue and will have same name issues no matter what if there is no providerid associated with them as was an issue in 4.7 and before.

[pj223 1]

9 minutes ago, Happy2Play said:

Sorry but I don't follow as do you have specific examples as everything appear to work just fine here.

2024-10-06 08:04:51.685 Debug SqliteItemRepository: GetitemById Person 121881 A:\Emby-Server\metadata\People\J\James McAvoy
2024-10-06 08:04:51.748 Debug App: Running MovieDbPersonProvider for A:\Emby-Server\metadata\People\J\James McAvoy
2024-10-06 08:04:51.748 Info HttpClient: GET https://api.themoviedb.org/3/person/5530?api_key=‌f6bd687ffa63cd282b6ff2c6877f2669‌&append_to_response=credits,images,external_ids&language=en-US
2024-10-06 08:04:52.019 Debug App: Running TvdbPersonProvider for A:\Emby-Server\metadata\People\J\James McAvoy
2024-10-06 08:04:52.020 Info HttpClient: POST https://api4.thetvdb.com/v4/login
2024-10-06 08:04:52.233 Info HttpClient: GET https://api4.thetvdb.com/v4/people/311034/extended
2024-10-06 08:04:52.373 Debug App: Running PersonNfoProvider for A:\Emby-Server\metadata\People\J\James McAvoy
2024-10-06 08:04:52.424 Debug App: Saving nfo metadata for A:\Emby-Server\metadata\People\J\James McAvoy to A:\Emby-Server\metadata\people\j\James McAvoy-tmdb-5530\person.nfo.

Only thing I don't quite understand would be paths as it is somewhat garbage now with paths with and without providerid littering the entire people folder do to changes over time.

 

But I guess I need to test with people with on online presence/providerids?

When running Emby 4.8.+ this type of logging would not appear. The setting to save Person info via NFO would be ticked and but no NFO would be generated. I have no logs of that now as they been overwritten by 4.7.14.0.

No need to think about online providers,  this a local only process for me. If the cast member is 'Mother' and I edit the 'Mother' Person data in Emby I expect name, birthday and bio all to be saved to an NFO in the metadata folder and across all these versions they didn't work for me except for 4.7.14.0.

The information is being sent to the database not to a NFO: 
 

	2024-10-06 16:35:18.834 Debug SqliteItemRepository: GetitemById Person 8 Shinji Ishikawa

I created a Person and I changed the bio information but it did not write it out to a NFO file it went to the database instead. 

[Happy2Play 9780]

I am not sure as I had no issues adding "Media" to anything and applying overview, Birthday/Place.

2024-10-06 08:47:05.135 Debug SqliteItemRepository: GetitemById Person 29297 Media
2024-10-06 08:47:05.143 Debug App: Saving nfo metadata for Media to C:\Users\Media\Desktop\TEST\programdata\metadata\people\m\Media\person.nfo.

 

Edited October 6, 2024 by Happy2Play

[pj223 1]

3 minutes ago, Happy2Play said:

I am not sure as I had no issues adding "Media" to anything and applying overview, Birthday/Place.

2024-10-06 08:47:05.135 Debug SqliteItemRepository: GetitemById Person 29297 Media
2024-10-06 08:47:05.143 Debug App: Saving nfo metadata for Media to C:\Users\Media\Desktop\TEST\programdata\metadata\people\m\Media\person.nfo.

 

I re-tested and destroyed programdata and system folders with a new fresh install of with 4.8.10.0 now NFOs are working again. There must have been something in there preventing this from working.

But this is the fifth time this when I've had to reset Emby like this, thanks for the help. This saga is done. I'll have to re-create the library, at least I have the NFOs.

[Happy2Play 9780]

3 minutes ago, pj223 said:

I re-tested and destroyed programdata and system folders with a new fresh install of with 4.8.10.0 now NFOs are working again. There must have been something in there preventing this from working.

But this is the fifth time this when I've had to reset Emby like this, thanks for the help. This saga is done. I'll have to re-create the library, at least I have the NFOs.

Really hard to say what these quirks come from unless something is caught via loggings.  But yes if possible it is always good if you can test on a clean install.  As upgrades could have legacy issues that can not happen in clean install.

Edited October 6, 2024 by Happy2Play

[pj223 1]

On 05/04/2024 at 07:19, Luke said:

OK I've got the saving resolved for the upcoming 4.8.4 release. Thanks.

@Luke
The people NFO not saving bug has appeared again in 4.9.3.0, media can edited in Emby and a Person's data is saved but it is saved to the database only. If there is a problem with the database any manually edited data that is not available online is wiped. No NFOs are generated.

On a fresh install of Emby I edited a person and the Person folder did not appear, neither did the named folder. This only appeared after adding an image to the Person but still no NFO appeared after changing the text bio of the person.

Is this a bug or a feature in version 4.9.3.0? If not, please fix at your earliest convenience.

[pj223 1]

@LukeIgnore previous post metadata was turned off after update. Not sure how that happened.