Hauppauge HD-PVR beta driver v1.5.6

[JerryB]

Originally Posted by Opus4

For those who could, are you still having lockup issues with your HD-PVR where you have to power cycle it?
- Andy

Add me to the list of individuals who haven't had a single problem with the HD-PVR since installing the 1.5.6 beta driver.

[spacecadet]

Originally Posted by Opus4

I see that some people weren't able to use these drivers, but for those who could, are you still having lockup issues with your HD-PVR where you have to power cycle it?

I've had more problems with this driver than with the previous version (1.5.3.0). I've had a couple of instances of "stop motion video" problem (where the audio is fine, but the video is choppy) and one case of it locking up. But this evidence is all anecdotal, so it could be the new driver or it could be something else completely.

I think I've had 1.5.6 installed for about 2 weeks now.

[Taddeusz]

I just installed this driver today. I'm going to keep my STB set to output PCM so I'll always get AC3 stereo audio. I've noticed that as far as Placeshifter is concerned that SageTV works better with AC3 audio vs AAC audio in HD-PVR recordings. We'll see how this works.

I suspect the problems people are having with the HD-PVR locking up are due to it's inability to gracefully handle the AC3 stream breaking.

For now I'm going to stay away from AC3 pass-through unless I hear that its working without locking up.

[MeInMaui]

I just finally got around to updating to the 1.5.6 drivers last night. All went smoothly and seemed to work fine in live TV tests with spdif audio input after a reboot. In fact everything seemed to respond a bit quicker after the update, though it could be my imagination. I'll post here if any lockups/problems crop up.

Aloha,
Mike

[gplasky]

I updated to the new drivers immediately after they were avaialble. I do not have any issues and I am using SPDIF for 5.1 AC3 sound for my recordings. It took all of abo9ut 5 minutes to run the update and reboot the server. This is on a WHS with a hd100, hd200 and various PC clients.

Gerry

[TechJunkie]

I also updated the drivers as soon as they came out becouse of the fix with FIOS STB. The AC3 worked finally with FIOS and I was very happy. But then my HD-PVR had to be restarted once a day. I switched back to the analog audio and the HD-PVR has not failed since. For now I am sruck with stereo. No surround sound for me.

[spacecadet]

Originally Posted by TechJunkie

I also updated the drivers as soon as they came out becouse of the fix with FIOS STB. The AC3 worked finally with FIOS and I was very happy. But then my HD-PVR had to be restarted once a day. I switched back to the analog audio and the HD-PVR has not failed since. For now I am sruck with stereo. No surround sound for me.

Yeah, I'm not quite rebooting once a day, but I am thinking of going back to the analog audio to see if my intermittent problems go away (one lock-up and a couple instances of stop motion video). I don't watch movie channels via the HD-PVR, so I'm not sure the AC3 audio is buying me all that much, anyway (listening to analog with PLII had always seemed pretty good to me).

[Taddeusz]

Originally Posted by spacecadet

Yeah, I'm not quite rebooting once a day, but I am thinking of going back to the analog audio to see if my intermittent problems go away (one lock-up and a couple instances of stop motion video). I don't watch movie channels via the HD-PVR, so I'm not sure the AC3 audio is buying me all that much, anyway (listening to analog with PLII had always seemed pretty good to me).

In my experience you don't have to go all the way to analog audio to keep the HD-PVR from locking up. Simply setting your STB to output stereo PCM instead of AC3 should have the same effect.

I've always used the SPDIF input and I've only ever had problems when I set my STB to output AC3. It works great when my STB is set to output PCM.

[spacecadet]

Originally Posted by Taddeusz

In my experience you don't have to go all the way to analog audio to keep the HD-PVR from locking up. Simply setting your STB to output stereo PCM instead of AC3 should have the same effect.

I've always used the SPDIF input and I've only ever had problems when I set my STB to output AC3. It works great when my STB is set to output PCM.

I don't think the Verizon (moto) boxes provide the ability to configure this. But I may have overlooked it.

[TechJunkie]

Originally Posted by Taddeusz

In my experience you don't have to go all the way to analog audio to keep the HD-PVR from locking up. Simply setting your STB to output stereo PCM instead of AC3 should have the same effect.

I've always used the SPDIF input and I've only ever had problems when I set my STB to output AC3. It works great when my STB is set to output PCM.

I found that switching cables and changing the settings in SageTV is more simple then switching settings on my Verizon STB since I my STB are not near a TV or Monitor.
Thank you for the info and I will keep this in mind the next time I change the configuration around.

[Taddeusz]

Originally Posted by TechJunkie

I found that switching cables and changing the settings in SageTV is more simple then switching settings on my Verizon STB since I my STB are not near a TV or Monitor.
Thank you for the info and I will keep this in mind the next time I change the configuration around.

Yea, changing the configuration on the STB can be a pain. Changing the audio settings while SageTV is viewing the HD-PVR can cause it to lock.

