Log Says Recorded OK, But Video Is Short

[4zm4r3d02]

I scheduled a recording for early this morning (USA eastern time zone) using the Guide plugin that comes with GB-PVR. When I awoke this morning, and began to edit out the commercials manually, I discovered that I only had 53 minutes of what should have been a 94 minute recording (90 for the show, with 2 minutes padding before and after).

According to these lines in the GBPVRRecordingService.exe.log, it recorded the whole thing:
---------------------------------------------------------
7/8/2006 12:58:00 AM.157 INFO [5] Found new programme requiring recording: Robert Schimmel: Unprotected
7/8/2006 12:58:00 AM.167 VERBOSE [5] Changing to channel (GBPVR.Backend.Common.NullTunerController): 107
7/8/2006 12:58:00 AM.177 VERBOSE [5] Requesting IRecordingSource to start recording: E:\Video Capture Temp\Robert Schimmel Unprotected\Robert Schimmel Unprotected_20060708_01000230.mpg
7/8/2006 12:58:00 AM.187 VERBOSE [5] DirectRecordingSource about to start recording oid:1 channel:107
7/8/2006 12:58:01 AM.860 VERBOSE [5] recording started
7/8/2006 12:58:01 AM.860 VERBOSE [5] Programme is now recording
7/8/2006 12:58:01 AM.880 VERBOSE [5] RecordingFactory.save()
7/8/2006 12:58:01 AM.950 VERBOSE [5] Save(): Updated existing scheduled recording
7/8/2006 12:58:01 AM.950 VERBOSE [5] getValue() loading new key/value into cache: /settings/ProcessCommercialsDuringRecording
7/8/2006 12:58:01 AM.960 VERBOSE [5] getValue: /settings/ProcessCommercialsDuringRecording : false
7/8/2006 12:58:01 AM.970 VERBOSE [5] Adding E:\Video Capture Temp\Robert Schimmel Unprotected\Robert Schimmel Unprotected_20060708_01000230.mpg to parallel processing queue
7/8/2006 12:58:01 AM.970 VERBOSE [3] getValue() loading new key/value into cache: /settings/CommercialDetectionScheme
7/8/2006 12:58:01 AM.970 VERBOSE [3] getValue: /settings/CommercialDetectionScheme : 0
7/8/2006 12:58:01 AM.970 INFO [3] Parallel Processing thread starting...
7/8/2006 2:32:00 AM.148 VERBOSE [5] Recording has passed endtime+padding. Stopping.
7/8/2006 2:32:00 AM.148 VERBOSE [5] Stopping recording oid:1
7/8/2006 2:32:00 AM.349 VERBOSE [5] getValue cached value: /settings/ProcessCommercialsDuringRecording : false
7/8/2006 2:32:00 AM.359 VERBOSE [5] Adding E:\Video Capture Temp\Robert Schimmel Unprotected\Robert Schimmel Unprotected_20060708_01000230.mpg to commercial detection queue
7/8/2006 2:32:00 AM.359 VERBOSE [5] Not adding E:\Video Capture Temp\Robert Schimmel Unprotected\Robert Schimmel Unprotected_20060708_01000230.mpg to conversion detection queue. Conversions are currently disabled.
7/8/2006 2:32:00 AM.359 VERBOSE [5] RecordingStatus is now RecordingStatus.RECORDING_COMPETED
7/8/2006 2:32:00 AM.359 VERBOSE [5] RecordingFactory.save()
7/8/2006 2:32:00 AM.359 VERBOSE [12] getValue cached value: /settings/CommercialDetectionScheme : 0
7/8/2006 2:32:00 AM.369 INFO [12] Post Processing thread starting...
7/8/2006 2:32:00 AM.379 INFO [12] Running postprocessing.bat on: E:\Video Capture Temp\Robert Schimmel Unprotected\Robert Schimmel Unprotected_20060708_01000230.mpg
7/8/2006 2:32:00 AM.519 VERBOSE [5] Save(): Updated existing scheduled recording
--------------------------------------------------------
Here is the contents of the GBPVRRecordingService.exe-native.log:
--------------------------------------------------------
00:58:00.267 INFO Log started
00:58:00.267 VERBOSE ConexantRecorder::StartRecording(1, 1, 107, 0)
00:58:00.267 VERBOSE target filename: E:\Video Capture Temp\Robert Schimmel Unprotected\Robert Schimmel Unprotected_20060708_01000230.mpg
00:58:00.297 VERBOSE Loading filter names
00:58:00.297 VERBOSE Found names:
00:58:00.297 VERBOSE Hauppauge WinTV PVR2 USB2 Crossbar
00:58:00.297 VERBOSE Hauppauge WinTV PVR2 USB2 Encoder
00:58:00.297 VERBOSE Hauppauge WinTV PVR2 USB2 TvTuner
00:58:00.297 VERBOSE Hauppauge WinTV PVR2 USB2 TvAudio
00:58:00.548 VERBOSE ConnectPins: 'Audio Decoder Out' to 'Analog Audio In'
00:58:00.848 VERBOSE Hardware Revision: 0x3be0117
00:58:00.848 VERBOSE Product ROM: 0x3be0117
00:58:00.858 VERBOSE Status = 0x3BE0004
00:58:00.858 VERBOSE About to query available formats
00:58:00.868 VERBOSE ConexantRecorder::SetConfigurationIVAC()
00:58:00.888 VERBOSE getSetting(EnableTeleText)
00:58:01.729 VERBOSE getSetting(ListGraphFilters)
00:58:01.729 VERBOSE Graph contains the following filters:
00:58:01.729 VERBOSE - GB-PVR Writer
00:58:01.729 VERBOSE - Capture
00:58:01.729 VERBOSE - Hauppauge WinTV PVR2 USB2 Crossbar
00:58:01.729 VERBOSE getSetting(SaveGraphFiles)
00:58:01.860 VERBOSE ConexantRecorder::StartRecording() done
02:32:00.148 VERBOSE ConexantRecorder::StopRecording()
--------------------------------------------------------
The only postprocessing that is run automatically is addepisode_v0.41, which (as far as I know) does nothing but change the recorded file name to the episode name, and updates the name in the database (sqlite). Here is the contents of my PostProcessing.bat:
--------------------------------------------------------
addepisode.exe %1 -log -eponly
--------------------------------------------------------
And the content of the addepisode.log:
--------------------------------------------------------
E:\Video Capture Temp\Robert Schimmel Unprotected\Robert Schimmel Unprotected_20060708_01000230 Renamed to E:\Video Capture Temp\Robert Schimmel Unprotected\Robert Schimmel Unprotected at 02:32 07/08/2006
--------------------------------------------------------
There was plenty of free space on the destination drive.

I made no changes to the original file while editing out the commercials, as I quit the editing program when I realised the recording was short.

Please let me know if you need any further info to determine why this recording came up short.

I just now saw that there is a new version of GB-PVR, so I will understand if you are busy handling the problems of those who have upgraded.

Thank you for your assistance, and for your (mostly) wonderful program.

[sub]

This happens sometimes for Hauppauge PVR USB2 (or PVR2 USB2) owners. The device just seems to stop producing data some times. All I can suggest is making sure you're using the most recent Hauppauge drivers for this device.