PVR150 Timestamp issue - new drivers.

[donschjr]

I've tried all the drivers in this thread and the registry settings and still have the timestamp problem. I finally gave up and quit using my card to record. I check back every once in a while to see if sonething new comes up.

[sub]

I dont remember any other reports of these drivers and registry setting not solving the problem, so its worth double checking you did everything correctly.

[donschjr]

I've done the every driver in this thread and applied the registry settings manually and with the on from the wiki and nothing has worked. I've totally given up. I've gone as far as uninstalling my card and wiped everything from the registry using the instructions for uninstall from here:
http://www.shspvr.com/smf/index.php?topic=10830.0

[sub]

Do you know for sure it was the timestamp problem? What symptoms were you seeing?

[donschjr]

When I record shows an hour in length they show as 37 minutes long. The whole show is there and is watchable as long as I don't try to fast foward thru the commercials. It all worked fine untill I upgraded to the version of gb-pvr before the current one.

[sub]

When I record shows an hour in length they show as 37 minutes long.

Yeah, that sounds like the sort of thing. Sorry, I'm not sure.

It all worked fine untill I upgraded to the version of gb-pvr before the current one.

I doubt its at all related to the release. Tons of other user used their PVR150's for ages, then started getting it at some random point over the last year or so, and assumed it was the last GB-PVR release, only for it to be fixed with these driver settings. Hauppauge had look at sample files and determined the PVR150 was resetting the timestamps several times during the recordings. Definitely a Hauppauge problem rather than GB-PVR.

[UncleJohnsBand]

When I record shows an hour in length they show as 37 minutes long. The whole show is there and is watchable as long as I don't try to fast foward thru the commercials. It all worked fine untill I upgraded to the version of gb-pvr before the current one.

Not sure if you read all the info that is on the wiki concerning this issue or not....

But here is an extended message concerning the timestamp issue that is available in a file that hauppage put out last August:

In an effort to investigate reports of timestamp resets in MPEG files created by the PVR 150 and PVR 500
we've put together the following information. We believe that this issue is highly system specific,
affecting limited environments [and of course none of them are ours ]. It is not recommended that you
try any of these approaches if you are not having an issue on your system.


Driver Version 2.0.43.24052 (and, presumably, later) will output "trace" information under 2 different
circumstances (known as TimeStampIssue1 and TimeStampIssue2). The trace info will contain either
"TimeStampIssue1" or "TimeStampIssue2" as a part of the message.


The following registry patch files are included here. The usage is described following...
HcwAmity2_TimeStampIssue1_Default.reg
HcwAmity2_TimeStampIssue1_Alternate.reg
HcwAmity2_TimeStampIssue2_Default.reg
HcwAmity2_TimeStampIssue2_Alternate.reg


ABOUT TIMESTAMP ISSUE 1
If you see a "TimeStampIssue1" trace message you should try applying the
"HcwAmity2_TimeStampIssue1_Alternate.reg" patch (according tothe instructions below).
If this does not help you should restore the driver to its default state by
applying the "HcwAmity2_TimeStampIssue1_Default.reg" patch.


ABOUT TIMESTAMP ISSUE 2
If you see a "TimeStampIssue2" trace message you should try applying the
"HcwAmity2_TimeStampIssue2_Alternate.reg" patch (according tothe instructions below).
If this does not help you should restore the driver to its default state by
applying the "HcwAmity2_TimeStampIssue2_Default.reg" patch.


VIEWING THE TRACE MESSAGES
You can view any trace messages if you are running a freeware utility such as DbgView from SysInternals (now microsoft)
(available at http://www.microsoft.com/technet/sysinternals/Miscellaneous/DebugView.mspx).
PLEASE NOTE that you must be running dbgview at the time the reset happens (opening it later will not
display information for past events).


PLEASE NOTE THAT TO APPLY ANY REGISTRY PATCHES YOU MUST DO THE FOLLOWING...
1. Open the reg file to by applied by double clicking on it.
(Windows actually refers to it as "Merging" rather than "Opening" the file.)
2. Respond "Yes" when Windows asks if you are sure you want to add the information to the registry.
3. Reboot your computer. Changes will not take place until you reboot.

[pastro]

Just for the record, I am using the newest beta drivers and I have not applied any patches since I upgraded to winxp. I plan on running without the patches to see if the timestamp problem shows up again on my system.

[DrDDT]

Hi,

I'm using the latest driver the wiki suggests, and in debugging problems with the transcode script, I think I might have the timestamp problem:

Code:

F:\downloads\Recorded TV\Toppers in concert 2007>"c:\Program Files\devnz\gbpvr\m
pgtx.exe" -i Toppers2.mpg
Toppers2.mpg
  Mpeg 2 Program Stream File [Video/Audio]
  Muxrate : 10.41 Mbps
  Estimated Duration: 02:19:58.80s
  Checking all time stamps (This may take a while.) ...
        Time stamps jumped from 6607.940700 to 418.920400 at position 12b4a000
        Time stamps jumped from 41759.419156 to 591.440400 at position 1a6cd000
        Time stamps jumped from 16126.602578 to 1267.840400 at position 38ab3000

        Time stamps jumped from 74125.587178 to 1602.480400 at position 47973000

        Time stamps jumped from 76833.007256 to 1774.480400 at position 4f477000

        Time stamps jumped from 7944.800178 to 2170.440400 at position 60fc3800
        Time stamps jumped from 67630.114367 to 2256.960400 at position 64d92000

        Time stamps jumped from 2266.320400 to 142.564744 at position 6547f015
        Time stamps jumped from 60202.000678 to 2805.320400 at position 7d603800

        Time stamps jumped from 89486.317033 to 3857.000400 at position ac5b5800

        Time stamps jumped from 49123.134933 to 6536.400400 at position 1240be00
0
        Time stamps jumped from 10672.134356 to 6564.280400 at position 1254c900
0
        Time stamps jumped from 54552.310033 to 6726.680400 at position 12c8cb80
0
        Time stamps jumped from 7363.080400 to 6897.265067 at position 148fb5815

        Time stamps jumped from 43657.329867 to 7648.720400 at position 155c3800
0
        Time stamps jumped from 24060.474689 to 7754.800400 at position 15a80b80
0
        Time stamps jumped from 76092.243289 to 7828.160400 at position 15dc9f00
0
  Time line is interupted at 17 times.
  That means at these points the time stamp is earlier than the previous one.
  You may have problems in joining and splitting this file, sorry.
  Aspect ratio 4/3 (TV)
  Not interlaced, chroma format: 4:2:0
  Size [720 x 576]     25.00 fps    8.25 Mbps
  Audio : Mpeg 1 layer 2
  224 kbps  48000 Hz
  Stereo,  No emphasis

Is this the timestamp problem?

[sub]

I dont know for sure, but it sounds like it. Did you remember to apply the registry settings and reboot?