2004-12-29, 06:33 PM
Hi,
I've been trying to get a home built PVR system working for a while now, and seem to be very close to getting it working with GBPVR. The system is based on a Hauppauge PVR250 and a Via EPIA M10000 running Windows XP MCE. We've had this problem on both GBVPR0227 and GBPVR02313, using the latest Hauppauge drivers (pvr250_22_22292).
When we try to watch LiveTV using GBPVR it fails with the error message "Error: Failure playing back file". From the various log files it seems to be a problem getting data from the TV card into the livetv file:
From GBPVR.exe-native.log:
<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">DirectShowHelperVMR9::playFile() - Waited ten seconds, and file size is still zero!!![/QUOTE]
From gbpvrrecordingservice.exe-native.log:
<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">18:15:55.290 VERBOSE Failed to connect pinNameCrossbarVideoDecoderOut to pinNameAnalogVideoIn
18:15:55.290 VERBOSE ConnectPins
18:15:55.290 VERBOSE ConnectPins failed!
18:15:55.290 VERBOSE Failed to connect pinNameCrossbarAudioDecoderOut to pinNameCaptureAnalogAudioIn
18:15:55.290 VERBOSE ConnectPins
18:15:55.380 VERBOSE ConnectPins failed!
18:15:55.380 VERBOSE Failed to connect pinNameCaptureOut to pinNameWriterInputIn
18:15:55.430 VERBOSE put_Mode(AMTUNER_MODE_TV)
18:15:55.450 VERBOSE put_CountryCode(44)
18:15:55.450 VERBOSE put_TuningSpace(44)
18:15:55.450 VERBOSE put_InputType(0, 1)
18:15:55.450 VERBOSE put_ConnectInput(0)
18:15:55.450 VERBOSE put_Channel(33, AMTUNER_SUBCHAN_DEFAULT, AMTUNER_SUBCHAN_DEFAULT)
18:15:55.650 VERBOSE get_VideoFrequency() returns 567312500
18:15:55.650 VERBOSE get_CountryCode() returns 44
18:15:55.830 VERBOSE Hardware Revision: 0x0207
18:15:55.830 VERBOSE Product ROM: 0x0207
18:15:55.840 VERBOSE Attempting to auto detect MSP Standard
18:15:56.051 VERBOSE Standard Result = 0x000A
18:15:56.061 VERBOSE Status = 0x0014
18:15:56.061 VERBOSE About to query available formats
18:15:56.061 VERBOSE Set to MPEG2 width:720 height:576[/QUOTE]
Running the Tuning Assistant shows similar errors in dialog boxes, but then successfully tunes into and displays some channels.
Following the suggestions of other posts on the forum we checked the direct.ini file against the pin names shown in graphedit but the pin names seemed largely correct. The only slight discrepancies were the reference to pinNameAnalogVidioIn in the error messages and PIN_CAPTURE_ANALOG_VIDIO_IN in the direct.ini, and the pin numbers before the pin names on the crossover filter shown in graphedit (e.g. 0: Video Decoder Out) which were missing in direct.ini (e.g. Video Decoder Out).
However changing direct.ini to try and correct these discrepancies didn't seem to have any effect on the error messages, in fact even deleting direct.ini didn't seem to have any effect.
Does anyone have any idea what the problem could be?
McClade
I've been trying to get a home built PVR system working for a while now, and seem to be very close to getting it working with GBPVR. The system is based on a Hauppauge PVR250 and a Via EPIA M10000 running Windows XP MCE. We've had this problem on both GBVPR0227 and GBPVR02313, using the latest Hauppauge drivers (pvr250_22_22292).
When we try to watch LiveTV using GBPVR it fails with the error message "Error: Failure playing back file". From the various log files it seems to be a problem getting data from the TV card into the livetv file:
From GBPVR.exe-native.log:
<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">DirectShowHelperVMR9::playFile() - Waited ten seconds, and file size is still zero!!![/QUOTE]
From gbpvrrecordingservice.exe-native.log:
<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">18:15:55.290 VERBOSE Failed to connect pinNameCrossbarVideoDecoderOut to pinNameAnalogVideoIn
18:15:55.290 VERBOSE ConnectPins
18:15:55.290 VERBOSE ConnectPins failed!
18:15:55.290 VERBOSE Failed to connect pinNameCrossbarAudioDecoderOut to pinNameCaptureAnalogAudioIn
18:15:55.290 VERBOSE ConnectPins
18:15:55.380 VERBOSE ConnectPins failed!
18:15:55.380 VERBOSE Failed to connect pinNameCaptureOut to pinNameWriterInputIn
18:15:55.430 VERBOSE put_Mode(AMTUNER_MODE_TV)
18:15:55.450 VERBOSE put_CountryCode(44)
18:15:55.450 VERBOSE put_TuningSpace(44)
18:15:55.450 VERBOSE put_InputType(0, 1)
18:15:55.450 VERBOSE put_ConnectInput(0)
18:15:55.450 VERBOSE put_Channel(33, AMTUNER_SUBCHAN_DEFAULT, AMTUNER_SUBCHAN_DEFAULT)
18:15:55.650 VERBOSE get_VideoFrequency() returns 567312500
18:15:55.650 VERBOSE get_CountryCode() returns 44
18:15:55.830 VERBOSE Hardware Revision: 0x0207
18:15:55.830 VERBOSE Product ROM: 0x0207
18:15:55.840 VERBOSE Attempting to auto detect MSP Standard
18:15:56.051 VERBOSE Standard Result = 0x000A
18:15:56.061 VERBOSE Status = 0x0014
18:15:56.061 VERBOSE About to query available formats
18:15:56.061 VERBOSE Set to MPEG2 width:720 height:576[/QUOTE]
Running the Tuning Assistant shows similar errors in dialog boxes, but then successfully tunes into and displays some channels.
Following the suggestions of other posts on the forum we checked the direct.ini file against the pin names shown in graphedit but the pin names seemed largely correct. The only slight discrepancies were the reference to pinNameAnalogVidioIn in the error messages and PIN_CAPTURE_ANALOG_VIDIO_IN in the direct.ini, and the pin numbers before the pin names on the crossover filter shown in graphedit (e.g. 0: Video Decoder Out) which were missing in direct.ini (e.g. Video Decoder Out).
However changing direct.ini to try and correct these discrepancies didn't seem to have any effect on the error messages, in fact even deleting direct.ini didn't seem to have any effect.
Does anyone have any idea what the problem could be?
McClade
