Changes between Version 43 and Version 44 of StreamingGuide

Timestamp:

11/04/2012 03:46:30 AM (7 months ago)

Author:

rogerdpack

Comment:

tcp wurking example woot

StreamingGuide

@@ -185 +185 @@
   ffmpeg -i INPUT -f mpegts tcp://host:port
 
-which I would guess will try and (as a client) establish a connection do that host on that port (assuming it has a server waiting for the incoming connection).
-
-Another option is to use rtp (which by default uses udp) but specify tcp:
-
-  ffmpeg... -rtsp_transport tcp [http://ffmpeg.org/ffmpeg.html#rtsp see here]
-
-Then you may be able to receive it like this:
-
- ffplay rtsp://blabla/file?tcp
-
-or possibly like
-
-  ffmpeg... -rtsp_flags listen [http://ffmpeg.org/ffmpeg.html#rtsp see here]
-
-ffmpeg also has a "listen" option for rtmp to it may be able to receive "straight" rtmp streams from a single client.
+which I would guess will try and (as a client) establish a connection do that host on that port (assuming it has a server waiting for the incoming connection).  You could receive it like this:
+
+  ffmpeg -i tcp://local_hostname:port?listen
+
+Another option is to use rtp (which by default uses udp) but by specifying it use tcp:
+
+  ffmpeg -i input -f rtsp -rtsp_transport tcp rtsp://localhost:8888/live.sdp [http://ffmpeg.org/ffmpeg.html#rtsp lists the option]
+
+Then you may receive it like this (ffplay or ffmpeg):
+
+ ffplay -rtsp_flags listen rtsp://localhost:8888/live.sdp?tcp # ending ?tcp may not be needed -- you will need to start the server up first, before the sending client
+
+ffmpeg also has a "listen" option for rtmp so it may be able to receive a "straight" rtmp streams from a single client that way.
 
 With tcp based streams you can probably use any formatting/muxer, but with udp  you need to be careful and use a muxer that supports 'connecting anytime' like mpegts.