Log in

View Full Version : MPEG2s not opening properly in TMPGEnc


nihilObstat
10th August 2009, 05:51
I am trying to encode some mpeg-2 files (26 files, ranging from 2.5 to 10 GB in size) that I got by running VHS tapes through a Compro VideoMate Vista E900F PCI card into my desktop, which has a DualCore AMD Athlon 64 X2, 2200 MHz and 3 GB of RAM, running Vista Home Premium.

The VHS capturing seemed to all go OK, BUT ... when I try to open the files in TMPGEnc 4.0 XPress, most of them (but not all of them) appear truncated. If I open them in GOM player, the entire file seems to be there (usually), but some are consistently shortened in TMPGEnc. For example, one file is all there in GOM, but consistently stops at the same point in TMPGEnc - when I load the file, then try to Cut/Edit (to top and tail) only the first part of the video appears.

Another interesting point is that different software (GOM, TMPG, GSpot) shows different file lengths (i.e. time of video) and sizes, none corresponding to 'reality'.

Anybody have any ideas about how I can get these mpegs to behave in TPMG? Thanks, Peter

Blue_MiSfit
10th August 2009, 10:30
What version of TMPGenc are you running?

What happens when you simply play the MPGs in VLC or Media Player Classic?

~MiSfit

nihilObstat
10th August 2009, 11:54
Misfit,

Version of TMPGEnc is 4.6.2.266.

I haven't got VLC loaded, but with Media Player Classic the same happens as with the GOM player - loads up OK and plays through all the way. Although the status bar tells me the file is over 7 hours long, and I know it is just over 3 hours.

Peter

von_Runkel
10th August 2009, 22:18
Could it be that the MPEG-2 files are transport streams?

"MPEG-2/Transport Stream record/playback in digital TV"

from

http://www.comprousa.com/en/product/e900f/e900f.html

If this is the case, I can understand that some software get upset about timings and you need to demultiplex the streams and feed the resulting elementary streams into TMPGEnc.

nihilObstat
11th August 2009, 01:32
OK, that's interesting.

I'm not sure whether the files are transport stream - the extension of the files is mpg, not ts. Anyway, when I demuxed one of the problem files, it displays (in the cut/edit screen) as the full length. BUT when I play the file, the video runs as far as the point where the file truncated previously. After that point the video goes black, but the audio continues.

Any ideas anyone? thanks, Peter

Guest
11th August 2009, 02:20
Open it in DGIndex and hit F5. Look at the stream type in the Info dialog. What does it say?

nihilObstat
11th August 2009, 02:36
I can't see 'stream type' in the info dialog in DGIndex. In the 'status' section of the info dialog it shows 'elapsed', 'remain', 'FPS', 'info'. The 'info' box states 'block error', so I suspect there's something wrong with the file. I'll try capturing from the VHS again.

thanks, Peter

Guest
11th August 2009, 03:11
Are you blind? It's the very first field at the top of the dialog in the Video section.

nihilObstat
11th August 2009, 07:46
It ain't there ...

http://www.tiefholz.com/nihill/DGIndex.jpg

I'm using version 1.4.3 if that makes any difference.

BTW I recaptured one of the problematic files and it seems to be behaving itself in TMPGEnc - might just be another case of Windoze not being as good at multitasking as it thinks it is. Someone else was using the machine during that capture, there may have been a few dropped ones or zeroes.

thanks, Peter

Guest
11th August 2009, 13:30
I'm using version 1.4.3 if that makes any difference. Um, yes. That version is ancient. Why aren't you using the latest version?

Ghitulescu
11th August 2009, 15:05
Download a trial version of Womble MPEG VCR and run one file through it, if there are any problems it will correct them (timestamps, GOP sizes etc.). I've heard that VideoReDo can do the same thing.

nihilObstat
11th August 2009, 17:57
Thanks, I'll try Womble. Does anyone know what it means when DGIndex reports a "block error" in the 'info' box in the 'status' field?

Peter

Guest
11th August 2009, 19:49
If it comes at the very end it may be dur to your cutting. If it comes in the middle it means your stream is corrupted.