summaryrefslogtreecommitdiff
path: root/vhook/hooks.texi
diff options
context:
space:
mode:
authorPhilip Gladstone <philipjsg@users.sourceforge.net>2002-11-21 03:50:36 +0000
committerPhilip Gladstone <philipjsg@users.sourceforge.net>2002-11-21 03:50:36 +0000
commit26b4bb70c20be6aa45211d8bde521662e232582e (patch)
treea8b58af860d52eb13f3881ca6367d64aace57875 /vhook/hooks.texi
parent65e70450de4bb3dc19474cf08573fe178bd56719 (diff)
Added three sample video hooks. See the (rudimentary) documentation on what
they do and their capabilities. Originally committed as revision 1265 to svn://svn.ffmpeg.org/ffmpeg/trunk
Diffstat (limited to 'vhook/hooks.texi')
-rw-r--r--vhook/hooks.texi49
1 files changed, 49 insertions, 0 deletions
diff --git a/vhook/hooks.texi b/vhook/hooks.texi
new file mode 100644
index 0000000000..7eb2da8848
--- /dev/null
+++ b/vhook/hooks.texi
@@ -0,0 +1,49 @@
+\input texinfo @c -*- texinfo -*-
+
+@settitle Video Hook Documentation
+@titlepage
+@sp 7
+@center @titlefont{Video Hook Documentation}
+@sp 3
+@end titlepage
+
+
+@chapter Introduction
+
+
+The video hook functionality is designed (mostly) for live video. It allows
+the video to be modified or examined between the decoder and the encoder.
+
+Any number of hook modules can be placed inline, and they are run in the
+order that they were specified on the ffmpeg command line.
+
+Three modules are provided and are described below. They are all intended to
+be used as a base for your own modules.
+
+Modules are loaded using the -vhook option to ffmpeg. The value of this parameter
+is a space seperated list of arguments. The first is the module name, and the rest
+are passed as arguments to the Configure function of the module.
+
+@section null.c
+
+This does nothing. Actually it converts the input image to RGB24 and then converts
+it back again. This is meant as a sample that you can use to test your setup.
+
+@section fish.c
+
+This implements a 'fish detector'. Essentially it converts the image into HSV
+space and tests whether more than a certain percentage of the pixels fall into
+a specific HSV cuboid. If so, then the image is saved into a file for processing
+by other bits of code.
+
+Why use HSV? It turns out that HSV cuboids represent a more compact range of
+colors than would an RGB cuboid.
+
+@section imlib2.c
+
+This allows a caption to be placed onto each frame. It supports inserting the
+time and date. By using the imlib functions, it would be easy to add your own
+graphical logo, add a frame/border, etc.
+
+
+@bye