Top Tabs

Thursday, March 27, 2008

How to Replace Smartskip with Comskip in BeyondTV

If you're a BeyondTV user you already know that it comes loaded with its own commercial detection they call SmartSkip. I've used Smartskip with BeyondTV and it works, but its not perfect and what they give you is what you get. If you want a commercial skipping engine that is constantly updated, more configurable and can run while your still recording the show then I recommend you give the excellent comskip program a try. I'll show you how to set up comskip within BeyondTV - it's not too difficult and you'll be happy you put in the extra effort.

Comskip is a program developed by Erik Kaashoek. It's freeware (donations accepted) and its continually updated to work with all of the popular HTPC programs and detect the latest in TV commercial methods.

ADVANTAGES OF COMSKIP OVER SMARTSKIP:

Commercial detection process is faster

Commercial detection is more accurate and methods are updated with new version often

Comskip is very configurable. Detect only certain channels or shows, detect during recording or after or only during certain times if you want.

6. Edit "CustomProcess.xml" (see copy of the file below) and replace "ENTER THE PATH OF YOUR COMMAND HERE" with the absolute path of an executable that takes a filename as a command line argument. In our case our command-line file will be called "batch.bat" so if you put it in C:\Program Files\BTVComskip\, you'll make this path "C:\Program Files\BTVComskip\batch.bat"

This executable will then be run on every file generated by Beyond TV.

This program (batch.bat) is executed for every recording in BeyondTV. Because it is set to Deferred it will execute immediately after a show finishes recording (as long as you have "time constraints" disabled in BTV Webadmin Settings.

EDIT: Per Snapstreams post-processing steps, if you change Deferred in the Priority tags with Immediate, the script will run regardless of the time constraints. Thanks to Nick Burns for this reminder :)

Note from the creator of the script: "For all of these scripts to work, you should NOT have any MPG, TP, or VPRJ files on the root of your video drive. The QSF and CUT scripts actually output video to the root of the drive, as a temporary location. They also check the root of the drive, to see if MPG, TP, or VPRJ files already exist there. This is done as a crude method of determining whether another QSF or CUT job is already running."

Credit to cmcquistion who worked all of this process out and continues to update his thread on the topic here. cmcquistion outlines a process to include cutting the commercials and fixing OTA recording errors as well, but for simplicity (and the fact I didn't need to do it) I've kept that portion of the process out of this post.