rtpdtmfsrc: clock-base and seqnum-base -> timestamp-offset and seqnum-offset

These were renamed in GstRTPBasePayload in 1.0
rtpmux: clock-base and seqnum-base -> timestamp-offset and seqnum-offset

These were renamed in GstRTPBasePayload in 1.0
rtpsource: Rename seqnum-base to seqnum-offset in caps

This was modified back in 1.0 in GstRtpBasePayload
pulsesink: Make emitting stream status messages synchronous

The stream status messages are emitted in the PA mainloop thread, which
means the mainloop lock is taken, followed by the Gst object lock (by
gst_element_post_message()). In all other locations, the order of
locking is reversed (this is unavoidable in a bunch of cases where the
object lock is taken by GstBaseSink or GstAudioBaseSink, and then we get
control to take the mainloop lock).

The only way to guarantee that the defer callback for stream status
messages doesn't deadlock is to either stop posting those messages, or
make sure that the message emission is completed before we proceed to
any point that might take the object lock before the mainloop lock
(which is what we do after this patch).

https://bugzilla.gnome.org/show_bug.cgi?id=736071
pulse: Add some documentation about threading and synchronisation

This gives a quick introduction to how the pulsesink/pulsesrc code
interacts with the pa_threaded_mainloop that we start up to communicate
with the server.
vp8enc: Allow caps renegotiation

https://bugzilla.gnome.org/show_bug.cgi?id=726329
vp9enc: Allow caps renegotiation

https://bugzilla.gnome.org/show_bug.cgi?id=726329
vp8enc/vp9enc: Protect the encoder with a mutex in all situations
vp8enc: finish() and drain() should return a GstFlowReturn
souphttpclientsink: Free queued buffers in ::reset

::render sets a new callback for writing out new buffers only if there aren't
already buffers queued for writing with a previously-scheduled callback.
However, if the previously-scheduled callback is interrupted by a state change
(either manually or due to an error) and there are still buffers in the queue,
restarting the pipeline will result in buffers being queued forever, and no
callbacks will ever be scheduled, and no buffers will be written out.

https://bugzilla.gnome.org/show_bug.cgi?id=737739
souphttpclientsink: Add some more useful debug logging
wavenc: Send CAPS event after the pad was activated

Otherwise the CAPS event will be dropped and we never configure any caps at
all, leading to weird behaviour in many situations. Especially header
rewriting is not going to work if a capsfilter is after wavenc.

https://bugzilla.gnome.org/show_bug.cgi?id=737735
aacparse: fix memory leak when prepending ADTS headers

https://bugzilla.gnome.org/show_bug.cgi?id=737761
souphttpclientsink: Fix lifetime of stream headers and queued buffers

Stream headers are updated whenever ::set_caps is called, so we can't assume
they'll be valid before the message body is written out. We *can* assume that
for queued buffers, but SOUP_MEMORY_STATIC is still wrong for those.

Also, add some debug logging for stream header interactions.

https://bugzilla.gnome.org/show_bug.cgi?id=737771
equalizer: Don't call iirequalizer's transform_ip in passthrough mode

It tries to map the read-only buffer with GST_MAP_READWRITE and crashes.

https://bugzilla.gnome.org/show_bug.cgi?id=737886
videobox: critical error when element properties set as max/min

left, right, top, bottom can be set from range of -2147483648 to 2147483647
when i launch the videobox element with that values, it gives a critical error

(gst-check-1.0:29869): GStreamer-CRITICAL **: gst_value_set_int_range_step: assertion 'start < end' failed
This happens because min cannot be equal to max.

https://bugzilla.gnome.org/show_bug.cgi?id=738838
rtpmux: Don't set PROXY_CAPS flag on the src pad

rtpmux behaves like a funnel in that it forwards whatever upstream is
sending buffers. So setting proxy caps doesn't make sense as the
upstream don't have to have compatible caps, thus resulting in an empty
caps set as a result of a caps query. Instead set fixed caps just
as funnel does.

https://bugzilla.gnome.org/show_bug.cgi?id=738722
rtspsrc: set full stream caps on internal src TCP pads

Set the complete stream caps on the TCP internal src pads. Otherwise,
ptdemux will not properly detect the caps change.

https://bugzilla.gnome.org/show_bug.cgi?id=737868
rtpjitterbuffer: make debug line less confusing
speex: Fix segfault when resetting the codecs multiple times

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