PVR150 Timestamp issue - new drivers.

[wtg]

Has anyone posted a description of the symptoms caused by this timestamp issue? A couple posts mentioned something about the player showing the duration of the file to be quite a bit less than the actual duration. Is that it?

There are plenty around here. Basically, when the timestamps are screwed up the file duration shows up wrong, sometimes just a few minutes off, other times hours. FF, rew and skipping (including trying to skip commercials) would result in skipping in the wrong direction or skipping past the end of the video, making it exit. Essentially you could do nothing more than watch the video... trying to skip or even resume a previously watched video would hose up the playback. Also, depending on the tools you were using, commercial cutting often didn't work.

It was a real mess, and for those of us that experienced it, it persisted for many, many months and numerous driver releases. I got to the point I didn't think it would ever be corrected, mostly because Hauppauge wouldn't even acknowledge it. I believe sub and the folks over at shspvr.com played a role in getting the Hauppauge engineers to focus on it.

[Jeckler]

I've been experiencing this issue recently. I didn't know about this bug, but may have inadvertantly found a workaround, but not sure it could be implemented through GBPVR. I'm at work right now, so (obviously) haven't tried the fix, and in fact I don't know what driver version I currently have. My 150 is only about 2 weeks old.

If I play an affected file through GBPVR or WMP (ver.10), it may only say it's a 10 min recording (for example), even though it's actually a one hour recording. And I experience the same issue as everyone else, no skip past that mark, it'll end (in GBPVR), or go back to the beginning.
Hoever, if I play the same file in Media Player Classic, it works fine. The timestamp is correct, and I can move the slider to anywhere in the recording.

My question then is there any way for GBPVR to use the same method that MPC uses to play back a file, both recorded, and probably in timeshift mode (might as well be consistent). I have no idea how GBPVR does it, though I thought I read something about directshow and GBPVR just passes control to it for playback.
If it is possible, is it a viable solution, or just a crutch that would require a user to install another piece of software.
Just thought I'd toss it out.
On another note, is it really an issue with the driver, or the way Microsoft is interpreting the recording.

[sub]

My question then is there any way for GBPVR to use the same method that MPC uses to play back a file, both recorded, and probably in timeshift mode (might as well be consistent). I have no idea how GBPVR does it, though I thought I read something about directshow and GBPVR just passes control to it for playback.

Its better to have Hauppauge fix the problem rather than me wasting time coming up with work arounds for problems that only occur on the PVR150 (and to lesser degree with PVR500).

On another note, is it really an issue with the driver, or the way Microsoft is interpreting the recording.

Yes, it is a driver bug. It only occurs with Hauppauge PVR150 (of PVR500) devices. Hauppauge looked at many recordings from GB-PVR and other apps, and confirmed that the timestamps were being reset mid stream - which is why they provided these drivers with registry settings to fix the problem.

[Jeckler]

Well,it was just a thought.

I found out that my 150 came with the 2.0.43.24103 driver, but the two keys do not exist in the registry. I'm currently running Dbgview to see what happens.

[groover km]

I am pretty confident that the reg keys fix the issue; I added these with sub's help way back when and haven't had a problem (or updated drivers) since.

[pens18aj]

yep the registry entries fixed me too, with these drivers 2.0.43.24054 running a 150, and 500

[cginzel]

same here!

[Jeckler]

So far, so good. I got both issues, so applied the alt keys for each. It's been about a week now.

[Mr. Cantrell]

Can I use the newer drivers for this fix, or should I downgrade to the older drivers?

I have the latest drivers installed from the Hauppauge site and I've entered the Registry keys, is that going to fix it, or do I need the specific versions listed in this thread?

TIA as usual.

[sub]

I'd guess so, but I dont know for sure.