Philipp Zabel 1d43f6d852 v4l2videodec: only set latency if the frame duration is valid
If the duration of the v4l2object is GST_CLOCK_TIME_NONE, because the
sink did not specify a framerate in the caps and the driver accepts the
framerate, the decoder element uses GST_CLOCK_TIME_NONE to calculate and
set the element latency.

While this is a bug of the capture driver, the decoder element should
not use the invalid duration to calculate a latency, but print a warning
instead.

https://bugzilla.gnome.org/show_bug.cgi?id=779466
2017-04-05 09:20:19 -04:00
..
2017-02-27 00:34:19 +00:00
2017-02-27 00:34:19 +00:00
2017-02-27 00:34:19 +00:00
2017-03-14 16:38:02 -04:00
2012-11-04 00:07:18 +00:00
2017-02-27 00:34:19 +00:00
2017-02-27 00:34:19 +00:00
2017-02-27 00:34:19 +00:00
2017-02-27 00:34:19 +00:00
2017-02-27 00:34:19 +00:00
2017-02-27 00:34:19 +00:00
2007-02-22 14:35:28 +00:00
2012-11-04 00:07:18 +00:00
2012-11-04 00:07:18 +00:00
2017-02-27 00:34:19 +00:00
2017-02-27 00:34:19 +00:00
2016-06-07 17:02:34 -04:00

v4l2 plugins
============

The idea is a bit the same as the idea for the v4l1 plugins. We want
one generic v4l2element, and a few child objects (probably only two:
v4l2src and v4l2sink):

                /-------- v4l2src
v4l2element ---=
                \-------- v4l2sink

Both v4l2src and v4l2sink have a uncompressed and a compressed
recording-/playback-mode. Since this is all part of v4l2, the 'client'
of these elements, i.e. an application using v4l2src/v4l2sink, will
hardly notice this. All capsnego stuff is done inside, and the plugin
knows which formats are compressed and which are not.

Please note that the v4l1 and the v4l2 plugins are *not* compatible
concerning properties. Naming has been kept the same where possible,
but in some cases, properties had to be removed or added to make
full use of v4l2.

V4L2 API: http://linux.bytesex.org/v4l2/.
          http://v4l2spec.bytesex.org/
          /usr/include/linux/videodev2.h or

Kernel patches available from
          http://dl.bytesex.org/patches/.

Articles:
          http://lwn.net/Articles/203924/