HD-PVR 1.0.3.53 Beta AC-3 5.1 Audio Drivers are out

[sleonard]

After a week of using this driver AC3 recording is working perfectly for me, 2.0 and 5.1. However, the issue where one of the HD-PVR's would randomly stop responding, give a "No Signal" error in Sage, and require a quick power cycle is happening more often. In addition, a new twist has popped up. Occasionally, an error message will pop up on all the active clients saying that there was an error recording from capture device so & so. When you press OK it will just pop back up in about 5 minutes. On the server I'll hear the same Windows bong that you hear if you turn off one of the HD-PVR's will start bonging in pairs and I'll get a message from Windows that says the there is a Hi-speed device connected to a lo-speed port and then give me a list of Hi-speed ports that are available. All 3 HD-PVR's are connected to Hi-speed ports (there are no lo-speed ports at all on this MB). I have to power-cycle the offending HD-PVR and usually reboot the server to get everything working properly again. Oh, on the HD-PVR itself, the red recording light is repeatedly turning on and off.

S

[Qusix]

Originally Posted by sleonard

After a week of using this driver AC3 recording is working perfectly for me, 2.0 and 5.1. However, the issue where one of the HD-PVR's would randomly stop responding, give a "No Signal" error in Sage, and require a quick power cycle is happening more often.
S

I am having the same no signal issue. It seems to happen every day for me. When I wake up in the morning I have to power cycle the HD PVR. Prior to installing the driver I had no issues with my system. It was running perfectly for about a month without me have to touch anything.

I am also getting the loud static pop during channel change. I am using the usb irt for channel changing. Is there anyone else that gets the loud static pop that is using either firewire or the included IR Blaster?


I have 2 Extenders and use a place shifter on my PC. Only one of the extenders is connected to an AV Receiver. All three of them have the static pop during channel change.

[Taddeusz]

Originally Posted by Qusix

I am having the same no signal issue. It seems to happen every day for me. When I wake up in the morning I have to power cycle the HD PVR. Prior to installing the driver I had no issues with my system. It was running perfectly for about a month without me have to touch anything.

I am also getting the loud static pop during channel change. I am using the usb irt for channel changing. Is there anyone else that gets the loud static pop that is using either firewire or the included IR Blaster?


I have 2 Extenders and use a place shifter on my PC. Only one of the extenders is connected to an AV Receiver. All three of them have the static pop during channel change.

I'm not getting the pop but I have a delay set so that I it doesn't detect the incorrect resolution for recordings. You might need to put in a short delay for your HD-PVR using the setting delay_to_wait_after_tuning in your properites file.

[mgleed]

I figured out the problem with the new beta driver not working on Vista x64. The issue is that the new driver isn't digitally signed yet. Microsoft in their infinite wisdom (read greed) has required that all drivers be signed before they will load in Vista x64. The work around is to hit F8 at boot time to get to the boot loader menu. Then select the option to disable digital driver enforcement. That should do the trick.

[Chriscic]

Originally Posted by Qusix

I am also getting the loud static pop during channel change. I am using the usb irt for channel changing. Is there anyone else that gets the loud static pop that is using either firewire or the included IR Blaster?

I can't imagine that method of channel changing would have any impact on the audio.

[sic0048]

Well I cannot change the channel via Sage, but I do not get any static or pops when changing the channel via the Hauppauge IR Config program.

[Chriscic]

