Hauppauge HD-PVR driver v1.5.6.1 whql

[SHS]

Yes read news page at buttom

[sic0048]

Originally Posted by SHS

Yes read news page at buttom

This isn't much clearer either.

8/8/2009
Good news the Forum online
FTP is still off line becuase it dosen't have a standard type ftp
Let say for Example you want file
http://www.shspvr.com/ftp/download/w...3.57.21126.exe
You need change to this
http://www.shspvr.com/ftp/download/w...3.57.21126.exe

But I get the point.

Thanks!

[SHS]

On the Forum
and only click below to go new web ftp
http://www.shspvr.com/ftp/download/

[sic0048]

That is quite a selection of software! Thanks for keeping it all together because apparently Hauppauge drops their links once they move on to a new version. Without your site, I would have been up the creek without a paddle.

[popechild]

1.5.6.1 causes lockups at least once a day for me - that's after a week or each day trying a different combination of settings (audio format, cable choice, install order, etc, etc.).

[stanger89]

Originally Posted by popechild

1.5.6.1 causes lockups at least once a day for me - that's after a week or each day trying a different combination of settings (audio format, cable choice, install order, etc, etc.).

Yeah, I think I need to recind my previous positive feed back on these 1.5.6.1. They surely are much better for me than the previous 1.5.6.0's as they don't start causing immediate, repeated lockups, but they do "lock up" frequently. so I'm back to the 1053/1.0.5.301 drivers that had been working quite well for me.

[reggie14]

Obviously, YMMV, but these drivers have been very stable for me. I'm running them on a WinXP x32 server, with optical audio, and a cable box set up to output 720p for HD content, and 480i for SD. I only have one HD-PVR and I use firewire for channel changing.

[Clift]

I don't know if it's these drivers or not, but every now and again I get an audio glitch. It was especially bad watching the Florida State game the other night... And not just because Florida State was getting the snot beat out of them.

[sic0048]

Originally Posted by Clift

I don't know if it's these drivers or not, but every now and again I get an audio glitch. It was especially bad watching the Florida State game the other night... And not just because Florida State was getting the snot beat out of them.

Go Tigers

[sic0048]

Don't forget to set up the Hauppauge IR program again after using the HWClear and reinstalling the drivers and software (if you are using the built in blaster).

I've gone through this process about a 1/2 dozen times over the last few days trying to get a stable system. Most of them because I forgot to set up the IRConfig program at some point and lost the ability to change channels. I went back to 1.0.5.301 then back to 1.5.6.1 and when it still didn't work, I realized my error. Then I went back to 1.0.5.301 to hopefully get a more stable system.

......I hate it when I do stupid things.....

[Taddeusz]

I haven't had any problems with 1.5.6.1 since I did a proper upgrade. It appears that the only difference between 1.5.6 and 1.5.6.1 is the firmware. I had previously been using 1.0.5.301. The ONLY problems I've had come from my STB. One problem was caused by a flaky signal which caused the audio to drop out momentarily and the other, I think, was caused by an update push from Cox. For whatever reason whenever my Scientific Atlanta cable box reboots it defaults to 480i rather than the fixed 720p I have it set at. This caused my Friday night recordings to be at the wrong resolution.

[mistergq]

Tried this driver because I was having a random audio glitch issue with the other drivers with my QIP FIOS box. Specifically, some times when the next recording begins, there would be a loud crackle, and then no sound.

With this driver, no issue. However, I am getting echo of part of the last frame on some fast moving frames. It happened with the Broncos Steelers Monday night game this week as well as Mall Cop movie.

[AtariJeff]

Well the good news is no HD-PVR errors like on 1.0.5.6. The bad, it still sounds like my recordings are under water occasionally. Back to 1.0.5.3 for me.

[mistergq]

I think the sound issue I was having was due to a bad stb. Last night it happened when it switched from one program to the next. Sound went out. before shutting down the recording, I went into my computer room and changed the channel up 1 and then back down to the channel it should be recording. Sound immediately came back. To me, this problem seems like a hardware error, not a driver error. This is also the same STB that one of the firewire ports went out on.

So I switched out the STB. We have a backup STB for guess to use.

I am debating about going back to 1.0.5.6 because of the artifact issues. Beyond that, everything else seems to be working.

