#Duplicating posters

1 messages · Page 1 of 1 (latest)

buoyant dew
#

Despite what I've been told here last time kometa is the one duplicating the posters. It ran tonight and duplication happened. My other script is completely uninstalled so that can't be it.

tawny capeBOT
#

Welcome @buoyant dew!

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.

buoyant dew
#

Overlay is setup correctly

echo mirage
#

Kometa should only upload a new overlaid poster in two cases:

  1. the visual appearance changed due to an updated overlay or something
  2. You have reapply_overlays turned on.

Can you provide a log?

buoyant dew
#

The config I use

Library:

 Films sur demande:
   operations:
     mass_critic_rating_update: imdb
   remove_overlays: false
   reapply_overlays: false
   overlay_files:
     - file: config/overlays/media_info.yml
     - file: config/overlays/movies_rating.yml
     - pmm: languages
       template_variables:
         languages:
           - fr
         use_subtitles: false
         file: config/overlays/flags/<<key>>.png
         text: " "
         back_width: 60
         back_height: 120
         back_color: "#FFFFFF00"
         horizontal_offset: 180
         horizontal_align: right
         vertical_offset: 35
         vertical_align: bottom

Kometa:

settings:
  run_order:
  - operations
  - metadata
  - collections
  - overlays

  cache: false
  cache_expiration: 60

  asset_directory: config/assets
  asset_folders: true
  asset_depth: 0
  create_asset_folders: false
  prioritize_assets: false
  dimensional_asset_rename: false
  download_url_assets: false
  show_missing_season_assets: false
  show_missing_episode_assets: false
  show_asset_not_needed: true
  
  sync_mode: append
  minimum_items: 1
  default_collection_order:
  delete_below_minimum: false
  delete_not_scheduled: false
  run_again_delay: 2
  missing_only_released: false
  only_filter_missing: false
  show_unmanaged: true
  show_unconfigured: true
  show_filtered: false
  show_options: true
  show_missing: true
  show_missing_assets: true
  save_report: false
  tvdb_language: eng
  ignore_ids:
  ignore_imdb_ids:
  item_refresh_delay: 0
  playlist_sync_to_users: all
  playlist_exclude_users:
  playlist_report: false
  verify_ssl: true
  custom_repo:
  overlay_artwork_filetype: webp
  overlay_artwork_quality: 90

plex: ***

tmdb: ***
tawny capeBOT
#

❌ YAML validation failed! YAML checked and is NOT valid.

Error message:

while scanning an alias
  in "<unicode string>", line 50, column 7:
    plex: ***
          ^
expected alphabetic or numeric character, but found '*'
  in "<unicode string>", line 50, column 8:
    plex: ***
           ^
buoyant dew
#

Are logs sanitized and safe to post here?

echo mirage
#

Yes, unless you are running in trace mode or with log-requests enabled

buoyant dew
tawny capeBOT
#

📝 If you want to review this again, gravelfreeman:
: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 05** - 💬💡️ **PLEX DB CACHE ADVICE**

💬💡️ PLEX DB CACHE ADVICE
Consider updating the Plex DB cache setting from 0.01 GB, to a value greater than 1 GB based on the total memory of 63.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).

buoyant dew
#

I can see these annoying Plex Error: resolution: 4K not found. I only got 1x 4K movie in another library and I'm thinking of getting rid of it because the tone mapping sucks for most clients and the movie is so dark freemanLOL

#

The bot recommends me to turn on the kometa cache?

#

It also recommends me to increase Plex cache

echo mirage
#

For some reason, Kometa determined that the overlays on all items have changed such that they needed to be reapplied.

Trace mode can help illuminate this as it should say for each one "applying new overlay because this is not the same as that"

#

If you have the cache disabled that could cause this as well, since Kometa keeps "here are the overlays I applied last time" in the cache.

#

If it has no idea what was there last time it has no way to know they don't need to be updated.

buoyant dew
#

So first thing to try is set remove_overlays to true on my library.

Enable kometa cache.

Then run again with remove_overlays to false.

#

