PVR150 Timestamp issue - new drivers.

[sub]

Sorry, I dont know. Its not something I've come across.

[UncleJohnsBand]

sub,
I just upgraded to the 43.24054. (I have 2 PVR500MCE's.) I haven't done any long-term testing but now see something that I'm almost certain wasn't there before.
Watching LiveTV or recordings, if I hit any button (such as hitting Pause) that causes the picture part of the screen to be 'grayed' (darkened) for a while, I see flashes of white horizontal lines, apparently randomly around the screen. There a perhaps 1-5 flashes per second and each flash is a fraction of the screen width. Once the 'grayed' screen goes to normal, the white flashes disappear.
Any thoughts? Is the 'graying' a software function or is it hardware or firmware?

Thanks .... Bob

You can try the newer drivers that are now available over shspvr.....

Driver Release 2.0.43.24073.PreRelease (03/14/06)
* Fixed issue which yielded no audio and/or video problems on some systems. Problem was rare but nevertheless possible.
* Experimenting with improved tuner picture quality under some circumstances on PVR500.

[b00sfuk]

If anyone wants to try then I've just noticed there are even newer beta drivers (2.0.43.24103) at http://www.hauppauge.com/pages/support/s...vr150.html in the beta section.
Release notes: Driver Release 2.0.43.24103 (04/13/06)

* Improved Firmware load time.
* Fixed issue which yielded no audio and/or video problems on some systems. Problem was rare but nevertheless possible.
* Improved Vista support/compliance.
* Improved audio initialization. FM volume correct on first run if this is the first source.
* Fix for lack of audio on some TV channels when using the WinTV-PVR-150 and WinTV-PVR-500 under Windows Media Center Edition, Linux, SageTV or BeyondTV:
* Fix for audio problems on some computer systems where a "popping" is heard in the audio, or when the recorded audio is distorted.
* Fix for line-in audio problems, where some audio sources (VCR's or DVD players) recorded distorted audio.

[UncleJohnsBand]

If anyone wants to try then I've just noticed there are even newer beta drivers (2.0.43.24103) at http://www.hauppauge.com/pages/support/s...vr150.html in the beta section.
Release notes: Driver Release 2.0.43.24103 (04/13/06)

* Improved Firmware load time.
* Fixed issue which yielded no audio and/or video problems on some systems. Problem was rare but nevertheless possible.
* Improved Vista support/compliance.
* Improved audio initialization. FM volume correct on first run if this is the first source.
* Fix for lack of audio on some TV channels when using the WinTV-PVR-150 and WinTV-PVR-500 under Windows Media Center Edition, Linux, SageTV or BeyondTV:
* Fix for audio problems on some computer systems where a "popping" is heard in the audio, or when the recorded audio is distorted.
* Fix for line-in audio problems, where some audio sources (VCR's or DVD players) recorded distorted audio.

These drivers are being tracked in this thread......the newest drivers are actually 24108 which are the same as 24103 except Wondows 2000 support has been added back in.

I should note that I have been experiencing a sporadic problem with the 24108 drivers. I occasionaly get spots in recordings where the video jumps in fast forward speed for a second or five.....this did not occur in the 24054 drivers.

[GoodGuys]

After installing the drivers, you'll need to add the following registry settings:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\hcwPP2\DriverData
"HcwTimeStampIssue1"=dword:00000001
"HcwTimeStampIssue2"=dword:00000000

I don't seem to have a DriverData key under hcwPP2!

Help?

Thanks,

GGF

[jksmurf]

ggf,

I think when sub said

you'll need to add the following registry settings:

he meant you'll need to add the following registry settings.

i.e. right click create new Dword, and name it as HcwTimeStampIssue1.
repeat for the other one. Then right click the key and choose to edit the key value change it to 1 and 0 respectively.

k.

[sub]

I meant you'd need to add the specific HcwTimeStampIssue1 & HcwTimeStampIssue2 settings, but would have expected the DriverData key to already be available. That said, I dont know exactly what this key is used for, so it might be valid that it is not there in some situations.

[jksmurf]

AFAIR, I "think" I had to add these keys, then the values. Perhaps someone else can confirm they had to add it too, so that ggf doesn't feel like he is missing out on something (poor wee pumpkin) :-)

k.

[GoodGuys]

Thanks, jksmurf, sub.

My concern was due to the fact that in my recent fiddling with the thing I noticed that I did have the key. However, I spent most of my time yesterday reinstalling the system from scratch - again :-( and now it isn't there.

I think the difference is that yesterday I didn't install the 150 stock drivers, but went directly to install the 24073 version (which works for me, and I'm not taking chances with any other version unless I have to - the Wife Acceptance Factor has taken a big hit these past few days).

So sub - do you think I should simply add this key?

GGF

[sub]

I dont know. I guess so. If you still get timestamp errors, we might need to look at another answer to that question