Release 1.14.31.14.3

6 files changed, 269 insertions, 9 deletions

diff --git a/ChangeLog b/ChangeLog
index 5092ed7f97..8e01277912 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,158 @@
+=== release 1.14.3 ===
+
+2018-09-16 16:13:01 +0100  Tim-Philipp Müller <tim@centricular.com>
+
+	* ChangeLog:
+	* NEWS:
+	* RELEASE:
+	* configure.ac:
+	* gstreamer.doap:
+	* meson.build:
+	  Release 1.14.3
+
+2018-09-16 16:13:00 +0100  Tim-Philipp Müller <tim@centricular.com>
+
+	* docs/plugins/inspect/plugin-coreelements.xml:
+	* docs/plugins/inspect/plugin-coretracers.xml:
+	  Update docs
+
+2018-08-27 22:32:01 +1000  Jan Schmidt <jan@centricular.com>
+
+	* tests/check/gst/gstsegment.c:
+	  gstsegment: Add check for gst_segment_offset_running_time()
+	  Add a check for gst_segment_offset_running_time() that values
+	  are taken directly from the segment base if possible.
+
+2018-08-23 22:34:47 +1000  Jan Schmidt <jan@centricular.com>
+
+	* gst/gstsegment.c:
+	* tests/check/gst/gstsegment.c:
+	  gstsegment: Handle positions before the segment properly
+	  Fixes for gst_segment_position_from_running_time_full() when
+	  converting running_times that precede the segment start (or
+	  stop in a negative rate segment)
+	  The return value was incorrectly negated in those cases.
+	  Add some more unit test checks for those cases, and especially
+	  for segments with offsets.
+
+2018-09-08 13:05:13 +0100  Philippe Normand <philn@igalia.com>
+
+	* gst/gstbin.c:
+	  bin: Fix use-after-free issue in gst_bin_add()
+	  gst_element_post_message() takes ownership of the message so we need to increase
+	  its refcount until we no longer require access to its data (context_type).
+	  https://bugzilla.gnome.org/show_bug.cgi?id=797099
+
+2018-09-03 12:06:35 +0100  Philippe Normand <philn@igalia.com>
+
+	* gst/gstutils.c:
+	  utils: Set default values for position and duration query results
+	  https://bugzilla.gnome.org/show_bug.cgi?id=797066
+
+2018-08-30 17:44:07 +0100  Philippe Normand <philn@igalia.com>
+
+	* libs/gst/base/gstbaseparse.c:
+	  baseparse: avg_bitrate calculation critical warning fix
+	  The avg_bitrate is an unsigned int, so the gst_util_uin64_scale() function can't
+	  be used for it, as it expects signed integers for the fraction parts arguments.
+	  https://bugzilla.gnome.org/show_bug.cgi?id=797054
+
+2018-08-31 12:15:16 +0300  Sebastian Dröge <sebastian@centricular.com>
+
+	* plugins/elements/gstinputselector.c:
+	  input-selector: Bring latency handling in sync with GstPad code
+
+2018-08-31 12:12:13 +0300  Sebastian Dröge <sebastian@centricular.com>
+
+	* gst/gstpad.c:
+	  Revert "pad: Don't drop LATENCY queries with default implementation"
+	  This reverts commit 794944f779f954375fc74a3fffcc2067bba6a3e5.
+	  Accumulating non-live latency values generally makes no sense and often
+	  gives invalid results with min>max
+
+2018-08-31 12:12:09 +0300  Sebastian Dröge <sebastian@centricular.com>
+
+	* gst/gstpad.c:
+	  Revert "pad: Accumulate live/non-live latency values separately"
+	  This reverts commit f5783e1cacb09867d81ba089b229faa7dd0edd0c.
+
+2018-08-31 11:47:03 +0300  Sebastian Dröge <sebastian@centricular.com>
+
+	* plugins/elements/gstinputselector.c:
+	  input-selector: Apply GstPad default latency handler fixes here too
+
+2018-08-31 11:41:47 +0300  Sebastian Dröge <sebastian@centricular.com>
+
+	* gst/gstpad.c:
+	  pad: Accumulate live/non-live latency values separately
+	  And only ever use the non-live values if all pads are non-live,
+	  otherwise only use the results of all live pads.
+	  It's unclear what one would use the values for in the non-live case, but
+	  by this we at least pass them through correctly then.
+	  This is a follow-up for 794944f779f954375fc74a3fffcc2067bba6a3e5, which
+	  causes wrong latency calculations if the first pad is non-live but a
+	  later pad is actually live. In that case the live values would be
+	  accumulated together with the values of the non-live first pad,
+	  generally causing wrong min/max latencies to be calculated.
+
+2018-08-02 10:55:40 +0300  Sebastian Dröge <sebastian@centricular.com>
+
+	* libs/gst/base/gsttypefindhelper.c:
+	  typefindhelper: Mark gst_type_find_helper_get_range_full() as Since 1.14.3
+
+2018-07-30 18:51:35 +0300  Sebastian Dröge <sebastian@centricular.com>
+
+	* gst/gstpad.c:
+	  pad: Ensure that the pad is blocked for IDLE probes if they are called from the streaming thread too
+	  IDLE probes that are directly called when being added will increase /
+	  decrease the "number of IDLE probes running" counter around the call,
+	  but when running from the streaming thread this won't happen.
+	  This has the effect that when running from a streaming thread it is
+	  possible to push serialized events or data out of the pad without
+	  problems, but otherwise it would deadlock because serialized data would
+	  wait for the IDLE probe to finish first (it is blocking after all!).
+	  With this change it will now always consistently deadlock instead of
+	  just every once in a while, which should make it obvious why this
+	  happens and prevent racy deadlocks in application code.
+	  https://bugzilla.gnome.org/show_bug.cgi?id=796895
+
+2018-07-30 18:10:31 +0300  Sebastian Dröge <sebastian@centricular.com>
+
+	* libs/gst/base/gsttypefindhelper.c:
+	* libs/gst/base/gsttypefindhelper.h:
+	* plugins/elements/gsttypefindelement.c:
+	* win32/common/libgstbase.def:
+	  typefind: Add new gst_type_find_helper_get_range_full() that returns flow return
+	  And make use of it in the typefind element. It's useful to distinguish
+	  between the different errors why typefinding can fail, and especially to
+	  not consider GST_FLOW_FLUSHING as an actual error.
+	  https://bugzilla.gnome.org/show_bug.cgi?id=796894
+
+2018-07-31 16:46:25 +0300  Sebastian Dröge <sebastian@centricular.com>
+
+	* gst/gstpad.c:
+	  pad: Update pad offsets on the current event if the offset changed in pad probes
+	  https://bugzilla.gnome.org/show_bug.cgi?id=796898
+
+2018-07-31 19:25:03 +0300  Sebastian Dröge <sebastian@centricular.com>
+
+	* plugins/elements/gstinputselector.c:
+	  inputselector: Forward LATENCY query to all sinkpads
+	  Otherwise downstream will consider the pipeline not live if the active
+	  pad is live, even though some inactive pads might be live and might
+	  require a non-zero latency configuration.
+	  https://bugzilla.gnome.org/show_bug.cgi?id=796901
+
+2018-07-27 23:22:42 +0200  Mathieu Duponchelle <mathieu@centricular.com>
+
+	* libs/gst/base/gstaggregator.h:
+	  aggregator: annotate GstAggregatorClass::update_src_caps
+
+2018-07-26 02:31:05 +0300  Sebastian Dröge <sebastian@centricular.com>
+
+	* libs/gst/base/gstaggregator.c:
+	  aggregator: Don't leak peer pad of inactive pads when (not) forwarding QoS events to them
+
 === release 1.14.2 ===
 
 2018-07-20 00:46:55 +0100  Tim-Philipp Müller <tim@centricular.com>
