Changes in:  gstreamer

 gstreamer:  3dc8ee97e50039c73fc322f687741a5b7193b750
 gst-plugins-base:  2f6f0ee2149e83841e0e7cb8c69197e385db3d51
 gst-plugins-good:  5d2ff288b3e373d031a75d5af53af0bfb15fd54c
 gst-plugins-ugly:  55037ab411218786a7625e2d8827ae253f4b4909
 gst-plugins-bad:  fb9fbc8fbac97e72339b9bd30ad35232ce3566c7
 gst-ffmpeg:  61153a5ac231141e4395b9f0bb28a26fa808a098
 gnonlin:  79624b830af08437d9a17464ba688c6a228f790b
 gst-editing-services:  28770ce53b97678dcd7e5d981e748f643bc9c8cd
 gst-python:  20860bc63376944cc7749255123e201feec5f39c

====== gstreamer =============

 commit 3dc8ee97e50039c73fc322f687741a5b7193b750
Author: Thiago Santos <thiago.sousa.santos@collabora.com>
Date:   Wed Sep 4 15:28:10 2013 -0300

    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