HDPVR Commercial Detection

[ericscottf]

Neat...

I'm curious, how'd the math work out? Is it a single constant offset, or a linear multiple of the time difference or something completely different?

[Fuzzy]

Seems to be a simple linear time adjustment.. the timestart is zero, they just 'stretch' it to fill out the mediafile time to equal (well, it's close) the airing time.

[stanger89]

Just curious, how much are the recordings short? Is it like 4 seconds or so?

[Fuzzy]

Mine have averaged around 8-12 seconds it seems... I think this is mostly delays from my R-5000 sources.

[ericscottf]

Actually, now that i think of it, this all makes a bit more sense with a related issue..

when the interface skips over a commercial, you can use the left arrow to jump back to where the commercial skipped from if the setting is set.
I've noticed that, especially later in a show, it doesn't jump back to where the commercial skipped from, it jumps back too far forward by some small amount of time. Perhaps that's because the jump forward from point is calculated as an absolute index from the beginning of the file and the jump back isn't?

just food for thought. Hopefully this fix will work, and i won't have to jump back anymore to begin with.

[Fuzzy]

Okay, here's what I've come up with.

First, download MediaInfo from sourceforge (CLI Version)

Second, set up the task in SJQ

if [IsObjMediaFile == true && $.IsTVFile{} == true && $.IsFileCurrentlyRecording{} == false && FileExists != "%d%/%p%.duration"]
{
   :PRIORITY 20
   DURATION
}

DURATION
{
   :RESOURCES 25
   :MAX 1
   :CPU LOW
   "C\:\\SJQC\\MediaInfo\\MediaInfo.exe --Inform=General;%Duration% --LogFile=\"%d%\\%p%.duration\" \"%c%\""
}

Third, remove the normal Comskip STVi from your client setup, and use the following instead. Don't use BOTH, as I'm sure it'll cause some sort of problems...

If the .duration file exists, it'll use it to correct the cutpoints when read from the edl file, and you should have far more accurate skipping.

-Fuzzy

EDIT: Download moved to here.

[ericscottf]

What's the best way to properly remove the old Comskip STVi?

thanks for the help!

[Taddeusz]

Do you know if this will replace the comskip that comes with SageMC?

[Fuzzy]

Originally Posted by ericscottf

What's the best way to properly remove the old Comskip STVi?

From the same screen that you use to add an STVi (Setup -> Detailed Setup -> Advanced -> Manage STVi Plugins), you click on it in the 'Current STVI Plugins' list and it will remove it. Then choose 'Add a new STVI plugin file' and select the 'Comslip_Playback_with_Correction' file. Choose 'Close' and it will ask you if you want to rebuilt the STV with the new imports. Choose yes, and wait for it to finish. that should be it.

Originally Posted by Taddeusz

Do you know if this will replace the comskip that comes with SageMC?

No, I'm pretty sure that won't work. Since the comskip feature is built into sagemc, someone a little more familiar with SageMC will have to port the changes over I'm thinking.

[ericscottf]

I use the same interface file (i forget what it's called) on all my hd-200s, so i'll probably have to shut them off before making this change?

I'm curious, is there some documentation on making stvis? I pawed through the file you posted and it looks like it was built from some other code. Where is the best place to start as far as learning how to make them?

thanks

[razrsharpe]

Originally Posted by ericscottf

I'm curious, is there some documentation on making stvis? I pawed through the file you posted and it looks like it was built from some other code. Where is the best place to start as far as learning how to make them?

Here and Here

[Fuzzy]

Originally Posted by ericscottf

I use the same interface file (i forget what it's called) on all my hd-200s, so i'll probably have to shut them off before making this change?

It really doesn't take long to do the change. Just do it once from each of your extenders.

[ericscottf]

Yeah, they just all use the same file. thanks for the help!

[Taddeusz]

It would be nice if someone more familiar with SageMC could add these modifications. I opened up Studio and I just couldn't tell what was what.

[ericscottf]

I'm adding the mediainfo part to my own software, can you tell me what this translates to:

"C\:\\SJQC\\MediaInfo\\MediaInfo.exe --Inform=General;%Duration% --LogFile=\"%d%\\%p%.duration\" \"%c%\""

I'm guessing, for a show named show.ts, it comes out as:

c:\path_to_mediainfo\mediainfo.exe --Inform=General;%Duration% --LogFile="c:\path_to_media\show.duration"
Is that right? Also, what is %c%?
%d is where the new comskip stvi will look for the duration file? -- same folder as the media?

Thanks

Edit: Of course, it would seem that "%C" is path_to_show and the show filename. silly me.

What's the contents of a duration file supposed to look like? Mine is one line:

3595478.756444

That's the whole file...
Good?

Lastly (i hope), is there any way to verify this is working? The comskip menu version number stayed the same at 1.5.4. Other than watching closely, deleting the duration file and watching again for different behavior, is there a good way to tell that this new version is installed and working right?

thanks

[Fuzzy]

I didn't think to go through the code and fine reference to the version numbers to change it.. However, if you removed the old and added the new form the manage stvi's section, and it rebuilt, rest assured it's in there.

[ericscottf]

ok, no prob

Could you please tell me:

1) what should the inside of a .duration file look like?
2) where will the code search for the .duration file? Same folder as the video, or elsewhere?

I'm almost done adding this to my code, i reckon i could always just put in a really wrong .duration file and see what happens to prove that things are all in the right spots...

[Fuzzy]

yes, you've got it right.. the duration file should contain the the length of the file, in milliseconds (as your example showed). It should be in the same place as the video (as shown in the SJQ codes I posted).

[Taddeusz]

Originally Posted by Fuzzy

yes, you've got it right.. the duration file should contain the the length of the file, in seconds (as your example showed). It should be in the same place as the video (as shown in the SJQ codes I posted).

Actually, it appears it is the length of the video in microseconds.

[Fuzzy]

Originally Posted by Taddeusz

Actually, it appears it is the length of the video in microseconds.

Yeah (well no) It's in milliseconds... sorry.. just woke up...