Release 1.2.3

This commit is contained in:
Sebastian Dröge 2014-02-08 11:36:27 +01:00
parent ae87b4fb6c
commit 3461ae6d95
8 changed files with 328 additions and 23 deletions

299
ChangeLog
View file

@ -1,9 +1,302 @@
=== release 1.2.2 ===
=== release 1.2.3 ===
2013-12-26 Sebastian Dröge <slomo@coaxion.net>
2014-02-08 Sebastian Dröge <slomo@coaxion.net>
* configure.ac:
releasing 1.2.2
releasing 1.2.3
2014-01-24 19:19:08 +0100 Arnaud Vrac <avrac@freebox.fr>
* plugins/elements/gstmultiqueue.c:
multiqueue: do not reduce single queue below current level
When the single queue size was just bumped by 1 to allow more buffers to
be added, the buffers limit could be reduced to the current level when
setting the max-size-buffers property. This would result in a stall
since the queue would not grow anymore at this point.
Prevent this by not reducing a single queue size below the current
number of buffers + 1.
https://bugzilla.gnome.org/show_bug.cgi?id=712597
2014-02-04 16:20:08 +0100 Sebastian Dröge <sebastian@centricular.com>
* po/id.po:
* po/nl.po:
* po/pt_BR.po:
* po/sk.po:
* po/sr.po:
po: Update translations
2014-01-17 22:53:01 -0300 Thiago Santos <ts.santos@sisa.samsung.com>
* gst/gstpad.c:
pad: fix sticky event leak after sticky_events_foreach
events_foreach adds an extra ref when giving the event to the
user function. In case it was unrefed by the user, this extra ref
disappeared, but events_foreach still should unref again to
lose its own ref before removing the event from the array.
https://bugzilla.gnome.org/show_bug.cgi?id=722467
2014-01-15 00:12:26 -0300 Thiago Santos <ts.santos@sisa.samsung.com>
* plugins/elements/gstmultiqueue.c:
multiqueue: prevent buffering forever with playbin
When prerolling/buffering, multiqueue has its buffers limit set
to 0, this means it can take an infinite amount of buffers.
When prerolling/buffering finishes, its limit is set back to 5, but
only if the current level is lower than 5. It should (almost) never be
and this will cause prerolling/buffering to need to wait to reach the
hard bytes and time limits, which are much higher.
This can lead to a very long startup time. This patch fixes this
by setting the single queues to the max(current, new_value) instead
of simply ignoring the new value and letting it as infinite(0)
https://bugzilla.gnome.org/show_bug.cgi?id=712597
2014-01-15 11:12:08 +0100 Sebastian Dröge <sebastian@centricular.com>
* gst/gstsegment.c:
segment: gst_segment_offset_running_time() will be available in 1.2.3
2014-01-08 15:47:10 +0100 Wim Taymans <wtaymans@redhat.com>
* tests/check/gst/gstsegment.c:
tests: improve check, also check stream-time
2014-01-08 15:31:28 +0100 Wim Taymans <wtaymans@redhat.com>
* tests/check/gst/gstsegment.c:
tests: add unit test for segment _offset_running_time()
Add a unit test to check that positive and negative offsets are applied
correctly in various cases.
2014-01-08 14:57:04 +0100 Wim Taymans <wtaymans@redhat.com>
* gst/gstpad.c:
pad: use new segment offset method to apply the offset
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=721422
2014-01-08 14:54:47 +0100 Wim Taymans <wtaymans@redhat.com>
* gst/gstsegment.c:
* gst/gstsegment.h:
* win32/common/libgstreamer.def:
segment: add method to offset the segment running-time
Add a method that can apply an offset to the calculated running-time of
a segment.
2014-01-08 16:28:54 -0300 Thiago Santos <ts.santos@sisa.samsung.com>
* libs/gst/base/gstbaseparse.c:
baseparse: do not ignore TIME segments
TIME segments are being ignored and a standard initialized
segment is used instead. This causes issues as not properly detecting
reverse playback or not cliping output based on the segment.
This seems to be a regression from one of the GstSegment/GstEvent
redesigns on the 0.10 -> 1.0 transition
2014-01-08 15:23:00 +0100 Wim Taymans <wtaymans@redhat.com>
* gst/gstsegment.c:
segment: take offset into account in _to_position()
Take the offset into account when converting between running-time and
segment positions.
2014-01-08 14:52:04 +0100 Wim Taymans <wtaymans@redhat.com>
* libs/gst/base/gstcollectpads.c:
collectpads: take offset into account for expected segment position
The firt valid segment position is start + offset.
Also add some more debug and a FIXME
2014-01-13 08:37:37 -0300 Thiago Santos <ts.santos@sisa.samsung.com>
* tests/check/libs/baseparse.c:
tests: baseparse: add test for reverse playback on passthrough
Baseparse stores buffers for reverse playback to push on the next
DISCONT, the issue was that it wouldn't ever check for a discont
on passthrough mode as it skips all real parsing. This test
was create to verify this issue and prevent it from happening again
https://bugzilla.gnome.org/show_bug.cgi?id=721941
2014-01-11 10:49:17 -0300 Thiago Santos <ts.santos@sisa.samsung.com>
* tests/check/Makefile.am:
* tests/check/libs/.gitignore:
* tests/check/libs/baseparse.c:
tests: baseparse: add basic test for baseparse
Just a small test to check that basic playback works
2014-01-10 09:10:06 -0300 Thiago Santos <ts.santos@sisa.samsung.com>
* libs/gst/base/gstbaseparse.c:
baseparse: do not accumulate buffers on passthrough mode
If on passthrough during reverse playback, do not accumulate buffers as
baseparse will never check for DISCONT flag to push those buffers.
So just push buffers downstream as if it was forward playback.
https://bugzilla.gnome.org/show_bug.cgi?id=721941
2014-01-02 16:22:37 -0300 Thiago Santos <ts.santos@sisa.samsung.com>
* libs/gst/base/gstbaseparse.c:
baseparse: remove pending_segment as it was being misused
It wasn't required, instead baseparse was using it to check the media
caps to identify if it was handling audio or video.
The pending_segment was removed and a checked_media boolean
replaced it for a more accurate naming.
https://bugzilla.gnome.org/show_bug.cgi?id=721350
2014-01-02 13:43:54 -0300 Thiago Santos <ts.santos@sisa.samsung.com>
* libs/gst/base/gstbaseparse.c:
baseparse: push pending events before GAP event
A GAP event is handled as an empty buffer by sinks and they expect
to receive start up events before GAP events (like a segment).
This is important specially if there is a GAP at the beginning of
a stream (before any buffers) so that the segment event can be
pushed downstream before the GAP
https://bugzilla.gnome.org/show_bug.cgi?id=721350
2014-01-02 13:41:25 -0300 Thiago Santos <ts.santos@sisa.samsung.com>
* libs/gst/base/gstbaseparse.c:
baseparse: refactor pending events pushing
Refactor code repeated 3 times to a common function
https://bugzilla.gnome.org/show_bug.cgi?id=721350
2013-12-04 00:10:36 +0100 Sebastian Rasmussen <sebras@hotmail.com>
* docs/Makefile.am:
* docs/design/Makefile.am:
docs: add missing files for distribution
* add some documentation files in docs/design
* add docs/list-ulink.xsl so check in docs/manual works
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=719814
2014-01-03 11:47:23 +0800 YanpingZhang <zhangyanping210@163.com>
* plugins/elements/gstmultiqueue.c:
multiqueue: Fix hanging if shut down while handling a serialized query
https://bugzilla.gnome.org/show_bug.cgi?id=721253
2014-01-02 13:34:52 +0100 Sebastian Dröge <sebastian@centricular.com>
* tests/check/gst/gstpad.c:
pad: Add unit test for adding/removing blocking probes while a pad is blocked
And make sure that these new probes are actually called if they should
instead of silently blocking the pad forever.
https://bugzilla.gnome.org/show_bug.cgi?id=721289
2014-01-02 13:33:20 +0100 Sebastian Dröge <sebastian@centricular.com>
* gst/gstpad.c:
pad: Check if new probes need to be called when adding/removing some
This allows blocking a pad, add a new blocking probe, removing
the first probe and then having the second probe called. Which
could then decide that data-flow should actually continue
instead of blocking now.
https://bugzilla.gnome.org/show_bug.cgi?id=721289
2014-01-02 11:13:27 +0100 Sebastian Dröge <sebastian@centricular.com>
* plugins/elements/gsttee.c:
* plugins/elements/gsttee.h:
tee: Remove dyn lock
It was used for pad-alloc in 0.10 but currently is completely unused
and not necessary. All pad access is protected by the tee object lock
and keeping another reference to the current pad.
2014-01-02 11:09:59 +0100 Sebastian Dröge <sebastian@centricular.com>
* plugins/elements/gsttee.c:
tee: Keep another ref to our one and only srcpad around while pushing
A pad probe on that pad might otherwise just release the pad, drop
the last reference and cause great misery.
https://bugzilla.gnome.org/show_bug.cgi?id=721300
2013-12-30 19:03:22 +0100 Sebastian Dröge <sebastian@centricular.com>
* gst/gstpad.c:
pad: Keep an extra ref of the pad when calling an IDLE probe immediately
The callback might destroy the pad.
2013-12-30 18:44:24 +0100 Sebastian Dröge <sebastian@centricular.com>
* gst/gstpad.c:
pad: Only call IDLE probes if we are actually idle
Also only check the data types for non-IDLE probes. When we
are idle, we have no data type obviously.
Previously we were calling IDLE probes during data flow whenever
a non-blocking probe would be called. The pad was usually not idle
at that time.
2013-12-30 10:01:39 +0100 Sebastian Dröge <sebastian@centricular.com>
* gst/gstpad.c:
pad: Don't ignore probe callback return value when immediately calling IDLE probe
https://bugzilla.gnome.org/show_bug.cgi?id=721096
2013-12-29 14:06:55 +0000 Pedro Côrte-Real <pedro@pedrocr.net>
* scripts/git-update.sh:
scripts: git-update.sh: fix for non-master branches
Pull from tracking branch instead of origin/master, so
that this works with e.g. 1.2 as well.
=== release 1.2.2 ===
2013-12-26 17:34:18 +0100 Sebastian Dröge <sebastian@centricular.com>
* ChangeLog:
* NEWS:
* RELEASE:
* configure.ac:
* docs/plugins/inspect/plugin-coreelements.xml:
* gstreamer.doap:
* win32/common/config.h:
* win32/common/gstversion.h:
Release 1.2.2
2013-12-26 17:31:38 +0100 Sebastian Dröge <sebastian@centricular.com>
* po/af.po:
* po/az.po:
* po/be.po:
* po/bg.po:
* po/ca.po:
* po/cs.po:
* po/da.po:
* po/de.po:
* po/el.po:
* po/en_GB.po:
* po/eo.po:
* po/es.po:
* po/eu.po:
* po/fi.po:
* po/fr.po:
* po/gl.po:
* po/hr.po:
* po/hu.po:
* po/id.po:
* po/it.po:
* po/ja.po:
* po/lt.po:
* po/nb.po:
* po/nl.po:
* po/pl.po:
* po/pt_BR.po:
* po/ro.po:
* po/ru.po:
* po/rw.po:
* po/sk.po:
* po/sl.po:
* po/sq.po:
* po/sr.po:
* po/sv.po:
* po/tr.po:
* po/uk.po:
* po/vi.po:
* po/zh_CN.po:
* po/zh_TW.po:
Update .po files
2013-12-26 16:44:57 +0100 Sebastian Dröge <sebastian@centricular.com>

