Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
CID 1394491.
|
|
CID 1394494.
|
|
And fail initialization if it is not the case, we make the assumption
it worked all around the codebase so we should really concider it fatal.
|
|
|
|
|
|
|
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=774751
|
|
|
|
|
|
It could yet be made be simpler, but it would require
touching the rest of the timeline editing code.
Fixes https://phabricator.freedesktop.org/T7587
Reviewed-by: Thibault Saunier <thibault.saunier@collabora.com>
Differential Revision: https://phabricator.freedesktop.org/D657
|
|
|
|
In some cases when rippling clip we could get the algo lost because
a transition existed between two clips (for example at the end of c1
and at the begining of c2) but while rippling it would have required
a transition at the end of c2 and beginning of c1, and we were properly
not destroying the old one (as the two clips were in the moving context)
but we were still creating the other transition in the end...
Reviewed-by: Alex Băluț <alexandru.balut@gmail.com>
Differential Revision: https://phabricator.freedesktop.org/D1362
|
|
Reviewed-by: Alex Băluț <alexandru.balut@gmail.com>
Differential Revision: https://phabricator.freedesktop.org/D1361
|
|
And make sure that we move the transition to the right layer, not trying
to figure it out.
Differential Revision: https://phabricator.freedesktop.org/D1360
|
|
Avoiding problems when using subproject:
'Failed to load plugin something.so file too short'
|
|
The seek action might currently be handled (in which case it is not in
the actions list and the action lock is not locked), but not actually
handled completely yet (the seqnum is not stored yet).
To prevent this, we remember what the current action is that is being
handled, and also compare to that.
https://bugzilla.gnome.org/show_bug.cgi?id=774149
|
|
If there are e.g. multiple video sinks, we would get the same seek event
multiple times. But we only want to handle it once.
https://bugzilla.gnome.org/show_bug.cgi?id=774149
|
|
|
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=773114
|
|
This reverts commit 5665c2bfc9cae531c6dd9a75766d06a4af25ab9a.
Does not actually work. See:
https://bugzilla.gnome.org/show_bug.cgi?id=773114#c31
|
|
|
|
|
|
Use the default for each compiler on every platform instead. This
improves our compatibility with compilers that don't have gnu99 as
a c_std.
|
|
Bump meson requirement to 0.35
|
|
We set TrackElement track type very early when creating effects
so it now uses that information to find TrackElement in clips
by track type.
Reviewed-by: Alex Băluț <alexandru.balut@gmail.com>
Differential Revision: https://phabricator.freedesktop.org/D1370
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Differential Revision: https://phabricator.freedesktop.org/D1329
|
|
Differential Revision: https://phabricator.freedesktop.org/D1328
|
|
Those tag are meaningless in for the new stream created by the composition
First step toward fixing T3070
Differential Revision: https://phabricator.freedesktop.org/D1327
|
|
Computation was not taking into account the fact that the start of
the element being moved could be at the middle of a group and not
necessarily at the start!
Fixes T7544
Reviewed-by: Alex Băluț <alexandru.balut@gmail.com>
Differential Revision: https://phabricator.freedesktop.org/D1282
|
|
We were only concidering that we should let the group handle moving
transitions when changing transitions but in fact as soon as a
transition is happenning between two clips that are in a same group
the group properly handles moving the transition, so let the
group do its job.
Fixes T7543
Differential Revision: https://phabricator.freedesktop.org/D1281
|
|
GESLayer is now responsible for setting clips priorites. Also
GESClip top effects priorities are now set by the
ges_clip_set_top_effect_index method, the user should never call
ges_timeline_element_set_priority as it will anyway be overriden
by GES itself.
Differential Revision: https://phabricator.freedesktop.org/D1280
|
|
All operations should have higher priorites and sources should be
on top of those. We now first set the operations priorities in
a first pass and then stack sources on top of those.
Differential Revision: https://phabricator.freedesktop.org/D1279
|
|
Until now fade out was just fading in the new clip, but this is not
correct and crossfade should at the same time fade out while fading
in.
Fixes https://phabricator.freedesktop.org/T3451
Differential Revision: https://phabricator.freedesktop.org/D1278
|
|
In case effects have been added priorites might become wrong,
but until the timeline is not commited, it does not matter.
Make sure all priorities are correct before commiting compositions
Differential Revision: https://phabricator.freedesktop.org/D1277
|
|
Fix all tests as we now have 1 priority inside the layer
dedicated to transitions (basically no source clip will
ever have a priority of 0 inside a layer).
Differential Revision: https://phabricator.freedesktop.org/D1276
|
|
And simplify the way we start computing children priority
making min_priority already relative to the clip itself.
Differential Revision: https://phabricator.freedesktop.org/D1275
|
|
Differential Revision: https://phabricator.freedesktop.org/D1274
|
|
We would seek on a NULL pad then, which gives ugly assertions.
https://bugzilla.gnome.org/show_bug.cgi?id=771843
|
|
By putting uridecodebin into a bin with a ghostpad. Without this,
nlesource tries to get a srcpad too early (before uridecodebin added
one) and everything fails miserably.
This has to be fixed properly in nlesource at some point, by properly
handling dynamically added pads. Currently they can only work if they
are added in states <= READY, which is not the usual case.
https://bugzilla.gnome.org/show_bug.cgi?id=771843
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=771792
|
|
Otherwise GstStructure might fail parsing some fields
containing brackets
https://bugzilla.gnome.org/show_bug.cgi?id=771434
|