Skip to content

Commit

Permalink
Release 1.14.5
Browse files Browse the repository at this point in the history
  • Loading branch information
@tp-m
tp-m committed May 29, 2019
1 parent f57c830 commit f5beb2d
Show file tree
Hide file tree
Showing 7 changed files with 494 additions and 19 deletions.
275 changes: 275 additions & 0 deletions ChangeLog
View file
@@ -1,3 +1,278 @@
=== release 1.14.5 ===

2019-05-29 17:32:39 +0100 Tim-Philipp Müller <tim@centricular.com>

* ChangeLog:
* NEWS:
* README:
* RELEASE:
* configure.ac:
* gstreamer.doap:
* meson.build:
Release 1.14.5

2019-05-29 17:32:39 +0100 Tim-Philipp Müller <tim@centricular.com>

* docs/plugins/inspect/plugin-coreelements.xml:
* docs/plugins/inspect/plugin-coretracers.xml:
Update docs

2018-11-05 11:07:14 +0800 Haihao Xiang <haihao.xiang@intel.com>

* .gitmodules:
* gstreamer.doap:
* scripts/create-uninstalled-setup.sh:
Clone the code from gitlab
This fixes https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/326

2019-04-23 14:54:03 +0300 Sebastian Dröge <sebastian@centricular.com>

* libs/gst/base/gstaggregator.h:
aggregator: Mark all public structs as Since: 1.14

2019-04-18 10:13:51 +0200 Olivier Crête <olivier.crete@collabora.com>

* libs/gst/base/gstbasesrc.c:
basesrc: Downgrade EOS warning
In the case of pushfilesrc, this is the expected behaviour, so let's
downgrade the warning to a debug message to avoid confusing users.

2019-04-10 10:18:54 +0300 Sebastian Dröge <sebastian@centricular.com>

* gst/gstcontrolbinding.c:
controlbinding: Check if the weak pointer was cleared before explicitly removing it
Otherwise we'll get an assertion if the object behind the weak pointer
was already destroyed in the meantime as we would pass NULL as first
argument to g_object_remove_weak_pointer().

2019-04-05 11:43:53 +0200 Antonio Ospite <antonio.ospite@collabora.com>

* tools/gst-inspect.c:
gst-inspect: fix printing the first field of a GstStructure
When printing a GstStructure property (e.g. the "stats" property in
rtpsession) the first field is printed on the same line of the type
description, and this is both inconsistent compared to how Enum values
are printed and confusing as the reader might miss the first field.
To fix this, add a newline before printing GstStructure fields in
properties.
NOTE: this does not change the existing inconsistent behavior of an
extra newline *after* a GstStructure property, but the latter is not as
annoying and it would take more effort to fix because GstStructure
fields are printed in CAPS descriptions too.

2019-03-21 18:55:16 +1100 Matthew Waters <matthew@centricular.com>

* libs/gst/base/gstaggregator.c:
aggregator: don't leak gap buffer when out of segment

2019-03-21 18:47:04 +1100 Matthew Waters <matthew@centricular.com>

* libs/gst/base/gstaggregator.c:
aggregator: take the pad lock around queue gap event removal
As is done for every other queue interaction

2019-03-20 17:43:02 +1100 Matthew Waters <matthew@centricular.com>

* libs/gst/base/gstbaseparse.c:
baseparse: don't reset the disable-passthrough property value
Resetting as a result of _reset() on PAUSED->READY is unexpected.

2019-03-08 16:19:29 +0100 Santiago Carot-Nemesio <scarot@twilio.com>

* gst/gsttaskpool.c:
gsttaskpool: Do not block tasks while cleaning up the taskpool
There is a deadlock if any thread from the pool tries to push
a new task while other thread is waiting for the pool of threads
to finish. With this patch the thread will get an error when it
tries to add a new task while the taskpool is being cleaned up.

2019-03-06 19:46:46 +0100 Marco Trevisan (Treviño) <mail@3v1n0.net>

