mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-11-24 02:31:03 +00:00
ff5494046a
Special case check for sub-buffers: In certain cases, places like GstBaseTransform, which might check that the buffer is writable before copying metadata, timestamp, and such, will find that the buffer has more than one reference to it. In these cases, they will create a sub-buffer with an offset=0 and length equal to the original buffer size. This could happen in two scenarios: (1) a tee in the pipeline, and (2) because the refcnt is incremented in gst_mini_object_free() before the finalize function is called, and decremented after it returns.. but returning this buffer to the buffer pool in the finalize function, could wake up a thread blocked in _buffer_alloc() which could run and get a buffer w/ refcnt==2 before the thread originally unref'ing the buffer returns from finalize function and decrements the refcnt back to 1! This is related to issue #545501 |
||
---|---|---|
.. | ||
.gitignore | ||
gstv4l2.c | ||
gstv4l2bufferpool.c | ||
gstv4l2bufferpool.h | ||
gstv4l2colorbalance.c | ||
gstv4l2colorbalance.h | ||
gstv4l2object.c | ||
gstv4l2object.h | ||
gstv4l2sink.c | ||
gstv4l2sink.h | ||
gstv4l2src.c | ||
gstv4l2src.h | ||
gstv4l2tuner.c | ||
gstv4l2tuner.h | ||
gstv4l2vidorient.c | ||
gstv4l2vidorient.h | ||
gstv4l2xoverlay.c | ||
gstv4l2xoverlay.h | ||
Makefile.am | ||
README | ||
v4l2_calls.c | ||
v4l2_calls.h | ||
v4l2src_calls.c | ||
v4l2src_calls.h |
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/