From: "Rémi Denis-Courmont" <remi@remlab.net>
To: linux-media@vger.kernel.org
Subject: Re: RFC: use of timestamp/sequence in v4l2_buffer
Date: Tue, 4 Sep 2012 15:26:49 +0300 [thread overview]
Message-ID: <201209041526.49196@leon.remlab.net> (raw)
In-Reply-To: <201209041238.07000.hverkuil@xs4all.nl>
Le mardi 4 septembre 2012 13:38:06, Hans Verkuil a écrit :
> 7) Should the timestamp field always be monotonically increasing? Or it is
> possible to get timestamps that jump around? This makes sense for encoders
> that create B-frames referring to frames captured earlier than an I-frame.
I would expect an encoder to output frames in DTS order rather than PTS and a
decoder to output frames in PTS order. The timestamp field is the only
indication of the PCR, so an application might not recover if the timestamp
jumps backward.
If there is an ambiguity between PTS and DTS, I think it should be documented
and specified per format what the timestamp is.
--
Rémi Denis-Courmont
http://www.remlab.net/
next prev parent reply other threads:[~2012-09-04 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 10:38 RFC: use of timestamp/sequence in v4l2_buffer Hans Verkuil
2012-09-04 12:26 ` Rémi Denis-Courmont [this message]
2012-09-13 18:44 ` Sakari Ailus
2012-09-26 11:38 ` 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=201209041526.49196@leon.remlab.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 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.