Re: How To Construct Xvid Header From Incomplete File

"Tesla 13" <[email protected]> Mon, 10 May 2004 03:39:41 -0400
Newsgroups gmane.comp.video.xvid.user
Message-ID <[email protected]>
>There was an answer by Bruno Harbulot on thursday, telling you that with 
>Linux you have a chance of saving stuff using mplayer/mencoder.

My sincere apologies. I just read it from the archives now. I indeed was 
replied but somehow it never reached my mailbox.

>I would have given the same advice, because first, that program is very 
>good playing broken files, and second, it has an specific option to skip 
>e.g. the first 10MB of a file and try to start decoding from there. It may 
>still fail, but it's worth a try.

Yes, after inputing the FPS, mplayer plays a while before crashing. Still 
this is something since no other player managed to get a frame out of it. I 
believe it is playing the key frames. Mencoder does not seem to be doing 
anything useful with Bruno's suggestion. I added -idx as well. The output 
file size keeps growing and growing. I will fiddle with other options (so 
many!).

>Of course it would have been great, but how many answers you get always 
>depends on what you ask. Your problem is in no way specific to XviD,

Since I am able to construct and play other headerless divx files, I thought 
this is Xvid specific.

>people have asked "I have a broken AVI file, what should I do?" a million 
>time already, so only few people are willing to spend the time explaining 
>again, what is already available by a google or archive search.

I did these all prior to posting but could not come up with anything useful.

>Every frame of MPEG-4 starts with a unique ID, somethink like (hex) 
>0x000001nn  which doesn't appear anywhere else in the MPEG-4 stream. So, by 
>searching the data file just for these bytes sequences, and hoping that the 
>AVI/MP3 overhead doesn't contain them (or by removing AVI chunk parts with 
>some different trick), you could get back the raw video data. The first 
>frames won't be decodable, because the first reference frame is missing, 
>but starting with the first I-VOP, things should work. The information 
>about resolution you provided might be helpful to identify which 0x000001nn 
>chunk really are video and which are AVI/MP3-noise.
>
>If you are willing to do something like that, or find somebody who will, I 
>can happily help you out with the details.

Yes, this would be a very good alternative if I can't succeed with mencoder.

>Maybe for audio the same would be possible? I don't know.

This really is not that important since I can get the audio from other 
sources.

Thank you.

Jimmy

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar – get it now! 
http://toolbar.msn.com/go/onm00200415ave/direct/01/