HD-PVR Windows drivers - what are you using?

[tvmaster2]

In my search to fix the ongoing HD-PVR mystery woes, can anyone running Windows 32/64 let me know what Hauppauge version of their driver your running, especially if it's running really well, and even better if it's being fed by either a cable set-top box, or satellite receiver.

I'm running 1.5.7.0 Why such an older version? Because it used to always work, until recently.

thanks

[Zogg]

I ran 1.5.7.0 for a long time, but upgraded a while back to 1.7.1.30059 and it has worked just fine for me on Windows 7. It records from an Arris cable STB with component inputs, stereo audio (not digital).

I can't check right now but I am 99% sure I'm also running this same driver on my HTPC as well, Win 10 also recording from an Arris STB with component/stereo.

[tvmaster2]

Originally Posted by Zogg

I ran 1.5.7.0 for a long time, but upgraded a while back to 1.7.1.30059 and it has worked just fine for me on Windows 7. It records from an Arris cable STB with component inputs, stereo audio (not digital).

I can't check right now but I am 99% sure I'm also running this same driver on my HTPC as well, Win 10 also recording from an Arris STB with component/stereo.

ok, thanks. I’ll try that one.

[mgpaulus]

I am still on Windows 7 and I am also running 1.7.30059.1.

Haven't had any glitches that I can really recall.

[tvmaster2]

Originally Posted by Zogg

I ran 1.5.7.0 for a long time, but upgraded a while back to 1.7.1.30059 and it has worked just fine for me on Windows 7. It records from an Arris cable STB with component inputs, stereo audio (not digital).

I can't check right now but I am 99% sure I'm also running this same driver on my HTPC as well, Win 10 also recording from an Arris STB with component/stereo.

Okay, I upgraded the driver to 1.7.1.30059, and it seemed to be working, until I discovered it was triggering Hauppauge’s Arcsoft Capture tool to reset that program’s Proc Amp to incorrect, overmodulated levels, which the HDPVR adopted. Happened every time I switched between tuners in Sage, so I’m back on 1.5.7.0 until I figure out why the Arcsoft Proc Amp is resetting.