#Help with Cleaning up config file after update to 1.18.0

1 messages · Page 1 of 1 (latest)

sly mica
#

I recently in a support chat and updated to 1.18.0. I now need help cleaning up my config.yml file and the movies.yml file.

sleek shuttleBOT
#

Please complete #938455615741775902 and someone from the community or one of our <@&938443185347244033> members will respond when they're available.

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

pulsar tendon
#

okay? and now?

#

dont you think that maybe sharing your config and movies.yml with us would be a good start? and a meta.log of a complete so we can see what errors you are getting?

cold gateBOT
#
Upgrading PMM Defaults to 1.18.0

As part of 1.18.0, a few major changes have been made to the PMM Default files that will impact how you use them within your config.yml

Merged into ribbon: oscars, imdb_top_250, rt_cert_fresh, mc_must_see, commonsense_selection
Merged into resolution: resolution_standards & special_release
Renamed to language_count: audio_language

To transition from pre-1.18.0 versions to 1.18.0, you must do the following, or you will see errors in your log and previously working overlays will no longer be applied.

Upgrading to the ribbon PMM Default file
1) Remove any reference to these files in your config.yml:

- git: PMM/overlays/oscars
- git: PMM/overlays/imdb_top_250
- git: PMM/overlays/rt_cert_fresh
- git: PMM/overlays/mc_must_see
- git: PMM/overlays/commonsense_selection

2) Add a reference to this file (only once!)

- pmm: ribbon

As only one ribbon image can be placed at a time, the priority list is currently:
oscars (weight 40)
imdb (weight 30)
rotten (Weight 20)
metacritic (Weight 10)
common (Weight 5)

To alter these positions,you can use template variables, like so:

- pmm: ribbon
  template_variables:
    weight_common: 100 #Makes it first on the list
    weight_imdb: 90 #Makes it second on the list

Upgrading to the resolution PMM Default file
1) Remove any reference to these files in your config.yml:

- git: PMM/overlays/special_release
- git: PMM/resolution_standards

Upgrading from audio_language to the language_count PMM Default file
1) Remove any reference to these files in your config.yml:

- git: PMM/overlays/audio_language

2) Add a reference to this file

- pmm: language_count
pulsar tendon
#

these are the general hints for updating to 1.18

#

go through them, adjust your config, let pmm run

#

if you have still trouble, then share the meta.log file with us and we can take a look

sly mica
#

Yep, this all started because I was trying to add writers to my movies.yml file and its not working. Plus, I wanted to change sorting so it would sort the actors from config.yml with the people I have in movies.yml

pulsar tendon
#
- git: PMM/movie/seasonal  

and all those in your config, as the bot message above explains, you need to change them to keep them working in 1.18.0

cold gateBOT
#
Upgrading PMM Defaults to 1.18.0

As part of 1.18.0, a few major changes have been made to the PMM Default files that will impact how you use them within your config.yml

Merged into ribbon: oscars, imdb_top_250, rt_cert_fresh, mc_must_see, commonsense_selection
Merged into resolution: resolution_standards & special_release
Renamed to language_count: audio_language

To transition from pre-1.18.0 versions to 1.18.0, you must do the following, or you will see errors in your log and previously working overlays will no longer be applied.

Upgrading to the ribbon PMM Default file
1) Remove any reference to these files in your config.yml:

- git: PMM/overlays/oscars
- git: PMM/overlays/imdb_top_250
- git: PMM/overlays/rt_cert_fresh
- git: PMM/overlays/mc_must_see
- git: PMM/overlays/commonsense_selection

2) Add a reference to this file (only once!)

- pmm: ribbon

As only one ribbon image can be placed at a time, the priority list is currently:
oscars (weight 40)
imdb (weight 30)
rotten (Weight 20)
metacritic (Weight 10)
common (Weight 5)

To alter these positions,you can use template variables, like so:

- pmm: ribbon
  template_variables:
    weight_common: 100 #Makes it first on the list
    weight_imdb: 90 #Makes it second on the list

Upgrading to the resolution PMM Default file
1) Remove any reference to these files in your config.yml:

- git: PMM/overlays/special_release
- git: PMM/resolution_standards

Upgrading from audio_language to the language_count PMM Default file
1) Remove any reference to these files in your config.yml:

- git: PMM/overlays/audio_language

2) Add a reference to this file

- pmm: language_count
analog citrus
pulsar tendon
#

go through them and update the config, then make a pmm run and see what the meta.log says

sly mica
#

I added that !17_ like someone told me to do but it doesn't work

analog citrus
#

because of how you added it, you have one template and you set that one template with the !17_

#

so everything you use with that template applies that sort

sly mica
#

I have a question about removing the overlay references and adding the - pmm: ribbon. I had a hard time getting the audience rating on my overlays and I don't want to lose that with the new way. I think I had to add this to it so it would show the audience rating. yaml operations: mass_audience_rating_update: mdb_tomatoesaudience

sly mica
pulsar tendon
#

im out

sly mica
#

Lol I don't understand the sorting and that's why I'm here for help

analog citrus
#

put quotes around your sort title

sly mica
#

like this? yaml "sort_title": !17_<<collection_name>>

analog citrus
#

no around your sort title

#

around !17_<<collection....

sly mica
#

Not sure what my sort title means. I really have no clue what !17_ means. Like this yaml sort_title: "!17_<<collection_name>>"

analog citrus
#

so if your collection is Denzel Washinton, then the sort_title will be !17_Denzel Washington

