#Overlay has both Returning and Airing applied
1 messages · Page 1 of 1 (latest)
Welcome @slow nest!
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.
Is that the only one?
If so. Delete the poster in Plex, remove the Overlay label and rerun. Problem will go away.
If the problem is more than that, provide logs
"There is another."
📝 If you want to review this again, docnmharti:
: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> 📝
📝 Great! Let's start to review and make recommendations, docnmharti... 📝
📝 If you want to review this again, docnmharti:
: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> 📝
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 - 💥 BAD PLEX VERSION ERROR
Page 12: Rec 04 - 💬 CONVERT ERROR
Page 13: Rec 05 - 💬 LEGACY SCHEMA DETECTED
Page 14: Rec 06 - 🛠️ INCOMPLETE LOGS
Page 15: Rec 07 - 🚫 MY ANIME LIST CONNECTION ERROR
Page 16: Rec 08 - 💥 NO ITEMS FOUND IN PLEX
Page 17: Rec 09 - 💬 LEGACY SCHEMA DETECTED
Page 18: Rec 10 - ⚠️ MEMORY RECOMMENDATION
Page 19: Rec 11 - 💡️ PLEX DB CACHE ADVICE
Page 20: Rec 12 - ❌ PLEX REGEX ERROR
Page 21: Rec 13 - 🚫 PLEX LIBRARY ERROR
Page 22: Rec 14 - 🚫 TRAKT CONNECTION ERROR
Rinse and repeat the process?
I don't understand
Likely your selected images had an overlay on them and the overlay label was removed and PMM applied an overlay on top of them
#1172986041007886427 message
Yes, but what am I supposed to repeat?
It's not the only one, though
I don’t know if it’s 2 out of 10,000 or two out of 10
If you want, we could bulk reset
Is that the easiest way? Is it the best way?
As I said, I don’t know how bad it is
2 (that I've noticed) out of 200
How would I know?
It would be in your config.yml file
That’s the page for assets
Basically… how do you decide which posters to select for your movies and shows?
settings:
asset_directory: config/assets
This is what I have
The formatting was messed up on that one.
settings:
asset_directory: config/assets
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
How do you decide what poster for your movies and shows?
Just whatever Plex matches with. When a new show is added, I manually check out the poster (and the season poster as well) to make sure it is a proper fit, then I leave it alone and let PMM do its thing.
Ok… because bulk reeet option means it will get the poster from Plex or from tmdb
Right. They aren't custom or anything.
Some people are very picky
I get that. I'm ok with the default posters, as long as everything works right.
So under overlay_path, use reset_overlays: plex
This example is commented and pointing to tmdb which is an option as well
And then I just have to restart the container, right?
Then you have to rerun PMM
Whatever that means in your setup
Starting a container does not always mean run PMM
I think it's running continuously, if I remember correctly
Then it will run on the next schedule
On a side note, reading the log used to be top to bottom, had nice ascii art for PMM. Now it reads bottom up and the art is all messed up. What's up with that? It happened when Docker migrated to Container Manager
That’s not a PMM thing
ok, thanks
I run pmm on my synology which uses container manager and I do not have the log issue you’re talking about
I wonder why, then. It makes it really difficult to read though.
This fixed it, thank you
Great. Make sure to turn it off for the next run
Will do, thank you
If there is nothing else, feel free to /close this