[Bug 790412] unit test failure: rtspclientsink test_record fails with GST_MESSAGE_TYPE (msg) != GST_MESSAGE_EOS

[GStreamer (GNOME Bugzilla)]

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

--- Comment #11 from Patricia Muscalu <patricia at axis.com> ---

(In reply to Sebastian Dröge (slomo) from comment #10)
> What would it do different?
There is a difference in rtsp-stream implementation when acting in client and
server mode, as far as I understand it.
In the client mode there is no need for dynamic pipeline support at all. The
clientsink knows what transport is supposed to be used, so after _join_bin()
has been called (on the client side) the pipeline controlled by the client, is
well known and should be fully configured (as all relevant information is in
place, no?).

If it's not desired to provide a separate implementation of rtsp-stream, it
should be enough to add transport related parts of the pipeline after
_join_bin().

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