GitLab

Needed for use via the boxed type.

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

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

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

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

This is minor style fix to not mix *var and var[N].

Currently the scan uses Boyer-moore method and its performance is good.
but, it can be optimized from an implementation of view.

The original scan code is implemented by byte array and index-based access.
In _scan_for_start_code(), the index is increasing from start to end and the
base address of the byte array is referred to as return value.

In the case, index-based access can be replaced by pointer access, which
improve the performance by removing index-related operations.

Its performace is enhanced by approximately 8% on arm-based embedded devices.
Although it seems trivial, it can affect the overall performance because the
_scan_for_start_code() function is very often called when H.264/H.265 video is
played.

In addition, the technique can apply for all architectures and it is good in
view of readability and maintainability.

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

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

Without we would not actually expand and access
memory beyond the allocated region for the array.

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

The gpointer argument is passed to all three callbacks, not just one.

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

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

Previously, many constants were prefixed with # or unprefixed,
some functions and macros were prefixed with # instead of suffixed
with (), etc.

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

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

And move type stuff from GstValue to GstDateTime.

The start and stop should represent the currently downloading region.
The estimated-total should represent the remaining time to download
the currently downloading region. This makes it a lot more useful
for applications because they can then use those values to update
the fill region and use the estimated time to delay playback.
Update the docs with this clarification.

Coverity 1037155

Reset the read and write positions right after we open the file or flush
it. We are also in the buffering state with 0 percent buffered when we
start.

First handle all miniobjects before we attempt to dereference the first
field pointer and look at the GType. With the recent glib change to
speed up G_IS_OBJECT, this causes crashes on miniobjects otherwise.

GstDateTime does not have the GType as the first field so we can't use
it to detect its type.

Use the macros to check the type of objects instead of directly poking
at the first field.

Fixes criticals at runtime and makes stuff actually work.

Only EOS and segment should be deleted in that case.

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

This reverts commit 96361e9b.

This was not supposed to be pushed yet!

gst_mini_object_replace() can take NULL mini-objects.

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

This should help improve documentation generated for
languages other than C.

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

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

When a pad is added the need-parent flag is set to true, so when
they are removed the flag should be set back to false

This was preventing GstPads to be reused in elements (removed and
later re-added). A unit tests was added to verify that this is
working now.

The use case is tsdemux that has a program-number property and
allows the user to switch programs. In order to do that tsdemux
will remove the pads of the current program and add from the new
ones. The removed pads are kept in the demuxer for later if the
user selects the old program again.

The buffering status goes back to 0, so inform the application about it

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