- Jun 09, 2016
- Jun 07, 2016
-
-
Thibault Saunier authored
Makes it simpler for python users to be able to retrieve children properties iterating over them.
-
Mainly (transfer xxx) and (nullable). Also fix some typo. https://bugzilla.gnome.org/show_bug.cgi?id=766459
-
We don't add internal bin, we remove it. https://bugzilla.gnome.org/show_bug.cgi?id=766455
-
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
-
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
-
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).
-
Thibault Saunier authored
-
Thibault Saunier authored
Fixes T7430
-
-
Thibault Saunier authored
When copying and splitting clips Fixes T7375
-
GstMetas are not allocated with all fields initialized to zeroes.
-
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
-
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.
-
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
-
- May 02, 2016
-
-
-
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
-
It is not feature compatible with deinterlace and is not safe to use
-
- Apr 30, 2016
-
-
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 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 26, 2016
-
-
Sebastian Dröge authored
-
- Apr 20, 2016
- Apr 05, 2016
-
-
Thibault Saunier authored
-
- Mar 24, 2016
- Mar 15, 2016
- Mar 11, 2016
-
-
Thibault Saunier authored
This reverts commit c4356db4. This commit was not ready and was not support to be pushed
-
Thibault Saunier authored
-
-
- Mar 09, 2016
-
-
Summary: sanitized_timeline is created when parsing command line, but it isn't free'd. Reviewers: thiblahute Differential Revision: https://phabricator.freedesktop.org/D382
-
- Mar 01, 2016
- Feb 26, 2016
-
-
Reviewed By: thiblahute Differential Revision: https://phabricator.freedesktop.org/D770
-
Thibault Saunier authored
-
Before this patch, NLE and GES did not support NleOperations (respectively GESEffects) that changed the speed/tempo/rate at which the source plays. For example, the 'pitch' element can make audio play faster or slower. In GES 1.5.90 and before, an NleOperation containing the pitch element to change the rate (or tempo) would cause a pipeline state change to PAUSED after that stack; that has been fixed in 1.5.91 (see #755012 [0]). But even then, in 1.5.91 and later, NleComposition would send segment events to its NleSources assuming that one source second is equal to one pipeline second. The resulting early EOS event (in the case of a source rate higher than 1.0) would cause it to switch stacks too early, causing confusion in the timeline and spectacularly messed up output. This patch fixes that by searching for rate-changing elements in GESTrackElements such as GESEffects. If such rate-changing elements are found, their final effect on the playing rate is stored in the corresponding NleObject as the 'media duration factor', named like this because the 'media duration', or source duration, of an NleObject can be computed by multiplying the duration with the media duration factor of that object and its parents (this is called the 'recursive media duration factor'). For example, a 4-second NleSource with an NleOperation with a media duration factor of 2.0 will have an 8-second media duration, which means that for playing 4 seconds in the pipeline, the seek event sent to it must span 8 seconds of media. (So, the 'duration' of an NleObject or GES object always refers to its duration in the timeline, not the media duration.) To summarize: * Rate-changing elements are registered in the GESEffectClass (pitch::tempo and pitch::rate are registered by default); * GESTimelineElement is responsible for detecting rate-changing elements and computing the media_duration_factor; * GESTrackElement is responsible for storing the media_duration_factor in NleObject; * NleComposition is responsible for the recursive_media_duration_factor; * The latter property finally fixes media time computations in NleObject. NLE and GES tests are included. [0] https://bugzilla.gnome.org/show_bug.cgi?id=755012 Differential Revision: https://phabricator.freedesktop.org/D276
-
Sebastian Dröge authored
From b64f03f to 6f2d209
-
- Feb 23, 2016
-
-
Differential Revision: https://phabricator.freedesktop.org/D619
-