- Apr 07, 2017
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Apr 06, 2017
-
-
Olivier Crête authored
Putting NULL for those is a valid serialization for the NULL value.
-
- Apr 05, 2017
-
-
Sebastian Dröge authored
They were (signed!) gint64 before because of G_GINT64_CONSTANT() already and they are actually used in signed calculations. With this change we at least ensure that an integer type of the correct size is used for GI (it was using gint before).
-
Sebastian Dröge authored
-
Sebastian Dröge authored
This makes C++ compilers a bit more happy without having the user of the constants cast. It also provides the correct type information to GI. https://bugzilla.gnome.org/show_bug.cgi?id=780923
-
Sebastian Dröge authored
-
Sebastian Dröge authored
Storing a -1 inside an unsigned integer confuses GIR based bindings generators.
-
- Apr 04, 2017
-
-
Nicolas Dufresne authored
In GES, the summary refers to options that are only available when built against gst-valdiate. Those where picked by our regex. This patch add a initial grep to try and filter-out as best as possible the content to which we will extract the command list.
-
Nicolas Dufresne authored
-
Nicolas Dufresne authored
This patch reorganize the bash completion scripts in order to install the binary helper (gst-completion-helper) in libexec path rather then share folder. Most Linux hierarchy compliance requires that no binary executable are placed in share. We also cleanup the unused .pc entries and remove copy pasted parts of the script. Note that other project including the common helper, should now use $_GST_HELPER to read the binary executable gst-completion-helper. This helper is not longer version, as it is placed in a versionned subfolder (libexec/gstreamer.10) just like the other helpers (scanner and ptp).
-
- Mar 31, 2017
-
-
-
Vincent Penquerc'h authored
The issue happens when the structure is printed by the logging subsystem: the object is included in the log, and this will cause the full object printout to be done there. However, after dispose, the queue was already cleared, so the access to it (to print the object) would assert, as the queue was already freed. The patch changes it so that the queue is merely empty, and only freed in _finalize. https://bugzilla.gnome.org/show_bug.cgi?id=776293
-
- Mar 27, 2017
-
-
Tim-Philipp Müller authored
But only if set. Helps debug issues with EOS propagation.
-
Tim-Philipp Müller authored
One less layer of escaping, but still lots of ugly \.
-
- Mar 24, 2017
-
-
Nicolas Dufresne authored
This should fix make distcheck
-
Nicolas Dufresne authored
A paramspec validation should modify the content to match what the spec requires and return TURE if a modification happened. This previous implementation would only fix the first element of the array and return. It was also return TRUE for empty array, while no modification was needed. https://bugzilla.gnome.org/show_bug.cgi?id=780111
-
Nicolas Dufresne authored
The GST_TYPE macro points to global variables initialized by the first call to get_type. This is not an issue if you call gst_init() but unfortunatly pygi will need to acces the param type before init can be called. This removes an assertion.
-
Nicolas Dufresne authored
Those aren't suppose to be called from multiple thread, but all fundamental get_type() function are thread safe. Fix it to be consistent and it may help if we change the typing mechanism in GStreamer come day.
-
Nicolas Dufresne authored
This is to help bindings access properties of type GST_TYPE_ARRAY. This function will get/set the property and convert form/to GValueArray. New API: gst_util_set_object_array gst_util_get_object_array https://bugzilla.gnome.org/show_bug.cgi?id=753754
-
Nicolas Dufresne authored
This adds a binding friendly interface to get and set arrays and list into GstStructure. New API: - gst_structure_set_array - gst_structure_set_list - gst_structure_get_array - gst_structure_get_list https://bugzilla.gnome.org/show_bug.cgi?id=753754
-
Nicolas Dufresne authored
This allow transforming a GValue of type G_TYPE_VALUE_ARRAY to and from GST_TYPE_ARRAY/LIST. https://bugzilla.gnome.org/show_bug.cgi?id=753754
-
Sebastian Dröge authored
-
Jan Schmidt authored
When registering GstParamSpecArray, use the gst_value_array_get_type() function to get the type, rather than the GST_TYPE_ARRAY macro, which gets it from the _gst_value_array_type, which is in turn only initialised during gst_init() Fixes criticals with (python) bindings that look up all the types from the gobject-introspection info as soon as they are imported. /usr/lib64/python3.5/site-packages/gi/module.py:178: Warning: g_param_type_register_static: assertion 'g_type_name (pspec_info->value_type) != NULL' failed g_type = info.get_g_type() /usr/lib64/python3.5/site-packages/gi/module.py:212: Warning: g_type_get_qdata: assertion 'node != NULL' failed type_ = g_type.pytype /usr/lib64/python3.5/site-packages/gi/module.py:226: Warning: g_type_get_qdata: assertion 'node != NULL' failed g_type.pytype = wrapper /usr/lib64/python3.5/site-packages/gi/module.py:226: Warning: g_type_set_qdata: assertion 'node != NULL' failed g_type.pytype = wrapper
-
- Mar 22, 2017
-
-
Jan Schmidt authored
If parsing returns a non-OK flow return in the middle of processing an input buffer, don't overwrite that if a later return is OK again - the subclass might return not-linked in the middle, and then discard subsequent data without pushing while returning OK. A later success doesn't invalidate the earlier failure, but we should continue processing after not-linked, so as to keep parse state consistent. https://bugzilla.gnome.org/show_bug.cgi?id=779831
-
- Mar 20, 2017
-
-
Tim-Philipp Müller authored
The 'mad' plugin has been removed. Mention mpg123audiodec instead. https://bugzilla.gnome.org/show_bug.cgi?id=776140
-
Vincent Penquerc'h authored
The internal representation uses bounds scaled by the step Add tests to catch those cases
-
- Mar 15, 2017
-
-
Thiago Sousa Santos authored
Return the correct flow return instead of returning always flushing. This would cause queue to convert not-linked to flushing and making upstream elements stop. Based on the previous patch for queue2. https://bugzilla.gnome.org/show_bug.cgi?id=776999
-
- Mar 11, 2017
-
-
Thiago Sousa Santos authored
Return the correct flow return instead of returning always flushing. This would cause queue2 to convert not-linked to flushing and making upstream elements stop. https://bugzilla.gnome.org/show_bug.cgi?id=776999
-
Thiago Sousa Santos authored
Add tests to confirm flags are persisted even after removing elements that have those suppressed flags
-
- Mar 10, 2017
-
-
Wim Taymans authored
-
Wim Taymans authored
-
- Mar 09, 2017
-
-
Jan Schmidt authored
If guessing that a string matches a flagset, be more thorough at checking that the string following a string of hex:hex: actually looks like a flag set string. Add some unit tests to catch more cases. https://bugzilla.gnome.org/show_bug.cgi?id=779755
-
Jan Schmidt authored
Remove a FIXME about making the minimum interleave buffering a configurable property
-
- Mar 08, 2017
-
-
Tim-Philipp Müller authored
In most cases people really want to know when an element could not be created.
-
- Mar 07, 2017
-
-
active-pad switch causes reconfigure event with lock taken, and upstream element might query the current position or duration before returning the reconfigure event. Meanwhile, gst_input_selector_get_linked_pad() is used to get srcpad inside of default query handle, and it takes also lock. Since inputselector is still locked by active-pad switch, and so the query cannot be handled further. https://bugzilla.gnome.org/show_bug.cgi?id=775445
-
- Mar 03, 2017
-
-
- Feb 24, 2017
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
Thibault Saunier authored
Not file that would for some reason end with 'so' or 'dll', etc... https://bugzilla.gnome.org/show_bug.cgi?id=779175
-