On 10/04/2010 06:01, Ryan C. Gordon wrote: > >> I mean, it already has VoIP right? > > If you wanted to do video, or still frames, from a webcam, you could > probably add a clc_video packet or something. You'd have to be careful > about sending too much data in one packet. Ideally, you'd want to dither > down the image to be tiny (64x64 or something), and maybe jpeg-encode > it, so it fits in a single packet. Otherwise, you have to deal with > splitting it up and unreliable transmission.
Actually you don't have to take that much care. JPEG was tailored to be loss tolerant. With a packet lost here and there it'd just get a little more blocky in some places, as long as the first packet doesn't get lost it will probably be all right. As the JPEG data stream goes from rough to fine-grained image detail, you could even base your transmission on something very detailed and just blindly send small packets for a given amount of time (e.g. 2 seconds) and drop the remaining data. The receiver would build the image from whatever came across. This way image quality would simply scale with the network connection quality. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? _______________________________________________ ioquake3 mailing list [email protected] http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
