Commit 7f0e7ddd authored by Sebastian Dröge's avatar Sebastian Dröge 🍵

Release 1.10.5

parent 1714489c
=== release 1.10.5 ===
2017-06-15 Sebastian Dröge <slomo@coaxion.net>
* configure.ac:
releasing 1.10.5
2017-05-12 13:08:30 +0900 Hyunjun Ko <zzoon@igalia.com>
* gst/vaapi/gstvaapisink.c:
vaapisink: keep handle_events flag except that if user want to set
When state of vaapisink is changed from PLAYING to NULL, the handle_events
flag is set to FALSE, and never recovered, and then event thread is never
going to run.
So we should allow to set the flag only when users try it.
https://bugzilla.gnome.org/show_bug.cgi?id=782543
2017-04-28 15:20:01 +0200 Víctor Manuel Jáquez Leal <vjaquez@igalia.com>
* gst/vaapi/gstvaapipluginutil.c:
plugins: remove par from caps negotiation
https://bugzilla.gnome.org/show_bug.cgi?id=781759
2017-04-26 15:48:01 +0200 Víctor Manuel Jáquez Leal <vjaquez@igalia.com>
* gst/vaapi/gstvaapipostprocutil.c:
* gst/vaapi/gstvaapisink.c:
plugins: handle pixel-aspect-ratio with value 0/1
When downstream negotiates a pixel-aspect-ratio of 0/1, the
calculations for resizing and formatting in vaapipostproc and
vaapisink, respectively, failed, and thus the pipeline.
This patch handles this situation by converting p-a-r of 0/1 to
1/1. This is how other sinks, such as glimagesink, work.
2017-04-27 14:42:55 +0900 Hyunjun Ko <zzoon@igalia.com>
* gst/vaapi/gstvaapivideobufferpool.c:
vaapivideobufferpool: fix leak of created allocator
Since it's created by itself, it should be unref-counted
after gst_buffer_pool_config_set_allocator call. Afterwards,
this allocator will be ref-counted again when assigning to priv->allocator.
https://bugzilla.gnome.org/show_bug.cgi?id=781577
2017-04-21 19:07:18 +0200 Víctor Manuel Jáquez Leal <vjaquez@igalia.com>
* gst/vaapi/gstvaapivideobufferpool.c:
vaapivideobufferpool: create or reconfig allocator
Sometimes a video decoder could set different buffer pool
configurations, because their frame size changes. In this case we
did not reconfigure the allocator.
This patch enables this use case, creating a new allocator inside
the VAAPI buffer pool if the caps changed, if it is not dmabuf-based.
If so, it is just reconfigured, since it doesn't have a surface pool.
https://bugzilla.gnome.org/show_bug.cgi?id=781577
2017-04-05 11:15:41 -0700 Scott D Phillips <scott.d.phillips@intel.com>
* gst-libs/gst/vaapi/gstvaapiencoder_vp9.c:
libs: encoder: vp9: Fix initialization of ref_list
gcc 7.0.1 gives a memset-elt-size warning in gst_vaapi_encoder_vp9_init:
'memset' used with length equal to number of elements without
multiplication by element size [-Werror=memset-elt-size]
https://bugzilla.gnome.org/show_bug.cgi?id=780947
2017-03-31 14:12:43 -0700 Sreerenj Balachandran <sreerenj.balachandran@intel.com>
* gst-libs/gst/vaapi/gstvaapiencoder_h264.c:
encoder: h264: Fix Backward ReferencePicture flag setting
This is a regression introduced by e829b62 which
override the reference flags and caused issues with
latest intel-vaapi-driver.
2017-03-28 10:53:20 -0700 Sreerenj Balachandran <sreerenj.balachandran@intel.com>
* gst-libs/gst/vaapi/gstvaapiencoder_h264.c:
encoder: h264: Fix B frame encoding artifacts
The current implementation is updating the POC values only
in Slice parameter Buffer.But we are not filling the
picture order count and reference flags in VAPictureH264
while populating VA Picture/Slice structures.The latest
intel-vaapi-driver is directly accessing the above fields
from VAPicutreH264 provided as RefPicLists, which resulted
some wrong maths and prediction errors in driver.
https://bugzilla.gnome.org/show_bug.cgi?id=780620
2017-03-21 17:39:28 +0100 Mathieu Duponchelle <mathieu.duponchelle@opencreed.com>
* meson.build:
meson.build: update version
https://bugzilla.gnome.org/show_bug.cgi?id=780363
2017-02-08 10:17:40 -0800 Scott D Phillips <scott.d.phillips@intel.com>
* configure.ac:
* gst-libs/gst/vaapi/Makefile.am:
* gst-libs/gst/vaapi/gstvaapidisplay.c:
* gst-libs/gst/vaapi/gstvaapiversion.h.in:
make: remove gstvaapiversion.h generation
https://bugzilla.gnome.org/show_bug.cgi?id=778250
https://bugzilla.gnome.org/show_bug.cgi?id=780363
2017-02-15 19:14:59 +0000 Tim-Philipp Müller <tim@centricular.com>
* meson.build:
meson: gstreamer-codecparsers is a required dep
Just like in configure.ac.
https://bugzilla.gnome.org/show_bug.cgi?id=780363
2017-02-06 15:46:20 -0800 Scott D Phillips <scott.d.phillips@intel.com>
* gst-libs/gst/base/meson.build:
* gst-libs/gst/meson.build:
* gst-libs/gst/vaapi/meson.build:
* gst-libs/meson.build:
* gst/meson.build:
* gst/vaapi/meson.build:
* meson.build:
* meson_options.txt:
vaapi: add meson build
https://bugzilla.gnome.org/show_bug.cgi?id=778250
https://bugzilla.gnome.org/show_bug.cgi?id=780363
2017-03-13 17:29:59 +0900 Hyunjun Ko <zzoon@igalia.com>
* gst/vaapi/gstvaapiencode_h264.c:
* gst/vaapi/gstvaapiencode_h265.c:
docs: h264/h265: put parser to the example pipeline
https://bugzilla.gnome.org/show_bug.cgi?id=778749
2017-03-13 16:20:59 +0900 Hyunjun Ko <zzoon@igalia.com>
* gst-libs/gst/vaapi/gstvaapiencoder_h265.c:
libs: encoder: h265: fix reserved length of bits
Fix reserved length of bits for bit_depth_luma_minus8 and bit_depth_chroma_minus8
https://bugzilla.gnome.org/show_bug.cgi?id=778749
2017-03-12 18:59:42 +0100 Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* gst-libs/gst/vaapi/gstvaapidisplay_drm.c:
* tests/test-display.c:
O_CLOEXEC needs _GNU_SOURCE defined
From man open(2):
The O_CLOEXEC, O_DIRECTORY, and O_NOFOLLOW flags are not specified
in POSIX.1-2001, but are specified in POSIX.1-2008. Since glibc
2.12, one can obtain their definitions by defining either
_POSIX_C_SOURCE with a value greater than or equal to 200809L or
_XOPEN_SOURCE with a value greater than or equal to 700. In glibc
2.11 and earlier, one obtains the definitions by defining
_GNU_SOURCE.
And indeed, with the uClibc C library, O_CLOEXEC is not exposed if
_GNU_SOURCE is not defined. Therefore, this commit fixes the build of
gstreamer-vaapi with the uClibc C library.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
https://bugzilla.gnome.org/show_bug.cgi?id=779953
2017-03-14 16:07:08 +0100 Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>
* README:
README: fix "Sources" section
Update the URL where the release source tarballs can be downloaded.
2017-03-12 21:39:53 +0100 Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* README:
README: fix "Reporting bugs" section
The "Reporting bugs" section gives
https://bugzilla.gnome.org/enter_bug.cgi?product=gstreamer-vaapi as the
link to report a bug, but this link says "Sorry, entering a bug into the
product gstreamer-vaapi has been disabled.".
This commit fixes the URL to point to the proper location, and also
removes the following paragraph that is no longer correct.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
https://bugzilla.gnome.org/show_bug.cgi?id=779954
2017-02-22 15:02:01 -0800 Sreerenj Balachandran <sreerenj.balachandran@intel.com>
* configure.ac:
configure: Add missing compiler flags
The AC_CHECK_HEADERS macro was failing to locate some headers, in
particular the va_enc_* headers due to missing compiler flags.
https://bugzilla.gnome.org/show_bug.cgi?id=779101
Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>
=== release 1.10.4 ===
2017-02-23 Sebastian Dröge <slomo@coaxion.net>
2017-02-23 16:13:10 +0200 Sebastian Dröge <sebastian@centricular.com>
* ChangeLog:
* NEWS:
* configure.ac:
releasing 1.10.4
* gstreamer-vaapi.doap:
Release 1.10.4
2017-02-07 16:17:39 +0900 Hyunjun Ko <zzoon@igalia.com>
......
# GStreamer 1.10 Release Notes
GStreamer 1.10.0 was originally released on 1st November 2016.
The latest bug-fix release in the 1.10 series is [1.10.4](#1.10.4) and was
released on 23 February 2017.
The latest bug-fix release in the 1.10 series is [1.10.5](#1.10.5) and was
released on 15 June 2017.
The GStreamer team is proud to announce a new major feature release in the
stable 1.x API series of your favourite cross-platform multimedia framework!
......@@ -13,7 +13,7 @@ improvements.
See [https://gstreamer.freedesktop.org/releases/1.10/][latest] for the latest
version of this document.
*Last updated: Thursday 23 Feb 2017, 15:00 UTC [(log)][gitlog]*
*Last updated: Thursday 15 Jun 2017, 09:30 UTC [(log)][gitlog]*
[latest]: https://gstreamer.freedesktop.org/releases/1.10/
[gitlog]: https://cgit.freedesktop.org/gstreamer/www/log/src/htdocs/releases/1.10/release-notes-1.10.md
......@@ -1159,7 +1159,7 @@ GIT logs or ChangeLogs of the particular modules.
### 1.10.4
The third 1.10 bug-fix release (1.10.4) was released on 23 February 2017.
The fourth 1.10 bug-fix release (1.10.4) was released on 23 February 2017.
This release only contains bugfixes and it should be safe to update from 1.10.x.
#### Major bugfixes in 1.10.4
......@@ -1181,6 +1181,32 @@ GIT logs or ChangeLogs of the particular modules.
[buglist-1.10.4]: https://bugzilla.gnome.org/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&classification=Platform&limit=0&list_id=187054&order=bug_id&product=GStreamer&query_format=advanced&resolution=FIXED&target_milestone=1.10.4
<a name="1.10.5"></a>
### 1.10.5
The fifth 1.10 bug-fix release (1.10.5) was released on 15 June 2017.
This release only contains bugfixes and it should be safe to update from 1.10.x.
This is most likely the last release in the stable 1.10 release series.
#### Major bugfixes in 1.10.5
- Various fixes for crashes, assertions, deadlocks and memory leaks
- Fix for regression in rtpjitterbuffer that caused PTS to be reset to 0 on
- Fix detection of some HLS streams
- Various fixes to the MOV/MP4 muxer and demuxer
gaps in the input
- gst-libav was updated to ffmpeg 3.2.5, fixing a couple of CVEs
- ... and many, many more!
For a full list of bugfixes see [Bugzilla][buglist-1.10.5]. Note that this is
not the full list of changes and also does not include bug reports that were
closed after the 1.12.0 release. For the full list of changes please refer to
the GIT logs or ChangeLogs of the particular modules.
[buglist-1.10.5]: https://bugzilla.gnome.org/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&classification=Platform&limit=0&list_id=187054&order=bug_id&product=GStreamer&query_format=advanced&resolution=FIXED&target_milestone=1.10.5
## Known Issues
- iOS builds with iOS 6 SDK and old C++ STL. You need to select iOS 6 instead
......
# gstreamer-vaapi package version number
m4_define([gst_vaapi_major_version], [1])
m4_define([gst_vaapi_minor_version], [10])
m4_define([gst_vaapi_micro_version], [4])
m4_define([gst_vaapi_micro_version], [5])
m4_define([gst_vaapi_nano_version], [0])
m4_define([gst_vaapi_version],
[gst_vaapi_major_version.gst_vaapi_minor_version.gst_vaapi_micro_version])
......@@ -16,9 +16,9 @@ dnl - interfaces added/removed/changed -> increment CURRENT, REVISION = 0
dnl - interfaces added -> increment AGE
dnl - interfaces removed -> AGE = 0
# gstreamer-vaapi library (libtool) version number
m4_define([gst_vaapi_lt_current], [1004])
m4_define([gst_vaapi_lt_current], [1005])
m4_define([gst_vaapi_lt_revision], [0])
m4_define([gst_vaapi_lt_age], [1004])
m4_define([gst_vaapi_lt_age], [1005])
# glib version number
m4_define([glib_version], [2.40])
......
......@@ -25,6 +25,15 @@
</GitRepository>
</repository>
<release>
<Version>
<revision>1.10.5</revision>
<branch>1.10</branch>
<created>2017-06-15</created>
<file-release rdf:resource="http://gstreamer.freedesktop.org/src/gstreamer-vaapi/gstreamer-vaapi-1.10.5.tar.xz" />
</Version>
</release>
<release>
<Version>
<revision>1.10.4</revision>
......
project('gstreamer-vaapi', 'c',
version : '1.10.4',
version : '1.10.5',
meson_version : '>= 0.36.0',
default_options : [ 'warning_level=1',
'buildtype=debugoptimized' ])
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment