ChangeLog
=========

2016-01-20  Sebastian Dröge <[email protected]>

        * configure.ac:
          releasing 1.6.3

2016-01-20 13:41:33 +0200  Sebastian Dröge <[email protected]>

        * ext/vpx/gstvp8enc.c:
          vp8enc: Ensure that we always have valid frame user data before using 
it
          Otherwise we're going to dereference NULL pointers.

2016-01-20 10:02:48 +0200  Sebastian Dröge <[email protected]>

        * ext/vpx/gstvp8dec.c:
        * ext/vpx/gstvp9dec.c:
          vpxdec: Unref frame in all code paths of handle_frame()
          https://bugzilla.gnome.org/show_bug.cgi?id=760666

2016-01-19 22:49:20 +0100  Thibault Saunier <[email protected]>

        * ext/vpx/gstvp8enc.c:
        * ext/vpx/gstvp9enc.c:
          vpxenc: Unref frame on ERROR
          All code paths for handle_frame() must somehow take ownership of the 
frame, be
          it by actually unreffing, forwarding the frame elsewhere or storing 
it for
          later.
          http://bugzilla.gnome.org/show_bug.cgi?id=760666

2016-01-20 10:08:50 +0200  Sebastian Dröge <[email protected]>

        * ext/vpx/gstvp9enc.c:
          vp9enc: Return FLOW_ERROR when an error accures
          FALSE would mean FLOW_OK
          https://bugzilla.gnome.org/show_bug.cgi?id=760666

2016-01-19 15:14:59 -0500  Nicolas Dufresne <[email protected]>

        * sys/v4l2/gstv4l2object.c:
          v4l2object: Don't set colorimetry for non YUV formats
          Setting colormetry in caps for RGB have no meaning, but worst it
          confuses the converters downstream.
          https://bugzilla.gnome.org/show_bug.cgi?id=759624

2016-01-19 14:57:03 +0200  Sebastian Dröge <[email protected]>

        * gst/wavparse/gstwavparse.c:
          wavparse: Don't play anything after the end of the data chunk even 
when seeking
          Especially in push mode we would completely ignore the size of the 
data chunk
          when not stop position is given for the seek. Instead make sure that 
the end
          offset is at most the end of the data chunk if known.
          Without this we would output anything after the data chunk, possibly 
causing
          loud noises if the media file is followed by an INFO chunk or an ID3 
tag.

2016-01-19 14:55:57 +0200  Sebastian Dröge <[email protected]>

        * gst/wavparse/gstwavparse.c:
          wavparse: Don't do calculations with -1 offsets when handling SEGMENT 
events
          We use that to signal "infinity", taking the difference between that 
and some
          other value is not going to give us any useful result for the end 
offsets of
          segments.

2016-01-12 14:01:21 -0800  Aleix Conchillo Flaqué <[email protected]>

        * gst/rtsp/gstrtspsrc.c:
          rtspsrc: handle rtcp/srtcp caps properly when using interleaved data
          We check the stream profile and use the proper RTCP caps:
          application/x-srtcp if we are using a secure profile and
          application/x-rtcp otherwise.
          https://bugzilla.gnome.org/show_bug.cgi?id=760556

2016-01-15 03:56:49 +0530  Nirbheek Chauhan <[email protected]>

        * sys/osxaudio/gstosxaudioringbuffer.c:
        * sys/osxaudio/gstosxcoreaudiohal.c:
          osxaudio: Fix error handling when selecting/opening devices
          Post an element error when the CoreAudio device cannot be selected or 
opened.
          Also ensure that we post a GST_ERROR with more detail.

2016-01-13 23:40:20 +0100  Sebastian Dröge <[email protected]>

        * gst/wavparse/gstwavparse.c:
          wavparse: When flushing on EOS, don't process more data than the 
"data" size
          Even if we have more data queued up when flushing than the size of 
the data
          chunk, don't process and output it. If the data size is known, this 
likely
          contains another chunk (e.g. an INFO chunk) or things like ID3 tags. 
Just
          outputting them as if they were data is going to cause unexpected 
behaviour
          and unpleasant audio noises.

2016-01-11 16:29:55 +0000  Tim Sheridan <[email protected]>

        * gst/audioparsers/gstsbcparse.c:
          sbcparse: Fix frame length calculation
          SBC frame length calculation wasn't being rounded up to the nearest 
byte
          (as specified in the A2DP 1.0 specification, section 12.9). This could
          cause 'stereo' and 'joint stereo' mode SBC streams to have incorrectly
          calculated frame lengths.
          Incorrect frame length calculation causes frame coalescing to fail, as
          subsequent frames in the stream aren't found in the expected 
locations.
          https://bugzilla.gnome.org/show_bug.cgi?id=742446

2016-01-15 11:36:35 +0000  Thibault Saunier <[email protected]>

        * ext/vpx/gstvp8enc.c:
          vp8enc: Return FLOW_ERROR when an error accures
          FALSE would mean FLOW_OK
          https://bugzilla.gnome.org/show_bug.cgi?id=760666

2016-01-07 20:27:29 +0000  Tim-Philipp Müller <[email protected]>

        * gst/rtp/gstrtpvrawdepay.c:
          rtpvrawdepay: fix major memory leak and performance issue
          We call gst_rtp_buffer_get_payload() which creates a sub-buffer
          of each input buffer, just to copy over metas, and then leak it.
          https://bugzilla.gnome.org/show_bug.cgi?id=760289

2015-12-25 11:41:19 +0100  Sebastian Dröge <[email protected]>

        * gst/audiofx/gstscaletempo.c:
          scaletempo: Free the various buffers in GstBaseTransform::stop()
          Previously we leaked them completely, but as they're specific to the 
caps
          freeing them in stop() instead of finalize() makes most sense.

2015-12-17 16:03:04 +0100  Vincent Dehors <[email protected]>

        * gst/rtp/gstrtpj2kdepay.c:
          rtpj2kdepay: Push one JPEG2000 frame per buffer, not a buffer list 
with multiple buffers
          https://bugzilla.gnome.org/show_bug.cgi?id=758943



Download
========
https://download.gnome.org/sources/gst-plugins-good/1.6/gst-plugins-good-1.6.3.tar.xz
 (3.05M)
  sha256sum: 24b19db70b2a83461ebddfe20033db432dadfdb5d4b54ffb1dfa0d830134a177

_______________________________________________
[email protected]
https://mail.gnome.org/mailman/listinfo/release-team
Release-team lurker? Do NOT participate in discussions.

Reply via email to