Skip to content
Snippets Groups Projects
  1. Jul 19, 2014
  2. Jul 18, 2014
  3. Jul 17, 2014
  4. Jul 16, 2014
  5. Jul 12, 2014
  6. Jul 11, 2014
  7. Jul 04, 2014
  8. Jul 03, 2014
    • Sebastian Rasmussen's avatar
      riff: Print invalid fourcc in error message in hex · 7807e2e6
      Sebastian Rasmussen authored and Sebastian Dröge's avatar Sebastian Dröge committed
      Previously this was printed as characters which caused later processing
      of the error message to sometimes warn about non-UTF-8 characters.
      
      Fixes https://bugzilla.gnome.org/show_bug.cgi?id=732697
      7807e2e6
    • Gwenole Beauchesne's avatar
      videodecoder: parse any source data that is still available. · fb44ec96
      Gwenole Beauchesne authored
      Fix gst_video_decoder_parse_available() to really parse any pending
      source data that is still available in the adapter. This is a memory
      optimization to avoid expansion of video packed added to the adapter,
      but also a fix to EOS condition when the subclass parse() function
      ultimately only needed to call into gvd_have_frame() and no additional
      source bytes were consumed, i.e. gvd_add_to_frame() is not called.
      
      This situation can occur when decoding H.264 streams in byte-stream/nal
      mode for instance. A decoder always requires the next NAL unit to be
      parsed so that to determine picture boundaries. When a new picture is
      found, no byte is consumed (i.e. gvd_add_to_frame() is not called)
      but gvd_have_frame() is called (i.e. priv->current_frame is gone).
      
      Also make sure to avoid infinite loops caused by incorrect subclass
      parse() implementations. This can occur when no byte gets consumed
      and no appropriate indication (GST_VIDEO_DECODER_FLOW_NEED_DATA) is
      returned.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=731974
      
      
      
      Signed-off-by: default avatarGwenole Beauchesne <gwenole.beauchesne@intel.com>
      fb44ec96
  9. Jul 02, 2014
  10. Jul 01, 2014
  11. Jun 28, 2014
  12. Jun 27, 2014
  13. Jun 26, 2014
  14. Jun 23, 2014
  15. Jun 22, 2014
  16. Jun 20, 2014
    • Sebastian Dröge's avatar
      audiodecoder: Don't be too picky about the output frame counter · 909dd783
      Sebastian Dröge authored
      With most decoder libraries, and especially when accessing codecs via
      OpenMAX or similar APIs, we don't have the ability to properly related
      the output buffers to a number of input samples. And could e.g. get
      a fractional number of input buffers decoded at a time.
      
      Previously this would in the end lead to an error message and stopped
      playback. Change it to a warning message instead and try to handle it
      gracefully. In theory the subclass can now get timestamp tracking
      wrong if it completely misuses the API, but if on average it behaves
      correct (and gst-omx and others do) it will continue to work properly.
      
      Also add a test for the new behaviour.
      
      We don't change it in the encoder yet as that requires more internal logic
      changes AFAIU and I'm not aware of a case where this was a problem so far.
      909dd783
  17. Jun 13, 2014
Loading