MPEG-2 Decoder Hell

[teegee420]

Recently for reasons unknown to me I began experiencing a problem where large mpeg-2 files(PVR captures >3gb) display the incorrect time code during playback. The only player that isn't affected is Media Player Classic, as I believe it has its own built-in decoder. Normally I wouldn't care about this problem at all, only it is now affecting my use of MPEG VCR. I have a file that's 1hour 23minutes and Womble only shows it as being 23minutes. I have another one that's over 2hours and Womble only lets me seek the first 20 seconds.

I have been using Direct Show Filter Manager and switching out various decoders like FFDSHOW, Intervideo, Cyberlink, Ligos, and Elecard but the problem persists. The last decoder that I remember working was Nero's, only I can't get it to register, even if I set the priority to "highest". I'm out of ideas. Re-installing Windows isn't an option. I have too much stuff on the drive that I can't move just yet. I'm thinking about unregistering all of my Directshow filters. Any other ideas?

[Krispy Kritter]

I believe VLC has its own mpeg2 decoder. You could install that long enough to see if it has the same issue.

It could just be corrupt files.

[The_Doman]

Recently for reasons unknown to me I began experiencing a problem where large mpeg-2 files(PVR captures >3gb) display the incorrect time code during playback.

With what application/card did you capture your recordings?
The problems sounds typical like the well known problems with the Hauppauge 150/500 cards.
Sometimes (or often) they can produce corrupted MPEG files..
See also:
SHSPVR: Topic: Captured video can't be edited

[teegee420]

I believe VLC has its own mpeg2 decoder. You could install that long enough to see if it has the same issue.

It could just be corrupt files.

I already have VLC and it's being thrown off as well. My biggest problem is the inability for these files to be edited. Thanks anyway though.

Recently for reasons unknown to me I began experiencing a problem where large mpeg-2 files(PVR captures >3gb) display the incorrect time code during playback.

With what application/card did you capture your recordings?
The problems sounds typical like the well known problems with the Hauppauge 150/500 cards.
Sometimes (or often) they can produce corrupted MPEG files..
See also:
SHSPVR: Topic: Captured video can't be edited

Thanks for pointing me in the right direction. It never ocurred to me that the files themselves might be bad. I'll do some more tinkering and come back later.

[teegee420]

Recently for reasons unknown to me I began experiencing a problem where large mpeg-2 files(PVR captures >3gb) display the incorrect time code during playback.

With what application/card did you capture your recordings?
The problems sounds typical like the well known problems with the Hauppauge 150/500 cards.
Sometimes (or often) they can produce corrupted MPEG files..
See also:
SHSPVR: Topic: Captured video can't be edited

ProjectX seems to have solved my issue with the problematic files. I did some minor cuttings and they're now seekable with Womble. Thanks again.

[The_Doman]

ProjectX seems to have solved my issue with the problematic files. I did some minor cuttings and they're now seekable with Womble. Thanks again.

Yeah, nice you were able to fix it...
But again, what is the source of your recordings?
Is it a Hauppauge PVR card?

[teegee420]

Yes, the 150. I figured you looked at my computer specs. I'm going to try lowering the bitrate on my default capture profile in WinTV 2000 and see if I get another screwy file. I won't need to do another 2hour capture until Sunday, so we'll see how that goes.

[The_Doman]

Yeah, my bad , not even thought about looking at your PC specs...

But about the corruptions, It sure must be some combination of drivers and hardware.
I have here now 3 PVR150's in 3 seperate PC's.
The PC with a celeron 1300 has NEVER made one corrupt recording with any driver I tried, but another PC I setup recently (old AMD 700) creates corrupted recordings almost 1 out of 2 times I use it...
My 3rd PC (P4,3,2 Ghz) very seldom makes a corrupt recordings, turning off HT seemed to help a bit..

See also:
Hauppauge UK: POLL - WINTV2000: Do you get "freezes" when recording?
SHSPVR: PVR150MCE and older BX board: No Boot??

There are quite a few of other people on the SHSPVR and GBPVR forums having the same issue....

[vhelp]

Evening everyone.

teegee420,

- I have an idea to nip this. Can you upload a sample that does this ??

If the mpeg's length matters, (to illustrate) you can do another capture, but
use a much lower bitrate, because *this time* we are not looking for quality,
we are looking for analizing the problem. Oh yeah.. back to my point..

What I'm on about is this. If we all have a chance to review it in *OUR OWN*
mpeg players, we might be able to determine that its your fault or your decoder
firmware that is at fault. See, if some us have no trouble with the time issue,
then its safe to assume your huntch was right, that it's a decoder thing. And
next steps would be to find *WHO* is using *WHAT* decoder. BTW -- You know,
just because your utility can desable a given decoder or codec, does not mean
that it is doing so. If the calling software bypasses the normal route, you
can be digging for horse shoes till the cows come home, and still not resolve it.

Please consider the above if it is not too much trouble on your end

Good luck,
-vhelp 4065

[teegee420]

Vhelp, I appreciate the offer, but it seems I only have this problem with captures longer than an hour. My bandwith is far too miniscule to even think about uploading something that big(16 KB/s up). As I stated earlier, I'm going to lower the bitrate for my next capture. I think I'll have it record for a couple of hours tonight just to see if it's still a problem. I'll post again in the morning when I check on the file.

[teegee420]

Apparetnly lowering the bitrate didn't help. I recorded a couple of hours and both Virtualdub MPEG2 and Womble only recognize an hour and a half, and one hour respectively. On the plus side, Womble does allow me to seek the entire file so I suppose that's all that matters to me. Maybe I'll try using different drivers and do another capture tonight.

[The_Doman]

- I have an idea to nip this. Can you upload a sample that does this ??

What I'm on about is this. If we all have a chance to review it in *OUR OWN*
mpeg players, we might be able to determine that its your fault or your decoder
firmware that is at fault. See, if some us have no trouble with the time issue,
then its safe to assume your huntch was right, that it's a decoder thing. And
next steps would be to find *WHO* is using *WHAT* decoder.-vhelp 4065

No need to bother with that....
It is a WELL KNOWN issue with the (newer?) Hauppauge cards....
Sometimes (or often) it will just produce a corrupted MPEG file which needs to be fixed /cutted with ProjectX..