Is the cache directory actually the asset_directory? Because mine is empty.

  asset_directory: config/assets```
#

Empty as you can see on this screenshot

echo mirage
#

You don't need remove overlays, that will add more images.

echo mirage
#

The asset directory is a different thing entirely and Kometa will not write anything there except for one specific instance.

That instance:
You have artwork specified as url_poster and you have download_url_assets enabled.

buoyant dew
#

url_poster isn't referenced anywhere in all of my files.

download_url_assets is set to false.

#

How come this happened?

echo mirage
#

[see here](#1334926178263371837 message)

#

Kometa thought it needed to send a new image.

My theory at this point is that this was caused by the lack of a cache.

No cache means that Kometa doesn't know what overlays got applied last time.

Since Kometa doesn't know that, it has no way to know that this run was the same.

So it sent another copy of the same image.

That's just a theory based on the symptom and the contents of one log

#

I'm running a few tests to see if I can repro it.

buoyant dew
#

Ok. I'll try to run it with cache enabled and will post results.

echo mirage
#

What's the rationale for disabling the cache? That's going to ensure that every run takes as long as possible.

buoyant dew
#

I have no idea. Maybe I was trying to troubleshoot something and I forgot since it's been like 3 weeks.

#

The run worked now! Bingo!

#

thanks man

#

I'll run imagemaid to delete the other posters.

echo mirage
#

It's the disabled cache.

First run:

| Star Trek: The Motion Picture
|   Overlays Applied: Overlay File (0) 1080P

Immediate second run:

| Star Trek: The Motion Picture
|   Overlay Update Not Needed (Current Overlays: Overlay File (0) 1080P)

remove overlays

disable cache, first run:

| Star Trek: The Motion Picture
|   Overlays Applied: Overlay File (0) 1080P

disabled cache, second run:

| Star Trek: The Motion Picture
|   Overlays Applied: Overlay File (0) 1080P
buoyant dew
#

I don't think we should be able to disable the cache since it has no positive effect but only destructive effects.

echo mirage
#

If you don't use overlays the main effect will be longer runs.

buoyant dew
#

It literally filled my Plex storage and could've led in the worst case to database corruption.

#

Anyway I'm glad you could fix my issue! 🙏

#

Could you help me fix the 4K error?

echo mirage
#

There should probably be more warnings in the docs about side-effects.

echo mirage
buoyant dew
#

Yes, looking into it. I was using something made a member of the community.

#

It's probably looking for 4K

echo mirage
#
[ERROR]    | Plex Error: resolution: 4K not found
           | Options: ['1080p']

You are running a search for 4K media in a library that contains only 1080p.

buoyant dew
#

Not sure exactly which value triggers it. Because I still want to identify 4K Remastered. They can be released in 1080p... It means the source material was remastered from 4k.

#
  resolution_info:
    conditionals:
      suppress_overlays:
        conditions:
          - use_<<key>>.exists: true
            value:
              - <<key>>
      resolution:
        conditions:
          - key: SD
            value: sd
          - key: 480P
            value: 480p
          - key: 576P
            value: 576p
          - key: 720P
            value: 720p
          - key: 1080P
            value: 1080p
          - key: Ultra-HD
            value: 4k
    optional:
      - use_<<key>>
      - use_<<type>>
    run_definition:
      - <<use_<<key>>>>
      - <<use_<<type>>>>
    ignore_blank_results: true
    plex_search:
      all:
        resolution: <<resolution>>
echo mirage
#

Ah, it's a filter, not a search, but same issue.

buoyant dew
#

might be this part - key: Ultra-HD value: 4k

echo mirage
#

That's not it. It's the 18 overlays of this type:

|============================== Validating Extended-Cut-4K Attributes ===============================|
buoyant dew
#

Thanks, then I'll just comment out everything that has the 4k mention in it. Not worth the hassle.

echo mirage
#

They are all built like this:

| Validating Method: plex_all
| Value: True
|
| Validating Method: filters
| Value: {'resolution': '4K', 'filepath.regex': '(?i)\\{edition-Extended Cut[^}]*\\}'}

which results in:

| modules.util.FilterFailed: Plex Error: resolution: 4K not found
| Options: ['1080p']
#

You can search the log for the error to see them in context for what you need to disable.

buoyant dew
#

It's also doing it for 1080p filters. ```Overlay Errors Summary

[INFO] No Items found for 54 Overlays: ['DV', 'HDR', 'Plus', 'DV-HDR', 'DV-Plus', 'DigitalPlus', 'DTS-HD', 'DTS-X', 'Atmos', 'TrueHD', 'TrueHD-Atmos', 'DV-DigitalPlus', 'HDR-DigitalPlus', 'Plus-DigitalPlus', 'DV-HDR-DigitalPlus', 'DV-Plus-DigitalPlus', 'DV-DTS-HD', 'DV-DTS-X', 'HDR-DTS-HD', 'HDR-DTS-X', 'Plus-DTS-HD', 'Plus-DTS-X', 'DV-HDR-DTS-HD', 'DV-HDR-DTS-X', 'DV-Plus-DTS-HD', 'DV-Plus-DTS-X', 'DV-Atmos', 'HDR-Atmos', 'Plus-Atmos', 'DV-HDR-Atmos', 'DV-Plus-Atmos', 'DV-TrueHD', 'HDR-TrueHD', 'Plus-TrueHD', 'DV-HDR-TrueHD', 'DV-Plus-TrueHD', 'DV-TrueHD-Atmos', 'HDR-TrueHD-Atmos', 'Plus-TrueHD-Atmos', 'DV-HDR-TrueHD-Atmos', 'DV-Plus-TrueHD-Atmos', 'IMAX-1080p', 'Unrated-Edition-1080p', 'Special-Edition-1080p', 'Collectors-Edition-1080p', 'Minus-Color-1080p', 'Open-Matte-1080p', 'Final-Cut-1080p', 'Restored-1080p', 'Signature-Edition-1080p', 'Theatrical-1080p', 'Theatrical-Cut-1080p', 'Uncut-1080p', 'Ultimate-Edition-1080p']```

#

Is there a way to modify the code so that those aren't seen as errors by kometa?

echo mirage
#

There is no settings-based way to turn those off.

buoyant dew
#

The intended behaviour is : if there's one, then add it, else ignore.

echo mirage
#

Those aren't reported as errors, just warnings and info.

#

If that fails silently, then you have no feedback that you made a spelling error or whatever.

buoyant dew
#

understood!

echo mirage
#

And if you have nothing that meets a given criteria and don't plan to ever have such, turn them off.

buoyant dew
#

it does in other librairies

#

and might in the future

echo mirage
#

Then that suggestion doesn't apply.

#

That file appears to be implemented in such a way as to make this cumbersome. For example, in the defaults you could disable all 18 of those 4K overlays with a single template variable without modifying the YAML.

buoyant dew
#

Yeah it's not the best but I find it the prettiest. I had to add SD myself since. It looks like the author have 100% HD movies :p

trim turtleBOT
#

bullmoose20 used !aenh

@buoyant dew, 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.