After reading about everything on here and from my own experience I'm convinced that much of the current issue with the HD-PVR is that it can't handle breaks in the AC3 stream very well. And that even breaks in the AC3 stream going between network to local commercials and back can cause problems. It seems it's just a roll of the dice away from whether the HD-PVR decides to lock up or not.

Since I switched my STB to stereo PCM the ONLY issues I've had are with my STB and not with the HD-PVR. I actually had a problem last night just as I was about to test out the 1.5.6 driver when I got home. And the STB was in an odd state. Audio was playing but no video. I pulled the power plug on the STB and let it reset and it began working fine. Really weird but at least its not my HD-PVR causing the problem.

[trini0]

Let me give it a try...

[babgvant]

Originally Posted by babgvant

Switched back to digital audio input on Friday, which always eventually caused a problem, so far so good.

locked up last night, so I'm back on analog inputs.

[michelkenny]

I set up 2 HD-PVRs (rev E1) a week or two ago with the 1.5.6 drivers from the start. I only have analog audio connected. I've had 2-3 problems with one unit (the same one as far as I can tell). I'm not sure if it is the same "lockup" as everyone else experiences... what I get is a black screen with "no signal" in SageTV, along with a "capture error" when the recordings starts. The file size stays at 0 bytes. Turning the HD-PVR off and on fixes the problem for a little bit then it happens again. I'm not sure if it's the HD-PVR locking up, or my GF pressing a ton of buttons during live TV and breaking something... I'm still investigating... I have debugging turned on in Sage. Is there any hints that I can find out what the problem is?

[trini0]

Originally Posted by trini0

Let me give it a try...

I'm still having my random problems.
I dont think there is anything wrong with my unit.
Hopefully Sage tech could figure something out...

[Brent]

I'm having trouble with SageTV using this HD-PVR 1.5.6 driver.

Here's the steps I went through to try it out:

• Downloaded & unzipped latest Hauppauge beta 1.5.6 driver
• Shut down SageTV entirely including service
• Ran “hcwdriverinstall.exe”
• Rebooted computer
• Ran Total Media Extreme to test playback of HD-PVR with SPDIF - everything worked perfectly
• Shut down TME
• Installed default STV without any plugins for testing purposes
• Ran SageTV and attempted to view LiveTV on one of the HD-PVR channels

Result when trying to tune was this error message popped up

Capture, ERROR (-4,0x8007001f): There was an problem using the capture device. Please be sure you have the latest drivers installed for your capture device, and that they are installed correctly.

Then on the playback window it said "No Signal" and a blue screen

Here's a clip of the relevant log if its useful to anyone or if anyone has a suggestion:

