Thanks for answering. The vloopback description seems to imply that it is possible to share a camera stream: "How to use multiple webcam applications with vloopback [...] Do "modprobe vloopback pipes=2". Then "resize /dev/video0 /dev/video1 640x480 640x480 & resize /dev/video2 /dev/video3 640x480 320x240". (Assuming that you have only one real video device at /dev/video0. You can check with dmesg). Now, you can watch your webcam with camstream at 640x480 (choose the device called vloopback0 output in camstream's menu, which is /dev/video2), at the sime time you can record a video of your webcam stream at 320x240 by doing "ffmpeg -vd /dev/video4 -s 320x240 picture.mpeg", you can at the same time run a webcam http server by running "camsource" (after editting camsource.conf to choose /dev/video2 or /dev/video4 as v4l_input source)." If it is not possible to have two applications access the same video stream, that is pretty detrimentical to quite a lot of use cases, e.g.: a.) Use motion to detect motion and record video. At the same time view the camera output on the screen. b.) Stream a webcam output over the net and at the same time view it on the screen. Actually, for me it would be no problem, if the stream needs to be the same format etc. So, really no way? :-( Thanks Michael > On Wed, 06 Feb 2013 14:57:43 +0100, Neuer User <auslands-kv@xxxxxx> wrote: >> So, my question ist: Is vloopback the right way to go for this >> requirement? If yes, how to get it working? > > No. Video loopback is just a way for an application to expose a virtual > camera, for another application to use. It is not a way to share a camera > within two applications. > > Sharing a camera is fundamentally impossible due to the limitation of the > hardware, which cannot capture in two different formats and sets of buffers > simultaneously. Live with it. > > -- Rémi Denis-Courmont Sent from my collocated server -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
