HD PVR version 1.0.5.3 whql

[SHS]

see here http://www.shspvr.com/smf/index.php?topic=11793.0
or http://www.hauppauge.com/site/suppor...ort_hdpvr.html

[sic0048]

Who wants to be the guinea pig this time? Hopefully these will work better, but personally I'll wait to hear some feedback before I install them. I just don't have time right now to screw around with it.

[SHS]

They work after all I was a guinea pig

[rdefino]

I need to see more guinea pigs. Last time, I had to rebuild my server.

[Olias]

I just downloaded them. Here goes!!!

[sleonard]

Do these fix anything besides Dolby 5.1? I don't have any problems with that but I'm getting sick of these mini-lockups that many here are experiencing.

S

[SD_Entertainmnt]

Well I crossed my fingers hoping this set would fix the fios box issues...

cant confirm any difference in stability as I get lock ups about once a week.

Oh YES! It looks like I have DD 5.1 that is not robotic sounding out of my QIP-6200

[Olias]

Well, that was interesting. A failure, but interesting.
First, a little background.
I have SageTV running on a server with a pair of ATSC tuners and two H23 DirecTV tuners. One H23 goes to an Intensity Pro, the other to the HDPVR using the optical connection for audio. Playback is on HD Extenders.
I installed the new drivers but kept the H23 set to PCM (2 channel) audio. Channel changing worked fine, taking about four seconds to switch between stations. Playback was smooth but I did notice that I would get an occasional freeze, no more than 1/2 a second, once in awhile. This only happened on a few stations.
Then I switched the H23 for 5.1 sound. The time to change channels shot up to about 13 seconds. The video would appear after 9 -10 seconds with the audio following another 3-4 seconds later. When I switched to the stations that had the occasional dropouts the real trouble began. Sometimes the audio would never start, there would be 1/2 second squeal every now and then. Switching to another channel and then back solved this. But now the 1/2 second freezes turned into 4 second freezes.
So I switched back to PCM audio.

I later did some investigation and found that the sat signal strength was very low for the channels that had the dropouts. Connecting a H23 directly to a monitor, I could see pixelation every now and then on those stations. I assume that the HDPVR in 5.1 mode has a very hard time resyncing audio and video when dropouts occur.

So for me, I'll continue to use use PCM until the next round of software upgrades comes along.

[Chriscic]

Does Hauppauge not provide release notes? Would be nice to know what the intended fixes are.

I'm gonna wait for a few more folks to try as well before I bite.

Come to think of it, weren't we already on the 1.1 drivers (not counting the 2.0 version which was quickly pulled)? Why now a 1.05.3 version? Am I supposed to "downgrade" to this new whql driver?

[Vaskill]

Originally Posted by Chriscic

Does Hauppauge not provide release notes? Would be nice to know what the intended fixes are.

I'm gonna wait for a few more folks to try as well before I bite.

Come to think of it, weren't we already on the 1.1 drivers (not counting the 2.0 version which was quickly pulled)? Why now a 1.05.3 version? Am I supposed to "downgrade" to this new whql driver?

It is not a visible downgrade. Version 1.053 driver package should be an improvement of functionality and considered the latest and greatest (unless there are some new or regression bugs introduced, thus the maybe since only time with users will tell).

Version 1.1 of Hauppauge's driver package supplies the 1.0.5.1 HD-PVR drivers.

Version 1.053 of Hauppauge's driver package supplies the 1.0.5.3 HD-PVR drivers.

There is obviously some confusion at Hauppauge about how they want to release driver package, either with a package number or with the supplied drivers build number.

[SHS]

alanjudy at avsforums all ready ask any way this how it is

1. Version 1.0.5.3 posted as a beta driver.

1.0.3.51 and 1.0.3.53 Beta

2. Version 1.1 posted as a production driver

Posted frist was 1.0.3.46 then come 1.0.3.47

3. Version 2.0 posted as a production driver

1.0.5.2

4. Version 2.0 pulled as a production driver, Version 1.1 again is listed.

1.0.3.47

5. Version 1.1 pulled as a production driver, now 1.0.5.3 listed as production driver.

1.0.5.3

[Cooper]

I installed the new driver last night and everything is working good. I just received a E1 unit so hoping between the new revision and the driver no more recycling.

[Chriscic]

Thanks SHS that's helpful. I guess I'll go ahead and try the new drivers soon.

Wow, up to E1 now on the versions.

[Muchacho]

Hi- I just updated and gave a try using a FIOS 6200 box. While it seems to work like before using analog sound input, it sound like it is comming through a tin can using SPDIF. This is with a C2 HDPVR. Any suggestions?

Thanks, Mike

[Cooper]

I am using a 6200 but with Comcast and sounds very good with opt. Always has though.

[TallMomof2]

Just waiting for an optical cable then I will try out the new driver.

[bmh]

I just installed this driver tonight and everything seems to be working (after I realized that the source needed to be changed to component/spif).

[spacecadet]

Originally Posted by SD_Entertainmnt

Well I crossed my fingers hoping this set would fix the fios box issues...

cant confirm any difference in stability as I get lock ups about once a week.

Oh YES! It looks like I have DD 5.1 that is not robotic sounding out of my QIP-6200

SD, do you find that the audio/video are staying in sync on your Fios recordings? After RMA'ing my unit, I thought I had DD working as well, but after a few minutes of watching, the A/V got badly out of sync and I reverted to the stereo inputs. I am interested in your experience.

Thanks!

[spacecadet]

Originally Posted by Muchacho

Hi- I just updated and gave a try using a FIOS 6200 box. While it seems to work like before using analog sound input, it sound like it is comming through a tin can using SPDIF. This is with a C2 HDPVR. Any suggestions?

Thanks, Mike

I think you need to contact support and RMA. I had to do this with my C2 unit and I got an E1 back. I think a hardware fix is required for this.

[Muchacho]

Originally Posted by spacecadet

I think you need to contact support and RMA. I had to do this with my C2 unit and I got an E1 back. I think a hardware fix is required for this.

Thanks- Will do.