AgeCommit message (Collapse)AuthorFilesLines
5 daysBack to development1.18Tim-Philipp Müller1-1/+1
5 daysRelease Müller5-7/+175
2020-12-06Back to developmentTim-Philipp Müller1-1/+1
2020-12-06Release Müller5-4/+219
2020-10-27Back to developmentTim-Philipp Müller1-1/+1
2020-10-26Release Müller5-21/+254
2020-09-08Back to developmentTim-Philipp Müller1-1/+1
2020-09-08Release Müller7-72/+2115
2020-09-07meson: dist pot file in tarballTim-Philipp Müller3-0/+47
Part-of: <>
2020-09-07x264: Update for gst_video_transfer_function_*() function renamingSebastian Dröge1-1/+1
Part-of: <>
2020-08-24x264enc: Allow maximum quantizer value of 63 instead of 51Sebastian Dröge2-6/+6
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: <>
2020-08-20Release 1.17.901.17.90Tim-Philipp Müller5-42/+143
2020-07-29amrnbenc: remove global variablesJordan Petridis1-4/+1
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: <>
2020-07-27rmdemux: Don't ignore the return value of gst_segment_do_seek()Jan Schmidt1-2/+5
If gst_segment_do_seek() fails, fail the seek. Part-of: <>
2020-07-27asfdemux: Don't ignore the return result of gst_segment_do_seek()Jan Schmidt1-6/+13
gst_segment_do_seek() can fail, and our seek should fail accordingly. Part-of: <>
2020-07-26asfdemux: Only forward SEEK event when in push mode.Derek Lesho1-5/+5
Part-of: <>
2020-07-25meson: add a plugin summaryStéphane Cerveau1-0/+15
This summary displays a list of plugins which have been enabled. Part-of: <>
2020-07-23x264enc: Add a 'Zero Latency' profileThibault Saunier1-0/+3
Part-of: <>
2020-07-22tests/x264enc: Don't declare variables inside the for loop headerMathieu Duponchelle1-6/+18
This is a C99 feature Part-of: <>
2020-07-22tests: x264enc: Test formats are compatible with profileJan Alexander Steffens (heftig)1-7/+50
Part-of: <>
2020-07-21x264enc: Separate high-10 video formats from 8-bit formatsJan Alexander Steffens (heftig)1-13/+18
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: <>
2020-07-21tests: x264enc: Test 10-bit formatsJan Alexander Steffens (heftig)1-6/+57
Part-of: <>
2020-07-21tests: x264enc: Test all (8-bit) video formatsJan Alexander Steffens (heftig)1-22/+30
Part-of: <>
2020-07-10x264enc: Forward downstream colorimetry and chroma-site upstreamThibault Saunier1-0/+6
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: <>
2020-07-08meson: set release date from .doap file for releasesTim-Philipp Müller2-0/+59
Part-of: <>
2020-07-03Back to developmentTim-Philipp Müller1-1/+1
2020-07-03Release Müller5-4/+41
2020-06-23meson: mark plugins cache target as always staleMathieu Duponchelle1-0/+1
2020-06-22doc: Stop documenting properties from parentsThibault Saunier1-594/+7
2020-06-20Back to developmentTim-Philipp Müller1-1/+1
2020-06-19Release Müller6-1251/+551
2020-06-10docs: Update plugins cacheThibault Saunier1-86/+86
2020-06-08docs: Update plugins cacheThibault Saunier1-0/+275
2020-06-06siddec: update gst_type_mark_as_plugin_api() callsPhilippe Normand1-2/+2
This was left behind in commit bc1ab5e8e00a7ed6ac5e192af9310bd2146e446a. Part-of: <>
2020-06-06plugins: uddate gst_type_mark_as_plugin_api() callsMathieu Duponchelle4-10/+10
2020-06-03doc: Require hotdoc >= 0.11.0Thibault Saunier1-0/+11
2020-06-03docs: Update gst_plugins_cache.jsonSebastian Dröge1-906/+764
2020-06-03plugins: Use gst_type_mark_as_plugin_api() for all non-element plugin typesSebastian Dröge5-0/+17
2020-06-02asfdemux: extract WM/PartOfSet disc number and count metadataTim-Philipp Müller1-0/+17
Fixes #30 Part-of: <>
2020-06-02asfdemux: sprinkle some INDENT-OFFTim-Philipp Müller1-0/+7
Part-of: <>
2020-05-27tests: fix meson test env setup to make sure we use the right gst-plugin-scannerTim-Philipp Müller1-2/+6
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: <>
2020-05-27dvdreadsrc: fix uninitialized warningGuillaume Desmottes1-1/+1
Variable is always set in actual code paths but let's keep gcc happy. Part-of: <>
2020-05-12meson: Pass native: false to add_languages()Nirbheek Chauhan2-24/+35
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: <>
2020-04-08asfdemux: Always re-initialize metadata and global_metadataDerek Lesho1-4/+23
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.
2020-04-02x264enc: Fix 'ref' property range and defaultNicolas Dufresne1-2/+2
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.
2020-03-19a52dec: Mark as converterThibault Saunier1-1/+1
It is able to do channel downminxing, so technically it is also a converter This is also important so validate knows about that when doing its checks
2020-01-07x264enc: Respect Youtube bitrate recommandationThibault Saunier5-12/+329
Properly follow google recommendations[0] concerning bitrate when the user wants to use the youtube profile. [0]:
2019-12-18ugly: use of g_value_dup_stringStéphane Cerveau1-1/+1
Use helper method to get string from GValue.
2019-12-14x264enc: fixed codestyleDmitry Shusharin1-1/+1
2019-12-14x264enc: corrected em_data value in CEA-708 CC SEI message (fixes #28)Dmitry Shusharin1-1/+1
Section 4.4 of CEA-708-D specification (table 2) requires all bits to be set inside em_data field. h264parse element (and possible third-party decoders such as libav) also follows this requirement.