#Updating Movie posters to images in Asset directory

1 messages · Page 1 of 1 (latest)

sour fern
#

Hi, I have started downloading image assets to use for poster images and wondering if this is correct for the config yml?
All image assets will be inthe asset folder, no subfolder for each movie. I do have overlays applied already so I guess I would need to reapply overlays when changing poster images? I have also put prioritize_assets = true in the settings. The image file names will be the same naming convention as the movies in my media directory for example:
Media directory > Harry Potter and the Chamber of Secrets (2002) > (movie filename.mkv)
and the image name will be** Harry Potter and the Chamber of Secrets (2002).png**

  Movies:
    metadata_path:
    - file: config/Movies.yml
    overlay_path:
    - remove_overlays: false
    - reapply_overlays: true
    - file: /config/MoviesOverlays.yml
    operations:
      mass_poster_update: plex
      assets_for_all: true```
tawdry yachtBOT
#

Welcome!

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.

wispy narwhal
#

Assuming the indentation is correct, that's how it works.

You don't have to do anything special with overlays; when PMM sees the new image it will update the poster.

sour fern
#

ohhh. before the copy and paste was lookin correct, so the indentation matches how the overlay_path and metadata_path is aligned

wispy narwhal
#

If you format in code blocks that won't happen

errant briarBOT
#

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
sour fern
#

I will have the reapply_overlays set back to false

#

now i have fixed to use code block

#

and to be clear for the operations portion when having
mass_poster_update: plex

#

this won't try to use the plex default poster? and ignore my poster in the asset folder?

wispy narwhal
#

I'm not sure how the two would interact.

#

Simple test to perform.

sour fern
#

You think I should remove the update operation and let PMM refresh the posters on its own?

wispy narwhal
#

It's up to you.

This operation:

mass_poster_update: plex

Will update every poster to the plex default. If you want that to happen, leave it.

This:

      assets_for_all: true

Will assign item posters if they exist in the asset directory.

The question is, what will happen to Harry Potter and the Chamber of Secrets (2002)? Will PMM:

  1. assign the plex default, then overwrite it with the asset?
  2. see that the asset exists, skip the plex default, then assign the asset?
  3. assign the asset, then overwrite it with the plex default?
  4. something else?

I don't know but it would be a simple test to perform.

sour fern
#

gotcha

#

I will remove the update line, since I have assets for all as true. rather not make it set posters to default and then apply new posters, or the opposite. lol

#

thank you for the explanation!

wispy narwhal
#

This:

mass_poster_update: plex

is for sure not something you want turned on all the time. You'd set this to assign new posters then turn it off.

sour fern
#

gotcha

wispy narwhal
#

No reason to keep setting the same poster run after run

sour fern
#

yea. exaclty, wasting resources of applying the same posters on top and then have the overlay again run

sour fern
#

So my posters did not change to the new posters in the asset folders. Not sure if I am missing anything?

#

I did not use mass poster update in the end. I removed that line.

wispy narwhal
#

Probably a naming or settings thing. Can you provide a log of this happening?

sour fern
#

I see there is a warning

Asset Warning: No poster or background found in the assets folder 'None'

#

but I have

asset_directory: config/assets

#

I just noticed in my config. where I have operations in my Movies for library section has assets_for_all: true
and in settings section it has assets_for_all: false

#

now I put both as true

wispy narwhal
#

Are your movies in folders in your media directory?

#

Seems like for at least several movies the asset directory is maybe getting set to None?

sour fern
#

In my media directory, each movie has its own folder

wispy narwhal
#

OK, so not that.

sour fern
#

There are some posters, where I do not have the movie in my media directory, but may get the movie later on, so I keep those few.

wispy narwhal
#

But in several case something's going wrong when trying to find the asset. Not all, though.

sour fern
#

You're right. I'm double checking now, and some movies did update their posters

#

Movies with overlays did not update their posters, only movies without overlays.

#

Maybe I need to reapply overlays for it to work?

wispy narwhal
#

changing the image should update the poster with overlays. reapply would force that, but it should happen automatically.

#

What's an overlaid movie that had an asset but didn't get updated?

sour fern
#

The fast and the furious movies are one example. Lol

#

From that series, Hobbs and Shaw movie I do not have.

#

That one can be ignored.

wispy narwhal
#

Odd:

[2023-05-19 05:01:28,075] [operations.py:98]          [INFO]     | Processing: 1/604 2 Fast 2 Furious                                                                 |
[2023-05-19 05:01:28,078] [plex.py:1238]              [WARNING]  | Asset Warning: 2 Fast 2 Furious (2003) has an Overlay and will be updated when overlays are run    |

but later:

                                                                 | 2 Fast 2 Furious                                                                                   |
[2023-05-19 05:03:56,415] [overlays.py:355]           [INFO]     |   Overlay Update Not Needed                                                                        |

In this case, "reapply overlays" should address this, but it's curious why it didn't happen automatically.

sour fern
#

the original poster has the overlay already applied, so only doing updates if no overlay or it follows another overlay

wispy narwhal
#

right, but "there's a new asset" should trigger reapplying overlays on the new asset poster as far as I know.

stoic kindle
#

If I remember correctly, someone had a similar issue like this yesterday and deleting the cache file allowed the poster to change correctly

wispy narwhal
#

worth a try

sour fern
#

is it the config.cache file?

wispy narwhal
#

that's the one.

sour fern
#

gotcha. I can give it a try and see. I am still looking for some more posters to replace my other original posters lol

sour fern
#

Looks like deleting the cache file worked. I see the posters with the overlay being updated.

wispy narwhal
#

excellent

sour fern
#

It looks like when deleting the cache file it also applies the overlay again. An alternative instead of using reapply overlay command.

wispy narwhal
#

the drawback to deleting the cache file is that it has to refill it, which can take a long time if you have large libraries.

#

This processing needs to be redone if you delete the cache file:

...
[INFO]     |  Cache  |  ^  | plex://movie/5d776d179ab544002151b669          | TMDb ID: 25539   | IMDb ID: tt0086605  | Winners & Sinners |
[INFO]     |                                                                                                    |
[INFO]     | Processed 604 Movies                                                                               |
sour fern
#

Yea. I ran the command to manually start PMM in synology docker terminal, and saw it cache everything again. Now it should be good going forward without the need of caching, unless I need to make more changes again.

wispy narwhal
#

Excellent; just due diligence in pointing out how the actions differ.

#

OK to close this?

sour fern
#

Oops. Yep. Can close this ticket now. Appreciate the help!