[gstreamer-bugs] [Bug 576729] New: EOS event is not fired when RTSP/RTP stream ends

[GStreamer (bugzilla.gnome.org) <bug...@bu...>]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=576729

  GStreamer | gst-plugins-good | Ver: 0.10.21
           Summary: EOS event is not fired when RTSP/RTP stream ends
           Product: GStreamer
           Version: 0.10.21
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gst...@li...
        ReportedBy: jav...@gm...
         QAContact: gst...@li...
     GNOME version: 2.23/2.24
   GNOME milestone: Unspecified


Please describe the problem:
When receiving an RTSP/RTP stream, at the end of the stream there's no message
reported by the pipeline bus, so it's impossible to manage properly some
application level tasks, such as playlist management.

During the RTSP message exchange, the server (tested with VLC 0.9.4 and
Live555MediaServer) replies to the client DESCRIBE RTSP message with a SDP
file, which includes the 'range' session attribute (e.g.
'range:npt=0-249.102'). 

However, when the client (gstreamer 0.10.21) sends a PLAY RTSP message, the
'Range' header has the value of 'npt=0-\r\n'.

The gstreamer RTP session manager should consider the 'range' attribute of the
SDP file sent by the server in order to know when the EOS of the configured
RTSP/RTP stream should be fired.

Steps to reproduce:
1. Use an RTSP server (I tested with both VLC 0.9.4 and Live555MediaServer) to
configure a VoD streaming environment.
2. Add a watch to the message bus of the gstreamer pipeline and try to get any
trace when the message type matches GST_MESSAGE_EOS.
3. Start receiving any content through an RTSP session and wait for the content
to finish.


Actual results:
No GST_MESSAGE_EOS (nor GST_STATE_CHANGED) is fired when the stream reaches its
end.

Expected results:
A GST_MESSAGE_EOS message fired just when the RTP stream finishes, so itcould
be handled in order to, for example, start the next local or RTSP content in a
playlist.

Does this happen every time?
Yes.

Other information:


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=576729.