2
NEWS
View file

@ -1,2 +1,2 @@
This is GStreamer 1.2.2
This is GStreamer 1.2.3

24
RELEASE
View file

@ -1,5 +1,5 @@
Release notes for GStreamer 1.2.2
Release notes for GStreamer 1.2.3
The GStreamer team is proud to announce a new bug-fix release
@ -42,12 +42,15 @@ contains a set of codecs plugins based on libav (formerly gst-ffmpeg)
Bugs fixed in this release
* 712597 : regression: playbin: buffering of live radio stream never finishes
* 719437 : ghostpad: Clearing ghostpad sticky events when switching targets causes regressions
* 707230 : flacparse: disregards container timestamps
* 712300 : gst-launch: exits with 0 error code even after an error occurred
* 714989 : docs/gst-utils: Fix escaping of stream id format
* 719575 : multiqueue: improve for adaptive scenario
* 712597 : multiqueue: regression: buffering of live radio stream never finishes
* 719814 : docs: add missing files for distribution
* 721253 : multiqueue: May cause hanging if shut down while handling a serialized query
* 721289 : pad: using multiple blocking probes doesn't work as expected
* 721300 : tee: Does not protect pad from being destroyed from pad probe during gst_pad_push()
* 721350 : baseparse: push pending events before GAP
* 721422 : Negative pad offsets don't work
* 721941 : baseparse: do not accumulate buffers on passthrough mode
* 722467 : pad: Leaks events when iterating sticky events and callback drops event
==== Download ====
@ -84,12 +87,11 @@ subscribe to the gstreamer-devel list.
Contributors to this release
* Mark Nauwelaerts
* Olivier Crête
* Philippe Normand
* Arnaud Vrac
* Pedro Côrte-Real
* Sebastian Dröge
* Sebastian Rasmussen
* Thiago Santos
* Tim-Philipp Müller
* Wim Taymans
* YanpingZhang
 

