Hi, If I'm not worng vloopback module create a third (or a forth...) video device. So try to open /dev/video2 or /dev/video3
husk
On Wed, Dec 1, 2010 at 11:10 AM, brandt@subnet.at wrote:
i have inserted the modules vloopback, videodev....coriander is neither complaining anymore about misseng etc/video0 nor avout missing v2l anymore.
and its running V4L output device /etc/video0
sofarsonice
by the way...i use GEM: ver: 0.91.3 'tigital' and PiDiP : additional video processing objects for PD version 0.12.23
if i try pdp_v4l2 console says pdp_v4l2: opening /dev/video0 pdp_v4l2: error: open /dev/video0: Device or resource busy
pdp_v4l2: opening /dev/video1 pdp_v4l2: error: open /dev/video1: Invalid argument get capabilities: Inappropriate ioctl for device
Gem pix_video
video driver 0: video4linux video driver 1: ieee1394 for linux
pd bash error: failed opening device: '/dev/video0' console says /dev/video0: Device or resource busy
if i try video driver 1 gem is telling me /dev/dv1394/0: No such file or directory console detto...wich is not a wonder, since i just have /dev/video1394 and no /dev/dv1394
any ideas?
markus
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list