#Movie is not getting split

1 messages · Page 1 of 1 (latest)

languid sorrelBOT
#

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

#

📝 If you want to review this again, rafa130397:
: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> 📝

#

Welcome @south spoke!

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.

languid sorrelBOT
#

Hey!

I just have a quick question. I added another copy of Memories of Murder (4k, I already had a 1080p copy), and I have the split duplicates true in my config so. Why did the movie not get split?

Thanks!

#
**Rec 05** - 💬 **CONVERT WARNING**

💬 CONVERT WARNING
Convert Warning: No * ID Found for * ID.
These sorts of errors indicate that the thing can't be cross-referenced between sites. For example:

Convert Warning: No TVDb ID Found for TMDb ID: 15733

In the above scenario, the TMDB record for The Two Mrs. Grenvilles ID 15733 didn't contain a TVDB ID. This could be because the record just hasn't been updated, or because The Two Mrs. Grenvilles isn't listed on TVDB.

The fix is for someone like you, perhaps to go to the relevant site and fill in the missing data.
For more information on handling these, [https://kometa.wiki/en/latest/kometa/logs/#warning]
814 line(s) with Convert Warnings. Line number(s): 6295-6299, 13594-13598, 14755-14874, 14936-15267, 15329-15360, 15422-15525, 15590-15630, 15692-15704, 15766-15857, 15919-15960, 16022-16023, 16426-16451

Page 11/12
south spoke
#

Can somebody help? <@&938443185347244033>

fleet pewter
#

your config isn't needed, it's already redacted in log file

languid sorrelBOT
#

📝 If you want to review this again, antwanchild:
: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> 📝

languid sorrelBOT
# languid sorrel
**User Info**

Author of Linked Message: Luma
Person who Invoked the Command: Antwan
File Name: meta.log

Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation ✅
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - 🚀 VERSION UPDATE AVAILABLE
Page 08: Rec 02 - ❌ [ERROR]
Page 09: Rec 03 - ⚠️ [WARNING]
Page 10: Rec 04 - ⚠️ REAPPLY / RESET OVERLAYS
Page 11: Rec 05 - 💬 CONVERT WARNING
Page 12: Rec 06 - 💬💡️ PLEX DB CACHE ADVICE

Page 1/12
languid sorrelBOT
fleet pewter
#

reapply_overlays: should really never be true. Kometa will automatically reapply overlays as needed

#

the split_duplicates: true not working, that i am not sure why that would not be working.

south spoke
#

I have had this issue before. If I don't have the reapply_overlays in true, it just doesn't update my overlays. I have spoke with you guys multiple times and we have arrived at the conclusion that nobody knows why that happens to me

fleet pewter
#

reapply overlays creates bloat, there had been an issue related to plex that caused ratings issue, which has been fixed.

south spoke
#

I have image maid that runs immediately after kometa

#

so no problem regarding bloat

fleet pewter
#

Ok. Well just mentioning it as a way to save resources and shorten runs. So that overlays are not being applied on every run when not needed.

south spoke
#

I know, I really wanted it to work, but you can check my previous posts and check that we arrived at the conclusion that we don’t know why my overlays dont get updated when scores change

rustic carbon
#

Perhaps this is another instance of your setup behaving in unexplained ways.

fleet pewter
south spoke
#

maybe @fleet pewter is right, I will test it

fleet pewter
#

and it wasn't an issue caused by Kometa either

south spoke
#

Wait, but was the error fixed on kometa’s or on plex’s side? Because Im using an old plex server version (due to other reasons)

rustic carbon
south spoke
#

Do you happen to know the plex version?

frosty knoll
#

thread about the issue

#

version after 1.40.0.7998 is when it starts

#

1.40.3.8502 is when it was fixed

south spoke
#

I'm using 1.32.5.7349-8f4248874-ls178, so that is weird. So nothing was fixed from Kometa's side because there was nothing wrong in the first place right?

fleet pewter
#

There wasn’t anything broken with Kometa related to your overlay issue

south spoke
#

Okay, then I guess I will have the same issue due to my plex version

fleet pewter
#

But not caused by Kometa

south spoke
#

exactly

#

damn Plex lol

fleet pewter
#

I mean why are you staying on 1.32?

south spoke
#

because if I upgrade I get some stuttering, I have no idea why

fleet pewter
#

Maybe you find it works good now if you update?

south spoke
#

the stuttering you mean?

fleet pewter
#

Yes

south spoke
#

I tried recently without luck

fleet pewter
glass crestBOT
#

Anything further needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.