Ratings Help | Kometa | Page 1

hasty lilyBOT Oct 2, 2024, 4:29 PM

#

✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements

#

Welcome @steel orchid!

It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.

Someone from <@&938443185347244033> will assist when they're available.

Including meta.log from the beginning is a huge help. Type !logs for more information.

After attaching your log, do not forget to hit the green check boxes when prompted by our bot.

#

You can press the "Close Post" button above or type /close at any time to close this post.

hasty lilyBOT Oct 2, 2024, 4:29 PM

#

hasty lily You can press the "Close Post" button above or type `/close` at any time to clos...

#

#

📎 config.yml

#

I clearly do not get how the ratings work. When I view them on my overlays they do not match. IMDB and Rotten Tomatoes Audience currently have the same scores on the overlay (like 8.2 and 82%, for example). Rotten Tomatoes does have a separate score for some of them but I just do not understand how I have the ratings so mixed up.

dapper solar Oct 2, 2024, 4:32 PM

#

Please read through the article in the wiki that covers the concepts behind how this works; it should cover your questions:
https://kometa.wiki/en/nightly/kometa/guides/ratings/

steel orchid Oct 2, 2024, 4:33 PM

#

So from my understanding, I would need to put IMDB as the user source if my plex library's rating source is defaulted to Rotten Tomatoes?

dapper solar Oct 2, 2024, 4:34 PM

#

If you are setting ratings using Kometa, it doesn't matter what you set the library rating source to since you are overwriting whatever ratings Plex may set.

#

this:

    operations:
      mass_critic_rating_update: mdb_imdb
      mass_audience_rating_update: mdb_tomatoes
      mass_user_rating_update: mdb_tomatoesaudience

Is overwriting whatever Plex is putting in the ratings with these numbers, so it doesn't matter what the library is set to.

steel orchid Oct 2, 2024, 4:36 PM

#

I am not understanding why my yaml will not work, then. It is acting as if I have not matched up the correct mass_*_rating_update with the right image.

dapper solar Oct 2, 2024, 4:40 PM

#

Can you provide a log of this happening?

steel orchid Oct 2, 2024, 4:44 PM

#

Yes, one second.

dapper solar Oct 2, 2024, 4:44 PM

#

Those ratings on the poster seems to reflect the numbers in the fields.

steel orchid Oct 2, 2024, 4:46 PM

#

Right, but I don't believe that I defined them to reflect the ones that they currently are.

dapper solar Oct 2, 2024, 4:47 PM

#

You appear to be setting them correctly in the config:

    operations:
      mass_critic_rating_update: mdb_imdb
      mass_audience_rating_update: mdb_tomatoes
      mass_user_rating_update: mdb_tomatoesaudience   
...
      - default: ratings
        template_variables:
          rating1: critic
          rating1_image: imdb
          rating2: audience
          rating2_image: rt_tomato
          rating3: user
          rating3_image: rt_popcorn

steel orchid Oct 2, 2024, 4:48 PM

#

Wait, I see. So critic is considered rotten tomatoes on plex's client, audience -> tomatoes audience and user -> stars?

dapper solar Oct 2, 2024, 4:50 PM

#

This is explained in that article.

Plex has three boxes available for setting ratings:
Critic
Audience
User [the stars]

This item has Rotten Tomatoes set as the ratings source, so the UI displays the tomato and popcorn next to the critic and audience ratings.

Your config is putting an IMDB rating in the critic slot, but Plex doesn't know that happened; it continues to display the tomato icon.
Same with the audience rating.

Kometa then reads the value from the field and formats it the way you tell it to:

          rating1: critic
          rating1_image: imdb

Once Kometa puts the imdb rating in the critic slot, then only entity that knows that happened is you.

steel orchid Oct 2, 2024, 4:53 PM

#

Why would it decide to fill certain other ratings with the same score if Plex itself can't seem to find it like this one?

dapper solar Oct 2, 2024, 4:53 PM

#

That would be shown in the log.

#

What is shown in the XML for that item?

#

That will show what Kometa is basing the overlays on.

steel orchid Oct 2, 2024, 4:55 PM

#

rating="4.3" audienceRating="4.3" userRating="4.3"

dapper solar Oct 2, 2024, 4:56 PM

#

Kometa won't "decide to fill certain other ratings with the same score". It only does specifically as instructed. If it can't find a rating it won't set a rating.

Those got set to the same rating for some specific reason, and that would be shown in the log from when that happened.

dapper solar Oct 2, 2024, 4:57 PM

#

steel orchid rating="4.3" audienceRating="4.3" userRating="4.3"

That reflects what shows up on the poster, so that machinery is working as expected.

steel orchid Oct 2, 2024, 4:59 PM

#

📎 meta.log

hasty lilyBOT Oct 2, 2024, 4:59 PM

#

📝 If you want to review this again, whistlewrld:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#

**Rec 09** - 💬💡️ **PLEX DB CACHE ADVICE**

💬💡️ PLEX DB CACHE ADVICE
Consider updating the Plex DB cache setting from 0.04 GB, to a value greater than 1 GB based on the total memory of 15.00 GB.
Setting db_cache: 1024 within the plex settings in your config.yml is effectively 1024MB which is 1GB. For more info on this setting: https://kometa.wiki/en/latest/config/plex#plex-attributes
NOTE:The number you choose can vary wildly based on a number of factors (such as the size and number of libraries, and the amount of files/operations/overlays that are being utilized).

steel orchid Oct 2, 2024, 5:02 PM

#

Alright this seems like a lot lmao

dapper solar Oct 2, 2024, 5:08 PM

#

This run is doing overlays only , so none of the operations [like setting ratings] are happening.

[2024-10-02 16:04:48,351] [kometa.py:318]             [DEBUG]    | Run Command: kometa.py --overlays-only --run                                                       |

steel orchid Oct 2, 2024, 5:09 PM

#

ahhh that makes so much more sense.

dapper solar Oct 2, 2024, 5:10 PM

#

Then for every movie in the library:

                                                                 | Nothing in Common                                                                                  |
[2024-10-02 16:19:43,815] [overlays.py:529]           [INFO]     |   Overlay Update Not Needed                                                                        |

The overlays haven't changed, so they aren't reapplied.

#

Well, except one:

                                                                 | The Watchers                                                                                       |
[2024-10-02 16:20:47,511] [overlays.py:524]           [INFO]     |   Overlays Applied: Overlay File (1) 1080P, Overlay File (2) AAC, Overlay File (3) Rating1Rotten, Overlay File (3) Rating2Rotten |

#

This log ends abruptly while the TV overlays are being processed.

steel orchid Oct 2, 2024, 5:12 PM

#

So i need to do an operations only run then an overlays only run to avoid going through everything else, correct?

dapper solar Oct 2, 2024, 5:12 PM

#

Sure.

dapper solar Oct 2, 2024, 5:58 PM

#

You could also add a schedule to the things you don't want to happen.

plain flintBOT Oct 3, 2024, 12:16 AM

#

antwanchild used !aenh

@steel orchid, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.

#Ratings Help