2009-03-05, 03:44 AM
For some reason a hour long recording (todat's Lost) stopped at 33:40 altought the status indicator was going on for the whole hour. there was a second recording at the same time overlapping the first 30 minutes (Rick Steve travels) that one turned out OK. the odd thing is that i see this in the logs:
which is the exact length of the file. but the signal monitoring continues till 22:02:
i'm scratching my head here...
Quote:2009-03-04 21:33:40.921 VERBOSE [10] Conversion thread configured for ASAP
which is the exact length of the file. but the signal monitoring continues till 22:02:
Quote:2009-03-04 22:01:59.359 VERBOSE [5] Checking signal status on Hauppauge HVR-950:2
2009-03-04 22:02:00.171 VERBOSE [5] Recording has passed endtime+padding. Stopping.
2009-03-04 22:02:00.171 VERBOSE [5] Stopping recording oid:2
2009-03-04 22:02:00.593 VERBOSE [5] Adding O:\temp\dvr\Lost\Lost_20090304_21002202.mpg to commercial detection queue
2009-03-04 22:02:00.593 VERBOSE [5] Adding O:\temp\dvr\Lost\Lost_20090304_21002202.mpg to conversion detection queue
2009-03-04 22:02:00.640 VERBOSE [5] Checking signal status on Hauppauge HVR-950:2
2009-03-04 22:02:00.640 VERBOSE [5] RecordingStatus is now RecordingStatus.RECORDING_COMPETED
2009-03-04 22:02:00.640 VERBOSE [5] RecordingFactory.save()
2009-03-04 22:02:00.734 VERBOSE [5] Save(): Updated existing scheduled recording
i'm scratching my head here...
GBPVR 1.4.7
3 x HVR-950Q USB OTA ATSC HD TUNER
T2250 @ 2.5 GB RAM + ASUS Moca-AR Calcite
Roku HD + XD
3 x HVR-950Q USB OTA ATSC HD TUNER
T2250 @ 2.5 GB RAM + ASUS Moca-AR Calcite
Roku HD + XD