Using IMDB rating from Local Metadata

[GrimReaper 4740]

Just now, monkeylove said:

I asked TMM support about the issue, and they said that the NFO I sent does not have the "created by TMM" header or something like that, so they figured that something else wrote on the NFO.

They came to the same conclusion as already stated here:

On 9/1/2024 at 7:26 AM, GrimReaper said:

That is not only TMM-written NFO, as there are some tags TMM does not write + it is not stated in the header/footer. Wild guess would be you're letting Emby (re)write those NFOs - which is never a good idea having multiple software writing/rewriting NFOs as you're bound to eventually face issues and potentially end up in a loop at some point. Disable Emby NFO Metadata writer in library settings (and/or any other software that might be doing it). 

Something is messing with your NFOs (might be Emby, Sonarr or any other software), as a first step you need to trace that. 

[monkeylove 11]

20 hours ago, GrimReaper said:

I reckon OP should clarify their workflow/settings: what's scraping what, what's been imported by Emby and what's been downloaded, what's writing/rewriting NFOs. 

As I don't see any of the issues they're facing and I've been exclusively using TMM-provided metadata for years, all Emby's metadata downloaders and NFO writer are disabled, i.e. TMM backend/Emby frontend. 

I set the Emby server to use only local metadata except for downloading subtitles.

I turn off the Emby server.

I use TMM with IMDB to scrape the videos.

I turn on the Emby server and scan library files.

In light of that, I notice that TMM does not appear to delete old metadata when I rescrape videos, or maybe it doesn't recognize the NFO because there's no "created by TMM" header. In any event, this appears to be a problem involving TMM. Sorry to bother everyone.

 

[GrimReaper 4740]

4 minutes ago, monkeylove said:

I set the Emby server to use only local metadata

You need to have only Metadata Reader>NFO enabled - have you inadvertently enabled Metadata Saver>NFO as well (said option is located below all the other scrapers)? 

7 minutes ago, monkeylove said:

In light of that, I notice that TMM does not appear to delete old metadata when I rescrape videos, or maybe it doesn't recognize the NFO because there's no "created by TMM"

That would generally depend on your setting (both in app settings, clean NFO or not, and scrape item box, whether you overwrite existing data or not), as well as scraper and fields scraped. 

[monkeylove 11]

2 minutes ago, GrimReaper said:

They came to the same conclusion as already stated here:

Something is messing with your NFOs (might be Emby, Sonarr or any other software), as a first step you need to trace that. 

I don't know what Sonarr is. I only use TMM with Emby server.

I just tried the ff:

I took one show, removed it from TMM, and manually deleted the metadata.

I scraped it using TMM and IMDB, and the IMDB rating (and only that) shows up correctly.

I rescrape the same show but this time use TMDB, and the TMDB rating is added with that of IMDB.

"Do not overwrite existing data" was unchecked, and in NFO settings "Write clean NFO" was checked.

I rescrape the show a third time, choosing IMDB, and the two ratings still show up in TMM.

I go to Emby, scan the library files, check the show, and the IMDB rating is shown.

I shut down the server, go back to TMM, and rescrape the video using TMDB.

I repeat the process above, and the rating shown in Emby is still that from IMDB.

 

 

 

[monkeylove 11]

10 minutes ago, GrimReaper said:

You need to have only Metadata Reader>NFO enabled - have you inadvertently enabled Metadata Saver>NFO as well (said option is located below all the other scrapers)? 

That would generally depend on your setting (both in app settings, clean NFO or not, and scrape item box, whether you overwrite existing data or not), as well as scraper and fields scraped. 

That might be the problem: the metadata saver was enabled even though no metadata downloaders and fetchers were enabled. Thanks, I'll retest later.

[Happy2Play 9780]

4 hours ago, monkeylove said:

That might be the problem: the metadata saver was enabled even though no metadata downloaders and fetchers were enabled. Thanks, I'll retest later.

