- Jul 06, 2016
- Jun 29, 2016
-
-
Differential Revision: https://phabricator.freedesktop.org/D380
-
The return value of ges_project_get_uri should be freed after usage. Differential Revision: https://phabricator.freedesktop.org/D1142
-
- Jun 21, 2016
-
-
Nicolas Dufresne authored
From ac2f647 to f363b32
-
Thibault Saunier authored
-
- Jun 20, 2016
-
-
Thibault Saunier authored
And reuse the same previously created element when adding the clip back to a layer, avoiding losing all setting done on clip children in that situation This is a behaviour change but previous behaviour was actually totally unexpected and people working around that weird behaviour will moste probably not care about that change Differential Revision: https://phabricator.freedesktop.org/D1094
-
Thibault Saunier authored
Otherwise effect handling is broken Differential Revision: https://phabricator.freedesktop.org/D1099
-
Thibault Saunier authored
Differential Revision: https://phabricator.freedesktop.org/D1097
-
Some callers forgot to unref out child, pspec or both leading to leaks. https://bugzilla.gnome.org/show_bug.cgi?id=766449
-
- Jun 06, 2016
-
-
Sebastian Dröge authored
The asynchronous case in ges_uri_clip_asset_request_async() already considered it an error, do the same in ges_uri_clip_asset_request_sync(). https://bugzilla.gnome.org/show_bug.cgi?id=767293
-
- May 31, 2016
-
-
Sebastian Dröge authored
We might receive another seek from the application while the action task is handling a previous seek (and thus setting seeking_itself to TRUE). To prevent this seek to go through directly instead of being added as an action, also check if the seek event was received from our action task thread or some other thread. https://bugzilla.gnome.org/show_bug.cgi?id=767053
-
Thibault Saunier authored
-
- May 30, 2016
-
-
Thibault Saunier authored
Fixes T7430
-
- May 25, 2016
-
-
Tim-Philipp Müller authored
It's what introspection.mak does as well. Should fix spurious build failures on gnome-continuous (caused by g-ir-scanner getting compiler details via python which is broken in some environments so passing the compiler details bypasses that).
-
- May 16, 2016
-
-
To avoid compiler warning when using const string to create a new GESUriClip as string is not modified and only passed to functions which take a const string. https://bugzilla.gnome.org/show_bug.cgi?id=766523
-
Otherwise if frame positionner is disposed after track element has been finalized, it will raise a critical message because we will try to disconnect a signal handler on a freed track element object. https://bugzilla.gnome.org/show_bug.cgi?id=766525
-
Otherwise a capsfilter reference will be leaked since it has been got using gst_bin_get_by_name. https://bugzilla.gnome.org/show_bug.cgi?id=766524
-
- May 14, 2016
-
-
When nlecomposition is finalized with pending add action or io, associated elements are not unreffed as they should since caller gives us the reference when calling gst_bin_add causing them to be leaked. So to make sure we don't leak a reference on element when adding one to the bin, each stage (action and pending_io) hold a reference on element and release it when stage is done. https://bugzilla.gnome.org/show_bug.cgi?id=766455
-
We don't add internal bin, we remove it. https://bugzilla.gnome.org/show_bug.cgi?id=766455
-
Mainly (transfer xxx) and (nullable). Also fix some typo. https://bugzilla.gnome.org/show_bug.cgi?id=766459
-
- May 07, 2016
-
-
Thibault Saunier authored
Makes it simpler for python users to be able to retrieve children properties iterating over them.
-
- May 06, 2016
-
-
Thibault Saunier authored
Those are implemented with the exact same API at the GESTimelineElement level now, and user of those APIs with high level languages will get the exact same API.
-
Thibault Saunier authored
Otherwise it will fail on properties that are mandatorily prefixed like the newly added deinterlacing properties
-
Thibault Saunier authored
This is formally an API break but I am sure no one ever used that and we should make sure the method is removed as soon as possible because it has no reason to be exposed.
-
- May 03, 2016
-
-
Thibault Saunier authored
-
Thibault Saunier authored
Letting some control over the deinterlacing to the users
-
- Apr 30, 2016
-
-
Tim-Philipp Müller authored
-
This is the only header which shall be included by user. Otherwise some language using gir to generate binding, e.g Vala, will includes all headers files in alphabetical order which causes compilation errors due to incomplete type. https://bugzilla.gnome.org/show_bug.cgi?id=765856
-
because "track-element" is not a valid identifier for a parameter and will cause generated binding using GIR to be invalid. For instance in Vala. https://bugzilla.gnome.org/show_bug.cgi?id=765853
-
- Apr 29, 2016
-
-
Thibault Saunier authored
It is not feature compatible with deinterlace and is not safe to use
-
- Apr 28, 2016
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
Someone still should look through the unused.txt for more things to add or hide.
-
- Apr 25, 2016
-
-
Sebastian Dröge authored
-
- Apr 22, 2016
-
-
Thibault Saunier authored
It does not make sense for titles Handle element with no inpoint handling in the timeline Fixes https://phabricator.freedesktop.org/T7319
-
- Apr 14, 2016
-
-
Julien Isorce authored
From 6f2d209 to ac2f647
-
- Apr 13, 2016
-
-
Sebastian Dröge authored
-