GitLab

g_clear_pointer() is now preserving the type of its arguments for the
free function.

ges-xml-formatter.c: In function ‘_dispose’:
ges-xml-formatter.c:1635:7: error: function called through a non-compatible type [-Werror]
       (GDestroyNotify) g_hash_table_unref);
/usr/include/glib-2.0/glib/gmem.h:121:8: note: in definition of macro ‘g_clear_pointer’
       (destroy) (_ptr);                                                        \
        ^~~~~~~

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

https://github.com/mesonbuild/meson/pull/4169

When removing a top effect in the list of top effects, other
effects priorities need to take that into account to avoid
holes in the indices.

This autodetection is needed on iOS inside Cerbero where
gstreamer-check-1.0 is not available.

Requires Meson 0.48, but the feature will be ignored on older versions
so it's safe to add it without bumping the requirement.

Documentation:
https://github.com/mesonbuild/meson/blob/master/docs/markdown/Reference-manual.md#shared_library

There is no installed version of that, only an uninstalled version.

Previous commit makes the format not forward compat.

Marking them as children properties and properly allow serializing
clips children properties.

This doesn't handle several TrackElement of a same type with
different property values but this require more worked already
marked as fixme to allow specifying full path of elements in the
children properties API.

See https://gitlab.gnome.org/GNOME/pitivi/issues/1687

Until know we were doing it outside of the signal and subclasses didn't
have a chance to know that some assets was relocated.

This is required so that Pitivi can handle proxy delation and relocated
assets.

Required for https://gitlab.gnome.org/GNOME/pitivi/issues/2203

The remaining automagic options are in tests and examples.

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

The code was not taking into account the fact that testsuite could be
located in a different folder that the default one.

Now the testsuite is responsible for providing a path if it wants
to set extra scenarios or the user can set one by hand.

This segment is representing the last seek received
inside the composition. Or a simply initialized segment
if need seek occurred.

Meaning tests that do not need project at all

And stop leaking intermediary restriction caps.

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

Implementing it in the overrides as PyGObject won't be able to properly
convert python values to GValues in some cases. Using
g_object_set_property works as some logic is implemented inside
PyGObject for that particular case. This is a "regression" due
to https://bugzilla.gnome.org/review?bug=769789&attachment=348766 were
we end up with an OverflowError while setting G_TYPE_UINT children
properties.

Bastian Köcher authored Apr 01, 2018 and Tim-Philipp Müller committed Jul 07, 2018

Nixos configures a custom includedir.

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

This is what other modules use

Don't want to error out on deprecated API warnings and such.
Just drop -Werror for the examples until someone updates them
to recent gtk3 API. Maybe showing the warnings will motivate
someone.

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

Drop gtk2 option.

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

Still lots of deprecated API to update.

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

It makes no sense to snap in that context.

https://gitlab.gnome.org/GNOME/pitivi/issues/2193

Meaning that a reference file has to be present on disk with a
`.expected_result` extension.

This was a workaround for encoders bad behavior in the reconfigure case.

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

Also yield common options to the outer project (gst-build in our case)
so that they don't have to be set manually.

Just like the autotools build.

In the rendering case we were getting random issues and often the
pipeline was not be able to preroll as some pad were not linked inside
encodebin.

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

Refactor so that the same code is used to add children properties from
bin children and when inspecting a single element.

We used to update caps for any more because of missing brackets.

Those are the elements he cares about and we should expose their APIs
as is, event if they are not classified as effects. For example if
the user want to use a capsfilter as effect, he should be able to set
its caps.