=== release 1.12.5 === 2018-03-28 14:16:40 +0100 Tim-Philipp Müller * ChangeLog: * NEWS: * RELEASE: * configure.ac: * gstreamer.doap: * meson.build: Release 1.12.5 2018-03-28 14:16:40 +0100 Tim-Philipp Müller * docs/plugins/inspect/plugin-coreelements.xml: * docs/plugins/inspect/plugin-coretracers.xml: Update docs 2017-11-20 17:01:04 +0100 Edward Hervey * gst/gstregistrychunks.c: registrychunks: Make sure we use aligned memory This is in the same vein as for all other features. Some systems might not allow unaligned read. 2018-02-14 19:12:06 +0000 Tim-Philipp Müller * docs/libs/gstreamer-libs-docs.sgml: docs: add index for new symbols in 1.12 2018-02-14 19:37:35 +0000 Tim-Philipp Müller * docs/libs/gstreamer-libs-sections.txt: docs: add flow combiner ref/unref to docs So new-in-1.12 index actually has some entries. 2017-10-10 15:53:38 +0200 fengalin * libs/gst/base/gstflowcombiner.c: flowcombiner: Fix version for ref and unref functions The functions were introduced in version 1.12.1, GstFlowCombiner was introduced in 1.4. https://bugzilla.gnome.org/show_bug.cgi?id=788778 2018-01-20 15:30:53 +0000 Tim-Philipp Müller * gst/gstchildproxy.c: childproxy: gracefully handle methods being NULL Do this for all method invoke functions for consistency. https://bugzilla.gnome.org/show_bug.cgi?id=750154 2017-08-01 10:43:32 +0200 Michele Dionisio * libs/gst/net/gstptpclock.c: ptp: fix build failure with #undef USE_MEASUREMENT_FILTERING "Label ‘out’ used but not defined", since it's also used by the USE_MEDIAN_PRE_FILTERING branch. https://bugzilla.gnome.org/show_bug.cgi?id=785631 2018-01-11 17:10:45 +0000 Tim-Philipp Müller * gst/gstplugin.c: plugin: plugin_load() must return a ref even if it was loaded already Fix refcounting issue when plugin was loaded already. gst_plugin_load() is supposed to return a ref, so it must always return a ref. This also fixes the gstplugin unit test on windows where fork is not available and where test_load_coreelements() would unref a plugin ref it didn't get and then mess up the internal registry plugin list state for the next test, in case where the test registry does not exist yet. 2018-01-11 11:36:53 +0000 Tim-Philipp Müller * gst/gstinfo.c: info: reset default threshold to LEVEL_DEFAULT not 0 in set_threshold_from_string(). 2017-12-26 18:08:31 +0100 Sebastian Dröge * gst/gststreams.h: streams: GstStreamType/GstStream are available since 1.10 Annotate them as such. 2017-12-21 13:47:52 +0200 Sebastian Dröge * plugins/elements/gstdownloadbuffer.c: downloadbuffer: Don't hold the mutex while posint the download-complete message Something might handle it from a sync message handler and call back into downloadbuffer, causing a deadlock. 2017-12-20 18:56:23 +0200 Sebastian Dröge * gst/gstsystemclock.c: systemclock: set_default() clock parameter can be NULL 2017-12-20 18:11:48 +0200 Sebastian Dröge * gst/gstelement.c: element: Annotate set_clock() clock parameter with allow-none 2017-12-20 18:09:28 +0200 Sebastian Dröge * gst/gstelement.c: element: Annotate set_bus() bus parameter as allow-none It's possible to replace the bus with NULL/None 2017-12-17 14:18:38 +0200 Sebastian Dröge * gst/gstplugin.c: plugin: Annotate add_dependency() arguments as NULL-terminated arrays 2017-12-06 13:40:46 +0200 Sebastian Dröge * gst/gstevent.c: * gst/gstmessage.c: * gst/gstquery.c: event/query/message: Annotate get_structure() return value as nullable 2017-12-03 14:48:22 +0200 Sebastian Dröge * gst/gstdebugutils.c: * gst/gstplugin.c: * gst/gstregistry.c: gst: Annotate various strings as type filename if they represent a path/filename 2018-01-16 10:17:58 +0100 Edward Hervey * gst/gstpad.c: gstpad: Avoid stream-dead-lock on deactivation The following case can happen when two thread try to activate and deactivate a pad at the same time: T1: starts to deactivate, calls pre_activate(), sets in_activation to TRUE and carries on T2: starts to activate, calls pre_activate(), in_activation is TRUE so it waits on the GCond T1: calls post_activate(), tries to acquire the streaming lock .. but can't because T2 is currently holding it With this patch, the deadlock will no longer happen but does not solve the problem that: T2: will resume activation of the pad, set the pad mode to the target one (PUSH or PULL) and eventually the streaming lock gets released. T1: is able to finish calling post_activate() ... but ... the pad wasn't deactivated (T2 was the last one to "activate" the pad. https://bugzilla.gnome.org/show_bug.cgi?id=792341 2018-01-15 18:13:45 +0100 Edward Hervey * gst/gstpad.c: gstpad: Release pending g_cond_wait() when stopping/pausing task Otherwise we would deadlock waiting forever for the streaming lock to be released https://bugzilla.gnome.org/show_bug.cgi?id=792341