GitLab

No idea though why we even have GST_LIBRARY_ERROR_ENCODE or when one
would want to use that instead of GST_STREAM_ERROR_ENCODE.

There's no need to create these tables with duplicates of the
untranslated error message string constants, we can just use
old-fashioned switch/case and call gettext directly. This also
makes things slightly more thread safe and more robust to bad
input (invalid error codes).

Could have come up with something better for my 2000th commit
to GStreamer...

Skip ABI tests if some subsystems are off. Remove DISABLE_GST_DEBUG from
skipping export checks as this is safe now.

Debug print was using a variable that was not initialized.

Add a GstStructure to GstElementClass and GstElementFactory. Add setters/getter.
Handle it in the registry code. Print items in gst-inspect.
Fixes #396774.

API: gst_element_class_set_meta_data(), gst_element_factory_get_meta_data_detail()

From d3d9acf to c2e10bf

From ca1c867 to d3d9acf

And here's a reminder since I forgot to put them in my previous
commit.

API: gst_element_factory_list_filter
API: gst_element_factory_list_get_elements
API: gst_element_factory_list_is_type
API: gst_plugin_feature_list_debug
API: gst_plugin_feature_rank_compare_func
API: GstElementFactoryListType
API: GST_ELEMENT_FACTORY_TYPE_ANY
API: GST_ELEMENT_FACTORY_TYPE_AUDIOVIDEO_SINKS
API: GST_ELEMENT_FACTORY_TYPE_AUDIO_ENCODER
API: GST_ELEMENT_FACTORY_TYPE_DECODABLE
API: GST_ELEMENT_FACTORY_TYPE_DECODER
API: GST_ELEMENT_FACTORY_TYPE_DEMUXER
API: GST_ELEMENT_FACTORY_TYPE_DEPAYLOADER
API: GST_ELEMENT_FACTORY_TYPE_ENCODER
API: GST_ELEMENT_FACTORY_TYPE_FORMATTER
API: GST_ELEMENT_FACTORY_TYPE_MAX_ELEMENTS
API: GST_ELEMENT_FACTORY_TYPE_MEDIA_AUDIO
API: GST_ELEMENT_FACTORY_TYPE_MEDIA_IMAGE
API: GST_ELEMENT_FACTORY_TYPE_MEDIA_METADATA
API: GST_ELEMENT_FACTORY_TYPE_MEDIA_SUBTITLE
API: GST_ELEMENT_FACTORY_TYPE_MEDIA_VIDEO
API: GST_ELEMENT_FACTORY_TYPE_MEDIA_ANY
API: GST_ELEMENT_FACTORY_TYPE_MUXER
API: GST_ELEMENT_FACTORY_TYPE_PARSER
API: GST_ELEMENT_FACTORY_TYPE_PAYLOADER
API: GST_ELEMENT_FACTORY_TYPE_SINK
API: GST_ELEMENT_FACTORY_TYPE_SRC
API: GST_ELEMENT_FACTORY_TYPE_VIDEO_ENCODER

Fixes bug 623121

gstquery: Only fill the start/stop values of the buffering ranges if a non-NULL pointer was provided

Added a new query type to retrieve informations about the areas of the
media currently buffered. See bug 623121.

API: gst_query_add_buffering_range
API: gst_query_get_n_buffering_ranges
API: gst_query_parse_nth_buffering_range

https://bugzilla.gnome.org/show_bug.cgi?id=626181

Mention a few more useful environment variables in the 'Running GStreamer
applications' section of the API reference.

Remove a short cut that was ignoring src->data allocation mode. All
the called code-path below handle size==0.

Make code including GStreamer headers compile with -Wcast-qual by
maintaining const-ness when casting. Also fix function signature of
gst_byte_writer_set_pos(): the byte writer should not be marked as
const.

https://bugzilla.gnome.org/show_bug.cgi?id=627910

Sets up a GST_PKG_CONFIG_PATH variable for use in Makefile.am
(avoids trailing ':' in PKG_CONFIG_PATH used). A useful side
effect of this is also that the PKG_CONFIG_PATH environment
is now logged in the configure output.

new GstInt64Range to store gint64 ranges.

API: GST_TYPE_INT64_RANGE
API: gst_value_set_int64_range
API: gst_value_get_int64_range_min
API: gst_value_get_int64_range_max

Fixes bug #627826.

This was accidently removed in 7a722091

Avoids segfaults when using NULL arguments.

Allow to turn off signal emission and therefore extra locking if this is not needed.
Fixes #621299

GST_FLOW_IS_FATAL() and GST_FLOW_IS_SUCCESS() are deprecated,
so aren't available for the testsuite any more.

And use it for the fraction comparisons in gstvalue.c instead
of using comparisons by first converting the fractions to double.
Should fix bug #628174.

API: gst_util_fraction_compare()

Instead return after every iteration, which makes sure that the
stream lock is released for a short time after every iteration,
task state changes are checked, etc and this allows the task
to be stopped properly.

And document the special handling of WRONG_STATE.

The problem with both macros is, that they suggest something that isn't true.
If GST_FLOW_IS_FATAL is true, there could still be a problem for many elements
and they should stop what they're currently doing and return that value
upstream (e.g. not-linked in a parser). If GST_FLOW_IS_SUCCESS is false, it
could still be that this is "ok" for the element (e.g. not-linked for a demuxer
on a few of its pads but not all).

It's better to not have these "convenience" macros but instead let people
*think* about the handling of different flow returns, that makes sense for
their element. And we should document the expected handling of flow returns for
different classes of elements in the plugin writer's guide.

Fixes bug #628014.