An open letter to SageTV and Hauppauge management

[jack_leach]

Originally Posted by stanger89

About all I really know is all my problems went away around the time I updated to the next to most recent WHQL drivers

I'm not familiar with WHQL drivers, but a quick Google on the acronym appears to be related to video drivers. Is that correct? If I'm not using SageTV client software and only viewing video with HD-200 extenders, than does that mean that I needn't be concerned about WHQL drivers? Thanks!

Jack

[MeInMaui]

WHQL = Windows Hardware Quality Labs testing (wikipedia link)

In this case it refers to the certified HD-PVR drivers.

[PGPfan]

WindowsHardwareQualityLabs and it's for any hardware/drivers.

-PGPfan

[mayamaniac]

Originally Posted by jack_leach

I'm not familiar with WHQL drivers, but a quick Google on the acronym appears to be related to video drivers. Is that correct? If I'm not using SageTV client software and only viewing video with HD-200 extenders, than does that mean that I needn't be concerned about WHQL drivers? Thanks!

Jack

He's talking about official drivers for the HD-PVR. Hauppauge releases beta drivers often and made them freely available to download and install. But in most cases, it is best to install official (WHQL) drivers.

[GKusnick]

Basically, WHQL certification is Microsoft's Good Housekeeping Seal of Approval for drivers deemed reasonably well tested and bug-free.

[stanger89]

Originally Posted by mayamaniac

He's talking about official drivers for the HD-PVR. Hauppauge releases beta drivers often and made them freely available to download and install. But in most cases, it is best to install official (WHQL) drivers.

Or even more to the point of my meaning, the first several sets of drivers for the HD PVR were beta/not-WHQL. IIRC the 1.0.5.3 were the first WHQL ones.

[jack_leach]

I'm always impressed with the helpful replies on this forum. Thanks!

So is 1.0.5.3 the most current WHQL driver?

Jack

[stanger89]

Actually 1.0.5.6 is the most recent, but 1.0.5.3 is working for me and I don't feel like finding out if 1.0.5.6 do too

[mayamaniac]

Yeah, why mess with it when it is working perfectly fine. Heck, not needing SPDIF, I'm still using the driver from july last year when I initially installed the HD-PVR. It has been running 24/7 nonstop and without issues since.

[waynedunham]

Originally Posted by jack_leach

Thanks Wayne! (sorry for the delayed response). You gave me several good tips that might help me out here.

Jack

Hopefully something there might help you figure out what's happening to you.

[waynedunham]

Originally Posted by Chriscic

If you're able to get the HD-PVR working again with a server reboot, WITHOUT power cycling the HD-PVR itself, then you're encountering a different issue than most of us; I always have to power cycle the HD-PVR itself. A server reboot won't fix.

I have actually had different problems at various times. There are times when a reboot of the server is necessary (Java Heap overload and some Java components stop working).
Some times a power cycle of the HD-PVR works without rebooting the server. I'm not sure exactly what happens, but my best guess is a Java heap overload that only kills the HD-PVR and/or the drivers for it. This is usually the first thing that dies when the Java heap overloads and is then followed by other things within SageTv.
Some times I need to shut down the computer, power off the HD-PVR for 15 seconds or so, turn the HD-PVR back on and wait for it to finish its self-test/startup and then power the computer back on.

Usually it is the first problem. I rarely try the power cycle of the HD-PVR without rebooting the server and sometimes when I do it leads to the 3rd problem where I have to power cycle the HD-PVR and shutdown/reboot the server.

[stanger89]

Sounds like you really need to contact SageTV support with that information.

[Chriscic]

Just curious if anyone if engaging with Sage support on the lock-ups yet.

I *finally* got my setup moved over to my Dish install, and just had things about working this morning when apparently my WHS system drive started flaking out. Possible something came loose when I moved the server downstairs, although I'm not optimistic on that since it ran all night ok.

As soon as things are working (probably after a drive replacement and WHS reinstall), I'll be reaching out to Sage support myself. I'm convinced it's not a Sage but rather a Hauppauge issue, but the Sage folks are generally more helpful so I'll start there.

[Chriscic]

No one engaging with Sage on this? Really?

[Skirge01]

I updated the drivers to 1.0.5.301 on both HD-PVRs since my last post. I still have one HD-PVR using the stereo connections and outputting the same on my DirecTV box and the other using SPDIF with DD output on the other DirecTV box. I hadn't NOTICED any stop/start instances in about a week or two, so I turned on debugging about 3 days ago and am keeping an eye on the log files for any "halt" messages. So far, no instances at all. I'm going to let this go for another week or two with debugging turned on and see if any "halts" show up. If not, I'll swap the stereo and DD outputs on the DirecTV boxes and see if anything changes. If nothing happens there for a couple of weeks, I'll re-enable DD on both boxes.

[HelenWeathers]

I am using my HD-PVRs with DirecTV STBs. I've been using the Hauppauge 1.5.6.0 beta HD-PVR drivers since the 27th of April and am having no problems with my C2s using DD via S/PDIF. From the posts I've read in numerous forums it seems that the DirecTV boxes are very stable in their output thru S/PDIF. I've used DD as default and S/PDIF with these boxes (HD-PVR & DTV) since the first S/PDIF drivers were released in (I think) October.

I do reboot my system daily though as a preventive measure.

[Skirge01]

I don't believe in reboots. At least, not to prevent a problem that may or may not happen. I have a server on a UPS for a reason: it's supposed to be UP!

[Brent]

I had trouble with the 1.5.6.0 beta when I first installed it. SageTV gave a "no signal" when I tried to tune any of the HD-PVR channels.

But after a tip on the forums and a suggestion from SageTV Support, I re-installed the 1.5.6.0 driver, shut off the HD-PVR, rebooted, started SageTV (without starting TME or anything else) and then powered on the HD-PVR.

Since then all has been smooth sailing. I'm getting S/PDIF and no lockups (didn't really have lockups before though) so knock on wood, the latest SageTV beta with the latest HD-PVR beta seem to have found the way.

Only problem I have now is my stinky cable box that likes to shut off every once in a while. Once I get that figured out my HD-PVR should be as good as my beloved HDHR tuners (except for the slower IR blasting).

EDIT: And I don't do reboots unless there is a reason. It has to run on its own without my constant care or it won't survive long in my home.

[Skirge01]

See... now that really gets to me. From what I've read here on the forums, it seems like folks using a cable box with the HD-PVR seem to have much better luck getting DD, compared to DirecTV folks.

[Brent]

Originally Posted by Skirge01

See... now that really gets to me. From what I've read here on the forums, it seems like folks using a cable box with the HD-PVR seem to have much better luck getting DD, compared to DirecTV folks.

I wonder what could be different between capturing from a DirecTV box versus a cable box though.