Comskip runs on every recording except one!!

[hazeleye65]

I have a external drive that Records all my tv shows. With 2020 it creates a season folder and inside is a recording thats episode and number. Ie 2020.S48E4.ts and comskip will not even run on it. My other videos are labeled as ie DatelineNBC202550056.ts

I do have "Use episode number when possible" but 2020 is the only show using season and episode numbers.

I would appreciate any help!!

Thank you!!

[mvallevand]

File naming is based on the guide source and comskip will run on every program. We need your zipped logs to answer your questions on what might be happening.

Martin

[hazeleye65]

File naming is based on the guide source  and comskip will run on every program.  We need your zipped logs to answer your questions on what might be happening.

Martin

Here you go!

[mvallevand]

All the files going to your PostProcessing.sh are passed a nice filename when available with title.season.episode name so it will be your script that is renaming them. Of note for 20/20

2025-10-17 23:02:00.457 [DEBUG][273] Starting: bash -c "'/var/opt/nextpvr/scripts/PostProcessing.sh' '/media/sandy/Recordings/2020/Season 48/2020.S48E04.ts' 9.1 36628 21 '20/20'"
2025-10-17 23:02:00.459 [DEBUG][132] > /var/opt/nextpvr/scripts/PostProcessing.sh: line 2: /var/opt/nextpvr/logs/comskip-20/20.log: No such file or directory

It seem that your script is using the last parameter for the comskip log name but it is not guaranteed to be a valid filename

Dateline starts off ok

2025-10-17 23:02:00.243 [DEBUG][241] Starting: bash -c "'/var/opt/nextpvr/scripts/PostProcessing.sh' '/media/sandy/Recordings/Dateline NBC/Season 34/Dateline.NBC.S34E04.A.Perfect.Spring.Morning.ts' 2.1 36626 22 'Dateline NBC'"

and your comskip-Dateline NBC.log clearly shows

Code:

The commandline used was:
    /usr/local/bin/comskip
    --ini=/etc/comskip.ini
    "/media/sandy/Recordings/Dateline NBC/Season 34/Dateline.NBC.S34E04.A.Perfect.Spring.Morning.ts"

so not sure what your script is doing to mangle them after that.

Martin

[hazeleye65]

#!/bin/bash
/usr/bin/nice -n 19 /usr/local/bin/comskip --ini=/etc/comskip.ini "$1" > /var/opt/nextpvr/logs/"comskip-${5}.log"

This is what's in my PostProcessing script. Should there be something else?

[mvallevand]

As I said using parameter $5 is not safe.

Are you sure all you files are named incorrectly? If the metadata for Dateline sometimes is basically empty or doesn't have S/E data , so it will use the YYYYMMDD_HHHHMMSS format. Here is a generic entry you have

Code:

<recording>
      <id>36502</id>
      <name>Dateline NBC</name>
      <group>Dateline NBC</group>
      <desc>Compelling mysteries, powerful documentaries, in-depth investigations.</desc>
      <subtitle></subtitle>
      <start_time>10/10/2025 9:00:00 PM</start_time>
      <start_time_ticks>1760144400</start_time_ticks>
      <duration>02:00</duration>
      <duration_seconds>7200</duration_seconds>
      <status>Pending</status>
      <reason></reason>
      <quality>QUALITY_DEFAULT</quality>
      <size>0</size>
      <firstrun>true</firstrun>
      <significance></significance>
      <genres>
        <genre>News</genre>
      </genres>
      <pre_padding>1</pre_padding>
      <post_padding>2</post_padding>
      <red>False</red>
      <blue>False</blue>
      <green>False</green>
      <yellow>False</yellow>
      <epg_event_oid>19465682</epg_event_oid>
      <epg_end_time_ticks>1760151600</epg_end_time_ticks>
      <channel>WESH</channel>
      <channel_id>7149</channel_id>
      <recurring_parent>63</recurring_parent>
      <recurring>true</recurring>
      <daymask>ANY</daymask>
      <recurring_start>9/25/2022 1:00:00 AM</recurring_start>
      <recurring_start_ticks>637996644000000000</recurring_start_ticks>
      <recurring_end>9/25/2022 2:00:00 AM</recurring_end>
      <recurring_end_ticks>637996680000000000</recurring_end_ticks>
    </recording>

That recorded as Dateline NBC_20251010_21002300.ts I can't explain the odd display you are indicating since the file play I expect it is filesystem viewer you are using.

Martin

[hazeleye65]

As I said using parameter $5 is not safe. 

Are you sure all you files are named incorrectly?  If the metadata for Dateline sometimes is basically empty or doesn't have S/E data , so it will use the YYYYMMDD_HHHHMMSS format. Here is a generic entry you have

