#Mass Poster Update That Ignores Edition_Contains

1 messages · Page 1 of 1 (latest)

sudden thicket
#

I think I'm close to my solution, but I don't know how to put the pieces together.

I want to run a mass poster update for my movies, but ignore my fanedits (which are all lumped in to the same movie library). Every fanedit has an edition that contains "fan", and I see that there's a way to use that metadata attribute, as well as a way to ignore locked posters, but I don't see a way to ignore posters that match a given attribute.

If it helps, I also have local poster image files stored with the fanedit video files, so if there's a way I can tell Kometa (or Plex) to ignore the mass poster update in favor of local assets, then that would solve it too.

I don't want to ignore locked posters because that would impact every poster with an overlay from what I understand.

Is it possible to make this happen?

neat oarBOT
#

Welcome @sudden thicket!

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.

neat oarBOT
sudden thicket
#

Here's what that part of my config file looks like;

libraries:
Movies:
library_type: movie
operations:
- schedule: daily
delete_unmanaged_collections: false
- schedule: weekly(sunday)
mass_audience_rating_update: mdb_average
mass_critic_rating_update: mdb_metacritic
mass_content_rating_update: mdb
mass_genre_update: imdb
- schedule: monthly(1)
mass_poster_update:
source: tmdb
seasons: false
episodes: false

desert rover
#

There is no way to apply a filter to any of the mass operations aside from the lock status that you've seen.

#

You could probably do this by setting the custom art via assets and then using prioritize assets and assets for all.

sudden thicket
#

When you say using prioritize assets, is that a Kometa function, or do you mean through the Plex library settings?

#

I have the setting to use local assets ticked on through Plex. The last time I ran the mass update, it still overrode my local assets. Maybe I needed to run another native Plex scan to have it switch back over?

#

I'm running the mass update now. I had Plex set to use local assets, but I hadn't checked the box beneath it that says to prefer local metadata. With that checked, it's still updating to new posters via TMDb. Once it's finished, I'll run a Plex scan on the library and see if that reverts them back, and then update here.

desert rover
#

The Kometa asset pipeline, not the Plex setting. Kometa has no idea about the plex setting.

The mass update will always stomp everything [aside from optionally locked things]

#

If you are going to mass update the posters using Kometa, you will also need to tell Kometa to re-set the specific posters you want after the mass update, using the asset pipeline or a metadata file.

sudden thicket
#

Interesting. I'll have to look into the asset pipeline and metadata file options. Without getting too specific, would that mean that I need to move all of those fanedit posters to a central asset folder, and tell Kometa to run an update using any assets present there?

desert rover
#

For the asset directory you would at least copy to an asset directory. You could maybe point Kometa at the media directory as an asset directory, depending on naming and whether Kometa can see the media file system .

For the metadata file, you could refer to them at their present locations assuming Kometa can see that location.

sudden thicket
#

Last question, I think. Regarding an asset directory, I have my fanedit files housed in the same parent folder as the original movie.

└── Avengers Infinity War (2018) {tmdb-299536}
├── Avengers Infinity War (2018) {tmdb-299536} [HDTV-720p][AAC 2.0][x264].mp4
├── Avengers Infinity War (2018) {tmdb-299536} {edition-FanFix}.mp4
├── Avengers Infinity War (2018) {tmdb-299536} {edition-FanFix}.jpg

Would I need to separate the fanedit file(s) into their own folder with the edition tag so that Kometa doesn't update the original movie with the asset directory file for the fanedit? I asset directory documentation looks like it's updating based on the folder name, not the file name.

#

Or, would dropping that .jpg file into an asset directory that Kometa can see do the job since it shares the same file name?

desert rover
#

The asset directory system is based on folder, not filename.

#

You'd need to use a metadata file to target one of several movies in a folder.

#

Or, yes, put them in separate folders.

sudden thicket
#

So something like;

Movies
└── Avengers Infinity War (2018) {tmdb-299536}
├── Avengers Infinity War (2018) {tmdb-299536} [HDTV-720p][AAC 2.0][x264].mp4
└── Avengers Infinity War (2018) {tmdb-299536} {edition-FanFix}
├── Avengers Infinity War (2018) {tmdb-299536} {edition-FanFix}.mp4

And then in a separate location;