[HawgGuy]

Originally Posted by AtariJeff

Well the good news is no HD-PVR errors like on 1.0.5.6. The bad, it still sounds like my recordings are under water occasionally. Back to 1.0.5.3 for me.

I notice the underwater sound problem as well. Not sure if it's related to the new HD PVR drivers or not. I normally run 720p resolution. If I momentarily switch my STB (Dish vip 211) to 1080i and then back to 720p the glitch disappears -- until the next day after the daily update.

Hard to blame that on the HD PVR, I' more suspicious of the Dish STB.

[tomfisk]

I've been holding off on posting this, just because it seems to fly in the face of the conventional wisdom posted here. But after 50+ HD-PVR recordings without a problem, here is my "formula" for getting a stable HD-PVR / Sage TV setup.

This is on a relatively new server build and hardware (within the last month). The only "mod" I've made to the HD-PVR is to tape over the IR receiver. I'm using the HD-PVR with an Moto DCH-6200 with Hauppauge's blaster. System hasn't been rebooted in the last 2 weeks. I also have the PVR-500 analog tuner card, along with ATI HD-theater 650 and an HDHomeRun.

Driver installation: Initially installed the 1.5.6 driver (latest from Hauppauge's support website). Had some initial problems with recordings being missed so I "upgraded" to the 1.5.6.1 driver. Didn't do an HCWClear, nor unplug the HD-PVR from USB. Installed the driver and rebooted. Also had some missed recordings with the 1.5.6.1 driver so I "downgraded" to 1.5.6. Again, did not do an HCWClear, nor unplug the HD-PVR. Installed the driver and rebooted. Recording seemed much more stable, but I was still getting a few missed recordings.

Using Total Theater noticed that the output from the DCH-6200 on HD channels was initially not stable after tuning (using the remote to tune the channels). After some experimenting I found that tuning to a non-HD channel, then an HD channel produced a consistently stable output.

With this in mind, I wrote a script that uses firewire tuning (channelw.exe) to tune to a non-HD channel, waits 10 seconds, then tunes an HD channel when my system comes out of standby (typically 4 minutes before a scheduled recording).

Knock on wood...my HD-PVR has been working great for the last 2 weeks. No dreaded system messages...

YMMV...just what I've experienced. Now if we could only get reliable and fast H.264 commercial detection...

[Taddeusz]

Originally Posted by tomfisk

YMMV...just what I've experienced. Now if we could only get reliable and fast H.264 commercial detection...

The new ShowAnalyzer 1.0 is certainly fast but is not really reliable yet. I'm not even really sure why he was so itching to get it out as it's not a complete product compared to the old version. No SchoolHouse for tweaking detection and the default settings aren't really very accurate.

My HDPVR recording has been, other than caused by my STB, very stable. This Scientific Atlanta STB I have from the cable company causes me nothing but grief about every couple weeks. My HDPVR keeps on trucking though.

[jerryt]

Originally Posted by tomfisk

noticed that the output from the DCH-6200 on HD channels was initially not stable after tuning (using the remote to tune the channels). After some experimenting I found that tuning to a non-HD channel, then an HD channel produced a consistently stable output.

With this in mind, I wrote a script that uses firewire tuning (channelw.exe) to tune to a non-HD channel, waits 10 seconds, then tunes an HD channel when my system comes out of standby (typically 4 minutes before a scheduled recording).

Very cool, great job.

Could you change the delay in sageproperties, that sets amount of tuning time before a recording starts and get the same effect?

Or is tuning a SD channel first the only way to get a stable HD channel?

[tomfisk]

Originally Posted by jerryt

Very cool, great job.

Could you change the delay in sageproperties, that sets amount of tuning time before a recording starts and get the same effect?

Or is tuning a SD channel first the only way to get a stable HD channel?

I guess my thought was that when experimenting with Total Media that SageTV was out of the loop and that the stability of the HD output had more to do with the DCH-6200. In my naivety I was thinking that once an unstable HD signal was sucked up the HD-PVR that it wasn't able to recover cleanly...

[mistergq]

Okay, I switched out the set top box that I was having audio problems with. Well, all my problems are gone. No more video artifacts.

Overall, I find this driver to be very stable. SPDIF Audio works with the FIOS Box.