diff --git a/NEWS b/NEWS
index 1ce6d6dd15..efb2c98a9d 100644
--- a/NEWS
+++ b/NEWS
@@ -5,13 +5,13 @@ GSTREAMER 1.14 RELEASE NOTES
 
 GStreamer 1.14.0 was originally released on 19 March 2018.
 
-The latest bug-fix release in the 1.14 series is 1.14.1 and was released
-on 17 May 2018.
+The latest bug-fix release in the 1.14 series is 1.14.3 and was released
+on 16 September 2018.
 
 See https://gstreamer.freedesktop.org/releases/1.14/ for the latest
 version of this document.
 
-_Last updated: Thursday 17 May 2018, 12:00 UTC (log)_
+_Last updated: Sunday 16 September 2018, 13:00 UTC (log)_
 
 
 Introduction
@@ -1390,6 +1390,101 @@ For a full list of bugfixes see Bugzilla. Note that this is not the full
 list of changes. For the full list of changes please refer to the GIT
 logs or ChangeLogs of the particular modules.
 
+1.14.3
+
+The third 1.14 bug-fix release (1.14.3) was released on 16 September
+2018.
+
+This release only contains bugfixes and it should be safe to update from
+1.14.x.
+
+Highlighted bugfixes in 1.14.3
+
+-   opusenc: fix crash on 32-bit platforms
+-   compositor: fix major buffer leak when doing crossfading on some but
+    not all pads
+-   wasapi: various fixes for wasapisrc and wasapisink regressions
+-   x264enc: Set bit depth to fix “This build of x264 requires 8-bit
+    depth. Rebuild to…” runtime errors with x264 version ≥ 153
+-   audioaggregator, audiomixer: caps negotiation fixes
+-   input-selector: latency handling fixes
+-   playbin, playsink: audio visualization support fixes
+-   dashdemux: fix possible crash if stream is neither isobmff nor
+    isoff_ondemand profile
+-   opencv: Fix build for opencv >= 3.4.2
+-   h265parse: miscellaneous fixes backported from h264parse
+-   pads: fix changing of pad offsets from inside pad probes
+-   pads: ensure that pads are blocked for IDLE probes if they are
+    called from the streaming thread too
+
+Other noteworthy bugfixes in 1.14.3
+
+-   queries: Set default values for position and duration query results
+-   segment: make gst_segment_position_from_running_time_full() handle
+    positions before the segment properly
+-   aggregator: annotate GstAggregatorClass::update_src_caps for
+    bindings
+-   aggregator: Don’t leak peer pad of inactive pads when (not)
+    forwarding QoS events to them
+-   baseparse: avg_bitrate calculation critical warning fix
+-   typefind: improved flow return handling in pull mode, flushing is
+    not an error
+-   gl: Don’t steal callers reference when setting non-floating elements
+    via properties
+-   gl: Also don’t leak floating references to elements set via
+    properties
+-   tagdemux: Properly propagate gst_pad_pull_range() errors
+-   aacparse: fix codec_data buffer leak
+-   rtpgstpay: Add support for force-keyunit events
+-   rtpL8pay: don’t try to modify a read-only structure
+-   rtpvp8pay, rtpvp9pay, rtpopuspay: Fix VP8/VP9/OPUS dual encoding
+    name handling
+-   rtp payloaders: Use running_time instead of PTS for config-interval
+    calculations
+-   qtdemux: Don’t assert in prefill mode if a track has no samples at
+    all
+-   qmlgl: Ensure GL headers are included
+-   v4l2src: fix first input used is always used next times
+-   v4l2object: Only offer MMAP/DMABUF pool
+-   v4l2object: stop V4L2 from zeroing extended colorimetry for
+    non-mplane
+-   v4l2object: improve colorspace handling for JPEG sources
+-   splitmuxsink: fix handling of repeated timestamps and a leak if sink
+    pads are not released explicitly
+-   player: Set default position and duration value to
+    GST_CLOCK_TIME_NONE
+-   videoaggregator: Make sure to hold object lock while iterating sink
+    pads
+-   audiobuffersplit: improve resync handling and compensate better for
+    accumulated errors
+-   kmssink: add support for Xilinx DRM Driver, mxsfb-drm driver and the
+    Allwinner DRM driver (sun4i-drm)
+-   rsvg: Also accept </svg:svg> as ending tag
+-   ges: project: Compute relocation URIs in missing-uri signal
+-   ges: formatter: Serialize Transition border and invert properties
+-   ges: clip: Resync priorities when removing an effect
+
+Contributors to 1.14.3
+
+Christoph Reiter, Devarsh Thakkar, Edward Hervey, Gary Bisson, Iñigo
+Huguet, Jan Alexander Steffens (heftig), Jan Schmidt, Jerome Laheurte,
+Marcos Kintschner, Mathieu Duponchelle, Matthew Waters, Michael Olbrich,
+Nicolas Dufresne, Nirbheek Chauhan, Paul Kocialkowski, Philippe Normand,
+Philipp Zabel, Roland Jon, Sebastian Dröge, Seungha Yang, Thibault
+Saunier, Tim-Philipp Müller, Yuji Kuwabara, and many others. Thank you
+all.
+
+List of bugs fixed in 1.14.3
+
+For a full list of bugfixes see Bugzilla. Note that this is not the full
+list of changes. For the full list of changes please refer to the GIT
+logs or ChangeLogs of the particular modules.
+
+1.14.4 (future)
+
+The fourth 1.14 bug-fix release (1.14.4) is scheduled to be released
+around October 2018.
+
 
 Known Issues
 
