Wrong ratings from local nfo

[Coral]

I am new to Jellyfin and first of all, I want to thank you for this wonderful piece of software!
Nevertheless, I have a little problem with the ratings. My goal is for Jellyfin to display the IMDb ratings as the star rating and the Rotten Tomatoes ratings as the tomato rating, as the name suggests.
I am using Jellyfin Server 10.10.3 on Ubuntu and the "Ember Media Manager" to create my local .nfo files. These .nfo files contain ratings for IMDb, Metacritic, Rotten Tomatoes, and TMDb. However, Jellyfin does not correctly scrape the imdb rating that is contained in it and is set as default. Here’s how the rating section looks in the.nfo file for The Shawshank Redemption:

<rating>9.3</rating>
  <votes>2970162</votes>
  <ratings> 
    <rating name="imdb" max="10" default="true">
      <value>9.3</value>
      <votes>2970162</votes>
    </rating>
    <rating name="metacritic" max="100" default="false">
      <value>82</value>
    </rating>
    <rating name="themoviedb" max="10" default="false">
      <value>8.7</value>
      <votes>14545</votes>
    </rating>
    <rating name="tomatometerallcritics" max="100" default="false">
      <value>89</value>
    </rating>
  </ratings>

In this case, Jellyfin will not grab the 9.3 from the first <rating> tag, nor the IMDb rating (which is the default), but will instead display the TMDb rating of 8.7.
I shuffled and tested various combinations of the ratings, as shown below, and observed the star rating selected by Jellyfin in each case (bold):

meta, tomato, tmdb, imdb  ->9,3
imdb, meta, tomato, tmdb  ->8,7
tmdb, tomato, meta, imdb  ->9,3
tmdb, imdb, tomato, meta  ->82
tmdb, imdb, meta, tomato  ->82
tomato, tmdb, meta, imdb  ->9,3
tomato, tmdb, imdb, meta  ->82
tomato, imdb, meta, tmdb  ->8,7
imdb, meta, tmdb, tomato  ->8,7

Interestingly, the Rotten Tomatoes rating (89) is always selected correctly, regardless of its position in the file. From this, I conclude that Jellyfin always scrapes the Rotten Tomatoes rating properly and, for the star rating, selects the last rating entry in the .nfo file (excluding Rotten Tomatoes).
So the question: Is there a way to change this behavior without editing all my .nfo files or am I missing something obvious?
Before suggesting that I can scrape all my movies directly with Jellyfin, I want to explain why I prefer Ember generated .nfo files:

1. The process is historical grown...
   
2. Ember provides more detailed .nfo files, which I use with other software.
   
3. When I use the Jellyfin TMDb scraper, It seems I only get TMDb ratings and no imdb ratings. When I use the OMDb scraper, I get imdb ratings, but all the .nfo text like the plot is in English, which isn't my native language. So, regardless of the solution to my specific problem, I think it would be helpful in the future to at least be able to choose from which source to get the ratings and from which source to get the other information, to avoid this scenario.
   

Thank you very much for your help!

[TheDreadPirate]

If I'm reading the code correctly, it will not read the IMDB rating from NFOs. For some reason, it will read the IMDB rating if it is scraped from OMDB.

[Coral]

I’m not entirely sure what you’re describing. In my small test, it successfully read an IMDb rating, but only if it was the last one listed among multiple ratings in the local NFO file. When scraping information with Jellyfin, IMDb is only retrieved if the OMDb scraper is selected, but in that case, the language is restricted to English.

In the future, it would be great if the scraping options could be adjusted to extract information based on the name label instead of relying solely on its position in the local NFO file. Should I open a ticket on GitHub for this to get a chance? (Fingers crossed )

[theguymadmax]

The code loops through all ratings, overwriting the item.CommunityRating each time it encounters a new rating. As a result, the last non-Rotten Tomatoes score will be used as the community rating. Rotten Tomatoes ratings are treated separately due to their specific handling, so their position in the list doesn't affect the final result.

Currently, Jellyfin does not offer an option to designate a preferred source for the default rating. It simply picks the last rating in the list that is not a Rotten Tomatoes score, as you’ve observed. This is not a bug, but rather how the system is designed. If you'd like to see an option to prioritize certain ratings, that would be considered a feature request, which you can make here.

On a side note, I use tinyMediaManager to create local NFO files for my media, and it lists IMDb as the last rating when it scrapes items.

[Coral]

I wrote a Python script that changed the order of the ratings in my nfos. I will take a look at the feature requests. In the past I also used tinyMediaManager, but then they changed their model so I went back to Ember. But since TMM is evolving fast, I should consider taking a new look. So thanks for the info.