#Overlays mapping values are not allowed here help!

1 messages · Page 1 of 1 (latest)

fathom hatch
#

Hey Guys, I am having an error with my Overlays section of my PMM - error is as follows

| modules.util.Failed: YAML Error: mapping values are not allowed here                               |                                       
|         in "//config/config.yml", line 4, column 24                                                |                                                     
|                                                                                                    |                                                     
| YAML Error: mapping values are not allowed here                                                    |                                                     
|         in "//config/config.yml", line 4, column 24

Config -

libraries:
  Movies:
    overlay_path: config/Overlays.yml
      - remove_overlays: false
      - reapply_overlay: true
      - pmm: resolution                                                    # 1
      - pmm: audio_codec                                                   # 2
      - pmm: special_release
#

I understand exactly where it is, I just don't understand why it's not allowed

#

Line 4 - Col 23 is - remove_overlays: false and it's right inbetween the s on overlays and :

fathom hatch
#

this will make it a lot easier to understand - apologies it wasn't there earlier

weak verge
#

well it seems that you are on an older version of PMM. Can you uodate it?

lavish swallowBOT
#
Updating PMM

NOTE: This is addressing UPDATING your current setup, not changing from, for instance, latest to nightly.

The update method depends on how you installed it.

I'm running locally and got the code by downloading the zip file:
Download a new zip file, uncompress it, and move your config dir into that new directory. Reinstall requirements.

This is the "fussiest" method of update.

I'm running locally and retrieved the code via git:

cd DIRECTORY_WHERE_YOU_PUT_PMM
git checkout BRANCH_NAME
git stash
git stash clear
git pull

For BRANCH_NAME, substitute master, develop, or nightly

You may need to reinstall requirements if switching branch or updating to a new major version:
python -m pip install -r requirements.txt

Those stash commands are going to discard any changes you may have made to PMM's own files. If that's a concern, you are probably familiar enough with git to know what you need to do instead.

I'm using docker locally:

docker pull meisnate12/plex-meta-manager:TAG_HERE

replace TAG_HERE with latest, develop, or nightly

Then recreate your container via whatever means you used to create it [docker run, docker-compose, etc.].

I'm using docker on a NAS or some other remote context:

Update the image using whatever means the NAS provides.
Depending on the system, this might be a simple rebuild of the container, or you may need to manually pull the new image first.

fathom hatch
#

yes i can definitely update it, can i simply just drag over my previous configured files or will i need to start over?

#

Updated to v1.18.0 and still receiving the same error unfortunately

lavish swallowBOT
#
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
weak verge
#

So some will be transferable and others won’t

#

As of 1.18, we only need your meta.log

fathom hatch
#

okay no worries, that previous post has the meta log attatched

weak verge
#

And where did you get this config file… the overlay path line looks incorrect

lavish swallowBOT
#
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.

fathom hatch
weak verge
#

Hmmm… this is what I see in the wiki…

#

And you seem to have a path in the same line as the overlay_path: line

#

Maybe because I am on my phone I don’t see that…

fathom hatch
#

wow that's very odd, i see reapply_overlay: true instead of false

#

where on earth am i looking ahaha

weak verge
#

Like I said… and you don’t have the new naming as shown on that example

#

So maybe you copied your config from another location but this seems to be the source of your issues… an invalid config.yml file

fathom hatch
#

yep, i know my config works perfect as soon as i take out anything that has to do with overlays

weak verge
#

So in that case, ensure that you copy from the wiki?

#

At least the overlay section

fathom hatch
#

ahaha yes i can do it again

#

that image that you posted, is that from the bottom config?

#

cause the one i got was in the middle of the page

weak verge
#

And then review the mee6 message for the changes to 1.18 that might affect your other items

#

Yes mine from bottom

#

Let me look again

fathom hatch
#

ahhhh

#

i copied mine from where it says Note: This uses fonts not packaged with PMM. See bullmoose20’s Configs

#

right below "example poster overlays"

weak verge
#

Right… so this is what you have in your log file:

#

Show me where on that page does it actually have a line that has what I hilited above

#

Because we need to fix it if you do find it or others will run into the same problem as you.

