jpegformat: make the intention of the elements more clear

This commit is contained in:
Stefan Kost 2010-05-07 22:53:17 +03:00
parent 20a8666388
commit 418a791868
2 changed files with 9 additions and 3 deletions

View file

@ -24,7 +24,9 @@
* SECTION:element-jifmux * SECTION:element-jifmux
* @short_description: JPEG interchange format writer * @short_description: JPEG interchange format writer
* *
* Writes a JPEG image as JPEG/EXIF or JPEG/JFIF including various metadata. * Writes a JPEG image as JPEG/EXIF or JPEG/JFIF including various metadata. The
* jpeg image received on the sink pad should be minimal (e.g. should not
* contain metadata already).
* *
* <refsect2> * <refsect2>
* <title>Example launch line</title> * <title>Example launch line</title>

View file

@ -28,7 +28,7 @@
* Parses a JPEG stream into JPEG images. It looks for EOI boundaries to * Parses a JPEG stream into JPEG images. It looks for EOI boundaries to
* split a continuous stream into single-frame buffers. Also reads the * split a continuous stream into single-frame buffers. Also reads the
* image header searching for image properties such as width and height * image header searching for image properties such as width and height
* among others. * among others. Jpegparse can also extract metadata (e.g. xmp).
* *
* <refsect2> * <refsect2>
* <title>Example launch line</title> * <title>Example launch line</title>
@ -39,7 +39,11 @@
* HTTP and stores it in a matroska file. * HTTP and stores it in a matroska file.
* </refsect2> * </refsect2>
*/ */
/* FIXME: output plain JFIF APP marker only. This provides best code reuse.
* JPEG decoders would not need to handle this part anymore. Also when remuxing
* (... ! jpegparse ! ... ! jifmux ! ...) metadata consolidation would be
* easier.
*/
#ifdef HAVE_CONFIG_H #ifdef HAVE_CONFIG_H
#include <config.h> #include <config.h>
#endif #endif