summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2019-05-29Release 1.14.51.14.51.14Tim-Philipp Müller7-21/+297
2019-05-29Update docsTim-Philipp Müller13-14/+14
2019-05-02Update common submodule locationMatthew Waters1-1/+1
Remove the git directory
2019-05-02Clone the code from gitlabHaihao Xiang2-3/+3
This fixes https://gitlab.freedesktop.org/gstreamer/gst-plugins-ugly/issues/22
2019-05-02x264: Link to gmodule in the meson build if extra x264 libraries are providedSebastian Dröge1-1/+4
We would dynamically load additional x264 libraries then.
2019-05-02meson: Always require the gmodule dependencySebastian Dröge2-1/+2
It's needed by the dvdread plugin but also by the x264 plugin in certain circumstances. As it's part of GLib and always available, simply move it as a hard dependency to the top-level meson.build.
2019-05-01x264: Only enable dynamic loading code for x264 < 253Sebastian Dröge1-2/+2
Otherwise we get some compiler warnings: ../subprojects/gst-plugins-ugly/ext/x264/gstx264enc.c:200:1: warning: ‘unload_x264’ defined but not used [-Wunused-function] unload_x264 (GstX264EncVTable * vtable) ^~~~~~~~~~~ ../subprojects/gst-plugins-ugly/ext/x264/gstx264enc.c:154:1: warning: ‘load_x264’ defined but not used [-Wunused-function] load_x264 (const gchar * filename) ^~~~~~~~~
2019-05-01sid: Fix cross-compilation by using AC_TRY_LINK instead of AC_TRY_RUNHelmut Grohne1-6/+2
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917899
2018-10-02Release 1.14.41.14.4Tim-Philipp Müller6-9/+82
2018-10-02Update docsTim-Philipp Müller13-13/+13
2018-09-16Release 1.14.31.14.3Tim-Philipp Müller6-11/+156
2018-09-16Update docsTim-Philipp Müller13-13/+13
2018-08-17x264enc: Set bit depth for x264 ≥ 153Jan Alexander Steffens (heftig)1-0/+3
https://bugzilla.gnome.org/show_bug.cgi?id=796975
2018-08-16meson: Unify required version to 0.40.1Nicolas Dufresne1-1/+1
2018-07-20Release 1.14.21.14.2Tim-Philipp Müller6-144/+284
2018-07-20Update docsTim-Philipp Müller13-13/+13
2018-07-18asfdemux: Remove 0.10 codeEdward Hervey1-12/+0
This was used to "close" a segment. It's no longer needed anymore in 1.x (it was essentially sending the same thing again)
2018-07-18asfdemux: Only send flush event on seeking flushesEdward Hervey1-8/+6
And not on all the time
2018-05-17Release 1.14.11.14.1Tim-Philipp Müller6-25/+209
2018-05-17Update docsTim-Philipp Müller13-13/+13
2018-05-17Update translationsTim-Philipp Müller1-32/+29
2018-04-17asfdemux: Set the stream-format field of H264 streamsSebastian Dröge1-0/+8
If we have codec_data it will be AVC, otherwise assume byte-stream.
2018-03-19Release 1.14.01.14.0Tim-Philipp Müller6-65/+222
2018-03-19Update docsTim-Philipp Müller13-13/+13
2018-03-13Release 1.13.911.13.91Tim-Philipp Müller6-41/+945
2018-03-13Update docsTim-Philipp Müller13-13/+13
2018-03-12docs: plugins: minor addition to plugins listTim-Philipp Müller1-1/+2
2018-03-08configure.ac: enable largefile support if possibleMichael Tretter1-0/+6
https://bugzilla.gnome.org/show_bug.cgi?id=793103
2018-03-03Release 1.13.901.13.90Tim-Philipp Müller6-151/+842
2018-03-03Update docsTim-Philipp Müller14-14/+14
2018-03-01meson: enable more warningsMathieu Duponchelle2-1/+55
2018-02-28x264enc: fix build with newer x264 with support for multiple bit depthsTim-Philipp Müller1-1/+34
libx264 used to be built for one specific bit depth, and if we wanted to support multiple bit depths we would have to dynamically load the right .so from different paths. That has changed now, and libx264 can include support for multiple depths in the same lib, so we don't need to do the dlopen() dance any more. We'll keep the vtable stuff around until we can drop support for older x264. gstx264enc.c:2927:36: error: ‘x264_bit_depth’ undeclared https://bugzilla.gnome.org/show_bug.cgi?id=792111
2018-02-27x264enc: Add format example for option-stringAlicia Boya García1-1/+2
https://bugzilla.gnome.org/show_bug.cgi?id=793879
2018-02-21meson: simplify GST_DISABLE_GST_DEBUG check and don't use add_global_*Tim-Philipp Müller1-20/+8
add_global_arguments() can't be used in subprojects. It's entirely possible that -ugly is a subproject but gstreamer is picked up from an installed location, so we should really use add_project_arguments() in both cases.
2018-02-15Back to developmentTim-Philipp Müller15-17/+17
2018-02-15Release 1.13.11.13.1Tim-Philipp Müller4-624/+114
2018-02-15docs: update plugin docsTim-Philipp Müller16-18/+27
2018-02-15po: update translationsTim-Philipp Müller4-128/+120
2018-02-08meson: make version numbers ints and fix int/string comparisonTim-Philipp Müller1-5/+5
WARNING: Trying to compare values of different types (str, int). The result of this is undefined and will become a hard error in a future Meson release.
2018-02-05autotools: use -fno-strict-aliasing where supportedTim-Philipp Müller1-2/+6
https://bugzilla.gnome.org/show_bug.cgi?id=769183
2018-01-30meson: use -fno-strict-aliasing where supportedTim-Philipp Müller2-4/+11
https://bugzilla.gnome.org/show_bug.cgi?id=769183
2018-01-03amrnbdec: Don't use g_return_*_if_fail() on data parsingEdward Hervey1-4/+2
Those functions can be disabled. Instead just use the (existing) function. CID #1427121
2018-01-03amrwbdec: Don't use g_return_*_if_fail() on data parsingEdward Hervey1-4/+2
Those functions can be disabled. Instead just use the (existing) function. CID #1427093
2017-12-26meson: skip translations if gettext is not availableTim-Philipp Müller1-1/+5
2017-12-14Automatic update of common submoduleMatthew Waters1-0/+0
From e8c7a71 to 3fa2c9e
2017-12-08x264enc: add 'insert-vui' property for users to chooseJustin Kim2-0/+19
VUI(Video Usability Information) parameters should be set according to the specification. However, some of the existing hardware decoders refuse to decode in certain combinations of the resolution and VUI parameters. To support the legacy decoders, this patch provides 'insert-vui' to skip the settings. https://bugzilla.gnome.org/show_bug.cgi?id=791331
2017-12-06cdio: Fix build with cdio >= 1.0Sebastian Dröge3-9/+9
LIBCDIO_VERSION_NUM was defined as e.g. 94 for 0.94 but is now defined as 1 for 1.0. We had various checks for < 83, which of course succeeded now although we are >= 0.83. Fix this by checking for < 76 (0.76) too, as that is the minimum version we currently support and everything < 76 is going to be >= 1.0. https://bugzilla.gnome.org/show_bug.cgi?id=791301
2017-11-27Automatic update of common submoduleMatthew Waters1-0/+0
From 3f4aa96 to e8c7a71
2017-11-26configure: actually use -fvisibility if supportedTim-Philipp Müller1-2/+2
Fix up for previous commit.
2017-11-26autotools: stop controlling symbol visibility with -export-symbols-regexTim-Philipp Müller1-1/+11
Instead, use -fvisibility=hidden and explicit exports via GST_EXPORT. This should result in consistent behaviour for the autotools and Meson builds.