2005-12-03, 02:40 PM
I scheduled a recording to run from 7:00am-7:30am using the gbpvr TV Guide, with 2 minutes of padding at the beginning and end. However, when it was done, the recording was only 10:51 in length. Here is an excerpt of the GBPVRRecordingService.exe.log:
===================================================================================
12/3/2005 6:39:51 AM.741 VERBOSE [23] checking pending recordings
12/3/2005 6:39:51 AM.741 VERBOSE [23] - checking Dilbert
12/3/2005 6:39:51 AM.741 VERBOSE [23] pending: Dilbert
12/3/2005 6:58:00 AM.106 INFO [23] Found new programme requiring recording: Dilbert
12/3/2005 6:58:00 AM.126 VERBOSE [23] Changing to channel (GBPVR.Backend.Common.NullTunerController): 107
12/3/2005 6:58:00 AM.126 VERBOSE [23] Requesting IRecordingSource to start recording: D:\Video\Dilbert\Dilbert_20051203_07000730.mpg
12/3/2005 6:58:00 AM.146 VERBOSE [23] DirectRecordingSource about to start recording oid:1 channel:107
12/3/2005 6:58:03 AM.461 VERBOSE [23] recording started
12/3/2005 6:58:03 AM.461 VERBOSE [23] Programme is now recording
12/3/2005 6:58:03 AM.481 VERBOSE [23] RecordingFactory.save()
12/3/2005 6:58:03 AM.491 VERBOSE [23] Save(): Updated existing scheduled recording
12/3/2005 6:58:03 AM.571 VERBOSE [23] getValue() loading new key/value into cache: /settings/ProcessCommercialsDuringRecording
12/3/2005 6:58:03 AM.571 VERBOSE [23] getValue: /settings/ProcessCommercialsDuringRecording : false
12/3/2005 6:58:03 AM.571 VERBOSE [23] Adding D:\Video\Dilbert\Dilbert_20051203_07000730.mpg to parallel processing queue
12/3/2005 6:58:03 AM.701 VERBOSE [996] getValue() loading new key/value into cache: /settings/CommercialDetectionScheme
12/3/2005 6:58:03 AM.701 VERBOSE [996] getValue: /settings/CommercialDetectionScheme : 0
12/3/2005 6:58:03 AM.701 INFO [996] Parallel Processing thread starting...
12/3/2005 7:32:00 AM.029 VERBOSE [23] Recording has passed endtime+padding. Stopping.
12/3/2005 7:32:00 AM.029 VERBOSE [23] Stopping recording oid:1
12/3/2005 7:32:00 AM.590 VERBOSE [23] getValue cached value: /settings/ProcessCommercialsDuringRecording : false
12/3/2005 7:32:00 AM.590 VERBOSE [23] Adding D:\Video\Dilbert\Dilbert_20051203_07000730.mpg to commercial detection queue
12/3/2005 7:32:00 AM.600 VERBOSE [23] Not adding D:\Video\Dilbert\Dilbert_20051203_07000730.mpg to conversion detection queue. Conversions
are currently disabled.
12/3/2005 7:32:00 AM.600 VERBOSE [23] RecordingStatus is now RecordingStatus.RECORDING_COMPETED
12/3/2005 7:32:00 AM.600 VERBOSE [23] RecordingFactory.save()
12/3/2005 7:32:00 AM.610 VERBOSE [23] getDatabaseConnection() creating new connection
12/3/2005 7:32:00 AM.640 VERBOSE [23] Save(): Updated existing scheduled recording
12/3/2005 7:32:00 AM.650 VERBOSE [914] getValue cached value: /settings/CommercialDetectionScheme : 0
12/3/2005 7:32:00 AM.650 INFO [914] Post Processing thread starting...
12/3/2005 7:32:00 AM.670 VERBOSE [23] RecordingFactory.loadSchedule()
12/3/2005 7:32:00 AM.670 VERBOSE [23] getValue cached value: /settings/AutoRemoveMissingRecordings : true
12/3/2005 7:32:00 AM.670 VERBOSE [23] getDatabaseConnection() creating new connection
12/3/2005 7:32:00 AM.680 VERBOSE [23] checking pending recordings
12/3/2005 7:32:00 AM.680 VERBOSE [23] - checking D:\Video\Dilbert\Dilbert_20051203_07000730.mpg
====================================================================================
It looks to me as if the log shows that the recording was successful, even though it wasn't.
There was plenty of free space on the drive (over 18 gigs).
My computer's clock is and was correct. I checked the log from my clock synchronising program, and it shows a correction of .939 seconds about 20 minutes before the recording started.
Can anybody think of a reason why this recording came-up short? If I need to post any more log entries, let me know.
I was using gbpvr v0.95.11. I just now found out about the update to v0.95.14.
--------------------------------------------------------------------------------------------------------------------------------------
ABIT KT-7A RAID
AMD Athlon, 1.2Ghz
512MB PC133 SDRAM
ATI All-in-wonder 128 PCI(using as display only, the on-board capture disabled in device manager)
Hauppauge Win-TV USB2
VIA USB2 PCI Adapter
Windows XP Professional Service Pack 2
===================================================================================
12/3/2005 6:39:51 AM.741 VERBOSE [23] checking pending recordings
12/3/2005 6:39:51 AM.741 VERBOSE [23] - checking Dilbert
12/3/2005 6:39:51 AM.741 VERBOSE [23] pending: Dilbert
12/3/2005 6:58:00 AM.106 INFO [23] Found new programme requiring recording: Dilbert
12/3/2005 6:58:00 AM.126 VERBOSE [23] Changing to channel (GBPVR.Backend.Common.NullTunerController): 107
12/3/2005 6:58:00 AM.126 VERBOSE [23] Requesting IRecordingSource to start recording: D:\Video\Dilbert\Dilbert_20051203_07000730.mpg
12/3/2005 6:58:00 AM.146 VERBOSE [23] DirectRecordingSource about to start recording oid:1 channel:107
12/3/2005 6:58:03 AM.461 VERBOSE [23] recording started
12/3/2005 6:58:03 AM.461 VERBOSE [23] Programme is now recording
12/3/2005 6:58:03 AM.481 VERBOSE [23] RecordingFactory.save()
12/3/2005 6:58:03 AM.491 VERBOSE [23] Save(): Updated existing scheduled recording
12/3/2005 6:58:03 AM.571 VERBOSE [23] getValue() loading new key/value into cache: /settings/ProcessCommercialsDuringRecording
12/3/2005 6:58:03 AM.571 VERBOSE [23] getValue: /settings/ProcessCommercialsDuringRecording : false
12/3/2005 6:58:03 AM.571 VERBOSE [23] Adding D:\Video\Dilbert\Dilbert_20051203_07000730.mpg to parallel processing queue
12/3/2005 6:58:03 AM.701 VERBOSE [996] getValue() loading new key/value into cache: /settings/CommercialDetectionScheme
12/3/2005 6:58:03 AM.701 VERBOSE [996] getValue: /settings/CommercialDetectionScheme : 0
12/3/2005 6:58:03 AM.701 INFO [996] Parallel Processing thread starting...
12/3/2005 7:32:00 AM.029 VERBOSE [23] Recording has passed endtime+padding. Stopping.
12/3/2005 7:32:00 AM.029 VERBOSE [23] Stopping recording oid:1
12/3/2005 7:32:00 AM.590 VERBOSE [23] getValue cached value: /settings/ProcessCommercialsDuringRecording : false
12/3/2005 7:32:00 AM.590 VERBOSE [23] Adding D:\Video\Dilbert\Dilbert_20051203_07000730.mpg to commercial detection queue
12/3/2005 7:32:00 AM.600 VERBOSE [23] Not adding D:\Video\Dilbert\Dilbert_20051203_07000730.mpg to conversion detection queue. Conversions
are currently disabled.
12/3/2005 7:32:00 AM.600 VERBOSE [23] RecordingStatus is now RecordingStatus.RECORDING_COMPETED
12/3/2005 7:32:00 AM.600 VERBOSE [23] RecordingFactory.save()
12/3/2005 7:32:00 AM.610 VERBOSE [23] getDatabaseConnection() creating new connection
12/3/2005 7:32:00 AM.640 VERBOSE [23] Save(): Updated existing scheduled recording
12/3/2005 7:32:00 AM.650 VERBOSE [914] getValue cached value: /settings/CommercialDetectionScheme : 0
12/3/2005 7:32:00 AM.650 INFO [914] Post Processing thread starting...
12/3/2005 7:32:00 AM.670 VERBOSE [23] RecordingFactory.loadSchedule()
12/3/2005 7:32:00 AM.670 VERBOSE [23] getValue cached value: /settings/AutoRemoveMissingRecordings : true
12/3/2005 7:32:00 AM.670 VERBOSE [23] getDatabaseConnection() creating new connection
12/3/2005 7:32:00 AM.680 VERBOSE [23] checking pending recordings
12/3/2005 7:32:00 AM.680 VERBOSE [23] - checking D:\Video\Dilbert\Dilbert_20051203_07000730.mpg
====================================================================================
It looks to me as if the log shows that the recording was successful, even though it wasn't.
There was plenty of free space on the drive (over 18 gigs).
My computer's clock is and was correct. I checked the log from my clock synchronising program, and it shows a correction of .939 seconds about 20 minutes before the recording started.
Can anybody think of a reason why this recording came-up short? If I need to post any more log entries, let me know.
I was using gbpvr v0.95.11. I just now found out about the update to v0.95.14.
--------------------------------------------------------------------------------------------------------------------------------------
ABIT KT-7A RAID
AMD Athlon, 1.2Ghz
512MB PC133 SDRAM
ATI All-in-wonder 128 PCI(using as display only, the on-board capture disabled in device manager)
Hauppauge Win-TV USB2
VIA USB2 PCI Adapter
Windows XP Professional Service Pack 2
Intel Core i7-4790 / 32GB RAM / Windows 10 Pro 64 bit / HDHomeRun CONNECT DUO Model: HDHR5-2US