Hey Richard, On Wed, 2003-03-19 at 01:59, [EMAIL PROTECTED] wrote: > I also noticed that lavplay (and lavtrans) use different reader routines than > lav2yuv: [..] > I'm not sure why they are different. Perhaps lavplay/lavtrans needs random > access to frames, while lav2yuv just needs to stream the data? Or maybe the > programs are just out of sync. Anyway this puzzled me...
lavplay was originally intended to play back MJPEG video in hardware, so decoding in software never happens (assuming the input is MJPEG video). Only later, we got interested in software playback (or playback of non-MJPEG video), which means decoding (and possible re-encoding to MJPEG on-the-fly). But it's still primarily intended as a hardware playback tool, that's where most of its code points to. The decoding part was never really implemented, neither was the re-encoding (though divxdec does something like that). lav2yuv, on the other hand, is just a decoding tool, so it works differently. ;-). Ronald -- Ronald Bultje <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en _______________________________________________ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
