# Stream Desktop/Video/Webcam to Kodi/Beamer/other PCs Gregor and I had a closer look at the following projects: # Laplace Simple WebRTC implementation in GO: https://github.com/adamyordan/laplace.git Simple to compile and just works. WebRTC actually uses SRTP (Secure Real-time Transport Protocol). IPv6+IPv4, and no TLS: ./laplace -addr "[::]:8080" -tls=false # gstreamer * Supports RTP * Supports webcam capture via v4l (video for linux) * Supports screen capture via xmanager/ximagesrc * Interesting URLs: * WebRTC in one direction only: https://stackoverflow.com/questions/57430215/how-to-use-webrtcbin-create-offer-only-receive-video * gstreamer to VLC via RTP: https://stackoverflow.com/questions/13154983/gstreamer-rtp-stream-to-vlc * https://github.com/intel/gstreamer-media-SDK/issues/138 * https://developer.ridgerun.com/wiki/index.php?title=GstWebRTC_Pipelines * https://developer.ridgerun.com/wiki/index.php?title=GstWebRTC_-_H264-Opus_Examples#Receive_Pipeline ## WebRTC gstreamer has a WebRTC implementation. The examples at https://github.com/centricular/gstwebrtc-demos.git work once export OPENSSL_CONF='' has been set (see https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/811) ## gstreamer examples gst-launch-1.0 -v playbin uri=file:///home/philipp/tmp/GerisGame.mp4 # VLC Note that you have to close VLC and open it again for new streaming as VLC leaves the connections open (I spent hours figuring out why http based streaming doesn't work - `netstat -4 --ip` is nice for debugging in that respect). ## RTP ### Source The address has to be the address where the video should be streamed **to**. In the following examples, a multicast address is used. It is either the IP address of the device receiving the video (unicast address) or a multicast address like 239.255.12.42 (multicast addresses are between 224.0.0.0 and 239.255.255.255, some of them being reserved, 239.0.0.0 to 239.255.255.255 are Organization-Local Scope so they are good candidates, see https://www.iana.org/assignments/multicast-addresses/multicast-addresses.xhtml). cvlc -vv --sout '#transcode{vcodec=h264,acodec=mpga,channels=2,vb=800,ab=128}:rtp{mux=ts,dst=239.255.12.42,sdp=sap,name="Geris Game"}' GerisGame.mp4 cvlc -vv --sout '#transcode{vcodec=h264,acodec=mpga,ab=128,channels=2,samplerate=44100,scodec=none}:rtp{dst=239.255.12.42,port=5004,mux=ts,sap,name=Geris Game}' :no-sout-all :sout-keep GerisGame.mp4 cvlc -vv --sout '#transcode{vcodec=h264,acodec=mpga,channels=2}:rtp{mux=ts,dst=239.255.12.42,sdp=sap,name="Videokamera"}' v4l2:///dev/video0 # long latency cvlc -vv --sout '#transcode{vcodec=h264,acodec=mpga,channels=2}:rtp{mux=ts,dst=239.255.12.42,sdp=sap,name="Desktop"}' screen:// # not convincing ### Player cvlc rtp://239.255.12.42 ## RTSP For VLC, RTSP means RTSP combined with RTP. ### Source We assume that the video source computer has the external IP 192.168.1.54. Instead of rtsp://192.168.1.54:8554/ we could also use rtsp://192.168.1.54:8554/mystream.sdp cvlc -vv --sout '#transcode{vcodec=h264,acodec=mpga,ab=128,channels=2,samplerate=44100,scodec=none}:rtp{sdp=rtsp://:8554/}' :no-sout-all :sout-keep GerisGame.mp4 cvlc -vv --sout '#rtp{dst=239.255.12.42,port=1234,sdp=rtsp://192.168.1.54:8554/}' :no-sout-all :sout-keep GerisGame.mp4 ### Player The address needs to be the address of the source. Note the backslash at the end. vlc rtsp://192.168.1.54:8554/ ## VLC Remarks * Latency: The following options are said to reduce latency: --network-caching=150 --clock-jitter=0 --clock-synchro=0 * Duplicating a stream is nice for debugging: cvlc -vv --sout '#duplicate{dst=display,dst="transcode{vcodec=h264,acodec=mpga,channels=2,vb=800,ab=128}:rtp{mux=ts,dst=239.255.12.42,sdp=sap,name=Geris Game}"}' GerisGame.mp4 cvlc rtp://239.255.12.42 ## HTTP The address at the source side has to be the external one of the local computer. ### Source (server) cvlc -vv --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:standard{access=http,mux=ogg,dst=0.0.0.0:8080}' GerisGame.mp4 ### Player (client) vlc http://192.168.1.54:8080 # Kodi The player built into code knows at least the following streaming protocols: http, rtsp. https://kodi.wiki/index.php?title=Internet_video_and_audio_streams