View file

@ -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.2.2],[http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer],[gstreamer])
AC_INIT([GStreamer],[1.2.3],[http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer],[gstreamer])
AG_GST_INIT
dnl initialize automake (we require GNU make)
@ -64,7 +64,7 @@ dnl 1.2.5 => 205
dnl 1.10.9 (who knows) => 1009
dnl
dnl sets GST_LT_LDFLAGS
AS_LIBTOOL(GST, 202, 0, 202)
AS_LIBTOOL(GST, 203, 0, 203)
dnl *** autotools stuff ****

View file

@ -3,7 +3,7 @@
<description>GStreamer core elements</description>
<filename>../../plugins/elements/.libs/libgstcoreelements.so</filename>
<basename>libgstcoreelements.so</basename>
<version>1.2.2</version>
<version>1.2.3</version>
<license>LGPL</license>
<source>gstreamer</source>
<package>GStreamer source release</package>

View file

@ -38,6 +38,16 @@ hierarchy, and a set of media-agnostic core elements.
</GitRepository>
</repository>
<release>
<Version>
<revision>1.2.3</revision>
<branch>1.2</branch>
<name></name>
<created>2014-02-08</created>
<file-release rdf:resource="http://gstreamer.freedesktop.org/src/gstreamer/gstreamer-1.2.3.tar.xz" />
</Version>
</release>
<release>
<Version>
<revision>1.2.2</revision>

