[Bug 753661] New: dashdemux: Reverse playback doesn't work well

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 753661
           Summary: dashdemux: Reverse playback doesn't work well
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: slomo at coaxion.net
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

See the validate.dash.playback.reverse_playback.* tests

=========================================
Running scenario seek_backward on pipeline playbin0
=========================================
Executing (subaction) seek: name=Backward-seek playback-time=0:00:05.000000000
rate=1 start=0:00:00.000000000 flags=accurate+flush 
Executing (subaction) seek: name=Backward-seek playback-time=0:00:10.000000000
rate=1 start=0:00:05.000000000 flags=accurate+flush 
Executing (subaction) seek: name=Backward-seek playback-time=0:00:15.000000000
rate=1 start=0:00:10.000000000 flags=accurate+flush 
Executing (subaction) stop: playback-time=0:00:15.000000000 ed: 1,000000 />

seek_backward --> State change request NULL, quiting mainloop
   warning : buffer timestamp is out of the received buffer timestamps' range
             Detected on <avdec_aac0:src>
             Description : a buffer leaving an element should have its
timestamps in the range of the received buffers timestamps. i.e. If an element
received buffers with timestamps from 0s to 10s, it can't push a buffer with
with a 11s timestamp, because it doesn't have data for that

     issue : SEGMENT events that are part of the same pipeline 'operation'
should have the same seqnum
             Detected on <souphttpsrc0:src>
             Detected on <souphttpsrc1:src>
             Description : when events/messages are created from another
event/message, they should have their seqnums set to the original event/message
seqnum

   warning : a field in caps has an unexpected value
             Detected on <avdec_aac0:src>
             Description : fields set on a sink pad should be propagated
downstream via set caps

   warning : a serialized event received should be pushed in the same order as
it was received
             Detected on <aacparse0:src>
             Description : serialized events should be pushed in the same order
they are received.

   warning : received the same caps twice
             Detected on <avdec_aac0:sink>
             Detected on <avdec_h264-0:sink>

Issues found: 5

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.