Dear Doma, motion optional package 'vloopback' is a V4L compliant tool and is *not* V4L2-aware. libavg should report the incompatibility explicitly, this is a good hint to make it happens.
To overcome your problem, try to use v4l2vd package, which is a good spinoff of vloopback, exclusively based on V4L2. http://v4l2vd.sourceforge.net Probably you have to tweak mplayer too, and I don't know if effectv is supporting version 2. bye! On 11/lug/08, at 16:13, #! /usr/bin/doma wrote: > OXullo Intersecans wrote: >> On 11/lug/08, at 13:58, #! /usr/bin/doma wrote: >>>> libavg's V4L2 implementation has been surely tested with Bt8x8 PCI >>>> boards and a bunch of webcams, but I personally have no reports >>>> about >>>> vloopback. >>>> What version are you using? >>> I'll put all my sys infos here. Basicly i'm using vloopack [1] >>> from the >>> svn trunk. I compiled it last week for Kernel 2.6.24-16 on Ubuntu >>> 8.04/Hardy. It works really good with effectv,xawtv and pd. >>> >>> Setting up vloopback is quit easy.. >> ok, please, also provide a py/avg pair that you are using to test >> libavg functionality over your set up video pipeline > > here you go - i'm testing with TestVideo.py/camera.avg from > libavg-0.7.0/src/test. hope attachement works. -- OXullo Intersecans 0 2 L > Outside Standing Level http://www.02L.net _______________________________________________ libavg-users mailing list [email protected] https://mail.datenhain.de/mailman/listinfo/libavg-users