#

this keeps them all grouped together, rather than having actors mixed with directors, or genres, etc

sly mica
#

That makes sense. I guess we chose "17" just because that's the number following the actor sorting in config.yml? Also, why does it need a "!"? Is that just the syntax?

analog citrus
#

it has to do with asci sorting

sly mica
#

Yea, I don't know anything about asci sorting. So is my syntax above correct for where to put the quotes or do the quotes only go around !17_ like yaml sort_title: "!17_"<<collection_name>>

analog citrus
#

it goes like i showed you, and what you had above with quotes around the sort title

#

and what editor are you using? cause that would also help show you errors

sly mica
#

I downloaded Visual Studio Code like you or someone else suggested. I did see that line in red when I had no quotes.

#

The program shows that line is okay if I have the quotes around !17_ or around the entire thing.

analog citrus
#

ok, like i said they need to go around the whole thing

sly mica
#

okay, thanks. So these lines should be good now? yaml templates: Actor: actor: tmdb tmdb_person: <<person>> tmdb_actor_details: <<person>> sort_title: "!17_<<collection_name>>" sync_mode: sync collection_order: release collection_mode: hide Director: director: tmdb tmdb_person: <<person>> tmdb_actor_details: <<person>> sort_title: "!18_<<collection_name>>" sync_mode: sync collection_order: release collection_mode: hide Producer: director: tmdb tmdb_person: <<person>> tmdb_actor_details: <<person>> sort_title: "!19_<<collection_name>>" sync_mode: sync collection_order: release collection_mode: hide

coral prism
#

There is nothing magic about the !. Pies sorts things in alphabetical order based on that sort title field. That's what ASCII sorting is. The ! pushes it to the top of the list since it sorts alphabetically before most characters.

analog citrus
#

@sly mica did you try this?

iron kraken
#

That person that explained all of this would be me. 😉

pulsar tendon
#

and now you can do it all again!

iron kraken
#

We had a really nice long thread where I prescribed steps to take and where we reviewed all of this.

iron kraken
#

Did you open this thread for reason as opposed to the other thread? Maybe it got closed but we should have continued there IMO.

pulsar tendon
#

that one maybe?

iron kraken
#

Yup thanks Zap

#

I guess it was closed after two days of not hearing anything…

#

But it still has all that great reading material for squidbillies

analog citrus
#

Bull did a great job of explaining this already

iron kraken
#

Yeah I think it was because that thread got closed to inactivity

#

However, we could have reopened it to continue the discussion… in any case, hopefully, squidbillies can get things sorted out. (Pun intended)

cold gateBOT
#
PMM Defaults

Plex Meta Manager provides a set of pre-made Metadata and Overlay files, allowing you to get the most commonly-used collections and overlays without having to manually set them up yourself.

You can learn more about them here
basically:

libraries:
  Movies:
    metadata_path:
    - pmm: actor
    - pmm: genre
    overlay_path:
    - remove_overlays: false
    - pmm: ribbon
    - pmm: ratings

and so on.

They offer a degree of customization. That customization mechanism is described at the link.

If you ALSO want to use your local My-Movies.yml, you can add it to the config like this:

libraries:
  Movies:
    metadata_path:
    - file: config/My-Movies.yml
    - pmm: actor
    - pmm: genre
    overlay_path:
    - remove_overlays: false
    - pmm: ribbon
    - pmm: ratings

It should be noted that users running the on nightly branch of Plex Meta Manager will receive all updates to the PMM Defaults as soon as they are published via GitHub, which may at times involve bugs or implementations that need to be further addressed. Users of the develop and master branches will only receive updated Defaults files when an update to Plex Meta Manager is released - this helps to keep these branches stable and prevent bugs from reaching the wider user-base.

sleek shuttleBOT
#

This post has been marked as Resolved and will be closed in one hour.

If you require further assistance on this issue, you can send another message in this post to re-open it.

If you require further support that is unrelated to this post, please start a new post and do not re-open this one.

Thanks for using Plex Meta Manager.

sly mica
#

It won't let me open that other ticket is why I started this one. I checked this morning and the sorting did work how I wanted. It also added the two writers but sorted them oddly. How do I sort these two lines with the other !17_ items? I guess these are writers and should be !20_ but I don't know where to add the sort_title: for these two items. yaml George Lucas: tmdb_writer_details: 1 Stephen King: tmdb_writer_details: 3027

pulsar tendon
#
  George Lucas:
    tmdb_writer_details: 1
    sort_title: "!20_George Lucas"
  Stephen King:
    tmdb_writer_details: 3027
    sort_title: "!20_Stephen King"
#

or you make a template for writers too like you did for directors and actors and producers

#

It won't let me open that other ticket is why I started this one.
it was closed because you didnt reply anymore for ~2 days.
and it can be reopened for you if you had let anyone know. i have now reopened the old thread for you and its up to @iron kraken and you in which thread you want to continue this journey down the rabbit hole...

iron kraken
#

Rabbits everywhere

iron kraken
pulsar tendon
#

yeah i just edited it now 🙂

iron kraken
#

Lol

#

Correct

pulsar tendon
#

but regardless, !17 or !20 should be simple enough to figure out for himself

iron kraken
#

Agreed

iron kraken
#

Is that calculus?

sly mica
sly mica
pulsar tendon
#

thats a common theme "someone said to use this" and i am quite sure that it was also explained why to use this but apparently nothing was learned from that