The whole tree is likely to switch to GTK 3.0 at some point, but
we might as well continue building with slightly less new versions
if it's not hard to do.
camerabing example had a missing ')' and the fix to build against GTK+3
that was introduced in commit 516c977c76
is also applied to the camerabin2 example.
The scaletempo demo was using API which has been removed, so that's
wrapped in a version check.
A flags property has been added to encodebin to toggle whether the
conversion elements (ffmpegcolorspace, videoscale, audioconvert,
audioresample, audiorate) are created and linked into the appropriate
branches of encodebin.
Not including these elements avoids some slow caps negotiation and
allows the first buffers to flow through encodebin much more quickly.
However, it imposes that the uncompressed input is appropriate for the
target profile and elements selected to meet that profile.
Adds performance (timing) measure feature to gst-camerabin2-test, it allows
users to specify some target values for commonly measured times and the
application will print out a table of values at the end of its execution
with the measured times and averages of them.
Add command-line options for setting image-capture, viewfinder
and video-capture caps as strings.
The width and height properties are now used only if these new caps
properties aren't set.
We must wait for camerabin2's stop-capture procedures to finish before quitting
the main loop or firing off the next capture. If we get stuck waiting for
camerabin2 to become idle, this is a bug that needs fixing.
Adds gst-camerabin2-test example application, similar to
gst-camerabin-test for camerabin.
It is useful for taking pictures and recording videos using
camerabin2 and providing arguments for most of camerabin2
properties
--no-window flag is false by default and selection based on the option whether
to create XWindow is done before options are parsed. Therefore XWindow is never
created.
https://bugzilla.gnome.org/show_bug.cgi?id=641712
Don't set any default values for source element GstPhotography interface
settings, source elements should have sane defaults themselves.
Also, setting scene-mode is tricky as it is a superset of other GstPhotography
settings. This might cause problem with defaults e.g. setting scene-mode to
'night' may configure flash-mode as 'on' by definition, and after that
we don't want to override this flash-mode setting with gst-camerabin-test default
value. Moreover, user needs have an option to set scene mode first and then force
some individual setting to a different value from the scene-mode definition.
https://bugzilla.gnome.org/show_bug.cgi?id=639841