Code:

    <recording>
      <id>36502</id>
      <name>Dateline NBC</name>
      <group>Dateline NBC</group>
      <desc>Compelling mysteries, powerful documentaries, in-depth investigations.</desc>
      <subtitle></subtitle>
      <start_time>10/10/2025 9:00:00 PM</start_time>
      <start_time_ticks>1760144400</start_time_ticks>
      <duration>02:00</duration>
      <duration_seconds>7200</duration_seconds>
      <status>Pending</status>
      <reason></reason>
      <quality>QUALITY_DEFAULT</quality>
      <size>0</size>
      <firstrun>true</firstrun>
      <significance></significance>
      <genres>
        <genre>News</genre>
      </genres>
      <pre_padding>1</pre_padding>
      <post_padding>2</post_padding>
      <red>False</red>
      <blue>False</blue>
      <green>False</green>
      <yellow>False</yellow>
      <epg_event_oid>19465682</epg_event_oid>
      <epg_end_time_ticks>1760151600</epg_end_time_ticks>
      <channel>WESH</channel>
      <channel_id>7149</channel_id>
      <recurring_parent>63</recurring_parent>
      <recurring>true</recurring>
      <daymask>ANY</daymask>
      <recurring_start>9/25/2022 1:00:00 AM</recurring_start>
      <recurring_start_ticks>637996644000000000</recurring_start_ticks>
      <recurring_end>9/25/2022 2:00:00 AM</recurring_end>
      <recurring_end_ticks>637996680000000000</recurring_end_ticks>
    </recording>

That recorded as Dateline NBC_20251010_21002300.ts  I can't explain the odd display you are indicating since the file play I expect it is filesystem viewer you are using.

Martin

You just told me that file naming is determined by guide data. Dateline is not the file I'm having problems with, it's 2020 that comskip will not run on!
Thanks!

[hazeleye65]

As I said using parameter $5 is not safe. 

Are you sure all you files are named incorrectly?  If the metadata for Dateline sometimes is basically empty or doesn't have S/E data , so it will use the YYYYMMDD_HHHHMMSS format. Here is a generic entry you have

Code:

    <recording>
      <id>36502</id>
      <name>Dateline NBC</name>
      <group>Dateline NBC</group>
      <desc>Compelling mysteries, powerful documentaries, in-depth investigations.</desc>
      <subtitle></subtitle>
      <start_time>10/10/2025 9:00:00 PM</start_time>
      <start_time_ticks>1760144400</start_time_ticks>
      <duration>02:00</duration>
      <duration_seconds>7200</duration_seconds>
      <status>Pending</status>
      <reason></reason>
      <quality>QUALITY_DEFAULT</quality>
      <size>0</size>
      <firstrun>true</firstrun>
      <significance></significance>
      <genres>
        <genre>News</genre>
      </genres>
      <pre_padding>1</pre_padding>
      <post_padding>2</post_padding>
      <red>False</red>
      <blue>False</blue>
      <green>False</green>
      <yellow>False</yellow>
      <epg_event_oid>19465682</epg_event_oid>
      <epg_end_time_ticks>1760151600</epg_end_time_ticks>
      <channel>WESH</channel>
      <channel_id>7149</channel_id>
      <recurring_parent>63</recurring_parent>
      <recurring>true</recurring>
      <daymask>ANY</daymask>
      <recurring_start>9/25/2022 1:00:00 AM</recurring_start>
      <recurring_start_ticks>637996644000000000</recurring_start_ticks>
      <recurring_end>9/25/2022 2:00:00 AM</recurring_end>
      <recurring_end_ticks>637996680000000000</recurring_end_ticks>
    </recording>

That recorded as Dateline NBC_20251010_21002300.ts  I can't explain the odd display you are indicating since the file play I expect it is filesystem viewer you are using.

Martin

Disreguard the question about parameter 5. 
Thanks!

[mvallevand]

This is my last post since I try and avoid talking about scripts when NextPVR is working find. It is confusing because you noted two problems neither of which are NextPVR problems.

What do you thing your comskip-${5}.log" is doing in your script and what do you think this log entry I showed you means?

2025-10-17 23:02:00.459 [DEBUG][132] > /var/opt/nextpvr/scripts/PostProcessing.sh: line 2: /var/opt/nextpvr/logs/comskip-20/20.log: No such file or directory

Hint If you don't see it it is trying to create a file called 20.log in a folder called comskip-20 because of the embedded slash in a parameter that should not be used to create files.

Martin

[hazeleye65]

This is my last post since I try and avoid talking about scripts when NextPVR is working find.    It is confusing because you noted two problems neither of which are NextPVR problems.

What do you thing your comskip-${5}.log" is doing in your script and what do you think this log entry I showed you means?

2025-10-17 23:02:00.459 [DEBUG][132] > /var/opt/nextpvr/scripts/PostProcessing.sh: line 2: /var/opt/nextpvr/logs/comskip-20/20.log: No such file or directory 

Hint If you don't see it it is trying to create a file called 20.log in a folder called comskip-20 because of the embedded slash in a parameter that should not be used to create files.

Martin

Isn't PostProcessing part of nextpvr?