Assets
└── Avengers Infinity War (2018) {tmdb-299536} {edition-FanFix}
├── Avengers Infinity War (2018) {tmdb-299536} {edition-FanFix}.jpg
└── Next Movie {edition-FanFix}
├── Next Movie {edition-FanFix}.jpg

desert rover
#

That's incorrect asset naming.

#

If you have these movies:

Movies/
  Avengers Infinity War (2018) {tmdb-299536}/
    whatever.mp4
  Avengers Infinity War (2018) {tmdb-299536} {edition-FanFix}/
    something else.mp4

Then the assets would be:

assets/
  Avengers Infinity War (2018) {tmdb-299536}/
    poster.png
    background.png
  Avengers Infinity War (2018) {tmdb-299536} {edition-FanFix}/
    poster.png
    background.png
sudden thicket
#

Oh! I see that now. Thank you.

#

If I only include assets for the fanedits in the asset folder, it should;
Mass update posters, then correct the few posters via available assets, and leave everything else alone. Is this correct?

desert rover
#

What is "everything else" that is being left alone?

sudden thicket
#

Sorry, I mean the posters for all of the other movies in the same library. I want to run mass update posters operation, and then run another operation to correct the 1% of posters (fanedits) that I didn't want changed.

#

That's where I'd tack on the
assets_for_all: true
operation after the mass poster update

desert rover
#

the posters for all of the other movies in the same library

will not be left alone. They will be reset by the mass update.

libraries:
  Movies:
    operations:
      assets_for_all: true  # look for assets for individual movies,
                            # not just collections
      mass_poster_update:
        source: tmdb        # update every poster for everything in the library
                            # with the default poster from TMDB
settings:
  prioritize_assets: true   # push assets to the top of the image source
                            # priority list
sudden thicket
#

Oh, so I don't need to run another operation to correct anything? If prioritize assets is true, then a mass poster update won't touch the few posters that are assets found in the asset directory?

#

I figured the mass poster update with a specified source would still override anything else.

desert rover
sudden thicket
#

That's excellent. Thank you so much for your help and patience!

desert rover
#

I would create a small test library and run a bunch of experiments to verify it works as you expect, or characterize how it works.

neat oarBOT
#

This post has been marked as Resolved and has now been closed.

You cannot reopen this thread - you must create a new one or ask a member of staff to reopen it in #general-chat.

Thanks for using Kometa.

desert rover
#

@sudden thicket Note that what you are doing here is going to be creating a huge amount of image bloat for no reason.

sudden thicket
#

Well that doesn't sound good. Image bloat beyond local assets that I put in that folder?

desert rover
#

Every time you run the mass poster update, a new poster gets uploaded to Plex.

#

Since you are not ignoring locked posters, then on every run every item gets a new copy of the very same poster.

#

These all get stored in the Plex app data.

sudden thicket
#

I see. I'll look into that, thanks for the warning.

desert rover
#

What is the problem you are trying to solve with these repeated mass poster updates?

sudden thicket
#

I had originally planned to have them run monthly, primarily to update posters for recently added movies/tv shows. Also, I suppose in case TVDb updated artwork for a particular show in the future, though that's probably uncommon.

Similar with overlays. I'm just running the default, and it's primarily for recently added media. But I suppose after award season it might be useful to update movies from that year as well.

desert rover
#

This would probably be a better task for an external script that only updates art for new things that haven't been updated before.

sudden thicket
#

Yes, I’ve found that Plex often picks art that I don’t prefer, and I’ve found that I almost always like the TMDb art.
I’ve installed Image Maid and will mess around with that for the time being. That’ll be a huge help for a problem I didn’t realize I was creating. Thank you for that!
I’ll also look around and see if there are any better ways I can find to do this poster update specifically for new media. Would that be related to Kometa, or completely separate?

desert rover
#

Something not quite right with that script.

desert rover
#

I have most of a script that does the right thing. It appears to fail unpredictably. for example:

Processing: Seven Samurai (1954)
  - Successfully updated art to the TMDB poster.
  - Removed the 'Overlay' label.
  - Added the 'Poster Updated' label.

yet:

image.png
#

Gr. No errors on either side, yet image does not change.

#

Only for some, though.

sudden thicket
#

How odd. Well, after testing Kometa with the asset directory and running image maid, I think that's going to work well for me for now.

desert rover
crisp pivotBOT
#

chazlarson used !aenh

@sudden thicket, 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.

sudden thicket
#

Sorry! I didn’t realize it had reopened when we continued the conversation.