Skip problem/Screen display

[HuskerGrad]

I have a problem from time to time when I hit the forward skip (>|) several times to skip several minutes. After hitting the button the second or third time, the playback keeps skipping and I cannot get it to resume normal playback. This happens when watching Live TV that is being recorded or watching a recording. The only way to stop it is to hit the stop button and then go back to watching it again.

This brings up another question. When watching a recorded program, is there a way to get to a specific point in it or jump ahead a large amount of time. I was watching a football game and this happened when I tried to skip through halftime. When I had to start watching it again, it started from the beginning and I didn't want to have to jump ahead one minute at a time.

Also, after hooking up my PC to the TV, whenever it wakes up, the screen display is such that only part of the screen is shown on the TV. I did not have this problem when using a monitor. I can only see about the top half. It is if the resolution has been changed and the new resolution won't fit on the screen. After rebooting the PC, it is fine until it goes to sleep the next time. It is not a GB-PVR issue since it occurs even if GB-PVR is not running.

I am running v1.2.13 on a 2.8GHz PC with an NVidia GeForce FX5200 128MB video card. It is hooked up to my TV (32-inch Sony) to the S-Video in.

[sub]

I have a problem from time to time when I hit the forward skip (>|) several times to skip several minutes. After hitting the button the second or third time, the playback keeps skipping and I cannot get it to resume normal playback. This happens when watching Live TV that is being recorded or watching a recording. The only way to stop it is to hit the stop button and then go back to watching it again.

I'm not aware of that happening for anyone else, but the only way I could see it happening is if that key continues to be pressed. Are you sure they key isnt sticking? or maybe you're using a wireless keyboard?

This brings up another question. When watching a recorded program, is there a way to get to a specific point in it or jump ahead a large amount of time. I was watching a football game and this happened when I tried to skip through halftime. When I had to start watching it again, it started from the beginning and I didn't want to have to jump ahead one minute at a time.

You can type a number of minutes then press skip. 16-Skip will jump 16 minutes.

[HuskerGrad]

I'm not aware of that happening for anyone else, but the only way I could see it happening is if that key continues to be pressed. Are you sure they key isnt sticking? or maybe you're using a wireless keyboard?

I am using the Hauppauge 45 key remote when it happens. I don't think the key is sticking, but I will try to get it to happen again and see if I can further isolate it.

You can type a number of minutes then press skip. 16-Skip will jump 16 minutes.

Thanks, does that work with the remote also?

One more question, is there a way to do a frame by frame advance?

[sub]

Thanks, does that work with the remote also?

Yes

One more question, is there a way to do a frame by frame advance?

No

[HuskerGrad]

I am still having the problem where skipping ahead causes it to go backwards. I have noticed that it is when I am watching a program that I am recording and the skip causes it to go to (or past) the end of the recording. It appears to start rewinding and is difficult to get it back to play mode. On a few occasions, I was able to pause and then play, but I lost the sound. The only solution is to stop watching and start over, jumping to a minute or so before the current recording point.

[sub]

Is it from an analog device like PVR150?

Or is it from a digital capture device? If so what mux are you using?

[HuskerGrad]

It is from a PVR-150. I am using the default mux.

[sub]

I'm pretty sure it'll be the PVR150 driver timestamp bug. See http://forums.nextpvr.com/showthread.php?t=14006

[HuskerGrad]

I finally got around to installing the driver for the timestamp bug fix. That seems to have fixed it. Thanks!