[mythtv-users] mythcommflag stops early on a fast machine (maybe ?)

[Christopher X. Candreva]

On Wed, 26 Nov 2008, Michael T. Dean wrote:

> Most likely mythcommflag is segfaulting because of bad/unexpected data 
> in the recording causing a segfault in some of the libav* code.

The obvious test was to re-flag one of these recordings after it finished, 
and on re-transcode it flaggs the entire file and doesn't stop.

The test this morning was the Macy's Thanksgiving Parade - a three hour 
show. The first commflagging caught up with real-time at about 25 minutes 
in, and stoped finding only 1 break.

I restarted commflagging with 1hour 20 min left to record, and it finished 5 
minutes after the show ended, flagging the entire 3 hours and finding 21 
breaks.

I think this proves it isn't a problem with the file, other than one caused 
by the recording still being in progress. Unless there is another idea I'll 
open a big report on this.

==========================================================
Chris Candreva  -- chris at westnet.com -- (914) 948-3162
WestNet Internet Services of Westchester
http://www.westnet.com/