#Overlays are not working after upgrade

1 messages · Page 1 of 1 (latest)

north ermine
#

I was running Version: 1.16.5 for ages because it worked well enough for me. I finally upgraded to Version: 1.19.1 (Windows)

I'm assuming the way in which the overlays are applied is/has changed at some point. So hopefully someone smarter than me can assist.

All I functionally want to do, is get the 4K or 4K HDR overlay on my 4K films. I have roughly ~1000 4K films, and all of them have the old(?) 4K-HDR black banner on the top of the poster which serves it purpose. What would be the process/what do I need to change in order to accomplish this?

wary caveBOT
#

Welcome @north ermine!

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

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

#

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

north ermine
wary caveBOT
#

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

#
**User Info**

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

Table of Contents:
Page 01: User Info
Page 02: PMM Info
Page 03: PMM Summary Info
Page 04: PMM Config.yml YAML Validation
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Plex Configuration - Section 3
Page 08: Plex Configuration - Section 4
Page 09: Rec 01 - ❌ [ERROR]
Page 10: Rec 02 - ❌⏰ PMM SCHEDULED TIME CONFLICT
Page 11: Rec 03 - ⚠️ [WARNING]
Page 12: Rec 04 - ⚠️ LEGACY SCHEMA DETECTED
Page 13: Rec 05 - 💬 CONVERT ERROR
Page 14: Rec 06 - 💬💡️ PLEX DB CACHE ADVICE

craggy monolith
#

I’m fairly new to this. Looks like you don’t have overlays setup?

naive crest
#

not overlay related, but all your best of year collectoins are failing due to changes at imdb. This is why we recommend using defaults if you can. it seems like what you are tryig to do, can be done with defaults.

#

overlays aren't happening, because it's erroring out and not processing. Appears to be a connection issue

tepid kite
#

It's going to be a tedious task to move from 1.16.5 up to 1.19.1 😄

#

a lot has changed

north ermine
#

I figured. Not sure where to even start

tepid kite
#

Honestly I'd use PMM Overlay Reset to revert all of your overlays

#

and then build up from the ground

#

for a throwback, can you send me one of your YAML files? I can't remember what a 1.16.5 YAML file looks like 😄

mint cedar
#

These:

|     1 | Unknown Error: No connection adapters were found for 'C:\\plexstuff\\Colour Logos (Dark)\\tbs.jpg' |

are all because you're using url_poster and handing it a file path. Those should be file_poster.

#
| Collection Error: item_overlay attribute not supported                                             |

The structure of overlays have changed somewhat, and they are now called out separately in the config, basically something like:

  4K Movies:
    metadata_path:
      - file: config/4K.yml
    overlay_path:
      - file: config/4K-overlays.yml

where the overlays have been moved to that other file.

If you provide that file we can help translate them.

#
IMDb Error: Failed to parse URL: https://www.imdb.com/search...

As mentioned, all those are caused by a change on the IMDB side; there's a new imdb_search builder to address this.

#
TMDb Error: No Network found for TMDb ID XXXX

TMDB doesn't have a network with that ID.

north ermine
#

collections:
4K Overlay:
plex_search:
all:
resolution: 4K
hdr: false
item_overlay: 4K
build_collection: false
4K-HDR Overlay:
plex_search:
all:
resolution: 4K
hdr: true
item_overlay: 4K-HDR
build_collection: false
HDR Overlay:
plex_search:
all:
hdr: true
filters:
resolution.not: 4K
item_overlay: HDR
build_collection: false

#

That's what it looks like now, the 4k.yml

raw yoke
#

oh man thats an old setup

tepid kite
#

this is from the wiki:

overlays:
  4K:
    overlay:
      name: 4K    # This will look for a local overlays/4K.png in your config folder
    plex_search:
      all:
        resolution: 4K
  HDR:
    overlay:
      name: HDR
      pmm: HDR
    plex_search:
      all:
        hdr: true
  Dolby:
    overlay:
      name: Dolby
      url: https://somewebsite.com/dolby_overlay.png
    plex_all: true
    filters:
      has_dolby_vision: true
#

probably close to what you want

north ermine
#

That does look like what I'm trying to accomplish more or less with the banners.

So in my existing:

Plex-Meta-Manager\config folder, I do not have an Overlays.yml. I'm assuming this is the new way of applying....the overlays. Inside this new .yml file (using the format supplied above) it calls out all the things I want. HDR banners, DV .etc etc. So, I would get rid of both the old/existing 4k.yml and 4ktv.yml files as the overlays are now handled by the Overlays.yml.

Am I understanding it all correctly?

tender trellis
#

or just use the defaults and use template_variables to replace pngs

north ermine
#

I'd be happy to, but I'm still not sure if I'm just creating an Overlays.yml file inside Plex-Meta-Manager\config folder with this

