|
Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
HD PVR puzzle
I have been using the HD PVR for years and have been very happy. I have upgraded to SageTV v9 on a new machine, and am struggling to get the HD PVR working again. The key issue is that Sage does not seem to be able to connect to the HD PVR to record. It sees the device and always offers it up in the add new source dialogs.
I'm looking for suggestions on what to try next - any ideas would be much appreciated!!! New machine: Windows 10 Pro 64 bit Old machine: Windows 7 Pro 64 bit HD PVR: Rev F2 connected via component and SPDIF to DirecTV Key debugging points: - On a fresh install, errors are first seen when trying to preview a channel on the HD PVR during Source Setup. Blue light on the rim does not appear and Sage can't display the picture. If you continue without preview, it will add the HD PVR as a source but will not be able to activate it when you tune a channel that tunes the HD PVR. - HD PVR hardware is working as verified by going back and forth with the old SageTV v7 machine - HD PVR is working on the new machine when using the Hauppauge Capture software - New (v9) machine configures fine with 4 HDHR tuners which work well - many re-installations produce the same result (I moved the old SageTV directory after uninstalling and rebooting) - currently using driver 1.7.30059.0 , tried reverting to 1.5.7.0 with no success then reinstalled new version. - I tried removing the HD PVR drivers and rebooting to have the machine forget about the HD PVR, then reinstalling with the same results - USB Hardware location in sagetv_0.txt matches the HD PVR hardware location in the Device Manager - HD PVR worked on my first installation of v9 on the new machine, but I ended up overwriting that and resinstalling fresh because after adding the HDHRs the server was only able to tune one device at a time. It would correctly tune one HDHR or the HD PVR, but would give an error when tying to run any two tuners simultaneously. I believe the problem is depicted by the following entries from sagetv_0.txt: Code:
Wed 4/5 21:22:41.451 [main@132e575] Capture device Hauppauge HD PVR Capture Device (0) exists Wed 4/5 21:22:41.451 [main@132e575] Get CaptureMask from registry SOFTWARE\Frey Technologies\Common\AdditionalCaptureSetups\Hauppauge HD PVR Capture Device, 0x800 (hybrid:'') Wed 4/5 21:22:41.452 [main@132e575] @DEBUG@ device found 'Realtek HD Audio Line input' (index:0) for 'Hauppauge HD PVR Capture Device'. Wed 4/5 21:22:41.452 [main@132e575] @DEBUG@ device found 'Realtek HD Audio Mic input' (index:0) for 'Hauppauge HD PVR Capture Device'. Wed 4/5 21:22:41.452 [main@132e575] @DEBUG@ device found 'Realtek HD Audio Stereo input' (index:0) for 'Hauppauge HD PVR Capture Device'. Wed 4/5 21:22:41.452 [main@132e575] @DEBUG@ device found 'Hauppauge HD PVR Capture Device' (index:0) for 'Hauppauge HD PVR Capture Device'. Wed 4/5 21:22:41.453 [main@132e575] Device desc:'@oem26.inf,%hcw49cap.devicedesc%;Hauppauge HD PVR Capture Device'. Wed 4/5 21:22:41.453 [main@132e575] It's Hauppauge device. Wed 4/5 21:22:41.455 [main@132e575] BAD Tuner index :1 dev:\\?\usb#vid_2040&pid_4903#00a8ffd3#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{a5d44047-56a5-4afd-a61c-176bb4ed375b} name:@device:pnp:\\?\usb#vid_2040&pid_4903#00a8ffd3#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{a5d44047-56a5-4afd-a61c-176bb4ed375b} loc:usb:Port_#0002.Hub_#0001 (1 0) select Wed 4/5 21:22:41.456 [main@132e575] Check BDA capture device:Hauppauge HD PVR Capture Device-0 (\\?\usb#vid_2040&pid_4903#00a8ffd3#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{a5d44047-56a5-4afd-a61c-176bb4ed375b}) on location:'usb:Port_#0002.Hub_#0001' id:'USB\VID_2040&PID_4903&REV_0000' [state1, index:0] . Wed 4/5 21:22:41.456 [main@132e575] >>BDA capture device found:@device:sw:{FD0A5AF4-B41D-11D2-9C95-00C04F7971E0}\Silicondust HDHomeRun Tuner 10327CD5-0; loc:'Silicondust HDHomeRun Tuner 10327CD5-0' id:'' guid: desc: Wed 4/5 21:22:41.456 [main@132e575] >>BDA capture device found:@device:sw:{FD0A5AF4-B41D-11D2-9C95-00C04F7971E0}\Silicondust HDHomeRun Tuner 10327CD5-1; loc:'Silicondust HDHomeRun Tuner 10327CD5-1' id:'' guid: desc: Wed 4/5 21:22:41.456 [main@132e575] >>BDA capture device found:@device:sw:{FD0A5AF4-B41D-11D2-9C95-00C04F7971E0}\Silicondust HDHomeRun Tuner 104828E3-0; loc:'Silicondust HDHomeRun Tuner 104828E3-0' id:'' guid: desc: Wed 4/5 21:22:41.456 [main@132e575] >>BDA capture device found:@device:sw:{FD0A5AF4-B41D-11D2-9C95-00C04F7971E0}\Silicondust HDHomeRun Tuner 104828E3-1; loc:'Silicondust HDHomeRun Tuner 104828E3-1' id:'' guid: desc: Wed 4/5 21:22:41.456 [main@132e575] BDA capture is not found on location:'usb:Port_#0002.Hub_#0001' id:'USB\VID_2040&PID_4903&REV_0000' for Hauppauge HD PVR Capture Device. Wed 4/5 21:22:41.456 [main@132e575] BDA CaptureDetail:0x800; hasBDAInput:0x0; BDA type:0x0 Wed 4/5 21:22:41.456 [main@132e575] DeviceCap: 0x100800 Wed 4/5 21:22:41.461 [main@132e575] BAD Tuner index :1 dev:\\?\usb#vid_2040&pid_4903#00a8ffd3#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{a5d44047-56a5-4afd-a61c-176bb4ed375b} name:@device:pnp:\\?\usb#vid_2040&pid_4903#00a8ffd3#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{a5d44047-56a5-4afd-a61c-176bb4ed375b} loc:usb:Port_#0002.Hub_#0001 (1 0) select Wed 4/5 21:22:41.461 [main@132e575] Check BDA capture device:Hauppauge HD PVR Capture Device-0 (\\?\usb#vid_2040&pid_4903#00a8ffd3#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{a5d44047-56a5-4afd-a61c-176bb4ed375b}) on location:'usb:Port_#0002.Hub_#0001' id:'USB\VID_2040&PID_4903&REV_0000' [state1, index:0] . Wed 4/5 21:22:41.462 [main@132e575] >>BDA capture device found:@device:sw:{FD0A5AF4-B41D-11D2-9C95-00C04F7971E0}\Silicondust HDHomeRun Tuner 10327CD5-0; loc:'Silicondust HDHomeRun Tuner 10327CD5-0' id:'' guid: desc: Wed 4/5 21:22:41.462 [main@132e575] >>BDA capture device found:@device:sw:{FD0A5AF4-B41D-11D2-9C95-00C04F7971E0}\Silicondust HDHomeRun Tuner 10327CD5-1; loc:'Silicondust HDHomeRun Tuner 10327CD5-1' id:'' guid: desc: Wed 4/5 21:22:41.462 [main@132e575] >>BDA capture device found:@device:sw:{FD0A5AF4-B41D-11D2-9C95-00C04F7971E0}\Silicondust HDHomeRun Tuner 104828E3-0; loc:'Silicondust HDHomeRun Tuner 104828E3-0' id:'' guid: desc: Wed 4/5 21:22:41.462 [main@132e575] >>BDA capture device found:@device:sw:{FD0A5AF4-B41D-11D2-9C95-00C04F7971E0}\Silicondust HDHomeRun Tuner 104828E3-1; loc:'Silicondust HDHomeRun Tuner 104828E3-1' id:'' guid: desc: Wed 4/5 21:22:41.462 [main@132e575] BDA capture is not found on location:'usb:Port_#0002.Hub_#0001' id:'USB\VID_2040&PID_4903&REV_0000' for Hauppauge HD PVR Capture Device. Wed 4/5 21:22:41.462 [main@132e575] Found the pin2 ;) Wed 4/5 21:22:41.462 [main@132e575] BDA FindVideoPin:0x3998085c hasBDAInput:0 on Hauppauge HD PVR Capture Device Wed 4/5 21:22:41.463 [main@132e575] not found tuner pin in crossbar for device, try search second cross bar Hauppauge HD PVR Capture Device Wed 4/5 21:22:41.463 [main@132e575] Encoder passed the check:Hauppauge HD PVR Capture Device Wed 4/5 21:22:41.465 [main@132e575] Saving properties file to C:\Program Files (x86)\SageTV\SageTV\Sage.properties Wed 4/5 21:22:41.472 [main@132e575] Done writing out the data to the properties file |
#2
|
||||
|
||||
Start SageTV I hope lee you setup your decoder for playback if not you may want just install the latest LAV filter any way
Any go Setup | Detailed Setup | Video / Audio it should look like this EVR Default Default Default DirectShow Disabled Default Default Default 0 Disabled |
#3
|
|||
|
|||
Thanks SHS. Unfortunately, that wasn't the issue. I didn't have the computer playback configured at the time of the capture as I was more interested in getting the HD PVR to connect first. When I checked the playback page my settings matched your suggestions. (I spent several hours after my post debugging, and had the same settings as you recommend.) After continued problem solving yesterday, I was able to narrow the problem down to Sage not talking to the PVR correctly.
When I hooked up a second HD PVR, SageTV would cause the wrong HD PVR to fire up and show the blue light. This was _not_ the one that was being referenced by the following error. Wed 4/5 21:22:41.462 [main@132e575] BDA capture is not found on location:'usb:Port_#0002.Hub_#0001' id:'USB\VID_2040&PID_4903&REV_0000' for Hauppauge HD PVR Capture Device. Sage was still unable to connect and create a recording file (as verified by an HD300). Windows seems to have not been giving Sage the correct context on the HD PVR. With both HD PVRs hooked up, I deleted and reinstalled the drivers (multiple times and versions) to no success. The issue was finally solved when I forced Windows to re-run the hardware installation dialog and it reinstalled the Hauppauge support from scratch using the following link https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx After doing this, Sage was able to see the HD PVR, connect and record. Now I'm in the process of rebuilding the box to make sure I get a clean box from all of the debugging steps I went through. |
#4
|
||||
|
||||
I see well at lease you have it working now
|
#5
|
|||
|
|||
Interesting issue!
I'm having an intermittent issue with a clean install of Windows 10 Pro 64-bit and Sage v9 using two HD PVR's. When I first installed the new system, everything went smoothly and as expected. The system ran for a good week or so, recording flawlessly from both HD PVR's. Then, one of the HD PVR's stopped responding in Sage and I missed a bunch of recordings. Removing it from Sage, deleting from Device Manager and then reinstalling again seemed to have fix it...for a while. It happened again this weekend and it was back through the same process to get it working again. When adding it back into Sage as a source, the preview would work fine but then no signal in Sage attempting to tune to it. I'm scratching my head now and wondering if maybe I should revert back to Windows 7 (and stay with Sage v9) or if this is a Sage v9 issue. FWIW, this never happened with my Windows 7 box on Sage v7. |
#6
|
|||
|
|||
I had a similar problem a while back where my (external) HD PVR appeared to go out on me and I thought it had died. As it turns out, it was only the power supply that died. I was able to get a compatible one for $15 on Amazon. Search amazon for PSM11R-050 Switching Power Supply which seems to have brought my HD PVR back to life. Before changing out the power supply, my HD PVR power light was on and Sage would recognize the HD PVR but it just would not record.
|
Tags |
hd pvr, hd-pvr, opensource |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
BMT import as recording - puzzle | jt4242 | Batch Metadata Tools | 4 | 11-04-2015 02:52 PM |
Need a solution to this network puzzle... | vvulture | SageTV Software | 12 | 04-27-2007 03:25 PM |
The picture looks like a puzzle | mcragoe | SageTV Beta Test Software | 9 | 03-03-2004 01:30 PM |