mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2025-05-05 16:04:50 +00:00
BT2020_12 is not represented in V4L2, so drivers providing full colority for BT2020 will set V4L2_XFER_FUNC_709 transfer function. To fix the issue, we bump this to BT2020_12 if the resoltion is 4K, but we should only do that if the colorspace is BT2020 to start with, otherwise it's not possible to use normal BT709 for 4K 8bit formats. |
||
---|---|---|
.. | ||
ext | ||
gstv4l2.c | ||
gstv4l2allocator.c | ||
gstv4l2allocator.h | ||
gstv4l2bufferpool.c | ||
gstv4l2bufferpool.h | ||
gstv4l2colorbalance.c | ||
gstv4l2colorbalance.h | ||
gstv4l2deviceprovider.c | ||
gstv4l2deviceprovider.h | ||
gstv4l2h263enc.c | ||
gstv4l2h263enc.h | ||
gstv4l2h264enc.c | ||
gstv4l2h264enc.h | ||
gstv4l2mpeg4enc.c | ||
gstv4l2mpeg4enc.h | ||
gstv4l2object.c | ||
gstv4l2object.h | ||
gstv4l2radio.c | ||
gstv4l2radio.h | ||
gstv4l2sink.c | ||
gstv4l2sink.h | ||
gstv4l2src.c | ||
gstv4l2src.h | ||
gstv4l2transform.c | ||
gstv4l2transform.h | ||
gstv4l2tuner.c | ||
gstv4l2tuner.h | ||
gstv4l2videodec.c | ||
gstv4l2videodec.h | ||
gstv4l2videoenc.c | ||
gstv4l2videoenc.h | ||
gstv4l2vidorient.c | ||
gstv4l2vidorient.h | ||
gstv4l2vp8enc.c | ||
gstv4l2vp8enc.h | ||
gstv4l2vp9enc.c | ||
gstv4l2vp9enc.h | ||
Makefile.am | ||
meson.build | ||
README | ||
tuner.c | ||
tuner.h | ||
tunerchannel.c | ||
tunerchannel.h | ||
tunernorm.c | ||
tunernorm.h | ||
v4l2-utils.c | ||
v4l2-utils.h | ||
v4l2_calls.c |
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/