diff options
author | Ronald S. Bultje <rbultje@ronald.bitfreak.net> | 2002-09-09 07:14:35 +0000 |
---|---|---|
committer | Ronald S. Bultje <rbultje@ronald.bitfreak.net> | 2002-09-09 07:14:35 +0000 |
commit | 3ec5a0a054fd36290f006aa2101da35d03d9f5ed (patch) | |
tree | e7a928b150417982d8998a2849f541d3223218af /sys/v4l2/README | |
parent | 86c99507a557afbf84459d85e1d1d4b287b457d5 (diff) | |
download | gst-plugins-bad-3ec5a0a054fd36290f006aa2101da35d03d9f5ed.tar.gz gst-plugins-bad-3ec5a0a054fd36290f006aa2101da35d03d9f5ed.tar.bz2 gst-plugins-bad-3ec5a0a054fd36290f006aa2101da35d03d9f5ed.zip |
this adds video4linux2 source and element plugins. The division in v4l2* plugins is the same as for v4l1 - i.e. an el...
Original commit message from CVS:
this adds video4linux2 source and element plugins. The division in v4l2* plugins is the same as for v4l1 - i.e. an element, a src and a sink, but there won't be separate encoding plugins (like v4lmjpegsrc) - all functionality is (thanks to video4linux2) integrated in one plugin: v4l2src. v4l2sink is still to be done, that'll come later.
Diffstat (limited to 'sys/v4l2/README')
-rw-r--r-- | sys/v4l2/README | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/sys/v4l2/README b/sys/v4l2/README new file mode 100644 index 00000000..f10c27c2 --- /dev/null +++ b/sys/v4l2/README @@ -0,0 +1,24 @@ +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 applicaiton 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://thedirks.org/v4l2/. Kernel patches available from + http://bytesex.org/patches/. |