From: Grazvydas Ignotas <notasas@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "Rémi Denis-Courmont" <remi@remlab.net>,
"Sakari Ailus" <sakari.ailus@iki.fi>,
linux-media@vger.kernel.org,
"Hans Verkuil" <hans.verkuil@cisco.com>
Subject: Re: (bisected) Logitech C920 (uvcvideo) stutters since 3.9
Date: Mon, 17 Nov 2014 17:36:03 +0200 [thread overview]
Message-ID: <CANOLnONSBRNQORRhhSemS14rf19OHj6NOz_y__omA1gWEb-6qA@mail.gmail.com> (raw)
In-Reply-To: <CANOLnOMrdk9Gq+9Cv_e5cboXtbtxHoKVQdNgBvb_NcJfFT7bHQ@mail.gmail.com>
On Thu, Nov 6, 2014 at 12:29 AM, Grazvydas Ignotas <notasas@gmail.com> wrote:
> On Wed, Nov 5, 2014 at 4:05 PM, Laurent Pinchart
> <laurent.pinchart@ideasonboard.com> wrote:
>> Hi Rémi,
>>
>> On Tuesday 04 November 2014 22:41:44 Rémi Denis-Courmont wrote:
>>> Le mardi 04 novembre 2014, 15:42:37 Rémi Denis-Courmont a écrit :
>>> > Le 2014-11-04 14:58, Sakari Ailus a écrit :
>>> > >> > Have you tried with a different application to see if the problem
>>> > >> > persists?
>>> > >>
>>> > >> Tried mplayer and cheese now, and it seems they are not affected, so
>>> > >> it's an issue with vlc. I wonder why it doesn't like newer flags..
>>> > >>
>>> > >> Ohwell, sorry for the noise.
>>> > >
>>> > > I guess the newer VLC could indeed pay attention to the monotonic
>>> > > timestamp flag. Remi, any idea?
>>> >
>>> > VLC takes the kernel timestamp, if monotonic, since version 2.1.
>>> > Otherwise, it generates its own inaccurate timestamp. So either that
>>> > code is wrong, or the kernel timestamps are.
>>>
>>> From a quick check with C920, the timestamps from the kernel are quite
>>> jittery, and but seem to follow a pattern. When requesting a 10 Hz frame
>>> rate, I actually get a frame interval of about 8/9 (i.e. 89ms) jumping to
>>> 1/3 every approximately 2 seconds.
>>>
>>> From my user-space point of view, this is a kernel issue. The problem
>>> probably just manifests when both VLC and Linux versions support monotonic
>>> timestamps.
>>>
>>> Whether the root cause is in the kernel, the device driver or the firmware,
>>> I can´t say.
>>
>> Would you be able to capture images from the C920 using yavta, with the
>> uvcvideo trace parameter set to 4096, and send me both the yavta log and the
>> kernel log ? Let's start with a capture sequence of 50 to 100 images.
>
> I've done 2 captures, if that helps:
> http://notaz.gp2x.de/tmp/c920_yavta/
>
> The second one was done using low exposure setting, which allows
> camera to achieve higher frame rate.
So, has anyone had time to look at these?
Gražvydas
next prev parent reply other threads:[~2014-11-17 15:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 2:03 (bisected) Logitech C920 (uvcvideo) stutters since 3.9 Grazvydas Ignotas
2014-11-02 22:57 ` Sakari Ailus
2014-11-03 23:16 ` Grazvydas Ignotas
2014-11-04 11:58 ` Sakari Ailus
2014-11-04 12:42 ` Rémi Denis-Courmont
2014-11-04 15:02 ` Paulo Assis
2014-11-04 15:36 ` Sakari Ailus
2014-11-04 23:32 ` Sakari Ailus
2014-11-05 10:13 ` Paulo Assis
2014-11-05 14:05 ` Laurent Pinchart
2014-11-05 22:29 ` Paulo Assis
2014-11-05 16:11 ` Sakari Ailus
2014-11-05 16:12 ` [RFC 1/2] uvc: Add a quirk flag for cameras that do not produce correct timestamps Sakari Ailus
2014-11-05 16:12 ` [RFC 2/2] uvc: Use UVC_QUIRK_BAD_TIMESTAMP quirk flag for Logitech C920 Sakari Ailus
2015-11-09 16:18 ` [RFC 1/2] uvc: Add a quirk flag for cameras that do not produce correct timestamps Laurent Pinchart
2014-12-05 14:58 ` (bisected) Logitech C920 (uvcvideo) stutters since 3.9 Laurent Pinchart
2014-11-04 20:41 ` Rémi Denis-Courmont
2014-11-05 14:05 ` Laurent Pinchart
2014-11-05 22:29 ` Grazvydas Ignotas
2014-11-17 15:36 ` Grazvydas Ignotas [this message]
2014-11-18 8:39 ` Hans Verkuil
2014-12-05 11:46 ` Laurent Pinchart
2014-12-06 0:25 ` Grazvydas Ignotas
2014-12-07 19:23 ` Laurent Pinchart
2014-12-07 21:23 ` Grazvydas Ignotas
2015-03-29 20:59 ` Milos Ivanovic
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=CANOLnONSBRNQORRhhSemS14rf19OHj6NOz_y__omA1gWEb-6qA@mail.gmail.com \
--to=notasas@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=remi@remlab.net \
--cc=sakari.ailus@iki.fi \
/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).