* gst/gsturi.c:
gsturi: Fix annotation on get_path to return a nullable
Use proper syntax or the (nullable): part will be part of the description

2019-03-06 19:34:12 +0100 Marco Trevisan (Treviño) <mail@3v1n0.net>

* gst/gstmessage.c:
gstmessage: Fix annotations on details
Details argument should be nullable, but the docstring uses a wrong syntax.

2019-02-28 16:48:57 +0100 Santiago Carot-Nemesio <sancane@gmail.com>

* gst/gsttaskpool.c:
taskpool: Set error in case something goes wrong in the default handlers

2019-02-15 13:23:37 +0200 Sebastian Dröge <sebastian@centricular.com>

* gst/gstbus.c:
bus: Make removing of signal/bus watches thread-safe
Between getting the GSource with the mutex and destroying it, something
else might've destroyed it already and we would have a dangling pointer.
Keep an additional reference just in case.

2019-02-15 13:20:27 +0200 Sebastian Dröge <sebastian@centricular.com>

* gst/gstbus.c:
bus: Don't allow removing signal watches with gst_bus_remove_watch()
Signal watches are reference counted and gst_bus_remove_watch() would
immediately remove it, breaking the reference counting. Only
gst_bus_remove_signal_watch() should be used for removing signal
watches.

2019-01-29 15:49:50 +0200 Sebastian Dröge <sebastian@centricular.com>

* gst/gstpadtemplate.c:
padtemplate: Constructors are all nullable as they check the template name

2019-01-14 16:22:16 +0800 Daniel Drake <drake@endlessm.com>

