[Bug 723380] codecparsers_h264: Add SEI recovery point message parsing.

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Thu Jun 26 08:28:46 PDT 2014


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

Gwenole Beauchesne <gb.devel> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |1.3.4

--- Comment #10 from Gwenole Beauchesne <gb.devel at gmail.com> 2014-06-26 15:28:41 UTC ---
commit 67df2072801012dd084b4da6e916db9967f5650f
Author: Aurélien Zanelli <aurelien.zanelli at parrot.com>
Date:   Fri Jan 31 17:07:42 2014 +0100

    codecparsers: h264: add support for Recovery Point SEI message.

    The recovery point SEI message helps a decoder in determining if the
    decoding process would produce acceptable pictures for display after
    the decoder initiates random access or after the encoder indicates
    a broken link in the coded video sequence.

    This is not used in the h264parse element, but it could help debugging.

    https://bugzilla.gnome.org/show_bug.cgi?id=723380

commit 0440cabf491f2f6e82e7bcde24a805ee966cbaab
Author: Gwenole Beauchesne <gwenole.beauchesne at intel.com>
Date:   Tue Mar 25 12:01:55 2014 +0100

    codecparsers: h264: add nal_reader_skip_long() helper.

    Add nal_reader_skip_long() helper function to allow an arbitrary number
    of bits to be skipped. The former nal_reader_skip() function is too
    limited to the actual cache size.

    Use this new function to simplify gst_h264_parser_parse_sei_message()
    default case, that skips unsupported payloads.

    v2: made args consistent from header to source file.

    Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne at intel.com>

-- 
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.


More information about the gstreamer-bugs mailing list