[mythtv-users] mythcommflag segmentation fault
Alan Anderson
andersonas at adelphia.net
Mon Oct 24 14:01:32 EDT 2005
Hi,
For the last week or so my Master Back End has been failing to transcode
recordings. No problems on the SBE but its not used as heavily.
THe erros is: Transcoding aborted, cutlist changed
I have been trying to correct this with a forced run of mythcommflag
mythcommflag --force-f /video/recording/whatever.nuv
I may need to run this three or four times as mythcommflag will sometimes fail
with a segmentation fault or a illegal instruction.
mythcommflag --force
-f /video/recordings/1022_20050919200000_20050919210000.nuv
2005-10-24 11:16:34.807 New DB connection, total: 1
2005-10-24 11:16:34.837 mythcommflag version: 0.18.1.20050523-1 www.mythtv.org
2005-10-24 11:16:34.837 Enabled verbose msgs :important
MythTV Commercial Flagger, started at Mon Oct 24 11:16:34 2005
Flagging commercial breaks for:
ChanID Start Time Title Breaks
------ -------------- ----------------------------------------- ------
2005-10-24 11:16:34.853 New DB connection, total: 2
1022 20050919200000 Just Legal
40%/457fpsIllegal instruction
I recently upgraded form 0.18-113 to to 0.18-114
Today I dumped the database and looking through the recordmarkup I see several
with a type filed of -3. Assuming a -3 is a bad type I have been doing a
forced commflag run on all of these recordings. Anybody know what the status
field of -3 indicates? The recordings with a -3 go back several months long
before the latest update. They probably back to when I upgraded form fc1
0.17 to fc3 0.18 via a re-install on a new system disk.
example:
INSERT INTO recordedmarkup (chanid, starttime, mark, offset, type) VALUES
(1012,'2005-09-21 21:00:00',0,NULL,-3);
Thanks
Alan Anderson
More information about the mythtv-users
mailing list