* gst/gstdeviceprovider.c:
deviceprovider: fix counting number of times started
GstDeviceProvider has a started_count private variable counter,
and the gst_device_provider_start() documentation emphasizes the
importance of balancing the start and stop calls.
However, when starting a provider that is already started, the
current code will never increment the counter more than once.
So you start it twice, but it will have start_count 1, which is the
maximum value it will ever see.
Then when you stop it twice, on the 2nd stop, after decrementing the
counter in gst_device_provider_stop():
else if (provider->priv->started_count < 1) {
g_critical
("Trying to stop a GstDeviceProvider %s which is already stopped",
GST_OBJECT_NAME (provider));
and the program is killed.
Fix this by incrementing the counter when starting a device provider that
was already started.

2018-12-19 00:34:40 +0000 Tim-Philipp Müller <tim@centricular.com>

* libs/gst/base/gstbasesrc.c:
basesrc: ensure submitted buffer list is writable
Fixes flaky appsrc unit test where depending on scheduling
the submitted list might not be writable if submitted via
an action signal from the application thread.
Fixes gst-plugins-base#522

2018-12-01 10:48:11 -0500 Dardo D Kleiner <dardokleiner@gmail.com>

* gst/gstbuffer.c:
buffer: Fix memory corruption in gst_buffer_foreach_meta() when removing metas
Fix corruption of meta list head when removing metas at the beginning
during iteration. Linked list handling in gst_buffer_foreach_meta
failed to track the previous entry and update the correct next pointer
when removing items from beyond the head of the list, resulting in
arbitrary list pointer corruption.
Closes #332

2018-04-02 12:43:57 +0200 Edward Hervey <edward@centricular.com>

* docs/gst/gstreamer-sections.txt:
docs: Update gst core doc

2018-11-04 12:45:57 +0200 Sebastian Dröge <sebastian@centricular.com>

* plugins/elements/gsttypefindelement.c:
typefind: Always forward RECONFIGURE events upstream
Based on a patch by Vincent Penquerc'h <vincent.penquerch@collabora.co.uk>
Fixes https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/67

2018-11-06 20:12:27 +0000 Nicolas Dufresne <nicolas.dufresne@collabora.com>

* plugins/tracers/gstlog.c:
tracers: log: Fix post query trace
The post tracer hooks have a GstQuery argument which was truncated from
the trace. As the post hook is the one that contains the useful data,
this bug was hiding the important information from that trace.

2018-09-20 01:42:48 -0700 Havard Graff <havard@pexip.com>

* gst/gstsystemclock.c:
systemclock: pre-calculate the ratio for multiplying the perf-count on win
Saves a lot of computations.

2018-10-28 12:46:09 +0100 Havard Graff <havard.graff@gmail.com>

* gst/gstpad.c:
* tests/check/gst/gstpad.c:
gstpad: use hook_id instead of hook in called_probes list
A pointer to a hook in this list can easily not be unique, given both
the slice-allocator reusing memory, and the OS re-using freed blocks
in malloc.
By doing many repeated add and remove of probes, this becomes very easily
reproduced.
Instead use hook_id, which *is* unique for a added GHook.

2018-09-20 23:17:52 +1000 Jan Schmidt <jan@centricular.com>

* gst/gstsegment.c:
* tests/check/gst/gstsegment.c:
segment: Allow stop == -1 in gst_segment_to_running_time() and rate < 0
If a segment has stop == -1, then gst_segment_to_running_time()
would refuse to calculate a running time for negative rates,
but gst_segment_do_seek() allows this scenario and uses a
valid duration for calculations.
Make the 2 functions consistent by using any configured duration
to calculate a running time too in that case.
https://bugzilla.gnome.org/show_bug.cgi?id=796559

2018-10-22 15:26:25 +0200 Edward Hervey <edward@centricular.com>

* plugins/elements/gstmultiqueue.c:
multiqueue: Don't clamp running times for position calculation
Since we use full signed running times, we no longer need to clamp
the buffer time.
This avoids having the position of single queues not advancing for
buffers that are out of segment and never waking up non-linked
streams (resulting in an apparent "deadlock").

2018-10-11 14:29:47 +1100 Jan Schmidt <jan@centricular.com>

* libs/gst/net/gstptpclock.c:
ptp clock: Increase tolerance for late follow-up and delay-resp
The follow-up and delay-resp messages carry precise
timestamps for the arrival at the clock master, but
the local return time is unimportant, so we should be very
lenient in accepting them late. Some PTP masters don't
prioritise sending those packets, and we reject all the
responses and never sync - or take forever to do so.
Increase the tolerance to 20x the mean path delay.
Also fix a typo in one debug output that would print
the absolute time of the delay-resp message, not the offset
from the delay-req that it's actually being compared against.

2018-10-11 14:34:40 +1100 Jan Schmidt <jan@centricular.com>

* libs/gst/net/gstptpclock.c:
ptp clock: Wait for ANNOUNCE before selecting a master
Previously, with opportunistic sync we'd track a master
clock as soon as we see a SYNC message, and hence sync up
faster, but then we'd announce we're synched before seeing
the ANNOUNCE, leaving the clock details like grandmaster-clock
empty.
A better way is to start tracking the clock opportunistically,
but not announce we're synched until we've also seen the ANNOUNCE.

2018-10-26 09:21:42 +0100 Sebastian Dröge <sebastian@centricular.com>

* plugins/elements/gsttypefindelement.c:
typefind: Lower debug level of some output related to the URI query
It's not a warning if an URI doesn't have an extension, and it's also
not mandatory that sources have an URI or even answer the URI query.

2018-10-22 13:45:52 +0200 Edward Hervey <edward@centricular.com>

* plugins/elements/gstqueue2.c:
queue2: Reset result flow when retrying
If we ever get a GST_FLOW_EOS from downstream, we might retry
pushing new data. But if pushing that data doesn't return a
GstFlowReturn (such as pushing events), we would end up returning
the previous GstFlowReturn (i.e. EOS).
Not properly resetting it would cause cases where queue2 would
stop pushing on the first GstEvent stored (even if there is more
data contained within).

=== release 1.14.4 ===

2018-10-02 22:53:01 +0100 Tim-Philipp Müller <tim@centricular.com>
Expand Down

0 comments on commit f5beb2d

Please sign in to comment.