content_rating not positioning correctly | Kometa | Page 1

glacial emberBOT May 7, 2024, 2:09 PM

#

📝 If you want to review this again, stash1989:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#

Welcome @somber sparrow!

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.

glacial emberBOT May 7, 2024, 2:09 PM

#

glacial ember You can press the "Close Post" button above or type `/close` at any time to clos...

#

📎 meta.log

rotund robin May 7, 2024, 2:11 PM

#

Config file isn’t needed. It’s already in the log file

glacial emberBOT May 7, 2024, 2:11 PM

#

**Kometa Config.yml YAML Validation** ❌

YAML Validation Results

❌ INVALID YAML detected

❌ INVALID YAML content

while scanning a block scalar
in "<unicode string>", line 252, column 65:
... | settings sub-attribute overlay ...
^
expected a comment or a line break, but found 's'
in "<unicode string>", line 252, column 67:
... | settings sub-attribute overlay_a ...
^

#

📎 parsed_meta.log_config_stash1989.yml

rotund robin May 7, 2024, 2:20 PM

#

@somber sparrow you need to adjust the vertical_offset: 30

#

try that, i think that's where you said you wanted it

cursive pawn May 7, 2024, 2:21 PM

#

default values:

horizontal_offset 15
horizontal_align  left
vertical_offset   270
vertical_align    bottom

somber sparrow May 7, 2024, 2:21 PM

#

yeah bottom-left-most position

#

oh... good to know!

rotund robin May 7, 2024, 2:21 PM

#

keep what you have, but add the vertical_offset, because you have to override the defaults

cursive pawn May 7, 2024, 2:22 PM

#

libraries:
  Test-Movies:
    overlay_files:
      - default: content_rating_us_movie
        template_variables:
          vertical_offset: 42
          horizontal_offset: 600

somber sparrow May 7, 2024, 2:23 PM

#

saved. What are those other errors it is screaming about?

#

with invalid yml?

cursive pawn May 7, 2024, 2:24 PM

#

There are no invalid yaml errors in that log that I can see.

somber sparrow May 7, 2024, 2:25 PM

#

Luma was saying there was on line 252

cursive pawn May 7, 2024, 2:26 PM

#

somber sparrow Luma was saying there was on line 252

It looks to me like you pasted in a config file with some extra junk at the end

#

Those two warnings [four lines] are not part of the config, and that's what luma is reporting.

somber sparrow May 7, 2024, 2:30 PM

#

they are on lines 156 & 157 in the config though... by default? I didn't add them

cursive pawn May 7, 2024, 2:32 PM

#

No, they aren't, not according to this log:

somber sparrow May 7, 2024, 2:32 PM

#

look at the config I included here though..

cursive pawn May 7, 2024, 2:32 PM

#

this one?
#1237405932116377631 message

somber sparrow May 7, 2024, 2:33 PM

#

if it is config.yml yes

cursive pawn May 7, 2024, 2:33 PM

#

Not there either:

glacial emberBOT May 7, 2024, 2:34 PM

#

📎 config.yml

somber sparrow May 7, 2024, 2:34 PM

#

if it isn't in this then Luma is removing it when redacting

cursive pawn May 7, 2024, 2:35 PM

#

Not in that file either.

#

DM me the file if you want

somber sparrow May 7, 2024, 2:35 PM

#

the commands are in there though...

#

showing right on top of your screenshot

cursive pawn May 7, 2024, 2:36 PM

#

I have no idea what you mean:

somber sparrow May 7, 2024, 2:36 PM

#

cursive pawn May 7, 2024, 2:37 PM

#

The "invalid yaml" error I've been looking at:

#

The "overlay artwork" things were added recently and Luma apparently doesn't know about them yet.

somber sparrow May 7, 2024, 2:38 PM

#

oh! that would explain a lot haha

#

sorry for being confused

cursive pawn May 7, 2024, 2:38 PM

#

I don't see any reference to those two fields in the luma output.

somber sparrow May 7, 2024, 2:39 PM

#

so its a case of Luma not being up to date or I'm just crazy

#

or both

cursive pawn May 7, 2024, 2:39 PM

#

Those line numbers [in that specific instance] are referring to the config file, not the log.

somber sparrow May 7, 2024, 2:40 PM

#

[2024-05-07 05:00:28,167] [config.py:195] [DEBUG] | root_folder_path: S:/Movies

#

that's line 252 in the log

cursive pawn May 7, 2024, 2:40 PM

#

?

