[gstreamer-bugs] [Bug 486659] xmp/exif metadata handling

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=486659

  GStreamer | gst-plugins-bad | Ver: HEAD CVS




------- Comment #18 from Stefan Kost (gstreamer, gtkdoc dev)  2008-11-18 12:24 UTC -------
Some more thinking (and discussion with tim) about the structure:
EXIF: can be in jfif (jpeg) and in tiff
  JFIF:
    APP1 (segment marker 0xFFE1), holds an entire TIFF file within
  TIFF: 
    Private Tag 0x8769 holds the Exif specified TIFF Tags,
    Private Tag 0x8825 holds GPS sub-IFD

XMP: can be in many filetypes
  XMP is most commonly serialized and stored using a subset of RDF,
  which is in turn expressed in XML

IPTC: ignore for now

What we should to is to have in gst-plugins-base/gst-libs/gst/tag
gstexiftag.{c,h}
gstxmptag.{c,h}
Those would, if feasible, implementing the standard without the external
dependencies.

Two new elements:
jfifparse: takes jfif, parses exif, xmp, outputs jpeg
jfifformat: takes jpeg, adds jfif framing including exif and xmp, outputs jfif

pngdec/enc, asfmux/demux, avimux/demux, flvmux/demux, qtmux/demux,
wavparse/wavenc could use libgsttag to add xmp support.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=486659.