Recording service fails every second recording

[wtg]

Since upgrading to the most recent release I've been having every second recording fail. I have this error message pop-up on screen: Recording Service Error Message

I don't see any errors in the logs that would indicate anything of interest, but I have finally figured out what seems to be happening. Every second recording the recording fails to stop at the ending time but instead just keeps on going until the disk drive fills up. Once it fills up, the above error is displayed and the service fails. If I restart the service, it works fine for the 1st recording, but fails on the next.

Any ideas?

Thanks,
Tim

[sub]

What recording device are you using?

Can you post you GBPVRRecordingService.exe.log and GBPVRRecordingService.exe-native.log?

[wtg]

Sure, the logs are below.

On further reflection, it may be a coincident that it's every second recording. It may just be recording from my composite inputs instead of the coax input. I may be wrong, but the last couple times that I can think of the first recording was a non-premium channel and the second recording was from my cable box, which would be the composite input instead of from coax. I'll find out tonight because I have another premium channel recording about to start at midnight this evening. I just restarted the service, so I should be able to confirm or refute my theory.

Also worth noting... the second recording does occur, it just doesn't stop. I can watch it afterwards, but of course have to cut hours off the end. =)

GBPVRRecordingService.exe.log

Code:

9/5/2005 9:12:28 PM.116 INFO [4] GB-PVR Recording Service starting 9/5/2005 9:12:28 PM.156 VERBOSE [4] installDirectory is D:\Program Files\devnz\gbpvr\ 9/5/2005 9:12:28 PM.166 VERBOSE [4] configurationFile is D:\Program Files\devnz\gbpvr\config.xml 9/5/2005 9:12:28 PM.206 VERBOSE [4] getValue() loading new key/value into cache: /settings/DatabaseConnectionString 9/5/2005 9:12:28 PM.206 VERBOSE [4] getValue: /settings/DatabaseConnectionString : Provider=Microsoft.Jet.OLEDB.4.0;Data Source=".\gbpvr.mdb";User Id=admin;Password= 9/5/2005 9:12:28 PM.206 VERBOSE [4] databaseConnectionString is Provider=Microsoft.Jet.OLEDB.4.0;Data Source="D:\Program Files\devnz\gbpvr\\gbpvr.mdb";User Id=admin;Password= 9/5/2005 9:12:28 PM.206 VERBOSE [4] getValue() loading new key/value into cache: /settings/DontAntiAlias 9/5/2005 9:12:28 PM.206 VERBOSE [4] getValue: /settings/DontAntiAlias : false 9/5/2005 9:12:28 PM.206 VERBOSE [4] getValue() loading new key/value into cache: /settings/LoggingLevel 9/5/2005 9:12:28 PM.206 VERBOSE [4] getValue: /settings/LoggingLevel : Error

GBPVRRecordingService.exe-native.log
Note: You'll notice the last recording started at 12:00am. It was supposed to stop at 2:00, but kept going until around 8am when my disk filled up.

Code:

23:05:00.525 INFO Log started 23:05:00.525 VERBOSE ConexantRecorder::StartRecording(1, 1, 41, 0) 23:05:00.635 VERBOSE Capture Device is based on BlackBird architecture 23:05:00.635 VERBOSE Capture Device is using Conexant (derived) drivers 23:05:00.635 VERBOSE Loading filter names 23:05:00.635 VERBOSE Found names: 23:05:00.635 VERBOSE Hauppauge WinTV PVR PCI II Crossbar 23:05:00.665 VERBOSE Hauppauge WinTV PVR PCI II Capture 23:05:00.665 VERBOSE Hauppauge WinTV PVR PCI II TvTuner 23:05:00.665 VERBOSE Hauppauge WinTV PVR PCI II TvAudio 23:05:01.086 VERBOSE ConnectPins: 'Analog Audio' to 'TVAudio In' 23:05:01.907 VERBOSE ConnectPins: 'Audio Decoder Out' to 'Analog Audio In' 23:05:01.937 VERBOSE Looking for encoder filter 23:05:01.987 VERBOSE - Hauppauge WinTV PVR PCI II Encoder 23:05:01.997 VERBOSE GetMedium(pCapturePin) returns: {0F8ED065-F820-4A1F-9822-EAAE043A19AB}-00000001-00000000 23:05:02.007 VERBOSE getSetting(AutoDetectEncoderMethod) 23:05:02.027 VERBOSE About try all encoders until we find one that works... 23:05:02.027 VERBOSE Hauppauge WinTV PVR PCI II Encoder 23:05:02.057 VERBOSE Encoder.GetMedium(p656Pin) returns: {0F8ED065-F820-4A1F-9822-EAAE043A19AB}-00000001-00000000 23:05:02.057 VERBOSE Pin mediums match... 23:05:02.078 VERBOSE using instance: 1 23:05:02.388 VERBOSE put_Mode(AMTUNER_MODE_TV) 23:05:02.388 VERBOSE put_CountryCode(1) 23:05:02.388 VERBOSE put_TuningSpace(1) 23:05:02.388 VERBOSE put_InputType(0, 0) 23:05:02.388 VERBOSE put_ConnectInput(0) 23:05:02.388 VERBOSE put_Channel(41, AMTUNER_SUBCHAN_DEFAULT, AMTUNER_SUBCHAN_DEFAULT) 23:05:02.568 VERBOSE get_VideoFrequency() returns 325250000 23:05:02.568 VERBOSE get_CountryCode() returns 1 23:05:02.568 VERBOSE About to query available formats 23:05:02.588 VERBOSE ConexantRecorder::SetConfigurationECP() 23:05:02.598 INFO Firmware Version 2.5.32 Audio Firmware Version <<can't read now>> Model 26032 Rev C182 Serial No: 2964406 Tuner: 82 Decoder: 28 AudioIC: 35 IR Input Map: C= 0x000f, S= 0x0003 23:05:02.708 VERBOSE getSetting(EnableTeleText) 23:05:02.799 VERBOSE getSetting(ListGraphFilters) 23:05:02.799 VERBOSE Graph contains the following filters: 23:05:02.799 VERBOSE - GB-PVR Writer 23:05:02.799 VERBOSE - Encoder 23:05:02.799 VERBOSE - Capture 23:05:02.799 VERBOSE - Hauppauge WinTV PVR PCI II Crossbar 23:05:02.799 VERBOSE - TV Audio 23:05:02.799 VERBOSE - TV Tuner 23:05:02.799 VERBOSE getSetting(SaveGraphFiles) 23:05:02.799 VERBOSE ConexantRecorder::StartRecording() done 00:00:00.130 VERBOSE ConexantRecorder::StopRecording() 00:00:05.548 VERBOSE ConexantRecorder::StartRecording(1, 1, 278, 0) 00:00:05.568 VERBOSE Capture Device is based on BlackBird architecture 00:00:05.568 VERBOSE Capture Device is using Conexant (derived) drivers 00:00:05.568 VERBOSE Loading filter names 00:00:05.568 VERBOSE Found names: 00:00:05.568 VERBOSE Hauppauge WinTV PVR PCI II Crossbar 00:00:05.568 VERBOSE Hauppauge WinTV PVR PCI II Capture 00:00:05.568 VERBOSE Hauppauge WinTV PVR PCI II TvTuner 00:00:05.578 VERBOSE Hauppauge WinTV PVR PCI II TvAudio 00:00:06.028 VERBOSE ConnectPins: 'Audio Decoder Out' to 'Analog Audio In' 00:00:06.108 VERBOSE Looking for encoder filter 00:00:06.118 VERBOSE - Hauppauge WinTV PVR PCI II Encoder 00:00:06.129 VERBOSE GetMedium(pCapturePin) returns: {0F8ED065-F820-4A1F-9822-EAAE043A19AB}-00000001-00000000 00:00:06.129 VERBOSE getSetting(AutoDetectEncoderMethod) 00:00:06.129 VERBOSE About try all encoders until we find one that works... 00:00:06.129 VERBOSE Hauppauge WinTV PVR PCI II Encoder 00:00:06.149 VERBOSE Encoder.GetMedium(p656Pin) returns: {0F8ED065-F820-4A1F-9822-EAAE043A19AB}-00000001-00000000 00:00:06.149 VERBOSE Pin mediums match... 00:00:06.179 VERBOSE using instance: 1 00:00:06.459 VERBOSE About to query available formats 00:00:06.459 VERBOSE ConexantRecorder::SetConfigurationECP() 00:00:06.479 INFO Firmware Version 2.5.32 Audio Firmware Version <<can't read now>> Model 26032 Rev C182 Serial No: 2964406 Tuner: 82 Decoder: 28 AudioIC: 35 IR Input Map: C= 0x000f, S= 0x0003 00:00:06.589 VERBOSE getSetting(EnableTeleText) 00:00:06.689 VERBOSE getSetting(ListGraphFilters) 00:00:06.689 VERBOSE Graph contains the following filters: 00:00:06.689 VERBOSE - GB-PVR Writer 00:00:06.689 VERBOSE - Encoder 00:00:06.689 VERBOSE - Capture 00:00:06.689 VERBOSE - Hauppauge WinTV PVR PCI II Crossbar 00:00:06.689 VERBOSE getSetting(SaveGraphFiles) 00:00:06.689 VERBOSE ConexantRecorder::StartRecording() done

[sub]

On further reflection, it may be a coincident that it's every second recording. It may just be recording from my composite inputs instead of the coax input. I may be wrong, but the last couple times that I can think of the first recording was a non-premium channel and the second recording was from my cable box, which would be the composite input instead of from coax. I'll find out tonight because I have another premium channel recording about to start at midnight this evening. I just restarted the service, so I should be able to confirm or refute my theory.

Ok, can you experiment with this a bit and let me know?

Also worth noting... the second recording does occur, it just doesn't stop. I can watch it afterwards, but of course have to cut hours off the end. =)

With an error message like the one you've shown, I'm not surprised the recording never stops. The process has effectively gone "belly up" and there is no intelligence left to tell the device to stop recording.

[wtg]

Ok, 12 am came, the recording started and I immediately got the same error message popping up. As long as I didn't hit ok, the recording service kept writing to disk but once I clicked Ok on the dialog, the service died.

So, it appears my real error is related to recording off the component video inputs. This is a new pvr150 card (my 250 died) that I installed just a few days before upgrading gbpvr to the latest, and I apparently hadn't tried recording component video since then.

I'm using the pvr150_22_22292 drivers which I downloaded from Hauppauge's website, but I suppose now I'll install the 23025 drivers from shspvr.com and see if that helps. Or should I use the 23123 beta drivers from Hauppauge's website? Any suggestions?

[sub]

I'd probably try these: http://www.shspvr.com/smf/index.php?topic=8708.0