View file

@ -62,7 +62,7 @@
#define GST_PACKAGE_ORIGIN "Unknown package origin"
/* GStreamer package release date/time for plugins as YYYY-MM-DD */
#define GST_PACKAGE_RELEASE_DATETIME "2013-12-26"
#define GST_PACKAGE_RELEASE_DATETIME "2014-02-08"
/* Define if static plugins should be built */
#undef GST_PLUGIN_BUILD_STATIC
@ -354,7 +354,7 @@
#define PACKAGE_NAME "GStreamer"
/* Define to the full name and version of this package. */
#define PACKAGE_STRING "GStreamer 1.2.2"
#define PACKAGE_STRING "GStreamer 1.2.3"
/* Define to the one symbol short name of this package. */
#define PACKAGE_TARNAME "gstreamer"
@ -363,7 +363,7 @@
#undef PACKAGE_URL
/* Define to the version of this package. */
#define PACKAGE_VERSION "1.2.2"
#define PACKAGE_VERSION "1.2.3"
/* directory where plugins are located */
#ifdef _DEBUG
@ -401,7 +401,7 @@
#undef USE_POISONING
/* Version number of package */
#define VERSION "1.2.2"
#define VERSION "1.2.3"
/* Define WORDS_BIGENDIAN to 1 if your processor stores words with the most
significant byte first (like Motorola and SPARC, unlike Intel). */

View file

@ -57,7 +57,7 @@ G_BEGIN_DECLS
*
* The micro version of GStreamer at compile time:
*/
#define GST_VERSION_MICRO (2)
#define GST_VERSION_MICRO (3)
/**
* GST_VERSION_NANO:
*