Sat 5/2 9:15:00.941 Change in record to another show. Entering device record mode. - NOW
Sat 5/2 9:15:00.941 Seeker.startRecord(Hauppauge HD PVR Capture Device FA[A[5160392,0,"SIGN OFF",0@0502.08:55,5256000]], currTime=Sat 5/2 9:15:00.937) currRecord=null switch=false
Sat 5/2 9:15:00.941 Setting up MMC video for recording new show & tuning channel conn=Hauppauge HD PVR Capture Device Component+SPDIF
Sat 5/2 9:15:00.942 Using quality setting "Great-H.264" for recording
Sat 5/2 9:15:00.942 Seeker resetting the encoder because it'll pass the max duration
Sat 5/2 9:15:00.942 MediaFile startSegment enc=Hauppauge HD PVR Capture Device Great-H.264 MediaFile[id=5160392 FA[A[5160392,0,"SIGN OFF",0@0502.08:55,5256000]] host=mediaserver encodedBy=Hauppauge HD PVR Capture Device Component+SPDIF format=MPEG2-TS 0:00:00 0 kbps [] \\MEDIASERVER\SageShows\HauppaugeHDPVRCaptureDeviceComponentSPDIF-0.mpgbuf, Seg0[Sat 5/2 9:12:09.027-Sat 5/2 9:12:21.716]]
Sat 5/2 9:15:00.959 Seeker channel string=1452
Sat 5/2 9:15:00.960 Playing IR tune command of 1452
Sat 5/2 9:15:03.927 setEncodingProperties0 968673928 Great-H.264
Sat 5/2 9:15:03.927 Set encoding property audiooutputmode to 0
Sat 5/2 9:15:03.927 Set encoding property audiocrc to 0
Sat 5/2 9:15:03.927 Set encoding property gopsize to 15
Sat 5/2 9:15:03.927 Set encoding property videobitrate to 7600000
Sat 5/2 9:15:03.927 Set encoding property inversetelecine to 0
Sat 5/2 9:15:03.927 Set encoding property closedgop to 0
Sat 5/2 9:15:03.927 Set encoding property vbr to 0
Sat 5/2 9:15:03.927 Set encoding property outputstreamtype to 1
Sat 5/2 9:15:03.927 Set encoding property width to 720
Sat 5/2 9:15:03.927 Set encoding property height to 480
Sat 5/2 9:15:03.927 Set encoding property audiobitrate to 384
Sat 5/2 9:15:03.928 Set encoding property audiosampling to 48000
Sat 5/2 9:15:03.928 Set encoding property disablefilter to 1
Sat 5/2 9:15:03.928 Set encoding property medianfilter to 3
Sat 5/2 9:15:03.928 Set encoding property fps to 30
Sat 5/2 9:15:03.928 Set encoding property ipb to 0
Sat 5/2 9:15:03.928 Set encoding property deinterlace to 0
Sat 5/2 9:15:03.928 Set encoding property aspectratio to 1
Sat 5/2 9:15:03.928 setupEncoding0 called for 968673928 'Hauppauge HD PVR Capture Device-0' (ver 1.0)
Sat 5/2 9:15:04.040 setupEncoding0 Trace1 
Sat 5/2 9:15:04.041 setupEncoding0 Trace2 
Sat 5/2 9:15:04.041 setupEncoding0 Trace3 
Sat 5/2 9:15:04.048 Using encoder filter (0)
Sat 5/2 9:15:04.048 setupEncoding0 Trace4 
Sat 5/2 9:15:04.049 setupEncoding0 Trace5 
Sat 5/2 9:15:04.050 setupEncoding0 Trace6 
Sat 5/2 9:15:04.050 is not ATI encoder.
Sat 5/2 9:15:04.050 setupEncoding0 Trace6-1 
Sat 5/2 9:15:04.050 setupEncoding0 Trace7 
Sat 5/2 9:15:04.050 Got VideoEncoder interface
Sat 5/2 9:15:04.066 Signal detected!
Sat 5/2 9:15:04.081 Detected capture input resolution lines=1080
Sat 5/2 9:15:04.097 setupEncoding0 Trace7-2
Sat 5/2 9:15:04.097 setupEncoding0 Trace7-3
Sat 5/2 9:15:04.097 setupEncoding0 Trace8 
Sat 5/2 9:15:04.097 setupEncoding0 Trace9 
Sat 5/2 9:15:04.098 setupEncoding0 Trace10 
Sat 5/2 9:15:04.098 Encoding to file \\MEDIASERVER\SageShows\HauppaugeHDPVRCaptureDeviceComponentSPDIF-0.mpgbuf
Sat 5/2 9:15:04.099 setupEncoding0 Trace27 
Sat 5/2 9:15:04.099 setupEncoding0 Trace28 
Sat 5/2 9:15:04.099 startEncoding0 called for 'Hauppauge HD PVR Capture Device-0'
Sat 5/2 9:15:09.119 Failed: startEncoding0 Run return code:8007001f  
Sat 5/2 9:15:09.119 Built:sage.EncodingException: ERROR (-4,0x8007001f): There was an problem using the capture device. Please be sure you have the latest drivers installed for your capture device, and that they are installed correctly.
Sat 5/2 9:15:09.119 Sending hook to client for MediaPlayerError args=[Capture, ERROR (-4,0x8007001f): There was an problem using the capture device. Please be sure you have the latest drivers installed for your capture device, and that they are installed correctly.]
Sat 5/2 9:15:09.195 Playing IR tune command of 1452

I'm submitting this to SageTV support as well of course, but wanted to share with others here to see if anyone had any suggestions. I think it is important to note that this seems to be a problem with SageTV and not the HD-PVR. I'm not experiencing lockups or anything and it works just fine using TME - just doesn't work with SageTV

[HelenWeathers]

Brent, had nothing but grief with this driver install. It killed even my OTA HDTV tuners.

I ended up saveing my wiz.bin, uninstalled Sage, deleted the SageTV folder and did a a fresh install of 6.5.14 beta. Did all the first time setup config (language, weather zip etc).

Then I set up one of the HD-PVRs as a source and got it to work (it seemed to take a long time to pick up a signal). Did my channel lineup anew. Tested that. That worked so added second HD-PVR and that worked. Added my three OTA tuners and setup channel lineup. Exited Sage. Copied my wiz.bin into the new SageTV\SageTV folder and everything has been working fine since then.

I do notice that when I watch live TV I get the NO Signal message on the HD-PVR channels for a few seconds, but then it clears and the video/audio comes up.

The only maybe pertinent thing I can think of here is that the fresh install set up a new properties file.

[Brent]

Thanks for the update. That doesn't sound too promising. I think I'll hold off before I change anything and see what SageTV support wants me to do.

[LehighBri]

Guys - best thing I can suggest rather than ranting in this thread is to contact Hauppauge support. As you may have seen, I had a horrible experience with my HVR-2250 recording 2 SD channels at once. I contacted Hauppauge support, they sent me a variety of "prerelease" drivers to test out, until they finally fixed the issue. I recommend you do the same... they are quite responsive.

Use the site below to submit your issue to Hauppauge:
http://www.hauppauge.com/site/suppor...t_contact.html

[bcjenkins]

For the record, this firmware update is working fine for Linux drivers.

B