On Tue, 10 Jul 2012, Jordi Ortiz wrote:
---
doc/protocols.texi | 8 +
libavformat/rtsp.c | 30 ++-
libavformat/rtsp.h | 12 +
libavformat/rtspcodes.h | 14 +
libavformat/rtspdec.c | 662 ++++++++++++++++++++++++++++++++++++++++++++---
5 files changed, 688 insertions(+), 38 deletions(-)
diff --git a/doc/protocols.texi b/doc/protocols.texi
index e75f108..9d85baa 100644
--- a/doc/protocols.texi
+++ b/doc/protocols.texi
@@ -347,6 +347,8 @@ Flags for @code{rtsp_flags}:
@table @option
@item filter_src
Accept packets only from negotiated peer address and port.
+@item listen
+Wait for incoming connections.
"Act as a server, listening for an incoming connection."
@end table
When receiving data over UDP, the demuxer tries to reorder received packets
@@ -379,6 +381,12 @@ To send a stream in realtime to a RTSP server, for others
to watch:
avconv -re -i @var{input} -f rtsp -muxdelay 0.1 rtsp://server/live.sdp
@end example
+To receive a stream in realtime:
+
+@example
+avconv -re -rtsp_flags listen -f rtsp -i rtsp://ownaddress/live.sdp
@var{output}
+@end example
+
You shouldn't ever use -re with realtime input sources. If you add -re, it
will sleep instead of reading from the input demuxer when it thinks it has
got enough data, easily leading to dropped/missed data. Conversely, you
should only use -re on files and similar, where you can get data "too
fast" and you actually need to limit it to realtime.
Other than this, it seems you've fixed all the other critical issues I
pointed out yesterday (the ones I fixed locally in order to test it). If I
don't run into anything else warranting yet another round, I'll fix up the
final nitpicks and push so we can move on.
// Martin
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
