- Oct 26, 2020
- Sep 08, 2020
-
-
Tim-Philipp Müller authored
-
- Sep 07, 2020
-
-
Tim-Philipp Müller authored
Part-of: <gstreamer/gst-plugins-ugly!69>
-
Sebastian Dröge authored
Part-of: <!68>
- Aug 24, 2020
-
-
QP_MAX_SPEC in x264 is set to 63 nowadays and in theory it allows even up to 81 (QP_MAX) but that seems to be outside the spec. Part-of: <!67>
-
- Aug 20, 2020
- Jul 29, 2020
-
-
gstcheck is declaring its own buffers glist which ends up overwritten, loks like the code meant to use that already gcc 10 is also complaining about this, but only on static builds for some reason ``` FAILED: subprojects/gst-plugins-ugly/tests/check/elements_amrnbenc /usr/bin/ld: subprojects/gstreamer/libs/gst/check/libgstcheck-1.0.a(gstcheck.c.o):(.bss+0x38): multiple definition of `buffers'; subprojects/gst-plugins-ugly/tests/check/708af1f@@elements_amrnbenc@exe/elements_amrnbenc.c.o:(.bss+0x18): first defined here collect2: error: ld returned 1 exit status ``` also remove unused var `current_buf` Part-of: <!62>
-
- Jul 27, 2020
-
-
If gst_segment_do_seek() fails, fail the seek. Part-of: <gst-plugins-ugly!45>
-
gst_segment_do_seek() can fail, and our seek should fail accordingly. Part-of: <gstreamer/gst-plugins-ugly!45>
-
- Jul 25, 2020
-
-
Part-of: <gstreamer/gst-plugins-ugly!48>
-
This summary displays a list of plugins which have been enabled. Part-of: <gstreamer/gst-plugins-ugly!65>
-
- Jul 24, 2020
-
-
Thibault Saunier authored
Part-of: <!42>
-
- Jul 22, 2020
-
-
Mathieu Duponchelle authored
This is a C99 feature Part-of: <gstreamer/gst-plugins-ugly!64>
-
Jan Alexander Steffens authored
Part-of: <gstreamer/gst-plugins-ugly!59>
-
- Jul 21, 2020
-
-
Jan Alexander Steffens authored
If downstream is constrained to an 8-bit profile, caps queries would still allow I420_10LE as input. If upstream actually sends such a caps event, downstream would fail to accept the high-10 profile. The following pipeline now fails earlier, during the negotiation phase instead of the stream start: gst-launch-1.0 videotestsrc ! video/x-raw,format=I420_10LE \ ! x264enc ! video/x-h264,profile=constrained-baseline \ ! fakesink Part-of: <gstreamer/gst-plugins-ugly!59>
-
Jan Alexander Steffens authored
Part-of: <gstreamer/gst-plugins-ugly!59>
-
Jan Alexander Steffens authored
Part-of: <gstreamer/gst-plugins-ugly!59>
-
- Jul 10, 2020
-
-
Thibault Saunier authored
So that the value can be used by upstream converters when necessary. This whole logic has been copied from `__gst_video_element_proxy_caps` but those 2 fields were missing. Part-of: <gstreamer/gst-plugins-ugly!60>
-
- Jul 08, 2020
-
-
Tim-Philipp Müller authored
Part-of: <gstreamer/gst-plugins-ugly!61>
-
- Jul 03, 2020
-
-
Tim-Philipp Müller authored
-
- Jul 02, 2020
- Jun 22, 2020
-
-
Mathieu Duponchelle authored
-
Thibault Saunier authored
-
- Jun 19, 2020
-
-
Tim-Philipp Müller authored
-
- Jun 10, 2020
-
-
Thibault Saunier authored
-
- Jun 08, 2020
-
-
Thibault Saunier authored
-
- Jun 06, 2020
-
-
Philippe Normand authored
This was left behind in commit bc1ab5e8. Part-of: <gstreamer/gst-plugins-ugly!55>
-
- Jun 05, 2020
-
-
Mathieu Duponchelle authored
-
- Jun 04, 2020
-
-
Thibault Saunier authored
-
-
-
- Jun 02, 2020
-
-
Tim-Philipp Müller authored
Fixes #30 Part-of: <gstreamer/gst-plugins-ugly!54>
-
Tim-Philipp Müller authored
Part-of: <gstreamer/gst-plugins-ugly!54>
-
- May 27, 2020
-
-
Tim-Philipp Müller authored
If core is built as a subproject (e.g. as in gst-build), make sure to use the gst-plugin-scanner from the built subproject. Without this, gstreamer might accidentally use the gst-plugin-scanner from the install prefix if that exists, which in turn might drag in gst library versions we didn't mean to drag in. Those gst library versions might then be older than what our current build needs, and might cause our newly-built plugins to get blacklisted in the test registry because they rely on a symbol that the wrongly-pulled in gst lib doesn't have. This should fix running of unit tests in gst-build when invoking meson test or ninja test from outside the devenv for the case where there is an older or different-version gst-plugin-scanner installed in the install prefix. In case no gst-plugin-scanner is installed in the install prefix, this will fix "GStreamer-WARNING: External plugin loader failed. This most likely means that the plugin loader helper binary was not found or could not be run. You might need to set the GST_PLUGIN_SCANNER environment variable if your setup is unusual." warnings when running the unit tests. In the case where we find GStreamer core via pkg-config we use a newly-added pkg-config var "pluginscannerdir" to get the right directory. This has the benefit of working transparently for both installed and uninstalled pkg-config files/setups. Part-of: <gstreamer/gst-plugins-ugly!53>
-
Guillaume Desmottes authored
Variable is always set in actual code paths but let's keep gcc happy. Part-of: <gstreamer/gst-plugins-ugly!51>
-
- May 11, 2020
-
-
Nirbheek Chauhan authored
This is needed for cross-compiling without a build machine compiler available. The option was added in 0.54, but we only need this in Cerbero and it doesn't affect older versions so it should be ok. Will just cause a spurious warning. Part-of: <gstreamer/gst-plugins-ugly!50>
-
- Apr 08, 2020
-
-
When transitioning from the PAUSED state, to the READY state, and back, metadata and global_metadata are left uninitialized, unlike when the demxuer transitions from NULL to READY, then to PAUSED. I have found this to cause a segmentation fault when fields in these structures are set.
-
- Apr 02, 2020
-
-
The --ref option indicate the size of the DPB, hence should be in the range of 0 to 16. This patch also fix the default to match x264enc default 3. This change isn't a behaviour change since we don't enforce the reported default.
-