- Apr 08, 2021
-
-
clocksync defaults to sync=true so should advertise it by default. Part-of: <gstreamer/gstreamer!786>
-
- Apr 07, 2021
-
-
If we set a custom GST_PLUGIN_SCANNER env var, then we probably want to use that and only that. Falling through to the one installed on the system is problamatic in cross-compilation environemnts, regardless of whether one pointed to by the env var succeeded or failed. taken from: http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch?id=0db7ba34ca41b107042306d13a6f0162885c123b Part-of: <gstreamer/gstreamer!669>
-
Part-of: <gstreamer/gstreamer!777>
-
- Apr 06, 2021
-
-
Sebastian Dröge authored
The peeked buffer was always reset after calling ::aggregate() but under no other circumstances. If a pad was removed after peeking and before ::aggregate() returned then the peeked buffer would be leaked. This can easily happen if pads are removed from the aggregator from a pad probe downstream of the source pad but still in the source pad's streaming thread. Part-of: <gstreamer/gstreamer!784>
-
- Apr 02, 2021
-
-
Chris White authored
For use with a single feature now that gst_caps_features_new() is G_GNUC_NULL_TERMINATED. gstreamer/gstreamer!774 (comment 855357) Part-of: <gstreamer/gstreamer!774>
-
Chris White authored
For cases where you only need a media type and no other fields. gstreamer/gstreamer!774 (comment 848664) Part-of: <gstreamer/gstreamer!774>
-
Chris White authored
Functions that require NULL as their last vararg are marked so the compiler can warn on missing NULL. Also, document the NULL terminator for gst_make_element_message_details() and gst_tracer_record_new(). gstreamer/gstreamer#669 Part-of: <gstreamer/gstreamer!774>
-
- Mar 31, 2021
-
-
Pieter Jordaan authored
Always use the monotonic clock's diff and end time for clock_nanosleep to have predictable behaviour even with other clock types. Part-of: <gstreamer/gstreamer!779>
-
- Mar 26, 2021
-
-
Jason Carrete authored
Fixed a small typo in the gst-launch-1.0 man page Part-of: <gstreamer/gstreamer!780>
-
This signal don't run the class handler in the CLEANUP stage. Part-of: <gstreamer/gstreamer!776>
-
- Mar 24, 2021
-
-
unit tests do not need to call deinit as it is already called in exit handler Part-of: <gstreamer/gstreamer!236>
-
Part-of: <gstreamer/gstreamer!236>
-
- Mar 19, 2021
-
-
This macro allows to register a device provider with a custom function which gives more flexibility when registering it (see v4l2 register). Part-of: <gstreamer/gstreamer!773>
-
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: <!775>
-
- Mar 18, 2021
-
-
Add a new property so that clocksync can setup "ts-offset" value based on the first buffer and pipeline's running time when the first arrived. Newly update "ts-offset" in this case would be a value that allows outputting the first buffer without clock waiting. Part-of: <gstreamer/gstreamer!702>
-
- Mar 17, 2021
-
-
This is required because the query could be intercepted and the application could send any other requests to the element from this thread. Part-of: <gstreamer/gstreamer!771>
-
Mathieu Duponchelle authored
Since acdb4ce0 , parsing of the value for a property can use the pspec to determine what type a value should be casted to. However, this broke the case where the value is explicitly casted to a type (eg <(float) 0.0>). In that situation, we want to respect the casting decision, and only use the pspec to perform "implicit" casts. Fixes gstreamer/gst-plugins-base#881 Part-of: <gstreamer/gstreamer!772>
-
- Mar 11, 2021
-
-
Guillaume Desmottes authored
GstClockID is secretly a gpointer so we can't use g_autoptr(), instead user can do: g_auto (GstClockID) clock_id = 0; Part-of: <!769>
-
- Mar 08, 2021
-
-
Stéphane Cerveau authored
The ret test is unrelevant and confusing. We dont want the code to fail and the register to succeed by example. In the case of a conditional element_init, the element should be defined with GST_ELEMENT_REGISTER_DEFINE_CUSTOM instead of GST_ELEMENT_REGISTER_DEFINE_WITH_CODE. Part-of: <gstreamer/gstreamer!768>
-
- Mar 03, 2021
-
-
Stéphane Cerveau authored
-d tests the folder which is existing but with .in file, so I prefered the -f to test if the gst file was available which is not the case, so it fallbacks on the pkg-config Part-of: <gstreamer/gstreamer!766>
-
- Feb 26, 2021
-
-
Stéphane Cerveau authored
Part-of: <gstreamer/gstreamer!766>
-
- Feb 24, 2021
-
-
Guillaume Desmottes authored
Part-of: <gstreamer/gstreamer!764>
-
- Feb 17, 2021
-
-
Mathieu Duponchelle authored
* add a SECTION comment * Misc cleanup / typo fixes / addition of links Part-of: <!760>
-
- Feb 16, 2021
-
-
* Don't repeat what annotations are stating with respect to ownership transfer, nullability * Misc cleanup / typo fixes / addition of links Part-of: <!759>
-
Mathieu Duponchelle authored
This reverts commit fc5cd959.
-
- Feb 15, 2021
-
-
Mathieu Duponchelle authored
* Document virtual methods in standalone comments, in order to properly annotate them * Don't repeat what annotations are stating with respect to ownership transfer, nullability * Mark GstControlBinding ABI field as private * Misc cleanup / typo fixes / addition of links Part-of: <!758>
-
* Don't mention explicitly that API is MT safe, this implies that other API is not. GStreamer API is assumed to be MT safe, thread safety should only be explicitly mentioned when API is *not* MT safe * Don't repeat what annotations are stating with respect to ownership transfer, nullability * Document virtual methods in standalone comments, so that parameters can be documented. This is not critical here, as parameters do not need annotations / specific documentation, but serves as an up to date example * Document enumeration members in standalone comments, so that their Since tag is accounted for by gobject-introspection * Misc cleanup / typo fixes / addition of links Part-of: <gstreamer/gstreamer!756>
-
Stéphane Cerveau authored
_GST_ELEMENT_REGISTER_DEFINE_BEGIN _GST_ELEMENT_REGISTER_DEFINE_END was introducing an extra extern "C" in case of c++ build. Add missing ";" in GST_ELEMENT_REGISTER_DECLARE Part-of: <gstreamer/gstreamer!757>
-
- Feb 11, 2021
-
-
Mathieu Duponchelle authored
* Don't mention explicitly that API is MT safe, this implies that other API is not. GStreamer API is assumed to be MT safe, thread safety should only be explicitly mentioned when API is *not* MT safe * Document virtual methods in standalone comments, in order to properly annotate them * Don't repeat what annotations are stating with respect to ownership transfer, nullability * Misc cleanup / typo fixes / addition of links Part-of: <!755>
-
- Feb 10, 2021
-
-
Mathieu Duponchelle authored
* Don't repeat what annotations are stating with respect to ownership transfer, nullability * Reword the warnings for caps nestability in light of the 1.20 improvements * Misc cleanup / typo fixes / addition of links Part-of: <!754>
-
Jan Schmidt authored
Add a test that removing a blocking probe on events when there is a different blocking probe on buffers releases the data flow. Part-of: <gstreamer/gstreamer!749>
-
Jan Schmidt authored
Explain that GST_PAD_PROBE_PASS will pass data even if there is another pad probe that says to block, and that GST_PAD_PROBE_REMOVE passes data and potentially unblocks the pad. Part-of: <gstreamer/gstreamer!749>
-
Jan Schmidt authored
Change the way the marshalled flag in the internal ProbeMarshall state is handled when iterating over pad probes so that it only counts probes that still exist and would be called when retrying. This improves the way that removing a blocking probe works when there are multiple blocking probes for different conditions (data vs events for example). As a side-effect, probes aren't put into the the called_probes array unless they actually match the current probe type and would be called, potentially reducing the number of hooks that get stored in the called_probes array, and the cost of the looping check on retries. Fixes gstreamer/gstreamer#658 Part-of: <gstreamer/gstreamer!749>
-
- Feb 09, 2021
-
-
Mathieu Duponchelle authored
* Don't mention explicitly that API is MT safe, this implies that other API is not. GStreamer API is assumed to be MT safe, thread safety should only be explicitly mentioned when API is *not* MT safe * Don't repeat what annotations are stating with respect to ownership transfer, nullability * Document virtual methods and the class structure * Misc cleanup / typo fixes / addition of links Part-of: <!753>
-
- Feb 08, 2021
-
-
Mathieu Duponchelle authored
* Don't repeat what annotations are stating with respect to ownership transfer, nullability * Document virtual methods in standalone comments, so that parameters can be documented. This is functionally useful here, as parameters require annotations, and should make the class more usable by bindings. * Misc cleanup / typo fixes / addition of links Part-of: <!752>
-
Mathieu Duponchelle authored
* Don't repeat what annotations are stating with respect to ownership transfer, nullability * Misc cleanup / typo fixes / addition of links Part-of: <!752>
-
Mathieu Duponchelle authored
Part-of: <gstreamer/gstreamer!752>
-
- Feb 05, 2021
-
-
Mathieu Duponchelle authored
* Don't mention explicitly that API is MT safe, this implies that other API is not. GStreamer API is assumed to be MT safe, thread safety should only be explicitly mentioned when API is *not* MT safe * Don't repeat what annotations are stating with respect to ownership transfer, nullability * Document enumeration members in standalone comments, so that their Since tag is accounted for by gobject-introspection * Misc cleanup / typo fixes / addition of links Part-of: <gstreamer/gstreamer!748>
-
- Feb 04, 2021
-
-
Mathieu Duponchelle authored
* Don't mention explicitly that API is MT safe, this implies that other API is not. GStreamer API is assumed to be MT safe, thread safety should only be explicitly mentioned when API is *not* MT safe * Don't repeat what annotations are stating with respect to ownership transfer, nullability * Document virtual methods in standalone comments, so that parameters can be documented. This is not critical here, as parameters do not need annotations / specific documentation, but serves as an up to date example * Document enumeration members in standalone comments, so that their Since tag is accounted for by gobject-introspection * Misc cleanup / typo fixes / addition of links Part-of: <gstreamer/gstreamer!747>
-
Mathieu Duponchelle authored
Part-of: <gstreamer/gstreamer!747>
-