Server Version#: 1.19.1.2589
Player Version#: N/A
Tuner Make/Model: HDHR Extend
Guide/Lineup name:
Using XMLTV?: No
Channel number/Name: Any channel
Yesterday I upgraded to the beta of 1.19.1.2589 and then did a couple test recordings. I found that the commercial skipper wasn’t working. It would run for about 15 seconds, produce a 0 byte “-comskipped.ts” file, and then copy three files to the show destination directory: 1. the original full .ts file 2. the 0 byte -comskipped.ts file" 3. the commercial_markers.mkr file.
I downgraded to 1.18.8.2468 so I could record some shows last night, and the commercial skipper ran normally. I do have a custom comskip.ini.
Today I upgraded again to 1.19.1.2589, rebooted this time, and then again ran some test records. The commercial skipper is now working, but I am still getting the commercial_markers.mkr file in the show’s directory. I’m now running a test to see if recording multiple episodes of the same show result in an error since the commercial_markers.mkr file name isn’t unique to the episode number, and will update this post with findings.
I can DM logs of both scenarios to a Plex bod once I know who to send to.
I have the same issue in that I am seeing a commercial_markers.mkr file in the recording destination directory. I am using the same server version and I have 2x HDHRs.
Thank you @sa2000! I’ve DMed the logs, noted the timestamp for where the commercial skipper failed, and also the timestamp for where it worked but put the .mkr file in the destination directory, and my custom comskip.ini file to you.
For public knowledge, I didn’t have to do anything to keep my custom comskip.ini. The Linux installer doesn’t overwrite a custom comskip.ini that is put at /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/DVR/comskip.ini.
Also, I was able to successfully record two shows in the same series. For the first episode it put a commercial_markers.mkr in the show’s final directory, and the second episode put a commercial_markers (copy 1).mkr in the same directory.
Thanks - will look into them and refer to the development team
OK - but if we release an updated ini file within the binaries files area - any custom ini file in the Application Support area would need to be recreated basing the custom ini file on the updated base file
Thank you! Do you know how to tell if a custom comskip.ini needs to be recreated? The installer keeps a custom comskip.ini during upgrades, and I searched the Plex Media Server release notes and can’t find any instance ever where guidance has been provided that a custom comskip.ini needs to be recreated.
I’ll try recreating my comskip.ini based on the beta’s default and report back if there is any difference.
I removed my custom comskip.ini, restarted Plex Media Server, and tested a recording. No change: I’m still getting the commercial_markers.mkr file in the show’s final destination directory. I also verified in the logs that the commercial skipper command --ini parameter specified /usr/lib/plexmediaserver/Resources/comskip.ini (the default, not an override.)
I have upgraded to 1.19.1.2621 and have completed two recordings, both with successful commercial skips and no commercial_markers.mkr file in the show’s directory. Thank you!
I’ve marked this as resolved since my issue has been addressed, though hopefully others can use this thread if they are having the same problem. I do see another ongoing thread about the commercial skipper not working on Win.
I looked back at previous recordings and noticed that they have not been fully completing since March 31st. On that date I updated to 1.19.1.2589. The problem for me has persisted up to and including the current release 1.19.1.2621
I am currently using 1.18.8.2527 and have gotten good recordings ever since.
