Since at least the 1.12.x timeframe, the Plex Commercial Skipper consistently fails. If I invoke it from the command line, it complains that it can’t read the plex-recorded file (can’t parse H264). The only way I’ve been able to make it work is if I replace the installed version of the Plex Commercial Skipper with a renamed comskip.exe. This has become so common, I’ve even written a batch file to do it everytime a new version of PMS comes out. Ridiculous.
I didn’t run the batch file after the last update. Bug is still there:
As others have reported (and myself) the only way to complete this is to kill the Plex Commercial Skipper process.
I’ve repeatedly reported this, and no one seems to care. This behavior exists on a newly installed instance of PMS on a newly built Windows box. Can someone on the Plex team please pay attention to this @anon18523487
Given that you all link to codec’s vs embed them, I wonder if some of the infrastructure that MCEBuddy installs messes with that. Specifically, ffdshow and haali media splitter.
2019-01-10T19:08:49 MCEBuddy.AppWrapper.Comskip → Starting process as a UISession process with Admin privileges. This requires atleast 1 user to be logged into the system (remote desktop or locally)
ERROR> 2019-01-10T19:08:49 → StartAppWithAdminPrivilegesFromNonUISession WTSQueryUserToken failed (No logged on users) with error 1008. An attempt was made to reference a token that does not exist.
WARNING> 2019-01-10T19:08:49 MCEBuddy.AppWrapper.Comskip → Unable to create UI Session process with Admin Privileges from NonUI Session. Is any user logged on?
I’m not familiar enough with comskip but this is the error preventing the process from running. Let me try to get someone more familiar to take a look at this.
Hi @anon18523487. I’m using a PostProcessing script to run the recordings through MCEBuddy and encode them to H265 MKV. Like I say, I don’t think those recordings will be of any use to you.
The excerpt above is from the MCEBuddy logs that are also in that shared folder, rather than the Plex logs. I’m having a separate issue with MCEBuddy because the HW API access for a service changed. Thankfully, I think I’ve gotten that mitigated.
I will repair the installation to return it to the installed default and let the Plex version of comskip run again. I’ll also grab that .ts file and link to it in this thread. I expect I’ll see the same behavior I’ve seen since 1.12 or so where the plex version of comskip hangs until I kill the process in task manager.
The Plex server logs are also in there, and a partial log from the plex commercial skipper.
From what I can tell, Plex Commercial Skipper is running, but very slowly. It’s set for “low” processor, so it takes forever to complete. Is there something that’s set in the compile of plex commercial skipper? The log also seems dramatically more verbose than if I run plex commercial skipper on the same ts file from the command line.
The .log file in there has been going for about 40 minutes so far. If prior experience is a guide, it will never complete.
The machine it’s running on is pretty beefy - an i7-7700 with 16 gigs of ram. The only thing running are Plex Media Server and MCEBuddy. It’s running the latest version of Windows 10 (1903).
Any help you can provide would be greatly appreciated. Thanks! Will.
I see in your log there are other things going on with your server. I’m checking to see how much comskip gets pushed to the background with all this activity.
Appreciate it. When I replace plex commercial skipper with a renamed comskip, it finishes the commercial detection in roughly 7 minutes for an hour show. I’ve never had plex commercial skipper complete since 1.12.x.
