- May 17, 2018
-
-
Tim-Philipp Müller authored
-
- May 14, 2018
-
-
If the connection is closed very early, the flushing marker might not get set and rtspclientsink can get deadlocked waiting for preroll forever. https://bugzilla.gnome.org/show_bug.cgi?id=786961
-
- Apr 20, 2018
-
-
When streaming data over TCP then is not the keep-alive functionality working. The reason is that the function do_send_data have changed to boolean but the code is still checking the received result from send_func with GST_RTSP_OK. The result is that a successful send_func will always lead to that do_send_data is returning false and the keep-alive will not be updated. https://bugzilla.gnome.org/show_bug.cgi?id=795321
-
- Apr 17, 2018
-
-
Sebastian Dröge authored
This reverts commit 3d275b13. While RFC 3264 (SDP) says that sendonly/recvonly are from the point of view of the requester, the actual RTSP RFCs (RFC 2326 / 7826) disagree and say the opposite, just like the ONVIF standard. Let's follow those RFCs as we're doing RTSP here, and add a property at a later time if needed to switch to the SDP RFC behaviour. https://bugzilla.gnome.org/show_bug.cgi?id=793964
-
- Apr 16, 2018
-
-
Set transport string to NULL after freeing it, so that at worst we get a NULL pointer if constructing a new transport string fails (which shouldn't really fail here). Also check return value of that, just in case. CID 1433768.
-
- Mar 30, 2018
-
-
Mathieu Duponchelle authored
This was broken since the work for delayed transport creation was merged: the creation of the transports string depends on calling stream_get_server_port, which only starts returning something meaningful after a call to stream_allocate_udp_sockets has been made, this function expects a transport that we parse from the transport string ... Significant refactoring is in order, but does not look entirely trivial, for now we put a band aid on and create a second transport string after the stream has been completed, to pass it in the request headers instead of the previous, incomplete one. https://bugzilla.gnome.org/show_bug.cgi?id=794789
-
- Mar 25, 2018
-
-
Sebastian Dröge authored
rtsp-media-factory-uri.c: In function ‘rtsp_media_factory_uri_create_element’: rtsp-media-factory-uri.c:621:17: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types] data->factory = g_object_ref (factory); ^
-
- Mar 19, 2018
-
-
Tim-Philipp Müller authored
-
- Mar 13, 2018
-
-
Tim-Philipp Müller authored
We need different export decorators for the different libs. For now no actual change though, just rename before the release, and add prelude headers to define the new decorator to GST_EXPORT.
- Mar 07, 2018
-
-
- Mar 03, 2018
- Mar 02, 2018
-
-
Mathieu Duponchelle authored
-
-
- Mar 01, 2018
-
-
Mathieu Duponchelle authored
-
- Feb 28, 2018
-
-
Sebastian Dröge authored
This allows us to later map signals from rtpbin/rtpsource back to the corresponding stream transport, and allows to do keep-alive based on RTCP packets in case of TCP media transport. https://bugzilla.gnome.org/show_bug.cgi?id=789646
-
- Feb 27, 2018
-
-
Mathieu Duponchelle authored
As READY_TO_PAUSED can no longer return async, the RECORD command will be queued before the OPEN command fails (for example in case the server could not be connected), and record then waits for ever. https://bugzilla.gnome.org/show_bug.cgi?id=793896
-
- Feb 26, 2018
-
-
Mathieu Duponchelle authored
If a bin is passed as the custom payloader, the caps of its factory will be empty, the correct way to obtain the caps is to query its sinkpad.
-
Mathieu Duponchelle authored
-
Mathieu Duponchelle authored
-
Mathieu Duponchelle authored
-
Mathieu Duponchelle authored
This was a FIXME item, and can be quite useful, also allowing to specify payloader properties from the command line, which is always nice. https://bugzilla.gnome.org/show_bug.cgi?id=793776
-
- Feb 23, 2018
-
-
Mathieu Duponchelle authored
The test_record case was working because async=false had been added in https://bugzilla.gnome.org/show_bug.cgi?id=757488 but that was incorrect, as it should not be needed. Removing async=false made the test fail as expected, this is fixed by not trying to preroll when preparing the media for RECORD, as start_prepare is called upon receiving ANNOUNCE, and our peer will not start sending media until it has received a response to that request, and sent and received a response to RECORD as well, thus obviously preventing preroll. https://bugzilla.gnome.org/show_bug.cgi?id=793738
-
Mathieu Duponchelle authored
-
- Feb 19, 2018
-
-
Víctor Manuel Jáquez Leal authored
res is a boolean variable which is defined in the function scope and redefined, with no reason, in the loop scope. This patch removes the redefinition. https://bugzilla.gnome.org/show_bug.cgi?id=793592
-
- Feb 16, 2018
-
-
...and replace all checks for RECORD in GstRTSPMedia which are really for "sender-only". This way the code becomes more generic and introducing support for onvif-backchannel later on will require no changes in GstRTSPMedia.
-
...in order to let subclasses building the onvif part of the pipeline check whether backchannel shall be included or not.
-
Sebastian Dröge authored
They are wrong in the ONVIF streaming spec. The backchannel should be recvonly and the normal media should be sendonly: direction is always from the point of view of the SDP offerer (the server) according to RFC 3264.
-
Sebastian Dröge authored
This adds a new RTSP server, client, media-factory and media subclass for handling the specifics of the backchannel. Ideally this later can be extended with other ONVIF specific features.
-
Sebastian Dröge authored
We need to add an appsrc/appsink in that case because otherwise the media bin will be a sink and a source for rtpbin, causing a pipeline loop. https://bugzilla.gnome.org/show_bug.cgi?id=788950
-
- Feb 15, 2018
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Feb 14, 2018
-
-
Mathieu Duponchelle authored
create_watch can only return NULL from the API guards, no need for nullable.
-
- Feb 13, 2018
-
-
Mathieu Duponchelle authored
-
- Feb 12, 2018
-
-
Mathieu Duponchelle authored
-
Mathieu Duponchelle authored
The meson test suite runs tests in parallel, trying to bind a single port made the test fail.
-
- Feb 08, 2018
-
-
Tim-Philipp Müller authored
WARNING: Trying to compare values of different types (str, int). The result of this is undefined and will become a hard error in a future Meson release.
-
- Feb 06, 2018
-
-
Mathieu Duponchelle authored
The return value type is defined with G_DEFINE_POINTER_TYPE, and gi emits the following warning: Invalid non-constant return of bare structure or union; register as boxed type or (skip)
-
Mathieu Duponchelle authored
gi doesn't seem to be able to figure out the type of the signal parameters when defined with G_DEFINE_POINTER_TYPE
-