HD PVR version 1.0.5.4 Beta

[SHS]

http://ftp://ftp.shspvr.com/download/wintv-hdpvr/hdpvr1.0.5.4beta.zip
Post any problem have rigth here
Also I upload a newer ver IRBlaster
http://ftp://ftp.shspvr.com/download/wintv-hdpvr/irblast.exe

[cat6man]

hi shs,
any release notes re: functionality?

[SHS]

No release notes sorry

[tledford]

FWIW, the device wouldn't work at all with this beta driver in my setup.  Running Vista Ultimate x64 and my 1212 is a Rev C1.

Specific results:  After installing 1.0.5.4 beta drivers by running HcwDriverInstall.exe as "Adminstrator" and rebooting, the device is unrecognized by Windows.  Device shows up with a yellow exclamation point in Device Manager and neither the ArcSoft capture software nor SageTV "finds" the device (naturally, given Windows doesn't, either).

Used System Restore to drop back to 1.0.5.3 and all is well.

YMMV.

[dhnj]

http://ftp://ftp.shspvr.com/download/wintv-hdpvr/hdpvr1.0.5.4beta.zip
Post any problem have rigth here
Also I upload a newer ver IR32
http://ftp://ftp.shspvr.com/download/wintv-hdpvr/ir32.exe

Works fine with XP SP 3. Rev. C2.
What is new is when you press the Format Setting Button:
New Quality Meter with Good Better & Best Scale.
Tested with Default setting 9.0 works just as 1.0.5.3

[bloodydrake]

http://ftp://ftp.shspvr.com/download/wintv-hdpvr/hdpvr1.0.5.4beta.zip
Post any problem have rigth here
Also I upload a newer ver IR32 and IRBlaster
http://ftp://ftp.shspvr.com/download/wintv-hdpvr/ir32.exe
http://ftp://ftp.shspvr.com/download/wintv-hdpvr/irblast.exe

problem with the ir files
irblast.exe is the irblaster program 7.1.26273
ir32 as well is the irblaster program 7.1.26365

neither are the ir program ..which is the right version for the blaster file?
sounds like a packaging mix up

[SHS]

Yes your rigth there was a mix up
The latest IR32 2.57.26021 which come on all ver HD-PVR CD and there no new one

[falcomadol]

In the encoder properties, peak variable mode and average variable mode are replaced by "Variable Bitrate" with only one bitrate slider.  Which mode is this comparable to?

-edit-

Looks like it's more like Peak Variable, I don't know where it is maxing out (presumably at 20, like before), but the file sizes are comparable on comparable content to what I was getting using Peak with both sliders set to the maximum.

[SHS]

falcomadol take the time read this
http://en.wikipedia.org/wiki/Variable_bit_rate

[falcomadol]

falcomadol take the time read this
http://en.wikipedia.org/wiki/Variable_bit_rate

I'm familiar with what variable bit rates are, I was asking about the specifics of the change in the drivers.  I'm not the one who originally tagged the modes that way.

[dhnj]

http://ftp://ftp.shspvr.com/download/wintv-hdpvr/hdpvr1.0.5.4beta.zip
Post any problem have rigth here
Also I upload a newer ver IR32
http://ftp://ftp.shspvr.com/download/wintv-hdpvr/ir32.exe

Works fine with XP SP 3. Rev. C2.
What is new is when you press the Format Setting Button:
New Quality Meter with Good Better & Best Scale.
Tested with Default setting 9.0 works just as 1.0.5.3

I have just found that the 1.0.5.4 Beta under XP Pro SP 3 causes severe system faults & reboots,
on 2 Computers. I have now gone back to 1.0.5.3 version drivers.

[SHS]

dhnj make your mind frist say it work and it not?.
For me it works fine with XP SP3 and I also have Rev C2.

[dhnj]

dhnj make your mind frist say it work and it not?.
For me it works fine with XP SP3 and I also have Rev C2.

As 1.0.5.4 was a Beta release I did give it a try since Jan. 4, 2009.
Few days ago the Computer was re-booting in the middle of a capture
& was reporting system faults. Used a second computer with 1.0.5.4 Beta drivers &
got the same results. Had to remove all Hauppauge,  Arcsoft software together
with HCWCLEAR. Re-installed 1.0.5.3 drivers & TME 1.0.9.6. Now the system is
running stable. I am only reporting my experience.

[SHS]

how long was your recording when it crash?.

[dhnj]

how long was your recording when it crash?.

At 5, 8 & 18 minutes.
As you are not having any problems runing XP SP3 with 1.0.5.4 Beta,
I think it may be due to hardware & other software installed.