All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neuer User <auslands-kv@gmx.de>
To: linux-media@vger.kernel.org
Subject: Re: Replacement for vloopback?
Date: Wed, 06 Feb 2013 15:42:54 +0100	[thread overview]
Message-ID: <ketq5c$8dc$1@ger.gmane.org> (raw)
In-Reply-To: <ketngk$dit$1@ger.gmane.org>

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@gmx.de> 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 




  parent reply	other threads:[~2013-02-06 14:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 13:57 Replacement for vloopback? Neuer User
2013-02-06 14:31 ` Rémi Denis-Courmont
2013-02-06 14:42 ` Neuer User [this message]
2013-02-06 14:51   ` Devin Heitmueller
2013-02-06 14:57     ` Neuer User
2013-02-06 15:14 ` Neuer User

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ketq5c$8dc$1@ger.gmane.org' \
    --to=auslands-kv@gmx.de \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.