somber sparrow May 7, 2024, 2:40 PM

#

dammit misread

cursive pawn May 7, 2024, 2:41 PM

#

RIght, and as I said that error is referring to line 252 in the config file

somber sparrow May 7, 2024, 2:41 PM

#

    # everything below is autofilled by the script
    access_token:
    token_type:
    expires_in:
    refresh_token:

line 252 refers to token_type

cursive pawn May 7, 2024, 2:41 PM

#

Which, if you copied extra lines out of the log, would be:

somber sparrow May 7, 2024, 2:42 PM

#

so Luma just doesn't know how to read the overlay_artwork_ stuff yet?

cursive pawn May 7, 2024, 2:43 PM

#

Luma didn't complain about those lines so far as I can see.

somber sparrow May 7, 2024, 2:43 PM

#

so why was it flagged as invalid yml then? That's what I'm confused about

cursive pawn May 7, 2024, 2:43 PM

#

Nothing about those lines were flagged.

#

Look at the Luma error:

somber sparrow May 7, 2024, 2:44 PM

#

so what does this mean then?

cursive pawn May 7, 2024, 2:45 PM

#

The text that Luma is complaining about is:
| settings sub-attribute overlay...

somber sparrow May 7, 2024, 2:45 PM

#

right... but you stated nothing was wrong with it

#

er stated Luma didn't complain about those lines

cursive pawn May 7, 2024, 2:47 PM

#

Which appears in the log here, at the end of the echoed config:

| Config Warning: settings sub-attribute overlay_artwork_filetype not found using jpg as default     |
| settings sub-attribute overlay_artwork_filetype added to config                                    |
| Config Warning: settings sub-attribute overlay_artwork_quality not found using None as default     |
| settings sub-attribute overlay_artwork_quality added to config                                     |

The config files that generated that complaint included those extra lines, which are not part of the config.

somber sparrow May 7, 2024, 2:47 PM

#

so its a non-issue then?

#

odd that it states overlay_artwork_filetype not found when I have it in there as overlay_artwork_filetype: jpg

cursive pawn May 7, 2024, 2:51 PM

#

It wasn't found, and Kometa added it, so it's there now.

Didn't find it so defaulting to using jpg

| Config Warning: settings sub-attribute overlay_artwork_filetype not found using jpg as default     |

Since it wasn't there, Kometa added it to the file

| settings sub-attribute overlay_artwork_filetype added to config                                    |

and same for the other one

| Config Warning: settings sub-attribute overlay_artwork_quality not found using None as default     |
| settings sub-attribute overlay_artwork_quality added to config                                     |

somber sparrow May 7, 2024, 2:52 PM

#

so where in my config do I need to place that as it is on line 156 in the config?

cursive pawn May 7, 2024, 2:52 PM

#

It's in the right place, as Kometa already added it.

somber sparrow May 7, 2024, 2:52 PM

#

then why can't kometa see it?

cursive pawn May 7, 2024, 2:53 PM

#

It couldn't see it at first because it wasn't there until Kometa added it. If you run again you will not see that message since those two things are in the file now that Kometa has added them.

somber sparrow May 7, 2024, 2:53 PM

#

that has been in the config for the last 3 runs now that I am making overlays...

cursive pawn May 7, 2024, 2:54 PM

#

Do you have the config open in an editor while you're doing that?

somber sparrow May 7, 2024, 2:54 PM

#

I save it and then run it. I don't edit while running. but yes

#

is that the flipping issue?

cursive pawn May 7, 2024, 2:55 PM

#

What's probably happening is that Kometa adds it to the file and saves it, then your editor doesn't read it back in, and when you save you stomp the file which contains those two new fields. Rinse, lather, repeat.

somber sparrow May 7, 2024, 2:56 PM

#

ugh so I'll close the file out, run it, then see if it complains again.

#

that seems to have done it.

#

interesting...

cursive pawn May 7, 2024, 2:59 PM

#

There's nothing Kometa can do about that.

#

You could tell Kometa to run with a read-only config, which would prevent it from patching the config like this, but Kometa can't affect what your editor does. Some editors, in this context, would throw up a window saying "Hey this file changed should I reload it?"

rotund robin May 7, 2024, 3:20 PM

#

somber sparrow that seems to have done it.

!afnh

velvet vergeBOT May 7, 2024, 3:20 PM

#

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.

somber sparrow May 7, 2024, 3:27 PM

#

nope seems to be working now. thanks.

#content_rating not positioning correctly