fathom hatch
#

Oh, that bit i did add in myself, sorry for that confusion...

#

i added that because it was throwing an error when it was empty

weak verge
#

Same thing for TV Shows one

fathom hatch
#

yep, both added by me

weak verge
#

Let’s remove that line, rerun… and post the logs

fathom hatch
#

the config/Overlays.yml was added by me

weak verge
#

Both addendums

fathom hatch
#

okay sure thing :)

weak verge
#

Secondly, as you may or may not be aware, yml files are very sensitive to spacing and indentation.

fathom hatch
#

that's awesome to know, thanks for the heads up - the test is currently running

weak verge
#

So we recommend some editors (free) to help ensure that you don’t run into issues around that.

lavish swallowBOT
#
Recommended Text Editors

We highly recommend to use a decent editor software to manage PMM´s .yml files.

Standard text editors (such as Notepad and TextEdit) often save text in a rich-text format which can result in text formatted in a way that PMM cannot read. But not only that, they also make it very hard to visually distinguish the formatting, such as indentation.
PMM requires indents to always be multiples of 2 spaces, and not TAB stops. If you have one space too much, or too few, it is very hard to notice that with a editor like Notepad.
An editor that is more focused on editing code instead of text will automatically detect the .YML fileformat and adjust things to make it easier to work. They can also try to detect possible errors even before you actually run the .yml in PMM.

This can save a lot of time and headaches.

Visual Studio Code (Windows/Mac/Linux, Opensource & Free)
Website

Notepad++ (Windows only, Opensource & Free)
Website

Sublime Text (Windows/Mac/Linux, Paid)
Website

For further details and a short list of highly recommended extensions, you can also take a look at our Reddit post.

fathom hatch
#

I am currently on Notepad++ :)

weak verge
#

Vscode with the indent-rainbow plugin are great

#

N++ is great, but it does not have the indent-rainbow plugin.

#

In any case, it’s more to ensure that you were aware. That’s all.

#

How is that run going?

fathom hatch
#

it's looking better now

#

apologies for the image, i tried to capture it as it was running

weak verge
#

Ok.. so it looks like it was a copy paste error then?

#

And maybe a version upgrade that was needed

fathom hatch
#

i think you might be right, i only deleted what you suggested and ran it again - nothing else was changed

weak verge
#

Because thé pmm: stuff only got implemented in 1.18

fathom hatch
#

ohhhhhh

weak verge
#

So it was a combo of things

#

Probably complained it was empty before 1.18 upgrade because it did not find any overlays using the PMM:

fathom hatch
#

i see now, it was just still stuck behind that first error that i created myself by having -pmm in a 1.17 version

weak verge
#

yes

fathom hatch
#

and having the custom config thing that i typed too

weak verge
#

And then the second error was because of the addendums

#

All good

#

Anything else?

fathom hatch
#

i appreciate your help, since this is the first time it's actually running, from looking at my config when will the posters start to update with the overlays?

weak verge
#

You should probably be seeing some of the overlays being applied to plex movies by now… 😉

fathom hatch
#

read my question even before it was there ahahahaha

weak verge
#

I would say check now…

#

How many movies do you have?

#

Ballpark?

fathom hatch
#

1.7k :)

weak verge
#

Might still be processing

#

I would need to see the logs to tell you when

fathom hatch
#

currently i can see it's re-building the collections again

weak verge
#

Argh

#

Can you kill it?

fathom hatch
#

yes

weak verge
#

I will show you a truck about runtimes

fathom hatch
#

yes please!

weak verge
#

How do you run PMM?

#

Docker?

#

Unraid?

fathom hatch
#

yep

#

docker under synology nas

weak verge
#

Native Python?

fathom hatch
#

yep

weak verge
#

Ok… can you terminal in to the container to run commands?

fathom hatch
#

sure can :)

weak verge
#

Get to the command prompt there and run the following

#

python plex_meta_manager.py -r -ov -rl “Movies”

#

This says run overlays only for the Movies library and then stop

fathom hatch
#

running now!

weak verge
#

Those special runtime variables are all explained in above link

fathom hatch
#

is it a problem that it says redacted config each time a run starts?

