[AG-TECH] sorry, Osprey-200 instead

[shudo at ni.aist.go.jp]

Hi all,

Robert Olson wrote:

> At 10:48 PM 6/21/2001 -0700, Jay Beavers wrote:
> >  However, 640x480 causes VIC
> >to crash in all my tests, so this is of limited value.

> How were you capturing 640x480 (which codec)? h.261 supports only up to
> 352x288; you may have hit bugs in other codecs which would be best fixed.

I succeeded in managing 640x480 video and VIC. I could
use a build-in camera of SONY VAIO C1 Picturebook as an
input device for VIC.

  a screen shot (1024x480):
    http://www.shudo.net/diary/data/20010618/vic_w_meye.jpg
  smaller version (512x240):
    http://www.shudo.net/diary/data/20010618/s-vic_w_meye.jpg

Linux 2.4.5-ac13 and later have the video4linux (v4l)
driver for the built-in camera of
Picturebook. Unfortunately, VIC cannot get images from
the camera correctly. I guess the reason is that the
driver can produce only 640x480 or 320x240.

But there are methods to resize v4l video. The following
tools are useful for the purpose:

  video4linux loopback (vloopback) device
    http://motion.technolust.cx/vloopback/
  EffecTV
    http://effectv.sourceforge.net/

The vloopback device provides a pipe of v4l video
stream. For example, it can reads from /dev/video1 and
writes to /dev/video2. EffecTV or similar tools can
resize v4l video. I use the EffecTV to read from
/dev/video0, resize the video and write to /dev/video1.
The whole picture is:

  built-in camera  --(/dev/video0)-->  EffecTV  --(/dev/video1)-->
  vloopback device  --(/dev/video2)-->  VIC

I'm interested in compact AG setting, then we are trying
such a small devices including USB cameras. We are also
very intrested in high quality video, especially with
IEEE 1394.

  Kazuyuki Shudo, Ph.D.		shudo at ni.aist.go.jp, http://www.shudo.net/
  Information Technology Research Institute
  National Institute of Advanced Industrial Science and Technology (AIST)