[gstreamer-bugs] [Bug 598915] New: qtdemux: propagate jpeg2000 header data in image/x-j2c

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=598915
  GStreamer | gst-plugins-good | git

           Summary: qtdemux: propagate jpeg2000 header data in image/x-j2c
    Classification: Desktop
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: wingo at pobox.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


Created an attachment (id=145779)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=145779)
patch implementing these image/x-j2c fields in qtdemux

JPEG2000 inside ISO containers, called MJPEG2000 sometimes, with a normal file
extension of .mj2 -- yes. The deal is that when we demux out a J2K stream, what
qtdemux pushes is just the raw codestream. The codestream contains information
about the number of components and their sizes, but we need more information
than that to accurately present the data.

Some of this information is in the colr atom, currently exported as a "fourcc"
field in the caps. That's cool. But we also need component ordering -- is it
RGB, or BGRA, or whatever. This information is in the "component mapping" and
"channel definition" atoms.

The attached patch pushes out the contents of these atoms in a fairly raw
format, as a list of integers under the "component-mappings" and
"channel-definitions" caps fields. It's probably the least lossy way to do
that. These fields will not be present if the file has the default mapping for
the colorspace with no alpha channels, which is to say RGB in that order for
RGB caps, or YUV in that order for YUV, or the single greyscale channel for
greyscale.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.