[mythtv-users] Commercial skips about 5-15 seconds early
Chris Pinkham
cpinkham at bc2va.org
Sun Oct 16 18:31:17 EDT 2005
> Ok. I applied this patch and the uncomment change to my remote frontend
> (for completeness, this is does *not* include the change we made before
> to initialize framesPlayed and use an incrementer). I noted the cutlist
> that was generated by the previous run of mythcommflag and I ran the
> patched mythcommflag from my remote frontend against the program in
> question. Results:
<snip>
> It now begins the skip at the correct point but seems to skip too far by
> about 12 seconds or so. You'll notice that while the start skip
> increased by about 73 frames, the end skip increased by about 700 or so,
> ie: the duration of the commflag changed as well as the start point with
> this change. It seems that if the duration had stayed the same but the
> start point increased as it did, this would have been a perfect skip as
> I usually find.
This could be because the patch pretends the skipped frames were blank.
Maybe that is a bad thing since it could cause false detection. I think
I need to put in some more logic to make it so that these skipped frames
do not affect the detection logic, but if you want to try something,
you could comment out the following line that the patch inserted:
fInfo.flagMask = COMM_FRAME_BLANK;
I think there is other logic that would need to be changed later in the
analysis code to account for these frames, but this might fix it for
your test case.
Does the editor still function properly and do the frame numbers in the
editor match up to what you're seeing in the commercial skip list for
this recording?
--
Chris
More information about the mythtv-users
mailing list