<html>
At 03:52 PM 7/22/2001 -0700, Jay Beavers wrote:<br>
<blockquote type=cite cite>We are doing 640x480 @ 15 fps using Sony 1394
cameras, encoding them<br>
using software M-JPEG, and transmitting them with a RTP stack that<br>
supports Forward Error Correction which we found to be a
requirement<br>
when sending large frame video.</blockquote><br>
Which stack is this? I've not paid much attention to FEC, but that sounds
cool. Is it an RFC2733
(<a href="http://www.ietf.org/rfc/rfc2733.txt" eudora="autourl">http://www.ietf.org/rfc/rfc2733.txt</a>)
FEC stack?<br>
<br>
<blockquote type=cite cite>This system works side by side on the same box
with analog capture cards<br>
such as the Osprey 200 and Osprey 500 (which supports hardware<br>
deinterlacing of NTSC signals). We have found VIC quite unstable
when<br>
transmitting (receiving is just fine) video streams under Windows
2000<br>
and Windows XP, so side by side on one computer is problematic at
best<br>
because VIC keeps crashing. We've also found that VIC cannot deal
with<br>
our 1394 camera drivers which are based on the newer capture API
WDM<br>
(Windows Driver Model) instead of the older standard VfW (Video for<br>
Windows).</blockquote><br>
Found this about WDM:<br>
<br>
<a href="http://msdn.microsoft.com/library/en-us/dnwbgen/html/vidcap.asp" eudora="autourl">http://msdn.microsoft.com/library/en-us/dnwbgen/html/vidcap.asp<br>
<br>
</a>Do you have a simple example of video capture under WDM, where the
application code ends up with the bits from the camera?<br>
<br>
<blockquote type=cite cite>We'll be releasing the RTP stack and a
conference management application<br>
in December per my previous message. By December, I hope to
have<br>
support for not only M-JPEG (which is a bit of a CPU hog), but also
ISO<br>
MPEG-4 (decoding) </blockquote><br>
What are you using for MPEG-4 encoding?<br>
<br>
--bob</html>