overlays:
4K:
overlay:
name: 4K # This will look for a local overlays/4K.png in your config folder
plex_search:
all:
resolution: 4K
HDR:
overlay:
name: HDR
pmm: HDR
plex_search:
all:
hdr: true
Dolby:
overlay:
name: Dolby
url: https://somewebsite.com/dolby_overlay.png
plex_all: true
filters:
has_dolby_vision: true

and do I delete the old 4k .yml files? or if i am missing something

mint cedar
#

If the old 4k.yml files contain only overlays, then you can delete them.
If they contain collections and overlays, move the overlays and retain the remainder.

mint cedar
#

If all you want are overlays:

  4K Movies:
    overlay_files:
      - file: config/4K-overlays.yml

Where the name 4K-overlays [and the path to it] is totally arbitrary.

That file contains overlay definitions as shown above.

north ermine
#

this is what the 4k.yml looks like;

collections:
4K Overlay:
plex_search:
all:
resolution: 4K
hdr: false
item_overlay: 4K
build_collection: false
4K-HDR Overlay:
plex_search:
all:
resolution: 4K
hdr: true
item_overlay: 4K-HDR
build_collection: false
HDR Overlay:
plex_search:
all:
hdr: true
filters:
resolution.not: 4K
item_overlay: HDR
build_collection: false

#

so, good to delete that and create a new overlays.yml file

overlays:
4K:
overlay:
name: 4K # This will look for a local overlays/4K.png in your config folder
plex_search:
all:
resolution: 4K
HDR:
overlay:
name: HDR
pmm: HDR
plex_search:
all:
hdr: true
Dolby:
overlay:
name: Dolby
url: https://somewebsite.com/dolby_overlay.png
plex_all: true
filters:
has_dolby_vision: true

#

Sorry for the probably dumb questions, but this stuff is way outside my zone

peak flumeBOT
#

Please use code blocks when sending any code-related text (such as error messages or configuration file extracts.)

The Grave Accent key (`) is used to define code blocks and is typically found to the left of the number 1 key on a standard keyboard.

If you are posting any yaml-formatted text (such as collections), you can add yaml to your Grave Accent keys for coloured formatting. See the below sample text and output

YOU TYPE THIS

`​`​`yaml
collections:
  Documentaries:
    smart_filter:
      all:
        genre: Documentary
`​`​`

DISCORD DISPLAYS

collections:
  Documentaries:
    smart_filter:
      all:
        genre: Documentary
mint cedar
naive crest
#

but alot of the defaults will do what some of the older configs were doing.

#

so you might also check some of those out

mint cedar
#
overlays:
  4K:
    overlay:
      name: 4K        # This will look for a local overlays/4K.png in your config folder
    plex_search:
      all:
        resolution: 4K
  4K-HDR Overlay:
    overlay:
      name: 4K-HDR    # This will look for a local overlays/4K-HDR.png in your config folder
    plex_search:
      all:
        resolution: 4K
        hdr: true
  HDR Overlay:
    overlay:
      name: HDR       # This will look for a local overlays/HDR.png in your config folder
    plex_search:
      all:
        hdr: true

Depending on what your current overlay images look like you may need to add some positioning information.

#

But, yeah, simplest might be to transition to the built-in defaults.
I am assuming you have existing overlay images you want to keep using.

naive crest
#

might be simplest to transition to the defaults and see how they look, and then you can actually make changes using template_variables for things such as images or positioning

north ermine
#

The current overlay looks like that on a poster, its fine

All I want to do is retain that functionality

mint cedar
#

right, so depending on what that overlay image actually looks like [is it 1000x1500 with the banner where you want it? Is it just the banner?] you may need to add some positioning to the YAML above.

north ermine
#

The little HDR logo is a separate image than the 4K ULTRA HD image. As the HDR logo is only applied to films that are 4K and HDR. If its 4K without HDR, it just gets the singular banner. So, 2 separate image files, one or both get applied depending on the source file

#

Both images are 1000x1500

north ermine
#

I got the overlays working now, so that is great. Huge hurdle cleared.

ripe steppe
#

Dropping your log here for luma to review could be helpful

north ermine
wary caveBOT
#

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

#
**User Info**

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

Table of Contents:
Page 01: User Info
Page 02: PMM Info
Page 03: PMM Summary Info
Page 04: PMM Config.yml YAML Validation
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Plex Configuration - Section 3
Page 08: Plex Configuration - Section 4
Page 09: Rec 01 - ❌ ANIDB AUTH ERRORS
Page 10: Rec 02 - ❌🔒 BLANK API KEY ERROR
Page 11: Rec 03 - ❌ [ERROR]
Page 12: Rec 04 - ❌ MY ANIME LIST CONNECTION ERROR
Page 13: Rec 05 - ❌⏰ PMM SCHEDULED TIME CONFLICT
Page 14: Rec 06 - ⚠️ [WARNING]
Page 15: Rec 07 - 💬💡️ PLEX DB CACHE ADVICE

ripe steppe
#

Any questions about the recommendations?

north ermine
#

Well, I don't use/have any anime so that's all pretty self explanatory.

As is the scheduling conflict and DB size