@@ -1413,8 +1508,8 @@ unstable development version leading up to the stable 1.16 release. The
 development of 1.15/1.16 will happen in the git master branch.
 
 The plan for the 1.16 development cycle is yet to be confirmed, but it
-is expected that feature freeze will be around August 2018 followed by
-several 1.15 pre-releases and the new 1.16 stable release in September.
+is expected that feature freeze will be around September 2018 followed
+by several 1.15 pre-releases and the new 1.16 stable release in October.
 
 1.16 will be backwards-compatible to the stable 1.14, 1.12, 1.10, 1.8,
 1.6, 1.4, 1.2 and 1.0 release series.
diff --git a/RELEASE b/RELEASE
index 091aa4862e..b7ebbe0ed2 100644
--- a/RELEASE
+++ b/RELEASE
@@ -1,4 +1,4 @@
-This is GStreamer core 1.14.2.
+This is GStreamer core 1.14.3.
 
 The GStreamer team is pleased to announce another bug-fix release in the
 stable 1.x API series of your favourite cross-platform multimedia framework!
diff --git a/configure.ac b/configure.ac
index 912511bcd5..451381bbbc 100644
--- a/configure.ac
+++ b/configure.ac
@@ -4,7 +4,7 @@ dnl initialize autoconf
 dnl when going to/from release please set the nano (fourth number) right !
 dnl releases only do Wall, git and prerelease does Werror too
 dnl
