The GESTimeline's state might not be synced with parent

Tim-Philipp Müller authored Sep 24, 2018 and Thibault Saunier committed Dec 15, 2018

Export GES library API in headers when we're building the
library itself, otherwise import the API from the headers.

This fixes linker warnings on Windows when building with MSVC.

Fix up some missing config.h includes when building the lib which
is needed to get the export api define from config.h

Fixes #42

And add some missing API guards

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

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

In playsink the default video queue max size is 3 buffers, which is
sometimes not enough for our use case.

Allow up to 2 seconds of buffered data, giving us more time to do
the transition between clips, and thus avoiding dropping frames in
the sink when bringing up new clip takes too much time.

Differential Revision: https://phabricator.freedesktop.org/D1854

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

Aurélien Zanelli authored May 15, 2016 and Thibault Saunier committed May 14, 2016

Mainly (transfer xxx) and (nullable). Also fix some typo.

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

Justin Kim authored Sep 24, 2015 and Thibault Saunier committed Sep 24, 2015

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

API:
  ges_track_element_remove_control_binding

It is not correct to force a black frame at the end of the rendered
video and it also leads to rendering issue with vpX encoders.

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

Summary:
The user might want to render only some media type of the timeline,
for example he wants to only render the audio part of the timeline.

It was failing as we were not connecting the track but were still trying
to 'render' it.

Depends on D153

Reviewers: Mathieu_Du

Reviewed By: Mathieu_Du

Differential Revision: http://phabricator.freedesktop.org/D154

Reviewers: thiblahute

Differential Revision: http://phabricator.freedesktop.org/D62

That can be used to add filters at the very end of the pipeline,
and one can think of adding a watchdog element in there for
example.

In order to get the precise position of the pipeline, the only
way is to ask the 'application' to query the pipeline position and
use it.

Mathieu Duponchelle authored Oct 28, 2014 and Thibault Saunier committed Nov 10, 2014

+ ghost track src pad before calling track added so that
  pipeline has a pad to link.
+ Remove silly comment.

Port the timeline, track and pipeline to the new NLE API where
all objects have static src pads.

+ Simplify the support in ges-launch as we should not require the
profile desc to start with : in that case

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

Christoph Reiter authored Apr 07, 2014 and Thibault Saunier committed Apr 07, 2014

g-ir-scanner includes section docs as class/interface docs if the section name is equal to the lowercase type name.
Since all the documentation is in section blocks, rename them to match the type names.

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

That leads to freeze as encodebin will be waiting for a pad and EOS
forever

We currenty do not support multiple tracks with same type in GESPipeline
and we actually need to set the presence field to avoid a scenario where
we have only video in a video track, and no audio in the audio track. So
audiotestsrc is used and we end up encoding the whole audio stream but
no decoded video frame as reached the decodebin src pad, so the pad
has not been created and thus it will not be linked to the encodebin.
On the audio part, the EOS will be emitted so fast that the resulting stream will
not have any video in it as the muxer will not even have a video pad created.

Setting the presence will ensure that the muxer does have a video pad
(because of how encodebin behaves) and thus will create a pad for it
and wait for its EOS.

First, it was not in any namespace, second the name of the enum is
GESPipelineFlags.

API BREAKAGE:
        - ges_pipeline_add_timeline
        + ges_pipeline_set_timeline

Kishore Arepalli authored Oct 17, 2013 and Sebastian Dröge committed Oct 31, 2013

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

It is sometimes necessary

Kishore Arepalli authored Sep 12, 2013 and Sebastian Dröge committed Sep 12, 2013

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

Making it possible to use it with GstValidate LD_PRELOAD feature

We actually do not need it has everywhere where we would need it we are
already locked against the timeline.dyn_lock, we need to make sure it is
always the case in the future.

The hierarchy of the mutex was wrong and could possibly lead to
deadlocks

Setting the profile on an encodebin can fail, and if that happens, there
will be no profile set at all, we should return FALSE in GESPipeline
when that happens

rename ges_timeline_pipeline methods to ges_pipeline