My WHS Sage server is pretty weak, an old 1.3ghz P3. What are other folks using for their server? I wonder if there's any chance my servers feeble CPU power might be contributing to my problems running to my HD100. I wouldn't think so, since all the server is doing is sending the bitstream (not to mention my Core2Duo wasn't any better when I briefly tried it as server), but who knows.

[stanger89]

Mine's an Athlon XP 1800+ (1.53GHz), seems to run my extenders just fine (except for transcoding). I haven't been following, what problems are you having?

[killervette]

Originally Posted by Chriscic

My WHS Sage server is pretty weak, an old 1.3ghz P3. What are other folks using for their server? I wonder if there's any chance my servers feeble CPU power might be contributing to my problems running to my HD100. I wouldn't think so, since all the server is doing is sending the bitstream (not to mention my Core2Duo wasn't any better when I briefly tried it as server), but who knows.

I am running my WHS on a Q6600 quad core with 3GB ram. i have it running 3 instances of comskip loading the cpu to about 70% leaving the rest to record or stream to 1 HD100.

[Qusix]

Originally Posted by Taddeusz

I'm not getting the pop but I have a delay set so that I it doesn't detect the incorrect resolution for recordings. You might need to put in a short delay for your HD-PVR using the setting delay_to_wait_after_tuning in your properites file.

Thanks, this worked. I set the delay to 3000 and I no longer get the pop sound anymore. It also seems like the channels are changing much faster with the delay now.

The Vi

[TallMomof2]

The new drivers locked up my HD-PVR. Installed them with the executable program that came in the zipped package rebooted including cycling the HD-PVR and the thing locked up. All three status lights came on and you could hear the fan working but neither TME or SageTV could access the device. Had to roll back the driver to 1.0.3.47. Tried to reinstall with the same results.

Any thoughts?

[jerryt]

Originally Posted by TallMomof2

The new drivers locked up my HD-PVR. Installed them with the executable program that came in the zipped package rebooted including cycling the HD-PVR and the thing locked up. All three status lights came on and you could hear the fan working but neither TME or SageTV could access the device. Had to roll back the driver to 1.0.3.47. Tried to reinstall with the same results.

Any thoughts?

Run the driver cleaner program first.

[sic0048]

I also ended up having to roll back to the old drivers. Just to refresh ones memory, I got good sound and video with the new drivers (playback through a HD extender), but lost the ability to change channels via the Hauppauge IR blaster within Sage. I could change the channel via the IR Config program with the new drivers, just not through Sage.

Going back to the original drivers gives me the ability to change channels through Sage (which is obviously important since Sage needs to change the channel to record the correct shows).

[Chriscic]

I RMA'ed my C2 unit today. I'm not 100% sure it's the HD-PVR hardware, but I've spent hours upon hours trying to get things to work across 3 different server PCs and 2 different clients (one PC and and one HD100 extender) and I get various degrees of major problems across all.

There definitely have been some lost signal events (including in TME), so I'm fairly certain the unit is not working flawlessly.

We'll see if things are improved in a week or so and a new (or checked out) unit... if not, I'm officially giving up.

[jerryt]

Originally Posted by Chriscic

if not, I'm officially giving up.

Then it will be time for a R5000-HD

[Chriscic]

I'm going to consider that solution; I'll have to do some research on it.

Certainly I would prefer to get the HD-PVR(s) working, given the $800 cost difference for two.

It seems like some folks are getting good results... so hopefully I still can.

[spacecadet]

Originally Posted by spacecadet

I upgraded to the new drivers with no problem. Thanks to everyone who tried it before me for their great tips.

I'm getting 5.1DD sound, however the quality of the audio is very poor. It's got a very "electronic" or "static" quality to it, almost as if it were overcompressed. I haven't noticed anyone else reporting audio quality issues like this, so I am wondering if it is something about my setup? I've checked my set top box and it doesn't appear to have any way to control how the sound is output. I have Sage TV set up to use the Component + SPDIF input. The recodings report "AC3/384Kbps@48kHz 5.1" sound in the Sage TV detailed info.

In case anyone else is having this problem, it appears that it may be related to Verizon Fios in combination with the HDPVR. I filed a bug with Hauppauge tech support, and while the only response I received back was "Engineering is investigating the issue", there are a couple of posts on the SHS forum from other Verizon Fios customers that are experiencing the same sound issue.

So just a heads up if you use Verizon Fios and are considering upgrading to this driver.

[bcjenkins]

Originally Posted by spacecadet

In case anyone else is having this problem, it appears that it may be related to Verizon Fios in combination with the HDPVR. I filed a bug with Hauppauge tech support, and while the only response I received back was "Engineering is investigating the issue", there are a couple of posts on the SHS forum from other Verizon Fios customers that are experiencing the same sound issue.

So just a heads up if you use Verizon Fios and are considering upgrading to this driver.

I wonder if the issue is driver of firmware.. I am ordering an optical cable to connect up my HD box, but I run the hd-pvr in linux. If you have access to a linux box and are familiar enough to add in driver support, you may give it a try.

B

[TallMomof2]

Originally Posted by jerryt

Run the driver cleaner program first.

That did the trick. So far I cannot see a difference. Same micro stuttering and slightly jerky tickers. 1080i still doesn't work well. On the plus side 5.1 audio works.

[TallMomof2]

Originally Posted by spacecadet

In case anyone else is having this problem, it appears that it may be related to Verizon Fios in combination with the HDPVR. I filed a bug with Hauppauge tech support, and while the only response I received back was "Engineering is investigating the issue", there are a couple of posts on the SHS forum from other Verizon Fios customers that are experiencing the same sound issue.

So just a heads up if you use Verizon Fios and are considering upgrading to this driver.

But the 2 channel sound is fine. So you're no worse off than before.