-AC_INIT([GStreamer],[1.14.2],[http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer],[gstreamer])
+AC_INIT([GStreamer],[1.14.3],[http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer],[gstreamer])
 AG_GST_INIT
 
 dnl initialize automake (we require GNU make)
@@ -62,7 +62,7 @@ dnl      1.2.5 => 205
 dnl      1.10.9 (who knows) => 1009
 dnl
 dnl sets GST_LT_LDFLAGS
-AS_LIBTOOL(GST, 1402, 0, 1402)
+AS_LIBTOOL(GST, 1403, 0, 1403)
 
 dnl *** autotools stuff ****
 
diff --git a/gstreamer.doap b/gstreamer.doap
index ffb540cf55..dd56d24455 100644
--- a/gstreamer.doap
+++ b/gstreamer.doap
@@ -40,6 +40,16 @@ hierarchy, and a set of media-agnostic core elements.
 
  <release>
   <Version>
+   <revision>1.14.3</revision>
+   <branch>1.14</branch>
+   <name></name>
+   <created>2018-09-16</created>
+   <file-release rdf:resource="https://gstreamer.freedesktop.org/src/gstreamer/gstreamer-1.14.3.tar.xz" />
+  </Version>
+ </release>
+
+ <release>
+  <Version>
    <revision>1.14.2</revision>
    <branch>1.14</branch>
    <name></name>
diff --git a/meson.build b/meson.build
index 8ed427c43a..3a64f053b5 100644
--- a/meson.build
+++ b/meson.build
@@ -1,5 +1,5 @@
 project('gstreamer', 'c',
-  version : '1.14.2',
+  version : '1.14.3',
   meson_version : '>= 0.40.1',
   default_options : [ 'warning_level=1',
                       'buildtype=debugoptimized' ])