Replying to myself to update the thread. > this average FPS to make sure that the flagger does not catch up to > the recorder during ~realtime flagging. The flagger is supposed to > receive the DONE_RECORDING event from the recorder when the recording > finishes and this causes the flagger to go into normal speed and > not throttle itself anymore. I think there may be a problem picking > up this event, I'm not seeing it being received in some of my testing.
This does appear to be working on my production system. I noticed this in my logs while testing a fix for the "Finished, 0 break(s) found" bug. 2005-04-27 07:00:00.415 CommDetect::CustomEvent - Received Event: 'DONE_RECORDING 1 982' 2005-04-27 07:00:01.103 CommDetect::CustomEvent - Received a DONE_RECORDING event for card 1. This is the recording we are flagging, turning watchingRecording OFF. So, the flagger did receive the event like it should and the flagging throttling should have been turned OFF. So, it sounds like the low FPS is just indicative of the fact that the S in FPS is started soon after mythcommflag is started and before the sleep that lets the recorder get ahead a ways so that we can look for the logo. -- Chris
_______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
