From: "Daniel Glöckner" <daniel-gl@gmx.net>
To: Linos <info@linos.es>
Cc: video4linux-list@redhat.com
Subject: Re: bttv driver problem last kernels
Date: Fri, 6 Jun 2008 14:17:19 +0200 [thread overview]
Message-ID: <20080606121719.GA506@daniel.bse> (raw)
In-Reply-To: <484920B9.4010107@linos.es>
On Fri, Jun 06, 2008 at 01:34:17PM +0200, Linos wrote:
> Hello all,
> i am using a bttv multicapture board and i have been having
> increasing problems in last kernels, i am using two programs to capture my
> video input for security reasons (helix producer and mp4live from mpeg4ip
> project) since the first versions of v4l2 in 2.4 patched kernel versions i
> can attach the two programs at the same time at the same video input, only
> loss framerate
You are relying on undocumented behaviour when two v4l1 applications are
reading from bttv at the same time. Furthermore the v4l2 standards says
"1.1.4. Shared Data Streams
V4L2 drivers should not support multiple applications reading or writing
the same data stream on a device by copying buffers, time multiplexing
or similar means. This is better handled by a proxy application in user
space. When the driver supports stream sharing anyway it must be
implemented transparently. The V4L2 API does not specify how conflicts
are solved."
You should change your setup to use only one application accessing the
device.
Daniel
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-06-06 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 11:34 bttv driver problem last kernels Linos
2008-06-06 12:17 ` Daniel Glöckner [this message]
2008-06-06 12:22 ` Linos
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=20080606121719.GA506@daniel.bse \
--to=daniel-gl@gmx.net \
--cc=info@linos.es \
--cc=video4linux-list@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox