- May 31, 2021
- May 05, 2021
-
-
There are cases where the video size might be less than 16x16. This change allows the x264 encoder to accept this cases. Part-of: <!44>
-
- Apr 20, 2021
-
-
Doug Nazar authored
Also use seek seqnum for flush & segment events/messages. Part-of: <!81>
-
Doug Nazar authored
Part-of: <!81>
-
- Mar 29, 2021
-
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
Split plugin into features including dynamic types which can be indiviually registered during a static build. More details here: gst-build!199 gstreamer!661 Part-of: <!79>
-
- Mar 19, 2021
-
-
Matthew Waters authored
volatile is not sufficient to provide atomic guarantees and real atomics should be used instead. GCC 11 has started warning about using volatile with atomic operations. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1719 Discovered in gst-plugins-good#868 Part-of: <!78>
-
- Mar 15, 2021
- Nov 04, 2020
-
-
Nirbheek Chauhan authored
This makes it easier to do development with MSVC by making it warn on common issues that GCC/Clang error out for in our CI configuration. Continuation from gst-build!223 Part-of: <!71>
-
- Nov 02, 2020
-
-
Seungha Yang authored
If it's required, mpeg2dec should set it explicitly. Part-of: <!70>
-
- Sep 08, 2020
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Sep 07, 2020
-
-
Tim-Philipp Müller authored
Part-of: <!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
- Jul 25, 2020
- Jul 24, 2020
-
-
Thibault Saunier authored
Part-of: <gstreamer/gst-plugins-ugly!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>
-