GNOME Bugzilla – Bug 625634
sdpdemux does not handle EOS events
Last modified: 2018-05-04 09:13:47 UTC
The sdpdemux plugin seems to ignore EOS events. To reproduce the problem run the following gst-launch command (note the "-e" command line option): gst-launch -e filesrc location=some_sdp_file.sdp ! sdpdemux ! decodebin ! xvimagesink Wait some time and then press ctrl-c. gst-launch then prints out "Waiting for EOS..." and waits forever. Same behavior with a self written C program. Setting the filesrc and/or sdpdemux elements from state PLAYING to state READY does not trigger an EOS event on the pipeline.
(In reply to comment #0) > The sdpdemux plugin seems to ignore EOS events. To reproduce the problem run > the following gst-launch command (note the "-e" command line option): > > gst-launch -e filesrc location=some_sdp_file.sdp ! sdpdemux ! decodebin ! > xvimagesink > > Wait some time and then press ctrl-c. gst-launch then prints out "Waiting for > EOS..." and waits forever. That's a problem indeed. Not sure how to fix it because sdpdemux already received an EOS event. > > Same behavior with a self written C program. Setting the filesrc and/or > sdpdemux elements from state PLAYING to state READY does not trigger an EOS > event on the pipeline. That would be normal, doing a state change to READY should not trigger EOS.
This bug has an assigned developer but has not received activity in almost a year. Is the assigned person still working on this ?
This is actually behaving as intended, similar to adaptivedemux. The first part of the pipeline is properly EOS, so injecting a new EOS event is not going to have any effect whatsoever. A different approach for draining/finalizing is needed in these kinds of pipelines, and applications can relatively easily do that for specific cases at least.