Eike Hein 303f927d70 rtspconnection: Start CSeq at 1 ... RFC 7826 recommends (but does not require) starting at 0, but at least one known server implementation fails to copy request sequence numbers <1 into responses due to an incorrect null check. The server known to exhibit this behavior is the Parrot Streaming Server, serving video from their UAV devices. A fix has been submitted upstream as well: https://github.com/Parrot-Developers/librtsp/pull/2 The Parrot developers are known to have tested with LibVLC. In WireShark debugging, LibVLC appears to start with a CSeq of 2, which is likely why this bug went unnoticed. This reverts 487595a7d6, which set this to 0 citing the RFC. The switch to 0 was thus a recent one; it's therefore possible server implementors relied on the previous GStreamer client behavior in their tests as well. Fixes #624.		2019-06-12 16:21:41 +09:00
..
gst	rtspconnection: Start CSeq at 1	2019-06-12 16:21:41 +09:00
Makefile.am	configure.ac: added GST_LIB_LDFLAGS and GST_ALL_LDFLAGS	2005-11-27 16:18:50 +00:00
meson.build	Add support for Meson as alternative/parallel build system	2016-08-20 11:09:51 +01:00