๐ If you want to review this again, voltron4lyfe:
: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> ๐
#Generating commentary collection
1 messages ยท Page 1 of 1 (latest)
Welcome @mint adder!
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.
I'm struggling to create a collection containing movies that have commentaries. In the logs, I can see that the collection file has loaded but I don't see any other output and the collection doesn't appear in Plex.
Here is the sample "Get Info" from a movie in my library that has a commentary track:
Codec AC3
Channels 2
Bitrate 224 kbps
Language English
Language Tag en
Audio Channel Layout stereo
Comment true
Original true
Sampling Rate 48000 Hz
Title Commentary by Producer Jon Davison, Directors Jim Abrahams, Jerry Zucker, & David Zucker
Display Title English (AC3 Stereo)
Extended Display Title Commentary by Producer Jon Davison, Directors Jim Abrahams, Jerry Zucker, & David Zucker (English AC3 Stereo)```
๐ If you want to review this again, voltron4lyfe:
: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> ๐
**Rec 01** - โ ๏ธ **[WARNING]**
โ ๏ธ [WARNING]
Warning messages found in your attached log.
This is a Kometa warning and usually does not require any immediate action. Most [WARNING] lines can be ignored.
For more information on handling these, [https://kometa.wiki/en/latest/kometa/logs/?h=[warning]#warning]
16 line(s) with [WARNING] messages. Line number(s): 309, 347-355, 825, 922, 1422, 1476, 1530, 1584
Page 7/7
not the error, but you do need to fix this: yaml - mm: oscars
for your season this: yaml - default: seasonal template_variables: url_poster: https://raw.githubusercontent.com/voltron4lyfe/pmm-custom-repo-posters/master/seasonal/<<key>>.jpg collection_mode: hide use_independence: true use_halloween: true use_thanksgiving: true use_valentine: true use_memorial: false use_latinx: false use_lgbtq: false use_disabilities: false use_black_history: false use_women: false use_appi: false use_father: false use_mother: false use_patrick: false use_labor: false would be shorter and easier to do this: yaml - default: seasonal template_variables: url_poster: https://raw.githubusercontent.com/voltron4lyfe/pmm-custom-repo-posters/master/seasonal/<<key>>.jpg collection_mode: hide use_all: false #<--- add this use_independence: true use_halloween: true use_thanksgiving: true use_valentine: true
operations:
delete_collections:
less: 2``` is in the wrong place
@mint adder absolutely nothing happens in your Movies library as it's 13:05, and you told Kometa to schedule Movies library only during the 05 Hour

you can tell it to ignore schedules, but that will ignore all schedules. you could run collections only and ignore schedules
Run now will still honor any schedule, EXCEPT when told to ignore schedules
Ok, trying that. This documentation is confusing though:
"Some Commands or Variables can be combined in a single run, this is mainly beneficial when you want to run a specific command and have it run immediately rather than waiting until the next scheduled run.
For example, if I want to run Collections Only to only run Collection Files, and Run Immediately to skip waiting until my next scheduled run, I can use both commands at the same time:"
docker run -it -v "X:\Media\Kometa\config:/config:rw" kometateam/kometa --collections-only --run
Definitly is taking longer ๐
and will still honor schedules, which is why the ignore schedules runtime command exists
you can used both, but then you also need to include --ignore-schedules
antwanchild used !afnh
@mint adder, 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.
you're welcome
There are two levels of scheduling.
Scheduling when Kometa processes the config: this is the schedule that --run bypasses.
Internal schedules that are set in the config: these schedules have nothing to do with when Kometa processes the config, and these are the schedules bypassed with ignore schedules
and with that, i also think that your overlay runs may not process at the various times. You are telling Kometa to only process that library at the 5 oclock hour, so i think every other time that you want to process overlays, will not happen except the 5 oclock hour when the Movies library is running
This post has been marked as Resolved and has now been closed.
You cannot reopen this thread - you must create a new one or ask a member of staff to reopen it in #general-chat.
Thanks for using Kometa.