actor collection in tv

[wary horizon]

can anyone help me with some configs for actor collections in tv? i’ve got it working in movies with a simple
tmdb_actor: number
config but it doesn’t work in my tv folder… the default actor collection is way too many actors i don’t want or need. and please go easy on me this my first time with python and yaml files

[ember birch]

Welcome @wary horizon!

It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.

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.

[dense pulsar]

You're going to need to provide any semblance of information if you need help.
Post your config, post your logs, post what you've tried so far, etc.

[short plume]

You don’t need to know python.

And the default, you can limit that to specific individuals of you want

[ember birch]

these are my configs. i have only used kometa for genre, overlays, and actor collections. i got all 3 of those to work in the movie section but the tv actor collection i cant seem to figure out.

[wary horizon]

how would i limit it to the individuals i want? when i used the default: actor config it generated a ton of actors i dont need or want

[cunning briar]

i cant seem to figure out.

Specifically how? What are you expecting and what is happening instead?

[cunning briar]

The default actor collections count all the actors and create as many collections as you ask for from the top of the credit count going down.

libraries:
  Movies:
    collection_files:
      - default: actor
        template_variables:
          data:
            depth: 10 # Look 10 actors deep into the cast on all shows
            limit: 20 # Create collections for the 20 actors with the most credits.

libraries:
  Movies:
    collection_files:
      - default: actor
        template_variables:
          data:
            depth: 10 
            limit: 20 
          include:
           - John Doe
           - Jane Doe
           - Bill Smith

This will generate only those three collections, provided that those three actors are among the top 20. If they aren't, you'll have to increase the depth and limit to whatever they have to be to catch those three actors.

[cunning briar]

This isn't working because tvdb_people is not a valid builder.

This should work fine for tv:

collections:
  Bob Odenkirk:
    tmdb_actor: 290451

As noted:
https://kometa.wiki/en/latest/files/builders/tmdb/#standard-tmdb-builders

[wary horizon]

oops that was just something i was attempting last night. but the
collections:
Bob Odenkirk:
tmdb_actor: 290451
is not working for tv. which is why i’m here

[cunning briar]

is not working for tv.

Again, not working how specifically?

Please provide a log showing what's happening.

[wary horizon]

sorry to even ask this… but how do i get and show you the log?

[cunning briar]

The autoresponse above mentions that.

[quaint forum]

Providing Log Files

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ¯_(ツ)_/¯

Log file too big? USE PASTEBIN or ZIP THE FILE

Thanks for using Kometa

[wary horizon]

got it. ill upload that asap

[cunning briar]

dubzies.yml:

collections:
  Bill Hader:
    tmdb_actor: 19278

config.yml:

libraries:
  TV Shows:
    collection_files:
    - file: config/dubzies.yml

That TMDB ID you are using for Bob Odenkirk is not correct:

He's 59410

290451 is his TVDB ID, which won't work with tmdb_actor:
https://www.thetvdb.com/people/290451-bob-odenkirk

dubzies.yml:

collections:
  Bob Odenkirk:
    tmdb_actor: 59410

[wary horizon]

okay here is my log

[ember birch]

📝 If you want to review this again, dubzies:
: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> 📝

[wary horizon]

sorry for the confusion. i know that bob odenkirk 290451 is not correct. i attempted to use a tvdb_people: 290451 last night in place of tmdb actor config but it didnt work.

[cunning briar]

It's working fine and as expected for me so I'll have a look at the log

Neither of those files are being read because Kometa can't see them:

[INFO]     |     1 | File Error: File does not exist C:\Users\brada\Kometa\config\MovieActorCollection.yml      |
[INFO]     |     1 | File Error: File does not exist C:\Users\brada\Kometa\config\TVActorCollection.yml         |

So nothing defined in either is being processed; not even getting to the ID considerations.

Looks like they may have an extra extension:

[wary horizon]

okay i made new file as .yml only and it worked... briefly... beacuse i decided to switch to one singular "actor collection" .yml file instead of one for tv and one for movie and now it isnt working... this is the error im getting in the log, any ideas? i can post full log if needed

this is the collection config i used

[ember birch]

❌ YAML validation failed! YAML checked and is NOT valid.

Error message:

while scanning a simple key
  in "<unicode string>", line 6, column 3:
      Giancarlo Esposito
      ^
could not find expected ':'
  in "<unicode string>", line 7, column 15:
        tmdb_actor: 4808
                  ^

[cunning briar]

That's a YAML formatting error.

Compare those three actor names, paying particular attention to punctuation.

One of them is not like the others.

[wary horizon]

got it! looks like its working now... so one singular punctuation error, on any actor i add in the file, will result in the entire collection file failing to load?

[cunning briar]

Yes. Any YAML parsing error fails the entire file.

The parser can't ignore portions of the file. It reads the file and it is either all good or not. If it's not good, fail.

[wary horizon]

okay understood

[cunning briar]

If you use an editor which understands YAML syntax, these sorts of errors will be highlighted in the editor.

[barren meadow]

okay i didn't scroll down before posting apparently lol

[wary horizon]

do you have a suggestion for an editor that i should use?

[quaint forum]

Recommended Text Editors

We highly recommend to use a decent editor software to manage Kometa'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 Kometa cannot read. But not only that, they also make it very hard to visually distinguish the formatting, such as indentation.
Kometa 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 Kometa.

This can save a lot of time and headaches.

Preferred:
Visual Studio Code (Windows/Mac/Linux, Opensource & Free) Website
Additionally, install the indent-rainbow by oderwat extension and the YAML by Red Hat extension and leverage our schema.json file by adding this to the top of your config.yml file: # yaml-language-server: $schema=https://raw.githubusercontent.com/Kometa-Team/Kometa/nightly/json-schema/config-schema.json

Other options:
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 here.

Here is an example of how Visual Studio Code works with indent-rainbow plugin and using our Kometa schema (Click on image to get a better view):

Thanks for using Kometa

[cunning briar]

That screenshot of mine is VS Code.

[wary horizon]

okay im working on getting that now. thanks for all your help i learned quite a bit

[cunning briar]

Also note that these errors typically point you near the location of the problem:

while scanning a simple key
  in "YOUR_FILE_PATH", line 6, column 3:
      Giancarlo Esposito
      ^
could not find expected ':'
  in "YOUR_FILE_PATH", line 7, column 15:

And looking at the file:

1 collections:
2   Bob Odenkirk:
3     tmdb_actor: 59410
4   Kevin Hart:
5     tmdb_actor: 55638
6   Giancarlo Esposito
7     tmdb_actor: 4808
    ^           ^
  12345678901234567890

line 6 column 3 is where the issue starts [beginning of "Giancarlo"] and line 7 column 15 is where the parser becomes hopelessly confused [saw another colon without having seen the one it expected earlier], so those two locations bracket the actual location of the issue.

It's most likely between those two locations, so "what's different"...

Doesn't always make it easy, since sometimes those two locations are very far apart, but it's a diagnostic tip that can be useful.

[wary horizon]

that all makes sense i should be able to diagnose my own YAML formatting errors now thanks! i’m also going to use VS Code from now on. i added the two extensions, was a little confused at the “leverage our schema.json” portion but i’ll try and learn more to understand

[quaint forum]

antwanchild used !aenh

@wary horizon, 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.