✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
#Movie library not creating asset folders?
quiet crestBOT
Welcome @brisk jackal!
Thanks for being a Kometa Sponsor, we greatly appreciate it! Your ticket will now be diverted to <@&1097919568334311495> and <@&938443185347244033>.
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.
quiet crestBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
Not sure if I have got this in the wrong level but it's been bugging me for a few hours and now I need help, haha!
brisk jackal
quiet crestBOT
quiet crestBOT
quiet crestBOT
robust scarab
i screenshot for demonstrative purposes, but all that that's underlined in red is not in the correct place
assets for all is not a setting, you also have it as a global setting
assets for all is an operation
seasonal doesn't work for tv
libraries: # This is called out once within the config.yml file
Movies: # These are names of libraries in your Plex
remove_overlays: true # Set this to true to remove all overlays
template_variables:
collection_mode: hide
operations:
assets_for_all: true
settings:
asset_directory: C:\Windows\System32\Kometa\config\assets
asset_folders: true
asset_depth: 0
create_asset_folders: true
prioritize_assets: true
dimensional_asset_rename: true
download_url_assets: true
show_missing_season_assets: false
show_missing_episode_assets: false
show_asset_not_needed: true
collection_files:
- default: imdb # This is a file within Kometa's defaults folder
- default: seasonal
- default: franchise
# see the wiki for how to use local files, folders, URLs, or files from git
overlay_files:
- default: ribbon # This is a file within Kometa's defaults folder
# see the wiki for how to use local files, folders, URLs, or files from git
TV Shows:
remove_overlays: true # Set this to true to remove all overlays
template_variables:
collection_mode: hide```
Also why are you removing_overlays: true on every run? that's just as bad as having reapply overlays, cause you are removing them and rebuilding them every run. even when you apply assets, Kometa will see the new poster and will apply as needed. you don't need to tell Kometa to remove overlays✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
robust scarab
you need to fix the above so that assets are working properly
stiff coral
remove_overlays is relatively harmless; it just leaves the library without overlays. It won't repeatedly upload new art to Plex the way reapply would, but as long as it's there no overlays will be applied. On subsequent runs it will jsut report "no overlays to remove"
robust scarab
`remove_overlays` is relatively harmless; it just leaves the library without ove...
sorry, i might have misunderstood. i thought remove overlays would remove them, and then because overlays are still being run, they'll be applied again? according to the wiki, it says they'll be removed on every run.
stiff coral
If you look at this log, which has both an overlay defined and remove_overlays: true, it notes that there are no overlays to remove and then moves on without processing the overlay.
robust scarab
@stiff coral But even then, overlays aren't being processed at all. so maybe remove_overlays even prevents overlays from further processing; contrary to what the wiki implies. Thanks
stiff coral
It does. Perhaps that needs to be clarified in the docs.
brisk jackal
assets for all is an operation
I think this is where I’m getting stuck. I think I get the difference between operation & settings, but where exactly are operations being called? In the various called “seasonal.yml” & “franchise.yml”?
Of course, the way I have it set up, it’s calling the defaults but that’s where it’s grabbing the operations?
stiff coral
I think this is where I’m getting stuck. I think I get the difference between op...
You have this:
libraries: # This is called out once within the config.yml file
Movies: # These are names of libraries in your Plex
assets_for_all: true
Kometa is not looking for assets_for_all there. It needs to be in the config under operations::
libraries: # This is called out once within the config.yml file
Movies: # These are names of libraries in your Plex
operations:
assets_for_all: true
Then during the run, when Kometa processes operations [which is one of the standard steps in processing a library [operations, metadata, collections, overlays], Kometa will look for assets for all items.
quiet crestBOT
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
brisk jackal
Got it - that solved a good chunk of my issues. Only setting I couldn't get to work was collection_mode. Is that considered an operation too?
Okay - understanding the Operations piece of thing within libraries makes the Wiki make a lot more sense for me.
My 2 cents, I think it may help avoid some confusion if Operations: was added into the template config. That's where I was getting lost, though it is a very big piece of using Kometa correctly.
robust scarab
Got it - that solved a good chunk of my issues. Only setting I couldn't get to w...
as i showed above, you need to have collection_mode under template variables
brisk jackal
as i showed above, you need to have collection_mode under template variables
Is there any pro or con by doing it this way instead of mass_collection_mode?
robust scarab
like this ```yaml
libraries:
Movies:
remove_overlays: true
template_variables:
collection_mode: hide
operations:
assets_for_all: true
TV Shows:
remove_overlays: true
template_variables:
collection_mode: hide```
quiet crestBOT
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
robust scarab
not that i'm aware of
the one is an operation and the other is a template_variable
stiff coral
Is there any pro or con by doing it this way instead of `mass_collection_mode`?
Themass_collection_mode operation does this: Updates every Collection in your library to the specified Collection Mode.
If you set it as a template_variable, the collection mode will only be applied to collections created by the default collection files. [or collection files of your own that you have specifically written to use template variables]
There is no "pro/con" to one or the other. They do different things, so you should use the one that does what you want done.
robust scarab
Is there any pro or con by doing it this way instead of `mass_collection_mode`?
!afnh
broken yachtBOT
Anything further needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.