Hallo > I wrote a couple of days ago about an mpg that was giving my DVD player > fits when I tried to burn it to a VCD. I finally got it to work, but it > required reencoding the entire mpg, which was a little time consuming > and reduced the quality of the vid, not greatly but visibly. Now > working with a second mpg from the same series, vcdimager reports: > > ---- > INFO: scanning mpeg segment item #0 for scanpoints... > ++ WARN: mpeg stream will be padded on the fly -- hope that's ok for > you! > ++ WARN: mpeg scan: pack header code (0x000001ba) expected, but > 0x00000000 found (buflen = 2324) > ++ WARN: bad packet at packet #15877 (stream byte offset 32533760) -- > remaining > 418452228 bytes of stream will be ignored > ++ WARN: autopadding requires to insert additional 4364388 zero bytes > into MPEG > stream (due to 15813 unaligned packets of 15877 total) > INFO: scanning mpeg sequence item #0 for scanpoints... > ++ WARN: file `videocd.bin' exist already, will get overwritten! > ++ WARN: file `videocd.cue' exist already, will get overwritten! > INFO: writing track 1 (ISO9660)... > INFO: writing file `CDI/CDI_IMAG.RTF' (1315168 bytes, raw sectors > file) > INFO: writing file `CDI/CDI_TEXT.FNT' (13616 bytes) > INFO: writing file `CDI/CDI_VCD.APP' (102400 bytes) > INFO: writing track 2, MPEG1, NTSC SIF (352x240/29.97fps), audio[0]: > l2/44.1kHz/224kbps/stereo ... > ----- > > The bad packet that results in most of the stream being ignored is new, > but the need for autopadding of the majority (15813 of 15877 packets) is > just what I saw with the prior vid (before I reencoded it). > > Can anyone offer a diagnosis (or an educated guess) about what is wrong > with these mpgs. I know virtually nothing about the format of an mpg > stream, so this may be poppycock, but it seems to me that the frames are > actually ok (since the vid will play on my PC) but something about the > way they're structured into a stream is screwed up. That being said, is > there anyway to reassemble the mpg so it'll play nice without the > lossiness of a complete reencode. I tried demuxing and remuxing with > the last vid, and it didn't help. As long as you don't exactly know whit which options the mpegs were created helping is rather hard. A PC will playback nearly everything. It has not that limits that are in the VCD specs. And if a stream is not correct (like to high bitrate, to large buffer) it will still play the stream. But a HW player that can't handle the to high bitrate might simply stop playing.
> Any suggestions or pointers to info on diagnosing and fixing mpeg > problems would be appreciated. Do you have tried demuxing the streams with the linux version of bbdmux the bbtools and remuxing with mplex ? That should fix problems made by the multiplexer. auf hoffentlich bald, Berni the Chaos of Woodquarter Email: [EMAIL PROTECTED] [EMAIL PROTECTED] www: http://www.lysator.liu.se/~gz/bernhard ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
