ember finchBOT
Welcome @gusty blaze!
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.
ember finchBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
The following was shared by @gusty blaze and was automatically redacted by Luma as it may have contained sensitive information.
Hi,
I do an operation to update the tmdb score to rotten tomatoes audience score. When I apply jmxd overlay to a new tv show, it puts the correct score but for determining the color of the score it still uses the tmdb score instead of the rotten tomatoes audience score. When I reapply overlays it gets the right color. My running order seems correct. Do you know how I can fix this problem?
below are the relevant files
gusty blaze
ember finchBOT
ember finchBOT
ember finchBOT
indigo hearth
Which event is this log showing? The initial run that runs the operation and gets the color wrong, or the second run with the overlay reapplication that gets it right?
gusty blaze
The first event where it applies the colour of tmdb instead of rotten tomatoes
Wrong color but right score on the overlay
gusty blaze
Any idea? 🙂
toxic cliff
Any idea? 🙂
From looking at the logs the order of operations seems to be:
It looks to me like Kometa does not update the information held in memory for that one run, so when it gets to step 3, it does it based on the information that is read at the very start of the run.
I think that the solution would be either:
a. Update the "Operations" process to also alter the data held in memory by Kometa
b. Add a step between 2 and 3 that re-reads the library information after doing the processing
That's just from looking at the logs though. If Kometa is supposed to update the data it has during the run, then there does seem to be something odd going on. But if it is doing this, I don't see where that happens in the logs. Maybe @indigo hearth or @ebon yarrow would know more.
This would keep inline with the behaviour you're experiencing, though. The second run, it's now reading in the information in Plex, which now has the updated scores. So the colours are applied properly.
indigo hearth
I'm not aware of any caching of the ratings being done by Kometa; it seems like if this were the problem it would show up every time any one used operations to change ratings, and that's not reproducible.
Is there a specific show in here that is showing this issue?
Perhaps it's related to using plex_all: true with a filter rather than doing a plex_search on the ratings that were just set?
gusty blaze
From looking at the logs the order of operations seems to be:
1. Read in the lib...
Yes this is what I thought as well! how can I implement something that re-reads the library after the processing ?
gusty blaze
Is there a specific show in here that is showing this issue?
It’s the ones which have a different score which gives a different colour for tmdb than for audience score of rotten tomatoes
So it uses the score before the operation of the audience score of RT
hallow mesa
It’s the ones which have a different score which gives a different colour for tm...
Right. There are numerous ratings updates. Can you give us a specific example
gusty blaze
I can remember ncis Sydney, but not sure if that was in this scan..
indigo hearth
Yes this is what I thought as well! how can I implement something that re-reads ...
Simplest would be to change that custom overlay to use plex_search instead of plex_all: true with a filter.
Assuming my theory is correct; I'm running a couple tests.
gusty blaze
Simplest would be to change that custom overlay to use `plex_search` instead of ...
Okay thanks! Will check when I’m home
indigo hearth
This appears to be due to the use of:
plex_all: true
filters:
audience_rating.gte: <<audience_rating.gte>>
In the custom overlay rather than:
plex_search:
all:
audience_rating.gte: <<audience_rating.gte>>
changed it, thanks a lot for your help!
river pecanBOT
antwanchild used !aenh
@gusty blaze, 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.