weak verge
#

Not that I know of.

fathom hatch
#

right after it reads config.yml it says redacted

#

doesn't bother me then

weak verge
#

We don’t want to se your pins and api keys

#

So that gets redacted

fathom hatch
#

oh awesome

weak verge
#

Otherwise we would ask the following g

lavish swallowBOT
#
Providing a redacted config.yml file

You have been asked to provide your config file, which will allow us to support you further.

Please DO NOT share your config.yml file as is without redacting it. It contains information that you do not want the public to have, nor do we need it to troubleshoot your scenario in MOST cases.

We will use a regex parser to redact the file for you.

:one: Goto https://regex101.com/r/DMo1DQ/latest
:two: Copy the contents of your config.yml to the TEST STRING box in that page
:three: The results will be immediate and found in the SUBSTITUTION box below
:four: From the SUBSTITUTION box, select all, then copy and paste the redacted text into the channel where you want to share your config. (You will see (redacted) where confidential information was replaced)

Consider using Discord code blocks when sharing small parts of your config file. Check out !code for more info on code blocks

weak verge
#

Pre-1.18 we used the above a lot

#

Now it’s all built into the logs

fathom hatch
#

yep gotcha, lots of machine and account information

weak verge
#

Exactly

fathom hatch
#

okay overlays are thinking no

#

now

weak verge
#

So while the current command I gave you will skip operations and skip collections, it willl still need to look at the overlays you want to apply and decide what posters need the overlays… and once that completes it will apply

#

Hahah… !118

lavish swallowBOT
#
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
weak verge
#

See what it says in this message?? Your gonna want to remove the special_release… it was merged into resolution.

#

But that error should not crash the run

fathom hatch
#

oh man sorry

#

i have only done this once before

weak verge
#

It’s fine

#

You can remove that reference in your config.yml file

fathom hatch
#

removing it now

#

cause i had another error

#

but i think it was radarr, so i will check in a moment

#

oh wait i know why, don't mind me

#

okay gonna run it one more time while everything is working, give me a moment

weak verge
#

Radarr message should not affect overlays

#

Meaning that radarr should not come up in your meta.log

#

Because we are applying overlays

fathom hatch
#

will radarr break that?

#

I have all Arrs connected

weak verge
#

I edited what I wrote sorry

fathom hatch
#

oh, no problem :)

#

now i need to try and find the posters that are being edited in my library

#

to confirm that it's working ahaha

#

ah now i am having a plex error... why...

weak verge
#

Open your library… it’s the first poster first

fathom hatch
#

one moment

weak verge
#

A plex error will affect PMM of course

fathom hatch
#

definitely

weak verge
#

I am off to dinner but will check in later

fathom hatch
#

thanks for your help!

#

i'll post meta if i am stuck ahaha

weak verge
#

You will see the overlays applying messages in the logs and then you can look at the plex library

#

It’s fun to watch them being applied

#

Lol

fathom hatch
#

i could understand, i enjoy watching the collections being built from the logs ahahaha

#

i'm not sure what's up with the command that you gave me, the one to skip collections and move straight onto overlays, but that for some reason does not connect to my movies library, but when i run python plex_meta_manager.py -r it all runs fine

#

but then i need to proceed through the large collection building ahaha

weak verge
#

I would need the logs for the other command to tell you what is happening. Likely there is an error in the overlays section of your config.

#

It’s always the same process… run the command, if things don’t work, review the logs…if you don’t understand the logs, upload them here and get assistance. 🙂

#

Because likely, by moving to the -r only, you will wait until overlays and then it will fail again.

#

It’s important that we understand what the error is rather than saying it’s not connecting… what’s the actual error? 😉

#

I would also recommend setting reapply_overlays: false

#

Having it set to true is used in specific circumstances that the majority of people do not need to have. It does not hurt, but it will delay your runs as ALL overlays will be reapplied regardless of the need to update them or not.

fathom hatch
#

The overlays are working well, I appreciate your help - I don't mind not using that command to run for the overlays now as they will go back to a weekly schedule, oh yes I'll definitely change that value once the run is completed

#

Thanks so much, my posters look great now