Adds a new tag for indicating the used exposure compensation
level in EV used when capturing an image.

API: GST_TAG_CAPTURING_EXPOSURE_COMPENSATION

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

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

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

We don't compare the bitrates of consecutive mp3 frames on purpose
here.

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

gcc on OSX complains about ret being used uninitialized in
this function, and it is right. Don't leak element ref
when returning early because newsegment event is not in
TIME format.

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

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

Specifically, make sure that the return value of strtol is falling in
between the range of G_MININT and G_MAXINT.

Fixes #646952.

Top-level profiles don't have restrictions, only stream profiles,
so no need to serialise that here.

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

Should fix distcheck on x86_64.

psychadelic -> psychedelic. Spotted by Sébastien Wilmet.

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

Remove the android/ top dir
Fixe the Makefile.am to be androgenized

To build gstreamer for android we are now using androgenizer which generates the
needed Android.mk files.
Androgenizer can be found here:
http://git.collabora.co.uk/?p=user/derek/androgenizer.git

1) We need to lock and get a strong ref to the parent, if still there.
2) If it has gone away, we need to handle that gracefully.

This is necessary in order to safely modify a running pipeline. Has been
observed when a streaming thread is doing a buffer_alloc() while an
application thread sends an event on a pad further downstream, and from
within a pad probe (holding STREAM_LOCK) carries out the pipeline plumbing
while the streaming thread has its buffer_alloc() in progress.

It is possible that the element might be going down while the event arrives

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

The endianness was not set correctly before.

Fixes bug #646923.

The RFF flag is to be reused for buffers in the telecine state to
indicate that the buffer contains only unneeded repeated fields that are
present in other buffers and as such this buffer can be dropped.

... which avoids crashing in the off-chance that structure == NULL.

Leave dealing with the appearance of the window when we are not playing to the
applications. We anyway want to go to NULL as quickly as possible.

Fixes #635800

gstvorbistag.c: In function 'gst_tag_list_from_vorbiscomment_buffer':
gstvorbistag.c:371: warning: 'data' may be used uninitialized in this function

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

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

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

From 1ccbe09 to c3cafe1

A race was observed between query() and setcaps() where the latter would
change the ringbuffer spec while the former was performing operations
based this data.

Observed a case where the src went to null-state during the query,
hence the spec pointer was no longer valid, and
gst_util_unit64_scale_int crashed (assertion `denom > 0´failed)

Add locking to make sure the ringbuffer can't disappear.

Given a large enough drift-tolerance, one could end up in a situation
where one would keep aligning the written buffers behind the current
read-segment position. The result for the reader would be complete
silence, possible preceded by very choppy audio.

By checking the available headroom, one can determine if there is
room to do alignment, or if one should resort to a resync instead to get
the pointers back on track.

Also refactor the alignment-logic out of the render function for cleaner
code.