linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: <linux-media@vger.kernel.org>
Subject: UVC frame interval inconsistency
Date: Wed, 11 Apr 2012 12:27:08 +0200	[thread overview]
Message-ID: <c29fa93d58ec0a2289435bc92ac63e46@chewa.net> (raw)

   Hello guys,



I have been reworking the V4L2 input in VLC and I hit what looks like a

weird bug in the UVC driver. I am using a Logitech HD Pro C920 webcam.



By default, VLC tries to find the highest possible frame rate (actually

smallest frame interval in V4L2), then the largest possible resolution at

that frame rate.



When enumerating the frame sizes and intervals on the device, the winner

is 800x600 at 30 f/s. But when setting 30 f/s with VIDIOC_S_PARM, the

system call returns 24 f/s. Does anyone know why it is so? Is this a

firmware bug or what?



-- 

Rémi Denis-Courmont

Sent from my collocated server

             reply	other threads:[~2012-04-11 10:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 10:27 Rémi Denis-Courmont [this message]
2012-04-16 12:40 ` UVC frame interval inconsistency Laurent Pinchart

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=c29fa93d58ec0a2289435bc92ac63e46@chewa.net \
    --to=remi@remlab.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).