basetransform: Don't push out identical caps

This avoids triggering plenty of extra code/methods/overhead downstream when
we can just quickly check whenever we want to set caps whether they are
identical or not

https://bugzilla.gnome.org/show_bug.cgi?id=706600
tools: gst-launch: don't print properties being reset when shutting down

It's just noise.
tests: filesink: small refactoring
filesink: flush (discard data) on FLUSH_STOP

Reset the write position to 0 and truncate the file on FLUSH_STOP.
filesink: please gcc (avoid a warn_unused_result warning)
po: update translations
Update .po files
Release 1.1.4
Back to development
basesink: demote log message, don't spam INFO level when handling buffer lists
capsfilter: Delete link directly in pending_events.

When removing a segment event.

https://bugzilla.gnome.org/show_bug.cgi?id=707088
outputselector: Don't adjust segment->start to the current time when switching pads

This does not make any sense at all and breaks timestamp->running_time
calculations in unpredictable ways.

https://bugzilla.gnome.org/show_bug.cgi?id=707130
multiqueue: Don't reduce single queue visible size below its current level

If the multiqueue has automatically grown chances are good that
we will cause the pipeline to starve if the maximum level is reduced
below that automatically grown size.

https://bugzilla.gnome.org/show_bug.cgi?id=707156
tools: move gst-plot-timeline.py into scripts directory

So it's not in PATH in an uninstalled setup (thwarting
gst-play autocompletion).
typefind: Add missing break after handling the GAP event

Thanks to Edward Hervey for noticing.
Remove PyXML from spec file, it is not longer needed
collectpads: Don't unref NULL GstCollectData

If a pad is removed while a collectpads element (say adder) is in a chain
function waiting to be collected, there is a possibility that an unref happens
on a NULL pointer.

https://bugzilla.gnome.org/show_bug.cgi?id=707536
basesrc: preserve seqnum on segments after seeks

The seqnum of the segment after a seek should be the same of
the seek event. Downstream elements might rely on seqnums to
identify events related to a seek.

This is particularly important when a demuxer maps a TIME seek
into a BYTES seek for upstream and it needs to identify the
corresponding segment event and map it back into TIME to push
downstream, possibly using the values from the original seek
event.

https://bugzilla.gnome.org/show_bug.cgi?id=707530
Update the buffering state before stalling for more data

In some cases the wait for more data was happening without updating
the buffering state, meaning the API user would not be able to notice
it should pause the pipeline and update UI to indicate that is the
case, the video would likely stutter instead.

https://bugzilla.gnome.org/show_bug.cgi?id=707648
tests/capsfilter: Test caps-related queries and property