View Full Version : anachronistic or discontinous timestamp
unknownsoldierX
21st February 2006, 09:40
I have an mpeg-1 file that plays fine in WMP, but not in VLC. In VLC, while playing in fullscreen mode, the video in many spots causes VLC to quickly go to windowed mode and back to fullscreen.
I open the file in VDub and I get a few dozen errors saying "anachronistic or discontinous timestamp..."
I've tried TMPGEnc Plus 2.5, Womble MPEG Video Wizard, and Nero Vision. All of them only open about 2 min. of the total 30 min.
I used an AVS script to frameserve to TMPGEnc Plus 2.5 and the file came out fine, except the file size is almost twice that of the original. (143MB to 272MB)
Mug Funky
23rd February 2006, 07:19
select "MPEG-1 program (VBR)" in TMPGenc and the file size shouldn't increase (much). it pads in the normal mode because it likes to make CBR VCD style mpeg-1 stuff.
setarip_old
23rd February 2006, 07:51
Hi!
How did you create (software and procedures used) the original MPEG-1?
unknownsoldierX
23rd February 2006, 13:47
select "MPEG-1 program (VBR)" in TMPGenc and the file size shouldn't increase (much). it pads in the normal mode because it likes to make CBR VCD style mpeg-1 stuff.
In settings, under Rate Control Mode? All I see is "2-pass VBR(VBR)", "Manual VBR (MVBR)", and "Automatic VBR (CQ_VBR)"
unknownsoldierX
23rd February 2006, 13:48
Hi!
How did you create (software and procedures used) the original MPEG-1?
The file was given to me by a friend. I don't have any information on it, except that it was made a long time ago.
Mr_Odwin
23rd February 2006, 14:23
The file was given to me by a friend. I don't have any information on it, except that it was made a long time ago.
in a galaxy far, far away?
:p
unknownsoldierX
25th February 2006, 00:43
I tried "Automatic VBR (CQ_VBR)" and the file size turn out 434MB !!
foxyshadis
25th February 2006, 01:27
...and? What CQ did you use? (You probably have such a low-quality file already that constant quant recompression is pointless.)
unknownsoldierX
25th February 2006, 02:37
I didn't even know what CQ meant. Isn't there a way for me to find out the info on the original file? Bitrate, FPS, etc? Then I could set TMPGenc by that info, right?
Mug Funky
28th February 2006, 03:32
aah, you're re-encoding, huh?
try use TMPG for muxing only. quickest way is to go to "file > mpeg tools", then select the tab "simple multiplex", load up your mpeg(s) and select "mpeg-1 program (VBR)" or whatever it's called. this will not re-encode your video, so it will come out the same size as the input (plus a little muxing overhead).
unknownsoldierX
28th February 2006, 04:21
aah, you're re-encoding, huh?
try use TMPG for muxing only. quickest way is to go to "file > mpeg tools", then select the tab "simple multiplex", load up your mpeg(s) and select "mpeg-1 program (VBR)" or whatever it's called. this will not re-encode your video, so it will come out the same size as the input (plus a little muxing overhead).
Quoting my first post: "I've tried TMPGEnc Plus 2.5, Womble MPEG Video Wizard, and Nero Vision. All of them only open about 2 min. of the total 30 min."
Even the MPEG Tools in TMPEGenc won't open the entire video. I don't understand why there isn't a program that has the ability to scan the whole file and fix this type of problem.
I'm assuming my file has some kind of timestamp error? Where TMPEGenc opens the file, gets to a spot in the video thats broken, and assumes that's the end of the video?
I don't want to re-encode. I just can't find a tool that can open more than the first 2 minutes, besides V-dub.
foxyshadis
28th February 2006, 08:30
Elecard makes xmuxer, which may have error resilience like vdub (elecard engineers everything they make to be very rebust). It does sound like you've got trashed frame headers, possibly a long run of zeros in the file, and they can't recover so they just drop the stream. It's generally a lot harder to recover from structual errors than a corrupted macroblock.
Mug Funky
28th February 2006, 08:51
ah, sorry. didn't read the bit about loading an avs in properly.
well, if your avs shows the entire video, there's hope :)
with some whacked-out mpegs i've seen, ffmpeg or mplayer/mencoder have been able to demux the corrupt stream into something usable.
and if you used DGindex to get your mpeg file into avisynth, you might want to consider using that to demux the original - it can demux video and audio now.
unknownsoldierX
28th February 2006, 11:07
No, I didn't use DGindex. I just did the simple DirecShowSource=("")
I'll give DGindex a try tomorrow.
unknownsoldierX
28th February 2006, 18:58
DGindex opens the entire file. I demuxed the file with DGindex then multiplexed it with TMPGenc. TMPEGenc does the whole stream, but at the end I get this message:
http://img149.imageshack.us/img149/8393/tmpegencwarning4wn.jpg
I no longer get the "anachronistic or discontinous timestamp..." errors when I open the file in Vdub.
However, I still have probelms with VLC. (While playing in fullscreen mode, the video in many spots causes VLC to quickly go to windowed mode and back to fullscreen.)
unknownsoldierX
28th February 2006, 19:29
Elecard makes xmuxer, which may have error resilience like vdub (elecard engineers everything they make to be very rebust). It does sound like you've got trashed frame headers, possibly a long run of zeros in the file, and they can't recover so they just drop the stream. It's generally a lot harder to recover from structual errors than a corrupted macroblock.
I tried demuxing and muxing with Elecard Xmuxer and I get the same result. I get the whole file, but it doesn't play in VLC properly. Also, the output from Xmuxer doesn't have a timestamp(?), so the video plays but the time stays 00:00:00.
unknownsoldierX
4th March 2006, 11:22
Nobody has any other ideas?
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.