pvr150 video timing bug

[wtg]

Well, it sounds similar. I've found I can play the file fine but it's duration is shown completely wrong. For instance, I recorded a 3 hour movie but it's duration and time line in gbpvr and WMP shows as 6 minutes. If I attempt to skip, FF or anything, the position in the file gets completely screwed up because of the messed up timing. This happens due a bug in the pvr150 drivers, but only about 1 out of 4 recordings for me.

If this sounds about right but you can't play the entire file it might just be a difference with your decoder. The decoders I've tried keep playing it but can't position within the file correctly. If you're not sure, it certainly couldn't hurt to try one of the solutions posted here. I've found the easiest and fastest way to fix the file is to use mencoder. The following command line will re-write the file with the correct timestamps:

mencoder -of mpeg -ovc copy -oac copy input.mpg -o output.mpg

Good luck,
Tim

[pens18aj]

same issue here does, a certain pvr150 driver fix the issue? even if it is an older one? Currently running 2.0.35.23258

Also some times see where the video will just always fastforward even if you do not hit the button.

[mroy79]

The same timestamp problem has been popping up more and more for me. I tried the mencoder option as outlined in a previous post, however instead of having the length of the show displayed in GBPVR as 6:32 for example, it's now just 0:00. I've tried two different versions of mencoder, one downloaded from the GBPVR plugin page and another downloaded from the official site, both have the same results. Any ideas? I think mencoder could be a great option to solving this intermittent problem.

[wtg]

Hmm, I haven't had any trouble with mencoder. Does this happen for all files you try, or just one? It sounds like some there's a more serious problem with the file than most have.

If you haven't already, you might try the demux/remux option discussed on the wiki and some other threads around here. That worked for me but isn't quite as convenient as the mencoder option.

[mroy79]

At least after mencoder's handled the file it doesn't want to jump around when watching it in GBPVR. I want to avoid a demux/remux since it's a more demanding process. With a timestamp of 00:00 the only things I'm missing out on are the ability to pause, fast forward, having a comskip marked file and skipping commercials. While unfortunate, it's bearable.

I had 2 cards in my system a PVR150 and a MCE PVR 150. The PVR150 died and a replacement will be here in 2 days from Hauppauge. The problem didn't come up nearly at all when both the cards functioned and the PVR150 was used the most and the MCE PVR 150 only got the leftover shows when the PVR150 was already recording something. Even then I never really noticed any timestamp issues. So I'm going to wait and see before taking the next step with this. I'm just glad it can get shows to the point where they're watchable again.

[pens18aj]

Well, it sounds similar. I've found I can play the file fine but it's duration is shown completely wrong. For instance, I recorded a 3 hour movie but it's duration and time line in gbpvr and WMP shows as 6 minutes. If I attempt to skip, FF or anything, the position in the file gets completely screwed up because of the messed up timing. This happens due a bug in the pvr150 drivers, but only about 1 out of 4 recordings for me.

If this sounds about right but you can't play the entire file it might just be a difference with your decoder. The decoders I've tried keep playing it but can't position within the file correctly. If you're not sure, it certainly couldn't hurt to try one of the solutions posted here. I've found the easiest and fastest way to fix the file is to use mencoder. The following command line will re-write the file with the correct timestamps:

mencoder -of mpeg -ovc copy -oac copy input.mpg -o output.mpg

Good luck,
Tim

ok I have this issue I took a file and ran the command above it went from a 1 sec file to a 5:26 minute file. It now justs looks like I am constantly hitting the fast forward button. I am using NVIDIA PureVideo Decoder on machine but using MVP to play it. do you think I need to go back to a certain driver version or use a different decoder?. :confused:

[wtg]

ok I have this issue I took a file and ran the command above it went from a 1 sec file to a 5:26 minute file. It now justs looks like I am constantly hitting the fast forward button. I am using NVIDIA PureVideo Decoder on machine but using MVP to play it. do you think I need to go back to a certain driver version or use a different decoder?. :confused:

I don't know. I'm using the latest non-beta drivers from Hauppauge's website.

Have you had any luck fixing the file with other utilities? In the Community Announcements forum there's a similar thread that has the download links to retime.bat and associated utilities. It'll demux and remux the file. This worked for my originally, but it's slower and a multi-step process so you can't immediately start watching the resulting video. It did work however, and I wonder if this might work more reliably for you.

My experience is limited with mencoder, but using the latest build optimized for my Athlon, it works great. I don't know if your problem is just with your version of mencoder or if it's because your input file is worse off than the ones I've corrected.

Post back with your results.

[pens18aj]

ok, I have manually ran the
"mencoder -of mpeg -ovc copy -oac copy input.mpg -o output.mpg"
a few times and it has fixed my files each time so that one file i was having trouble with must just have been messed up. I am now going to automate it.

Thanks for the help ,still sucks that we can not just get good drivers so we do not have to do this.

[ww4397]

I just came upon this thread today. I'm having occasional problems, too. I downloaded PVAStrumento 2.1 as suggested early on in the thread. I had two problem files saved on the HDD and attemped to "fix" them with PVAStrumento 2.1.

PVAStrumento, using default parameters, split my files into pieces. Looking at the log, the splits occured because of "number of audio tracks has changed". Here are a couple of lines from the log:

"New program stream : \Dateline NBC_20051216_20002200.mpg
Number of audio tracks has changed. Splitting."

I took the split files (3 .mpg's) and joined them with TMPGEnc and the end resultant file was fine.

The same thing happened with my second problem file.

As others have reported, my original files would play fine, but my commercial removal programs just couldn't deal with them. I wonder if the tv networks are sending "extra" audio streams in an attempt to mess up people running commercial detection programs? Maybe they know some tuner cards can't deal with it well?

[groover km]

The fastest way I have found is to use PVAStrumento (available from the hauppauge.com support page) and to run the file through that - it usually takes about 10mins per hour of video. Make sure that you deselect "split on audio change" as well.

If you deselect these options it stops PVAS from splitting the file.

Incidentally, you make an interesting suggestion; I have wondered the same thing too regarding 'extra' audio streams. It seems that I get bad headers more on some channels than others, and when I run them through PVAS it always reports audio stream changes....