From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>
Cc: Keiichi Watanabe <keiichiw@chromium.org>,
linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org, tfiga@chromium.org,
jcliang@chromium.org, shik@chromium.org
Subject: Re: [PATCH] media: vivid: Support 480p for webcam capture
Date: Mon, 8 Oct 2018 14:03:02 -0300 [thread overview]
Message-ID: <20181008140302.2239633f@coco.lan> (raw)
In-Reply-To: <b2dc51d7-fc92-2e7b-3a07-55a076b95d8b@ideasonboard.com>
Em Wed, 3 Oct 2018 12:14:22 +0100
Kieran Bingham <kieran.bingham@ideasonboard.com> escreveu:
> > @@ -75,6 +76,8 @@ static const struct v4l2_fract webcam_intervals[VIVID_WEBCAM_IVALS] = {
> > { 1, 5 },
> > { 1, 10 },
> > { 1, 15 },
> > + { 1, 15 },
> > + { 1, 25 },
As the code requires that VIVID_WEBCAM_IVALS would be twice the number
of resolutions, I understand why you're doing that.
> But won't this add duplicates of 25 and 15 FPS to all the frame sizes
> smaller than 1280,720 ? Or are they filtered out?
However, I agree with Kieran: looking at the code, it sounds to me that
it will indeed duplicate 1/15 and 1/25 intervals.
I suggest add two other intervals there, like:
12.5 fps and 29.995 fps, e. g.:
static const struct v4l2_fract webcam_intervals[VIVID_WEBCAM_IVALS] = {
{ 1, 1 },
{ 1, 2 },
{ 1, 4 },
{ 1, 5 },
{ 1, 10 },
{ 1, 15 },
{ 2, 50 },
{ 1, 25 },
{ 1, 30 },
{ 1, 40 },
{ 1, 50 },
{ 1001, 30000 },
{ 1, 60 },
};
Provided, of course, that vivid would support producing images
at fractional rate. I didn't check. If not, then simply add
1/20 and 1/40.
> Now the difficulty is adding smaller frame rates (like 1,1, 1,2) would
> effect/reduce the output rates of the larger frame sizes, so how about
> adding some high rate support (any two from 1/{60,75,90,100,120}) instead?
Last week, I got a crash with vivid running at 30 fps, while running an
event's race code, on a i7core (there, the code was switching all video
controls while subscribing/unsubscribing events). The same code worked
with lower fps.
While I didn't have time to debug it yet, I suspect that it has to do
with the time spent to produce a frame on vivid. So, while it would be
nice to have high rate support, I'm not sure if this is doable. It may,
but perhaps we need to disable some possible video output formats, as some
types may consume more time to build frames.
Thanks,
Mauro
next prev parent reply other threads:[~2018-10-09 0:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 7:06 [PATCH] media: vivid: Support 480p for webcam capture Keiichi Watanabe
2018-10-03 7:08 ` Keiichi Watanabe
2018-10-03 11:16 ` Kieran Bingham
2018-10-05 9:18 ` Hans Verkuil
2018-10-06 10:29 ` Keiichi Watanabe
2018-10-08 8:35 ` Kieran Bingham
2018-10-08 9:00 ` Hans Verkuil
2018-10-08 9:47 ` Kieran Bingham
2018-10-03 11:14 ` Kieran Bingham
2018-10-08 17:03 ` Mauro Carvalho Chehab [this message]
2018-10-08 17:53 ` Hans Verkuil
2018-10-08 18:23 ` Mauro Carvalho Chehab
2018-10-08 18:28 ` Mauro Carvalho Chehab
2018-10-08 18:31 ` Hans Verkuil
2018-10-08 19:00 ` Mauro Carvalho Chehab
2018-10-09 6:01 ` Keiichi Watanabe
2018-10-09 6:33 ` Hans Verkuil
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=20181008140302.2239633f@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=jcliang@chromium.org \
--cc=keiichiw@chromium.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=shik@chromium.org \
--cc=tfiga@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox