I have this problem as well. I'm trying to use the commercial detection on the fly and as soon as I start recording the episode, I can bring up another mythfrontend and check the system status to see where the commercial flagging is. It's always says "Finished 0 Breaks Found". I'm using CVS from April 22nd.
Here's the important stuff from the output of "mythfrontend -v commflag" 2005-04-25 18:36:53.792 Invalid file handle when opening /stuff/recordings/1001_20050425183700_20050425190000.nuv. 4 retries remaining. 2005-04-25 18:36:54.308 Using protocol version 15 adding pes stream at pid 0x31 with type 2 adding pes stream at pid 0x34 with type 129 adding pes stream at pid 0x35 with type 129 2005-04-25 18:36:55.239 Commercial Detection initialized: width = 1280, height = 720, fps = 59.9401, method = 255 2005-04-25 18:36:55.239 Using Sample Spacing of 8 horizontal & 8 vertical pixels. 2005-04-25 18:36:55.241 CommDetect::ClearAllMaps() 2005-04-25 18:36:55.242 Opening audio device '/dev/dsp'. 2005-04-25 18:36:55.242 Opening OSS audio device '/dev/dsp'. 2005-04-25 18:36:55.248 Using XV port 357 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 142 Minor opcode: 14 Resource id: 0x4a 2005-04-25 18:36:55.250 Couldn't get the color key color, and we need it. You likely won't get any video. 2005-04-25 18:36:56.146 Changing from None to WatchingRecording 2005-04-25 18:36:56.145 Using realtime priority. 2005-04-25 18:36:56.276 Video timing method: SGI OpenGL [mpeg2video @ 0xb7677010]Warning MVs not available [mpeg2video @ 0xb7677010]Warning MVs not available [mpeg2video @ 0xb7677010]ac-tex damaged at 40 23 [mpeg2video @ 0xb7677010]ac-tex damaged at 32 43 [mpeg2video @ 0xb7677010]Warning MVs not available [mpeg2video @ 0xb7677010]ac-tex damaged at 61 12 [mpeg2video @ 0xb7677010]ac-tex damaged at 64 13 I'm not sure if it's supposed to tell you when it's complete but by this point I had already checked the system status and it was "Finished 0 Breaks Found". Weird.. -Greg On 4/25/05, Chris Pinkham <[EMAIL PROTECTED]> wrote: > If you're sure you're running the new binaries, can you try running > mythbackend with the "-v commflag" option so that it will tell > mythcommflag to print out some debugging info to see if we can see > where it is stopping at? > > I put the new version on my production system right after I committed > that patch, and it seems to have been working fine. I haven't > come back to find the "Finished, 0 breaks" message since the patch > went in. _______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
