From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Tomasz Borowczyk <tomboro88@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: cx231xx with 3 grabbers
Date: Tue, 14 May 2019 09:05:28 -0300 [thread overview]
Message-ID: <20190514090528.78965584@coco.lan> (raw)
In-Reply-To: <CAM+RvBRfLUPS7uaQG3Drj_oSX1ACj7cCT_fMM9o9NSwr=6JT3Q@mail.gmail.com>
Em Tue, 14 May 2019 00:18:31 +0200
Tomasz Borowczyk <tomboro88@gmail.com> escreveu:
> Hello linux-media.
>
> I use cx231xx driver with my August Vgb100 USB video grabber. It works
> great. It automatically detects my device and I can watch the video
> from analog camera on my Raspberry Pi, and I am very happy about how
> it works.
>
> But there is a catch. I want to connect 3 such cameras to my Raspberry
> Pi. When there are connected 2 of them, I can watch video from both of
> them without problems. When there are connected 3 adapters, I can
> watch the video from all three cameras, but the picture from one of
> them is flickering and blurring between blue screen and the correct
> data. And no matter in what order I connect them to the Raspberry, the
> problem exists always on the same adapter.
> The same problem exists when I connect the cameras to my laptop
> running Raspbian desktop.
> This could suggest that the one adapter is a little defective, but it
> works okay when there are connected only two adapters, or when it is
> the only connected. Also when I disconnect it and connect again to USB
> port, I can see correct image. But when I start to play picture from
> another camera, and then go back to the "defective" one, it flickers
> again. How can I find the reason of the problem?
The problem is related to the maximum bandwidth that an USB 2.0
provides. Most audio and video devices like cameras use an type of
USB package, called ISOC, with allows reserving bandwidth for them.
It actually reserves a number of USB slots. The maximum is 980 slots
per second, if I'm not mistaken.
The actual number of allocated slots depends on the resolution,
format, package size, number of frames per second, etc.
I don't have the numbers for cx231xx, but, with em28xx, a 640x480,
16 bits per pixel, 30 frames per second video uses about 60% of
the available USB 2.0 bandwidth. So, even two cameras at full
res can be too much.
I guess you can consider your self lucky to be able of having
two cameras working :-)
If you need more than that, you'll need to use a machine with
multiple USB buses and connect each camera on a different
bus.
Thanks,
Mauro
next prev parent reply other threads:[~2019-05-14 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 22:18 cx231xx with 3 grabbers Tomasz Borowczyk
2019-05-14 12:05 ` Mauro Carvalho Chehab [this message]
2019-05-18 10:20 ` Tomasz Borowczyk
[not found] ` <CAM+RvBRhG_Am=eGKog8a-rDAULrkNjKpbH+C+bqOk=wx5gXLJQ@mail.gmail.com>
2019-05-18 11:04 ` Mauro Carvalho Chehab
2019-05-19 9:43 ` Tomasz Borowczyk
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=20190514090528.78965584@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=tomboro88@gmail.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 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.