Just curious if there is a way to re run comskip on a video?
I seem to remember an easier way, but if you're on Linux you can use curl after getting the video ID number... I have a script that looks through the log files after I give it a show and season/episode number and it runs the recomskip.
curl -XPUT http://localhost:8089/dvr/files/${NUMBER}/recomskip
Edit: replace ${NUMBER} with the actual number if not using a bash variable:
curl -XPUT http://localhost:8089/dvr/files/487/recomskip
Thanks!
Can someone tell me how to find the file ID number? I tried the number that is part of the file name using both the full date with the 4 numbers at the end and also just the last four numbers of the file name and neither seem to work with the powershell command above. However, it doesn't seem to work.
One easy way is to find the recording on the web UI, then right click copy URL on the preview image. You can change the preview.jpg at the end of the url to recomskip
The file number also appears at the top if you select "Edit commercials". Otherwise, the UI (either app or DVR web UI) does not really expose the file ID, as it's basically used for internal database references.
Thanks guys. However, I must be doing something wrong - I tried both ways and this is the output error I get back in Powershell:
PS C:\Users\mcroy> iwr -Method Put http://localhost:8089/dvr/files/${379}/recomskip
iwr : {"error":"file not found"}
At line:1 char:1
- iwr -Method Put http://localhost:8089/dvr/files/${379}/recomskip
-
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc eption + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
Take out the ${} and just leave the number.
Thank you so much! That did it!
I am not very good at using powershell commands!
I could swear when I ran recomskip before that it showed up in the DVR Activities.
DVR web UI > Settings > Status > Activity
I just did a recomskip and it didn't show up there. Only post-recording comskips seem to appear there.
My faulty memory-stack, or was something changed?
UPDATE: It's showing up this morning, so maybe it's when one copy of comskip is already running as a post process for a just finished recording and I run recomskip on another recording. Will have to test later.
Reason I ask is I have changed my comskip.ini to use two cores (50% of 4-cores).
Running two comskips takes four cores (50% x 2 = 100%).
Running guide updates each morning takes 50% CPU and I don't know when it happens, see
So, 50% + 50% + 50% > what I have for CPU resources.
Guess for now I shouldn't run recomskips between 9-11am to be sure.
P.S. Yeah, I realize if used the default comskip.ini thread_count=1, I wouldn't have this issue