On Thu, Apr 17, 2008 at 02:22:09AM +0530, Sisir Koppaka wrote: > On Thu, Apr 17, 2008 at 2:16 AM, Mike Melanson <[EMAIL PROTECTED]> wrote: > > > Sisir Koppaka wrote: > > > There's no memory corruption/segfaults for ffmpeg. ffplay gets hit hard > > > though, and it gives a list of all sdl library files and .so files. That > > > output is listed below: > > > > That probably just means that 'ffmpeg' got lucky. Run the command line > > through valgrind (and use 'ffmpeg_g' so you get symbols) and see where > > your decoder is stepping on memory (I'm just guessing about the root > > problem here :) ). > > [...] > Input #0, bfi, from '/home/sisir/Desktop/bfi/2287.bfi': > Duration: 00:01:18.7, start: 0.000000, bitrate: 88 kb/s > Stream #0.0: Video: bfi, pal8, 320x140, 9.00 tb(r) > Stream #0.1: Audio: pcm_u8, 11025 Hz, mono, 88 kb/s > File 'test.mov' already exists. Overwrite ? [y/N] y > Output #0, mov, to 'test.mov': > Stream #0.0: Video: mpeg4, yuv420p, 320x140, q=2-31, 200 kb/s, 9.00 > tb(c) > Stream #0.1: Audio: 0x0000, 11025 Hz, mono, 64 kb/s > Stream mapping: > Stream #0.0 -> #0.0 > Stream #0.1 -> #0.1 > Unsupported codec for output stream #0.1
retry with a audio encoder which is supported by your ffmpeg [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB When you are offended at any man's fault, turn to yourself and study your own failings. Then you will forget your anger. -- Epictetus
signature.asc
Description: Digital signature
_______________________________________________ FFmpeg-soc mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-soc
