<p>Note the 192.168.11.4 IP address is my desktops IP address. As far
as I can tell the IP must be hardcoded for this to work. In other
words, if someone elses machine is going to do the steaming, you have
-to update screenstream.m4u on the Kodi machine and adjust the vlc
+to update screenstream.m3u on the Kodi machine and adjust the vlc
recipe. To get started, locate the file in Kodi and select the m3u
file while the VLC stream is running. The desktop then show up in my
big screen. :)</p>
x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
- udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \
+ udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
pulsesrc device=$(pactl list | grep -A2 'Source #' | \
grep 'Name: .*\.monitor$' | cut -d" " -f2|head -1) ! \
audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
<p>Note the trick to pick a valid pulseaudio source. It might not
pick the one you need. This approach will of course lead to trouble
if more than one source uses the same multicast port and address.
-Note the ttl-mc=0 setting, which limit the multicast packages to the
+Note the ttl-mc=1 setting, which limit the multicast packages to the
local network. If the value is increased, your screen will be
broadcasted further, one network "hop" for each increase (read up on
multicast to learn more. :)!</p>
<p>Having cracked how to get Kodi to receive multicast streams, I
could use this VLC command to stream to the same multicast address.
-The image quality is way better than the rtsp approach.</p>
+The image quality is way better than the rtsp approach, but gstreamer
+seem to be doing a better job.</p>
<blockquote><pre>
cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'