Yep as Emby records the info into db it pushes its fields back to nfo file even if read from in this case a different field.

[monkeylove 11]

Thanks. To clarify,

TMM won't replace the metadata if you rescrape, which is why ratings from other providers still show up. However, the rating of the last provider you use will be the default one.

Emby will still write to the NFO even if you don't check any of the fetchers as long as the metadata saver to NFO is left on. That means the TMM header in the NFO might be removed.

I think Emby can still search for subtitles and the latter can still be accessed correctly even if the metadata saver to NFO is turned off.

Emby can't show more than one rating because it only has one field for it.

[GrimReaper 4740]

6 hours ago, monkeylove said:

TMM won't replace the metadata if you rescrape, which is why ratings from other providers still show up. However, the rating of the last provider you use will be the default one.

Tbh, I always scrape all available ratings (and have multiple scrapers for various metadata fields under Universal scraper), so never really paid attention to that particular scenario with single scraper used; though I would still assume preferred rating getting default flag, depending on one's settings. 

6 hours ago, monkeylove said:

Emby will still write to the NFO even if you don't check any of the fetchers as long as the metadata saver to NFO is left on

Those settings are unrelated: NFO Saver is basically your db dump, it doesn't matter where from the data that was written into the dB came from, i.e. through enabled downloaders, externally written NFO ingestion or metadata edited manually. 

6 hours ago, monkeylove said:

I think Emby can still search for subtitles and the latter can still be accessed correctly even if the metadata saver to NFO is turned off.

As above, subtitle downloading feature is unrelated to NFO Saver, they share absolutely no dependency. 

6 hours ago, monkeylove said:

Emby can't show more than one rating because it only has one field for it.

Correct. 

[monkeylove 11]

According to TMM, the NFO I provided did not come from them because it has no TMM header. They also told me that I'm probably using a third-party program. I only have TMM and the Emby sever.

 

[GrimReaper 4740]

2 hours ago, monkeylove said:

According to TMM, the NFO I provided did not come from them because it has no TMM header. They also told me that I'm probably using a third-party program. I only have TMM and the Emby sever.

I'm somewhat confused now, wasn't that already established that you had library NFO Saver enabled:

On 9/2/2024 at 11:31 AM, monkeylove said:

That might be the problem: the metadata saver was enabled

That resulted in your NFOs being rewritten by Emby on every Metadata refresh or Edit Metadata. If you've disabled it now, you shouldn't see same occurence any more. 

However, I have a feeling you're still tying/relating it to enabled Metadata downloaders:

On 9/2/2024 at 11:31 AM, monkeylove said:

That might be the problem: the metadata saver was enabled even though no metadata downloaders and fetchers were enabled.

 

On 9/5/2024 at 5:40 AM, monkeylove said:

Emby will still write to the NFO even if you don't check any of the fetchers as long as the metadata saver to NFO is left on.

As said:

21 hours ago, GrimReaper said:

Those settings are unrelated

The only thing NFO Saver does is writing data from your database back to your NFOs (irrespective of where from that data came into the database in the first place). 

On 9/2/2024 at 4:30 PM, Happy2Play said:

as Emby records the info into db it pushes its fields back to nfo file even if read from in this case a different field.

Since it is writing it back in Emby format, you're getting your NFOs mangled. 

[monkeylove 11]

Metadata Savers - NFO, "Choose the file formats to save your metadata to."

When I read it, I thought that it simply asked if the metadata file format is NFO. How would I know that Emby would write to the NFOs even though no fetchers are enabled?

 

[GrimReaper 4740]

Would it make it more understandable if it was rephrased to something like:

"Choose the file formats (meta)data from your database will be saved to"

"Choose the file formats (meta)data from your database will be written to"

"Choose the file formats for the external file(s) (meta)data from your database will be saved/written to"

? 

Edited September 7, 2024 by GrimReaper